*** This bug is a duplicate of bug 75681 ***
https://bugs.launchpad.net/bugs/75681
I've had the same problem. After installation, while rebooting, ubuntu
complains about one of the devices /dev/md3, that was my home partition. It
happens with a fresh install and also with an an upgrade insta
*** 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
--
Software Raid Setup with feisty herd1 alternate on amd64
https://launchpad.net/bugs/7
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
I can confirm the same with Herd3.
>From my diagnosis, it appears that /dev/md? are missing or not generated
properly in the initramfs.
In the busybox shell, I proceeded to do:
mknod /dev/md0 b 9 0
mknod /dev/md1 b 9 1
etc..
mdadm --run /dev/md0 /dev/hda1 /dev/hdc1
mdadm --run /dev/md1 /dev/hda5
I can confirm that bug also on a new installation with alternate-cd
(herd2)
--
Software Raid Setup with feisty herd1 alternate on amd64
https://launchpad.net/bugs/7
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Same with herd2. Create the arrays, installed grub on the 2 disks and
tried to boot. Grub all goes okay, but then it doesn't detect the arrays
properly and ubunut fails to boot. You get dropped in the busybox shell
which is ran from the initrd image!
Now I have a boot partition without raid1 and t
