Public bug reported:
Binary package hint: lvm2
recent updates in feisty fixed a race condition at boot time between
mdadm and sata hard drives. This fix seems to have been working for me.
more recently, the kernel was updated to 2.6.20-14. This updates and the one
coming along broke my boot again.
Unfortunatly I do not have much time yet to rebuild the initramfs for the
2.6.20-13 kernel, to test if the problem comes from the kernel or from the
userland tools, but I plan to do so later today.
Here is a first report with logs collected in the busybox shell:
* boot with break=premount
* run udevd --verbose and store the output
* run udevtrigger
* at this point, NONE of my devices has been detected, they used to appear
immediatly with previous versions.
* near to one minute later, the console show a bunch of new lines and my hard
drives have been properly detected, and my /dev/md0 mdadm array is also here.
The only missing stuff if the lvm volumes.
* running lvm vgscan/vgchange -a y by hand creates the corresponding devices
without a problem
udev 108-0ubuntu3
lvm-common 1.5.20ubuntu12
lvm2 2.02.06-2ubuntu9
busybox-initramfs 1.1.3-3ubuntu3
initramfs-tools 0.85eubuntu8
linux-image-2.6.20-14-generic 2.6.20-14.22
I will post my initramfs in a web page and comment back later
tonight....
PS: PLEASE do something quickly, as I will move on next monday until
after the feisty release and will not be able to help tracking it :/
** Affects: lvm2 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
[feisty] boot stuck in the initramfs
https://bugs.launchpad.net/bugs/103608
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
