[Bug 872220] Re: Fails to boot when there's problems with softraid

[draco]

Not realy. I have multiple disk, and as they renumbered, mdadm tries to
assemble the arrays with the wrong disk so it can't.
The disk is not marked as faulty, but the arrays are not assembled.
I think mdadm could not do anything more as the hole system is read only at
this stage. So when i could repair the mdadm.conf, the arrays don't need to
be rebuild on the disk, as they were never started in read-write mode with
a missing device.

Do you mean that ubuntu is responsible for marking your disk as faulty? I
was thinking you are just reporting the side effect of this situation on
the boot process of ubuntu.

draco
Le 10 mai 2012 03:01, "Phillip Susi" <psusi at ubuntu.com> a écrit :

> Oh, so you also have a failed disk?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/872220
>
> Title:
>  Fails to boot when there's problems with softraid
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/872220/+subscriptions
>

-- 
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/872220

Title:
  Fails to boot when there's problems with softraid

Status in “mdadm” package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 11.10 has a new feature that it warns you while booting if
  there's a program with the softraid.

  It tells you that a hard disk in the softraid is missing, then asks,
  on the console:

  Continue to boot? y/N

  But it ignores all keypresses. After 5 seconds or so it then times
  out, falls to the default "N" option, and dumps you to a emergency
  bash prompt, with no indication on how to proceed.

  The feature is a good idea, but not in the current broken state.

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