what I don't get is why a broken array (with no mount point specified)
would result in an unbootable system.
This is again the glorious mdadm thing of setting up arrays according to
unreliable superblock information (device minor numbers, labels,
hostnames) combined with the idea of fixing the
The solution is a reliable UUID-based raid assembly mechanism.
One that does not depend on ARRAY definitions in mdadm.conf. At the same
time making sure never to create devices named equal to the legacy
'standard' non-uniqe and non-persistent naming scheme /dev/md0 etc.
causing much havoc.
OK, I have an answer to why this particular system ran into problems but
a different one didn't. I noticed it in the stuff that apport dumped to
this ticket.
Unbeknownst to me, these two disks were previously part of a 4-disk
RAID5 array, built from /dev/sda - /dev/sdd. /dev/sda and /dev/sdb
That's brilliant! Thank you. Since this bug has enough information
provided for a developer to begin work, I'm going to mark it as Triaged
and let them handle it from here, and good luck :)
** Changed in: mdadm (Ubuntu)
Importance: Undecided = High
** Changed in: mdadm (Ubuntu)
Status:
similar bug https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/407901
duplicate https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/314395
--
Installing mdadm package breaks bootup.
https://bugs.launchpad.net/bugs/158918
You received this bug notification because you are a member of Ubuntu
If there are duplicates of this, please mark them as such, as I don't
know much about mdadm or RAID, although debugging information is here.
Thank you.
--
Installing mdadm package breaks bootup.
https://bugs.launchpad.net/bugs/158918
You received this bug notification because you are a member of
Teej - you're welcome. Just holler if there's anything else I can gather
to help out.
As a final anecdote, I was able to work around the problem for this
particular system by hacking on mdadm's hook in initramfs. Because I
don't need to have the system boot from a RAID array, I was able to just
Done (obviously). Note that this was after reverting back to the
original initrd and rerunning grub-install to make it stick - dunno if
that matters much to you.
Oh, and I have one other data point for you - I was unable to reproduce
this problem on a Dell Poweredge T100 (Xeon E3110, ICH9R).
I'm seeing the same thing on a fresh install of the 32-bit release of
9.10.
Hardware: Dell T3500 (Xeon E5520, 6GB DDR3, nVidia Quadro 470, 2x
Seagate LP 1.5TB)
Steps to reproduce:
1. Install Ubuntu 9.10 to a single disk partition (doesn't appear to matter
which).
2. Boot to the new install.
3.
Thank you Craig. Can you run apport-collect 158918 and allow it full
permission to add debugging information to Launchpad. Thank you.
** Changed in: mdadm (Ubuntu)
Status: Invalid = Incomplete
--
Installing mdadm package breaks bootup.
https://bugs.launchpad.net/bugs/158918
You received
Thank you for reporting this bug to Ubuntu. Unfortunately, 7.10 has reached EOL.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
You can follow instructions at https://help.ubuntu.com/community/EOLUpgrades to
upgrade to Hardy or later.
Please
Thank you for this automated response.
I will testing to see whether this bug is still present in the Karmic
Pre-Release.
--
Installing mdadm package breaks bootup.
https://bugs.launchpad.net/bugs/158918
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It wasn't an automated response ;) but thank you.
--
Installing mdadm package breaks bootup.
https://bugs.launchpad.net/bugs/158918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hee is a diff between the original initrd.img-2.6.22-14-server, and the
one installed after mdadm has been installed (and the fix done above).
** Attachment added: Difference in initrd's after installation.
http://launchpadlibrarian.net/10220272/initrd.diff
--
Installing mdadm package
Version: mdadm 2.6.2-1ubuntu2
--
Installing mdadm package breaks bootup.
https://bugs.launchpad.net/bugs/158918
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
15 matches
Mail list logo
