[vox-tech] Re: mdadm failing to start RAID5 array

[Ryan]

It seems that it is still acting up.

After the array has been running a while, the checksums become bad. It keeps 
doing this.

[root at media scsi]# mdadm -E /dev/sda1
/dev/sda1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : d86d40e7:ae1734df:cf40df07:aef1e053
  Creation Time : Sun Apr 17 14:05:59 2005
     Raid Level : raid5
    Device Size : 195358336 (186.31 GiB 200.05 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0

    Update Time : Mon Apr 18 12:23:02 2005
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 3e4f7bda - expected 3e4f7b1e
         Events : 0.6050

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     0       8        1        0      active sync   /dev/sda1

   0     0       8        1        0      active sync   /dev/sda1
   1     1       8       17        1      active sync   /dev/sdb1
   2     2       8       33        2      active sync   /dev/sdc1
   3     3       8       49        3      active sync   /dev/sdd1


On Sunday 17 April 2005 02:27 pm, Ryan cjg5ehir02-at-sneakemail.com |lugod| 
wrote:
> On Sunday 17 April 2005 11:35 am, Ryan Castellucci
>
> cjg5ehir02-at-sneakemail.com |lugod| wrote:
> > On Sunday 17 April 2005 11:26 am, Ryan Castellucci wrote:
> > > I'm trying to use RAID5 with 4 200gb SATA drives on mandrake 10.1, and
> > > the array creates fine, but when I try to restart it, i get 'invalid
> > > argument' errors from mdadm, adding devices to /dev/md0
> > >
> > > [root at media root]# cat /etc/mdadm.conf
> > > DEVICE /dev/sd*1
> > > ARRAY /dev/md0 level=raid5 num-devices=4
> > > UUID=d9008623:c81eff0d:a8fc1629:4223b0b6
> > > devices=/dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
> > >
> > > [root at media root]# mdadm -v --assemble /dev/md0
> > > mdadm: looking for devices for /dev/md0
> > > mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 4.
> > > mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 2.
> > > mdadm: /dev/sdb1 is identified as a member of /dev/md0, slot 1.
> > > mdadm: /dev/sda1 is identified as a member of /dev/md0, slot 0.
> > > mdadm: failed to add /dev/sdb1 to /dev/md0: Invalid argument
> > > mdadm: failed to add /dev/sdc1 to /dev/md0: Invalid argument
> > > mdadm: no uptodate device for slot 3 of /dev/md0
> > > mdadm: failed to add /dev/sdd1 to /dev/md0: Invalid argument
> > > mdadm: failed to add /dev/sda1 to /dev/md0: Invalid argument
> > > mdadm: /dev/md0 assembled from 1 drive and -1 spares - not enough to
> > > start the array.
> >
> > output from dmesg....
> >
> > md: invalid superblock checksum on sdb1
> > md: sdb1 has invalid sb, not importing!
> > md: md_import_device returned -22
> > md: invalid superblock checksum on sdc1
> > md: sdc1 has invalid sb, not importing!
> > md: md_import_device returned -22
> > md: invalid superblock checksum on sdd1
> > md: sdd1 has invalid sb, not importing!
> > md: md_import_device returned -22
> > md: invalid superblock checksum on sda1
> > md: sda1 has invalid sb, not importing!
> > md: md_import_device returned -22
> > md: md0 stopped.
>
> Fixed :)
>
> I ran
>
> mdadm --assemble --update summaries /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1
> /dev/sdd1
>
> and now it works fine.

-- 
Ryan Castellucci - http://ryanc.org/
GPG Key: http://ryanc.org/files/publickey.asc