On Sat, 31 Mar 2012 15:38:23 -0400 Bryan Bush <bbushvt@xxxxxxxxx> wrote: > I've had another md issue. Not sure exactly what caused it but my > array is offline again. The reshape completed and I was about to > insert a new drive to replace the one that failed on the initial > reshape. > /proc/mdstat contains > md1 : inactive sdk1[13](S) sdh1[9](S) sdi1[10](S) sdc1[8](S) > sdj1[11](S) sdb1[4](S) sdd1[6](S) sde1[7](S) sdl1[0](S) sdn1[2](S) > sdo1[3](S) > 21488647746 blocks super 1.2 > > "mdadm -As --verbose /dev/md1 -u fa32e2c5:e7bda20b:32af7c90:c7ee61eb" returns > mdadm: looking for devices for /dev/md1 > <cut> > mdadm: /dev/sdo1 is identified as a member of /dev/md1, slot 3. > mdadm: /dev/sdn1 is identified as a member of /dev/md1, slot 2. > mdadm: /dev/sdj1 is identified as a member of /dev/md1, slot 10. > mdadm: /dev/sdl1 is identified as a member of /dev/md1, slot 0. > mdadm: /dev/sdk1 is identified as a member of /dev/md1, slot 8. > mdadm: /dev/sdi1 is identified as a member of /dev/md1, slot 11. > mdadm: /dev/sdh1 is identified as a member of /dev/md1, slot 12. > mdadm: /dev/sde1 is identified as a member of /dev/md1, slot 7. > mdadm: /dev/sdd1 is identified as a member of /dev/md1, slot 6. > mdadm: /dev/sdc1 is identified as a member of /dev/md1, slot 5. > mdadm: /dev/sdb1 is identified as a member of /dev/md1, slot 4. > mdadm: Cannot open /dev/sdl1: Device or resource busy Stop the array first. - it is half-started which confused mdadm. i.e mdadm -S /dev/md1 mdadm -As ....... NeilBrown
Attachment:
signature.asc
Description: PGP signature
