This may be caused by bringing up the system unconventionally (https://launchpad.net/distros/ubuntu/+source/initramfs- tools/+bug/52740)
[copying my comment from there] Re: [EDGY] Regression: can't boot from lvm root on raid anymore from Marty at 2006-09-24 14:37:00 EST 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 # /scripts/locat-top/lvm 1 logical volume(s) in volume group "foobar" now active # mount -t ext3 /dev/mapper/foobar-vg /root [ 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 -- Lilo error with boot on RAID1 and root on LVM on RAID1 https://launchpad.net/bugs/61338 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
