This bug happened to me also when upgrading 8.10 to 9.04 (with do- release-upgrade). Definately a buggy kernel.
Asus motherboard (not sure of exact - can get if needed) with RAID hardware disabled. 2 SATA hard disks as /dev/sdb and /dev/sdc Fails to boot due to a failure to start the RAID. Issues: 1) /dev/md0 vanished - it seems the new kernel wants to use /dev/md/0 2) Can't reconstruct the array because of a "Device or resource busy" error adding the second disk. There were no issues with 8.10. This prevents one from simply reconstructing the array with --assemble --scan and editing fstab. Temporary workaround: When boot fails and drops you into a shell, do this (device names will differ for you): losetup /dev/loop1 /dev/sdb losetup /dev/loop2 /dev/sdc mdadm --assemble /dev/md/0 /dev/sdb /dev/sdc If mdadm only starts one drive you may need to add the second: mdadm --manage /dev/md/0 --add <missing drive name> Then type 'exit' and watch your system boot. You may need to edit fstab to reference /dev/md/0 instead of /dev/md0 This allows one to use the box as intended but those commands have to be entered EVERY BOOT! -- no block devices found after an upgrade from 8.10 to 9.04 on a soft RAID1 system https://bugs.launchpad.net/bugs/358054 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
