Also confirmed. Happens on Feisty Herd 4-5 at least. My configuration:
2 sata drives sda1: /boot ext3, 1gb, bootable sda2: /srv/spare ext3, 20gb sda3: swap, 4gb sda4: RAID physical, 134gb sdb1: /srv/boot-backup ext3, 1gb sdb2: /srv/spare2 ext3, 20gb sdb3: swap, 4gb sdb4: RAID physical, 134gb md0: sda4+sdb4 RAID-0, root (/), ext3 Installation goes fine, no problems. On boot, the console shows: * Mounting root file system * Loading MD modules * md: raid0 personality registered/Success: loaded module raid0. * Begin: Assembling all MD arrays * mdadm: No devices listed in conf file were found. * Failure: failed to assemble all arrays * Waiting for root file system... [...] * Mounting /root/dev on /dev/.static/dev failed: No such file... * Target filesystem doesn't have /sbin/init And drops into an initramfs prompt. At that prompt, I can 'mdadm --assemble /dev/md0' without problems. Adding a 'break=mount' to the GRUB prompt, and then exiting when dropped into the prompt, allows the boot to proceed without any problem. Happens on both a white-box server and a virtual machine running in Parallels. For quite a while, I interpreted this behavior to mean that installing Ubuntu Feisty onto a RAID-0 root was not supported. I'm reinstalling from scratch because my Edgy upgrade broke the machine in a way I interpreted as initrd driver issues. In retrospect, it was probably this bug that hit me during upgrade. -- boot on md raid drives fails https://launchpad.net/bugs/79204 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
