Re: mdadm raid1 stops to work after kernel panic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday May 5, undicizeri@xxxxxxxxx wrote:
> >  What happens if you:
> >   mdadm -S /dev/md2
> >   mdadm -A /dev/md2 /dev/sda1 /dev/sdc1
> 
> root@persifae:~#mdadm -S /dev/md2
> mdadm: stopped /dev/md2
> root@persifae:~#mdadm -A /dev/md2 /dev/sda1 /dev/sdc1
> mdadm: failed to add /dev/sdc1 to /dev/md2: Invalid argument
> mdadm: /dev/md2 assembled from 0 drives - not enough to start the array.

Ahhh... They have a different "preferred minor".  Presumably when you
tried to boot with the wrong grub parameters it tried to assemble the
array as /dev/md0 instead of /dev/md2.

You can fix with:

  mdadm -A /dev/md2 /dev/sdc1
  mdadm /dev/md2 -a /dev/sda1

NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux