I believe that any disk listed on the fstab failing to mount will lead to the dreaded initramfs console.
** Description changed: - Booting from a software raid device can randomly or systematically fail. + Booting a system with a software raid device can randomly or systematically + fail. The system boot will fail at the initramfs stage and the system complain - that it can't find the root device. + that it can't find the software raid device. The user ends up on the initramfs console. Rebooting might solve the issue (or not). --- Happens at once on boot. I happened to use the kernel 3.0.0-17, because the computer would not boot because of the bug that the line udevadm settle is missing in function degraded_arrays() in the file /usr/share/initramfs-tools/scripts/mdadm-functions which results in a halt on an initram fs console. --- ProblemType: Crash Date: Mon Feb 27 17:46:23 2012 ExecutablePath: /usr/bin/update-manager ExecutableTimestamp: 1326448883 InterpreterPath: /usr/bin/python2.7 ProcCmdline: /usr/bin/python ./xorg_fix_proprietary.py ProcCwd: /tmp/update-manager-Qp_QfE PythonArgs: ['/usr/bin/update-manager'] Traceback: Traceback (most recent call last): File "./xorg_fix_proprietary.py", line 160, in <module> if ver and apt_pkg.VersionCompare(ver, "2:1.5.0") > 0: ValueError: _system not initialized UserGroups: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/942106 Title: software raid doesn't assemble before mount on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/942106/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
