*** This bug is a duplicate of bug 942106 ***
https://bugs.launchpad.net/bugs/942106
This also doesn't seem like a duplicate to me.
I built a brand new server with a Raid5. The array was in perfect
shape, but the system would not boot - dropped to the initramfs shell.
http://ubuntuforums.org
*** This bug is a duplicate of bug 942106 ***
https://bugs.launchpad.net/bugs/942106
@paul fox (pgf-launchpad)
I think for your unusual way you should write a udev rule to override
mdadm.udev rule to do the right thing for your special case, until
improvements are made to unconditionally star
*** This bug is a duplicate of bug 942106 ***
https://bugs.launchpad.net/bugs/942106
i can't tell from the initial description whether or not there was a
truly degraded array on his system. perhaps not, in which case the
fixes described in #942106 would help.
but since the topic of this bug
*** This bug is a duplicate of bug 942106 ***
https://bugs.launchpad.net/bugs/942106
** This bug is no longer a duplicate of bug 872220
Fails to boot when there's problems with softraid
** This bug has been marked a duplicate of bug 942106
software raid doesn't assemble before mount on b
*** This bug is a duplicate of bug 872220 ***
https://bugs.launchpad.net/bugs/872220
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/872220/comments/4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
*** This bug is a duplicate of bug 872220 ***
https://bugs.launchpad.net/bugs/872220
Why do you think it is not a duplicate?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917520
Title:
Regressi
*** This bug is a duplicate of bug 872220 ***
https://bugs.launchpad.net/bugs/872220
Please unmark this bug as a duplicate. It is not a duplicate of
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/872220.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
*** This bug is a duplicate of bug 872220 ***
https://bugs.launchpad.net/bugs/872220
just to be clear the switch to udev (instead of debian init script)
caused the problem. udev does not wait for the raid array to settle and
mistakenly marks it as degraded.
--
You received this bug notificat
*** This bug is a duplicate of bug 872220 ***
https://bugs.launchpad.net/bugs/872220
This bug is not a duplicate of #872220.
I run 6 large Raid5/6 arrays. After upgrade to precise from hardy all
of them were mistakenly detected as degraded by the init script. I can
absolutely confirm that no
*** This bug is a duplicate of bug 872220 ***
https://bugs.launchpad.net/bugs/872220
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mdadm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
B
*** This bug is a duplicate of bug 872220 ***
https://bugs.launchpad.net/bugs/872220
Sergey, thanks for the bug report. I understand that this seems too
harsh, but we are being perhaps overly careful not to boot up a system
with a broken array unless the user explicitly allows it.
Answering t
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917520
Title:
Regression: mdadm drops to initramfs shell on unregistered array
To manage notifications about this bug go to:
https://bugs.launchpad.net/
12 matches
Mail list logo
