Assuming segfault is amoung the fixes upstream or even already in more
recent releases.
** Changed in: mdadm (Ubuntu)
Status: Incomplete => Fix Released
--
Mdadm segfault on booting Hardy
https://bugs.launchpad.net/bugs/252485
You received this bug notification because you are a member of
Is this still an issue with recent releases using UUIDs in mdadm.conf?
** Changed in: mdadm (Ubuntu)
Status: New => Incomplete
--
Mdadm segfault on booting Hardy
https://bugs.launchpad.net/bugs/252485
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at [WWW]
https://wiki.ubuntu.co
Thx ceg for the hint. This bug however relates to a non degenerated
array and ocurs only because the mainboard assigns other device names!
--
Mdadm segfault on booting Hardy
https://bugs.launchpad.net/bugs/252485
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi, concerning the boot process you can test the current patches
https://wiki.ubuntu.com/BootDegradedRaid
for Bug #120375
--
Mdadm segfault on booting Hardy
https://bugs.launchpad.net/bugs/252485
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
