Problem booting 3.8 with root on raid on lvm
I decided to upgrade a machine to a 3.8 kernel. At the time the machine
was running a mostly squeeze system. The machine failed to mount the
root filesystem.
At first I thought this was related to the use of uuid for the root
filesystem, so I changed that to directly specifying /dev/md0 and it
made no difference. I also tried a rootdelay but that also made no
difference. Everything seems to happen long before the system drops me
at a shell.
I then tried upgrading the system to wheezy, this installed a wheezy 3.2
kernel which booted fine, however the experimental 3.8 kernel still
fails to boot.
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premoun[ 3.531519] device-mapper:
uevent: version 1.0.3
t ... done.
Beg[ 3.536742] device-mapper: ioctl: 4.23.1-ioctl (2012-12-18)
initialised: dm-devel@redhat.com
in: Mounting root file system ... Begin: Running /scripts/local-top ...
Begin: Assembling all MD arrays ... mdadm: No devices listed in conf
file were found.
Failure: failed to assemble all arrays.
done.
done.
Begin: Waiting for root file system ... [ 3.833233] ata7: SATA link
down (SStatus 0 SControl 300)
[ 3.838715] ata8: SATA link down (SStatus 0 SControl 300)
[ 3.844202] ata5: SATA link down (SStatus 0 SControl 300)
[ 3.849668] ata6: SATA link down (SStatus 0 SControl 300)
[ 4.017172] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 4.024566] ata3.00: ATA-8: ST31000524AS, JC4B, max UDMA/133
[ 4.030258] ata3.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 4.037083] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 4.044454] ata3.00: configured for UDMA/133
[ 4.048805] ata4.00: ATA-8: ST31000524AS, JC4B, max UDMA/133
[ 4.048936] scsi 2:0:0:0: Direct-Access ATA ST31000524AS
JC4B PQ: 0 ANSI: 5
[ 4.062661] ata4.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 4.070007] sd 2:0:0:0: [sda] 1953525168 512-byte logical blocks:
(1.00 TB/931 GiB)
[ 4.077757] sd 2:0:0:0: [sda] Write Protect is off
[ 4.082628] ata4.00: configured for UDMA/133
[ 4.082629] sd 2:0:0:0: [sda] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 4.092613] sda: sda1 sda2
[ 4.092825] sd 2:0:0:0: [sda] Attached SCSI disk
[ 4.103593] scsi 3:0:0:0: Direct-Access ATA ST31000524AS
JC4B PQ: 0 ANSI: 5
[ 4.111876] sd 3:0:0:0: [sdb] 1953525168 512-byte logical blocks:
(1.00 TB/931 GiB)
[ 4.119595] sd 3:0:0:0: [sdb] Write Protect is off
[ 4.124448] sd 3:0:0:0: [sdb] Write cache: enabled, read cache:
enabled, doesn't support DPO or FUA
[ 4.133627] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 4.139031] sd 3:0:0:0: Attached scsi generic sg1 type 0
[ 4.144436] sdb: sdb1 sdb2
[ 4.147526] sd 3:0:0:0: [sdb] Attached SCSI disk
done.
Gave up waiting for root device. Common problem[ 33.682545] uhci_hcd:
USB Universal Host Controller Interface driver
s:
- Boot args (cat /proc/cmdline)
- Check[ 33.691883] usbcore: registered new interface driver usbhid
rootdelay= (did[ 33.698855] usbhid: USB HID core driver
the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/md1 does not exist. Dropping to a shell!
BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)
It appears to me that it is trying and failing to detect the raid array
before the hard drives have been found then not re-trying to detect the
raid array afterwards.
Reply to: