[Bug 1030292] Re: initramfs does not boot with mdadm (3.2.5-1ubuntu0.1)

[Steve Langasek]

On Sun, Jul 29, 2012 at 10:53:09AM -0000, Eike Thaden wrote:
> Of course I can provide that information. But first I have a dumb
> question: Currently I don't know how to run apport-collect with the new
> mdadm in place because as reported the boot process does not complete
> and I'm dropped to a busybox command line. With the previous version of
> mdadm I can boot the system as usual.

> Is it sufficient to run apport-collect with that previous version of
> mdadm?

Yes, booting with the previous mdadm should be fine for these purposes. 
Mostly what we're looking for from apport-collect is information about the
system configuration.

> If not, how can I continue booting the system? Is it safe to
> continue with degraded partitions?

The system is designed such that booting with degraded partitions should be
safe.  But we can't really make any promises in the case where it's entering
degraded mode due to some as-yet-unidentified bug, and we don't know
anything about your RAID topology.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/1030292

Title:
  initramfs does not boot with mdadm (3.2.5-1ubuntu0.1)

Status in “mdadm” package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the mdadm in precise-proposed, all newly created
  initrds do not boot. I'm using a pseudo raid with to harddisks on a
  Sony Vaio Z. Raid level is 0.  I have one  unencrypted boot partition
  and an encrypted root.

  During startup the system asks for the password to decrypt the root
  partition as usual but fails to mount the partition afterwards. I
  always get the message that there are one or more degraded partitions.
  However, with an older version of mdadm everything works perfectly.

  My current solution: Downgrade to latest stable mdadm (precise).

  Please let me know what additional information is required. I can also
  perform some tests as long as my (prodcutive) system is not in danger.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1030292/+subscriptions