3.0.0-16-generic fails to boot with degraded raid array
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Hi,
I encountered a strange phenomenon with the 3.0.0-16-generic kernel - when booting a system that has a degraded RAID array, it drops the boot process back to a busybox prompt. just typing 'exit' at the prompt will continue the boot process properly. and, the raid array will be named something strange, like /dev/md127, instead of /dev/md0
booting the same system with a previous kernel, say 3.0.0-15-generic, it will display a warning prompt at boot about the failed array, asking if the array should be initialized. then it continues to boot.
my expectation would be that 3.0.0-16-generic acts the same way.
Akos
additional info:
$ lsb_release -rd
Description: Ubuntu 11.10
Release: 11.10
$ apt-cache policy linux-image-
linux-image-
Telepítve: 3.0.0-16.28
Jelölt: 3.0.0-16.28
Verziótáblázat:
*** 3.0.0-16.28 0
500 http://
500 http://
100 /var/lib/
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 938598
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.