mdadm: support external metadata arrays correctly (from debian)

Bug #1054773 reported by JK
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The mdadm package is currently seriously broken for Intel IMSM/"fakeraid" setups since mdmon is not part of the initrd (tested on quantal alpha3) and therefore only sets up a read-only array which breaks the boot process. If booted from a live cd and entered via a jail root, mdadm the devices can be properly mounted. Manually moving mdmon into the initrd allows for booting, but halting is more complex:

A patch has been proposed here [1] and I would suggest to also fix this problem ASAP, as this is a 100% show stopper.
Please refer to the discussion in [1] for further details.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684708

Revision history for this message
JK (j-c-k) wrote :

I should add that this is a problem only if the system / is part of the array itself and therefore must be setup in initrd.

Revision history for this message
JK (j-c-k) wrote :

Also related to this is [1].

[1] http://comments.gmane.org/gmane.linux.raid/36852

Revision history for this message
JK (j-c-k) wrote :
Revision history for this message
JK (j-c-k) wrote :

And it is not a duplicate of #957494

Revision history for this message
JK (j-c-k) wrote :

But maybe related/duplicate of #1030292

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

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mdadm (Ubuntu):
status: New → Confirmed
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.