Since updating to kernel 2.6.39-r9 revision:1 (also present in revision:2) Sabayon is failing to boot because it's not correctly auto-assembling the RAID device (mdadm). Last working config is kernel 2.6.39-r9 revision:0
I have run into the same problem on two different machines running /boot and / in software RAID-1.
Upon boot, it fails with:
- Code: Select all
>> Mounting root...
>> Using mount -t auto -o ro
mount: mounting /dev/md1 on /newroot failed: No such file or directory
!! Could not mount specified ROOT, try again
!! Could not find the root block device in .
Please specify another value or: press Enter for the same, type "shell" for
a shell, or "q" to skip...
root block device() ::
When I drop to the busybox shell, I am able to manually assemble the devices:
- Code: Select all
# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty]
unused devices: <none>
# mdadm --examine --scan
# mdadm --examine --scan > /etc/mdadm.conf
# mdadm --assemble --scan
# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty]
md4 : active raid0 sda7[0] sdb7[1]
173034496 blocks 512k chunks
md3 : active raid1 sda6[0] sdb6[1]
536870848 blocks [2/2] [UU]
md2 : active raid1 sda5[0] sdb5[1]
16777152 blocks [2/2] [UU]
md1 : active raid1 sda3[0] sdb3[1]
67108800 blocks [2/2] [UU]
md0 : active raid1 sda1[0] sdb1[1]
1048512 blocks [2/2] [UU]
unused devices: <none>
# exit
root block device() :: /dev/md1
... now normal bootup starts and completes successfully ...
Curiously, if I don't do mdadm --examine --scan > /etc/mdadm.conf first and just try mdadm --assemble --scan I get a whole bunch of strangely named devices that shouldn't exist, and with the incorrect member devices:
- Code: Select all
mdadm: WARNING /dev/sdb7 and /dev/sdb appear to have very similar superblocks.
If they are really different, please --zero the superblock on one
If they are the same or overlap, please remove one from the
DEVICE list in mdadm.conf.
mdadm: /dev/md/3_0 has been started with 1 drive (out of 2).
mdadm: /dev/md/2_0 has been started with 1 drive (out of 2).
mdadm: /dev/md/1_0 has been started with 1 drive (out of 2).
mdadm: /dev/md/0_0 has been started with 1 drive (out of 2).
mdadm: /dev/md/4_0 exists - ignoring
mdadm: /dev/md123 has been started with 2 drives
Has anyone else run into this issue? Any ideas?
