Ubuntu fails to boot with a dead drive in a RAID

Bug #1035958 reported by RoyK
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Setting up a server now, with some six drives in a raid-6 plus a spare. It seems, if one drie fails, the server reboots, and it boots into busybox, rendering it rather useless. What would be the use for a RAID-6 system (with a spare) if I can't lose a disk?

Tags: bot-comment
Revision history for this message
RoyK (roysk) wrote :

Details follow…

This is a server with a single root device on an SSD for multiple use. Currently there's only a single root device on it on lvm, apart from a small boot partition (1,5GB). The system boots well without the raid disks, but when the system finds a somewhat broken raidset, it panics and sends me to busybox. A system doing this, is rather worthless, making the redundancy of the MD RAID awkward.

Please, anyone, tell me how to fix this

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1035958/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
RoyK (roysk) wrote :

I don't think this is mdadm, but it might be - it may just as well be the kernel.

Is there a way to disable busybox altogether? It doesn't make sense for a server to jump into a useless commandline interface for the admin to type "exit" to start debugging...

affects: ubuntu → mdadm (Ubuntu)
Revision history for this message
RoyK (roysk) wrote :

btw, even if booting with "bootdegraded=true", it still jumps to busybox during boot. This is rather useless…

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Please create the bug report with apport to provide the necessary information about mdadm and your setup.

    $ sudo apport-bug mdadm

Or alternatively please provide the following:

* Ubuntu release: precise, quantal, etc
* mdadm package version: dpkg -l mdadm
* syslog / boot messages
* mdadm.conf

Please note there is an improved version of mdadm currently being verified in precise-proposed which has 10 bug fixes:
https://bugs.launchpad.net/ubuntu/precise/+source/mdadm

Changed in mdadm (Ubuntu):
status: New → Incomplete
Revision history for this message
RoyK (roysk) wrote :

Installing mdadm from -proposed seems to have fixed this - thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mdadm (Ubuntu) because there has been no activity for 60 days.]

Changed in mdadm (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.