I've just seen this infinite loop in 16.04 with kernel 4.15.
For me, this was just a leftover because I was transitioning from
software raid to btrfs raid. Therefore, I had commented out the old
software raid definition in /etc/mdadm/mdadm.conf. Which in turn brought
me to the loop problem.
Hi,
as I see it, #1334699 is the bug producing the symptoms described in the
initial post. Because of that, the fixes seem somewhat arbitrary (due to
many causes showing the same symptoms). Nastily hides true problems.
In my case, the underlying issue also was that a device could not be
found
I came across this while purposely breaking my sw RAID array to test if
booting through the mirror disk or degraded array was OK.
Comment #4 worked for me.
ls /dev/mapper on the initram shell really showed that my root device
(which is on LVM) was not available before running that udevadm
Forgot to add that I am using Ubuntu 14.04 on an IBM x3630 M4 hardware.
12.04 apparently didn't manifested this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335642
Title:
mdadm runs into
I solved by deleting /etc/default/grub.d/dmraid2mdadm.cfg file which
added the string "nomdmonddf nomdmonisw" to the kernel load options.
These in turn were the culprit for boot loop. At least in my case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hey,
I can confirm that #5 alone fixes the problem, which is way nicer than the
hackaround in #4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335642
Title:
mdadm runs into infinite loop and
I've gotten this issue after reordering the SATA ports my devices are
plugged into. The MD-device assembles fine on a Live CD and using the
steps in #4 in a chroot on the Live CD got the system booting again, but
only after having the error reported in the original issue repeated
three or four
Indeed the fix from #4 seems to solve the problem for me. I can confirm
that the update from #9 is likely right, this is certainly a race
condition, sometimes it will boot without problem and other times it
gets stuck.
If I run `ls /dev/mapper` from busybox before executing the `udevadm`
command,
Fwiw, I can also confirm that my RAID array is degraded, which indeed
looks related to #645575.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335642
Title:
mdadm runs into infinite loop and
I fixed my issue by the recipe from #4
I think it would be extremely beneficial to integrate some kind of fix to this
problem into _LTS_ release which is expected to be extremely reliable and stable
Thank you in advance for your efforts.
--
You received this bug notification because you are a
It is well possible that while I have the same symptom as the original
reporter, the underlying cause is different.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335642
Title:
mdadm runs into
@jtm-moon-forum-user+launchpad
So in my case, the problem is a missing device node. Not just anyone,
but the one that is given to the kernel with the command line parameter
root= This is needed quite early during boot. That is why I inject
break, which means break=premount, which is even
@staub
After that, ls /dev/mapper shows what is needed for the root parameter:
HOST--vg-root
Would you clarify where this is needed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335642
Hi,
Slammed into this last night in a bit of an emergency situation. If some poor
soul is running ubuntu this might help resolve it:
http://serverfault.com/questions/593734/mdadm-boot-error-incrementally-starting-raid-array-ubuntu-server-14-04
What is the status of the bug? It sounds like it
It seems like there are many solutions to this error message. I have
tried quite a few myself to no avail. Something I installed via apt-get
broke my mdadm. There is a question posted over
https://answers.launchpad.net/ubuntu/+question/248396 that also pertains
to this.
can anyone chime in
I had the same problem and after searching I found out that this
solution (https://bugs.archlinux.org/task/33851#comment106076) worked
for me. I just had to rename all `/dev/md/*` devices to `/dev/md*`
devices in `/etc/mdadm/mdadm.conf` and run `update-initramfs -u` to
update the initramfs.
--
Without really understanding, I tried to hack something and found the
following bits, use at your own risk. This is on a degraded mdadm RAID1
with the root filesystem as a LV.
The following procedure was found to help:
* Interrupt grub and edit the linux command line.
* Go to the end of the
Hello all!
Problem with same symptom (loops on the same massage).
My system boots on a USB stick and has 4 sata disks in RAID 5 with 3 active and
a hot spare. One of the disks failed and was kicked
out of the array (probably a transient failure, needs further investigation).
For some reason I
** Also affects: mdadm
Importance: Undecided
Status: New
** No longer affects: mdadm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335642
Title:
mdadm runs into infinite loop and
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335642
Title:
probably related
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/645575
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335642
Title:
mdadm runs into infinite loop and prevents initrd/initramfs
** Description changed:
Hi all,
probably the issue is caused by changing the SATA-port where RAID disks
were originally attached -- this is the only thing that happened before
my Ubuntu 14.04 (kernel-3.13.0-27) became unbootable.
-
- During the boot the OS runs into infinite loop
22 matches
Mail list logo
