[EDGY] Regression: can't boot from lvm root on raid anymore
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
Fix Released
|
High
|
Fabio Massimo Di Nitto |
Bug Description
I have a sparc system with 2 scsi disks sda/sdb and a bunch of partitions to have /boot on md0 and lvm on top of md1. Lvm has a few lv including root.
From the boot log i can see that local-top scripts are executed "too fast" (before the sda/sdb appear) and the md script can't start the raids properly.
I get of course dropped to the busybox shell where i can happily do:
# /scripts/
mdadm: /dev/md0 has been started with 2 drives.
mdadm: /dev/md1 has been started with 2 drives.
# /scripts/
3 logical volume(s) in volume group "sparc-vg" now active
# exit
[rest of the boot]
as usual please let me know what info are required and i am as usual ready to test patches.
Fabio
I have the same issue but my solution isn't as simple.
Using hints from the 'init' script I can bring my system up with:
# modprobe dm_mod locat-top/ lvm foobar- vg /root
# /scripts/
1 logical volume(s) in volume group "foobar" now active
# mount -t ext3 /dev/mapper/
[ 134.664391] kjournald starting. Commit intervals 5 seconds
[ 134.710296] EXT3 FS on dm-0, internal journal
[ 134.710358] EXT3-fs: mounted filesystem with ordered data mode
# mount -n -o move /sys /root/sys
# mount -n -o move /proc /root/proc
# mount -n -o move /dev /root/dev
# chroot /root /bin/bash
bash: no job control in this shell
bash# telinit 2
bash# exit
# exit