I still have this or a closely related issue with the latest initramfs
and 2.6.20-5.
If I set break=mount, the initramfs prompt appears well before the HDD
are detected.
If I wait until disks are detected and run scripts/local-top/mdadm, the
raids are created, but the system hangs waiting for
*** This bug is a duplicate of bug 75681 ***
ok this is not related to that bug at all the fixes there dont seem to
work. After the message it gives me above if i wait 5-15 minutes it will
drop me to busybox with an initramfs prompt. when i sttate 1 out of 10
times its more random. It seems to
*** This bug is a duplicate of bug 75681 ***
removing ## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
from /boot/grub/menu.lst works for kernel 2.6.20-2-generic here but doesnt
affect 2.6.20-3-generic at all it still doesnt boot. I am assuming it worked
with
*** This bug is a duplicate of bug 75681 ***
** This bug has been marked a duplicate of bug 75681
initramfs script: race condition between sata and md
--
2.6.20-* fails to boot in Feisty
https://launchpad.net/bugs/77737
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 75681 ***
Why did you mark this as a duplicate? this is not an mdadm issue its a
initramfs-tools issue and if it only fixes the 2.6.20-2 kernel than i
can positivly say its a dup of any bug because it should fix booting to
any kernel not just one. and it would
I cant seem to reproduce this issue after updating to initramfs-tools
version 0.85eubuntu1. Marking as fixed released
** This bug is no longer a duplicate of bug 75681
initramfs script: race condition between sata and md
** Changed in: initramfs-tools (Ubuntu)
Status: Unconfirmed = Fix