This bug report is being closed due to your last comment regarding this
being fixed with an update. Thanks again for taking the time to report
this bug and helping to make Ubuntu better. Feel free to submit any
future bugs you may find.
marcw - please open a separate bug report for your issue if
Since this looked a lot like my bug (#96511) I tried your workaround.
It didn't work. After adding init=/bin/sh I'm still returned to an
initramfs prompt. Oh well. Evidently 2 different bugs.
--
Feisty: Install to RAID fails to boot after install
https://bugs.launchpad.net/bugs/106238
You rece
Hmmm..
After manually booting the system with init=/bin/sh etc.. (as per above
comment), I then upgraded everything new from the past two days.
It now boots on it's own, so the but in initramfs-tools (or whereever)
seems to have been fixed recently.
Close this, I'll reopen if I see it again.
Ch
Tried again, this time removing the "splash quiet" boot parameters from
the grub command line, and added "init=/bin/sh" in place of them.
System booted to a bash prompt on the RAID1 rootfs.
I then typed "exec /sbin/init", and system appears to now be up and
running normally, until the next reboot
