This should be no issue with UUID-based raid assembly that makes
mdadm.conf ARRAY definition maintanance obsolete.
** Summary changed:
- MD/LVM boot broken
+ [-UUIDudev] MD/LVM boot broken
--
[-UUIDudev] MD/LVM boot broken
https://bugs.launchpad.net/bugs/328892
You received this bug
*** This bug is a duplicate of bug 332270 ***
https://bugs.launchpad.net/bugs/332270
This is not a duplicate of bug 332270! Would somebody please reopen
this bug!
I finally fixed this bug. My upgrade to Jaunty produced the attached
bad mdadm.conf. I ran dpkg-reconfigure mdadm and it
*** This bug is a duplicate of bug 332270 ***
https://bugs.launchpad.net/bugs/332270
This is not a duplicate. The bug appears to be in mdadm.
** Attachment added: the good mdadm.conf produced by running dpkg-reconfigure
mdadm
http://launchpadlibrarian.net/23856025/mdadm.conf
--
MD/LVM
Diff between bad and good mdadm.conf from the comments above:
--- mdadm.conf.backup 2009-03-14 15:39:56.0 +0100
+++ mdadm.conf 2009-03-14 15:41:53.0 +0100
@@ -1,5 +1,3 @@
DEVICE partitions
-ARRAY /dev/md0 level=raid5 num-devices=3
UUID=5ab28c4c:2cc90775:9b315729:d7b43017
*** This bug is a duplicate of bug 332270 ***
https://bugs.launchpad.net/bugs/332270
** This bug has been marked a duplicate of bug 332270
udev repeatedly generates change events for the same block device(s)
--
MD/LVM boot broken
https://bugs.launchpad.net/bugs/328892
You received this
*** This bug is a duplicate of bug 332270 ***
https://bugs.launchpad.net/bugs/332270
This is not a duplicate of bug 332270 -- the fix for 332270 just fixed
comment #3 -- the original problem is still extant.
--
MD/LVM boot broken
https://bugs.launchpad.net/bugs/328892
You received this bug
Same problem here. Cannot boot, even the mentioned solution does not
work
--
MD/LVM boot broken
https://bugs.launchpad.net/bugs/328892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The problem has just gotten severely worse. I did a apt-get dist-
upgrade today, and am no longer able to boot my machine.
At the (first) busybox prompt I type the above commands.
The computer then pauses for a few minutes and then returns with many
messages of the form:
I managed to boot with a 2.6.24 kernel -- both 2.6.27 and 2.6.28
exhibited the same problem. (Well, the 2.6.27 wasn't exactly the same).
However, in 2.6.24, my udevd eats up 80% of my CPU and makes my hard
disk churn!
Looking through my ps -ax, it may be the /lib/udev/watershed sh -c
/sbin/lvm
Note that I have two md's. The one I don't care about get's started
automatically, the mdadm --assemble --scan is only required to start the
md that has my root partition.
--
MD/LVM boot broken
https://bugs.launchpad.net/bugs/328892
You received this bug notification because you are a member of
On Mon, 2009-02-23 at 21:53 +, Bryan Larsen wrote:
I managed to boot with a 2.6.24 kernel -- both 2.6.27 and 2.6.28
exhibited the same problem. (Well, the 2.6.27 wasn't exactly the same).
However, in 2.6.24, my udevd eats up 80% of my CPU and makes my hard
disk churn!
This is bug
Thanks Scott, but udev 138-2 does not fix the second problem, but it
does make it different. Since this is quite probably two different
bugs, I've opened another report with the details at bug 333614.
--
MD/LVM boot broken
https://bugs.launchpad.net/bugs/328892
You received this bug
On Tue, 2009-02-24 at 00:48 +, Bryan Larsen wrote:
Thanks Scott, but udev 138-2 does not fix the second problem, but it
does make it different. Since this is quite probably two different
bugs, I've opened another report with the details at bug 333614.
Did you also upgrade lvm2?
Scott
Thanks for the pointer that there's a new lvm2. Unfortunately,
2.02.39-0ubuntu8 does not affect my problem in any way.
--
MD/LVM boot broken
https://bugs.launchpad.net/bugs/328892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
and watershed version 3
--
MD/LVM boot broken
https://bugs.launchpad.net/bugs/328892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
15 matches
Mail list logo
