Hi, In my experience, one device used in an md array has been renumbered after upgrading from oneiric to precise. At the first reboot, I've got the message 'Continue boot y/N' but can't enter anything. After few seconds, I've got a busybox/initramfs prompt on TTY1, but without any further informations for misassembled array. CTRL+D at prompt give me access to a root terminal so I can rename mdadm.conf and comment md array in fstab. I do that because it was the last messages in dmesg but there was no warning about devices not found. So, system boots fine, and then I could manualy : - change mdadm.conf to reflect the change of named device/partition ( sdc --> sda). - update initramfs and active mount in fstab.
I never though that making a 'simple' dist-updgrade could leave the system un-bootable without such admin (geek) skills !! Maybe a kind of warning can be added on release notes for people using softraid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/872220 Title: Fails to boot when there's problems with softraid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/872220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
