[Bug 188392] Re: mdam software raid fails to start up on reboot
*** This bug is a duplicate of bug 139802 *** https://bugs.launchpad.net/bugs/139802 ** This bug has been marked a duplicate of bug 139802 long bootup, dmesg full of md: array md1 already has disks! -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
yes, i have to correct myself (comment from 2008-07-31): it happened again.. but since i updated mdadm (several months ago), the issue is gone.. i did it the way Alan Jenkins described on 2008-07-29. i never did anything to the udev-rules or the raid-partitions -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
Hey everyone, I was having this exact same problem.
At some point an older array was defined, and there were superblocks for
md left on one (or more) of the partitions. Even if I zeroed them out
(using sudo mdadm --zero-superblock /dev/sda1), the superblock came back
after a reboot! It was very strange. Regardless if the partitions were
of type linux or linux raid autodetect, I was getting the above
errors and problems as people have already described. However, if the
partitions were CLEARED completely, the above repeating error did not
occur.
SOLUTION FOR ME:
In the file: /etc/udev/rules.d/85-mdadm.rules
Comment out the only line:
SUBSYSTEM==block, ACTION==add|change, ENV{ID_FS_TYPE}==linux_raid*,
RUN+=watershed -i udev-mdadm /sbin/mdadm -As
It looks like for some weird reason, udev is trying to be helpful and
searching for all devices with md superblocks and assemble any array it
might find? Clearly this is useless because mdadm itself already does
this.
HENCE: It makes sense that we're getting the above error: md: array
md0 already has disks! (although I'm not sure why it happens over and
over again).
Anyways, this is what worked for me (thanks to RaceTM for help!)
Cheers - hopefully my details will help the developers implement this bug fix.
--
mdam software raid fails to start up on reboot
https://bugs.launchpad.net/bugs/188392
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
PS: Apparently an upgrade of mdadm will fix this also? (I haven't verified) https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/139802 -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
another (strange) solution or workaround: it _seems_ like the problem is gone if i boot without the parameters quiet usplash !?! i modified my menu.lst, ran update-grub and since then the bug didn't occur once.. @ Alan Jenkins: if mdadm is buggy, shouldnt we expect an update via the repo when i gets fixed? -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
It's a reasonable request. I just don't automatically expect it. I confess I'm impatient about bugfixes for programs I rely on in the early boot process :-). If you've found a solution that works for you, however strange it seems, then patience is probably a virtue. -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
At least the message spam is fixed in the latest (upstream) version of mdadm. I advise you upgrade; there's at least one segfault bug which I was hitting which has also been fixed. Strong precautions are obviously necessary for those of use with root filesystems on MD. I suggest making sure you have at least two kernels. Copy mdadm to mdadm.bak, build from source, and overwrite mdadm. Run update-initramfs for *one* kernel, e.g. update-initramfs -u -k 2.6.24-19-generic. Then if that breaks you can recover by booting the *other* kernel and copying mdadm.bak back to mdadm. That's what I did. -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
ok, its NOT solved for me too.. it happens to me every 2nd cold boot or so.. after 2-5 x mdadm --stop /dev/md0 i get the array to work and can actually use the machine.. any chance to fix this??? anyone? is this bound to ubuntu or does it also happen to other distros? (tempted to try sidux) -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
I suspect not since I do not have an Array definition in my mdadm.conf yet I run into the problem with every reboot. -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
Thist annoying error just occurred to me. I have a simple raid1 with two devices as my home. worked fo years.. fresh hard-install a month ago.. i can find it in the mdadm .conf @ Johan Jefferey: your 4 steps worked! i could finally stop the dmesg- spam. thanks! after that i had a running md0. i did a soft reboot and everything went normal again !?! more details in my next post.. -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
This is happened when i stopped the spam (see above) 1000times md: array md0 already has disks! md: array md0 already has disks! md: array md0 already has disks! md: md0 stopped. md: unbindsdb2 md: export_rdev(sdb2) md: bindsdc2 md: bindsdb2 raid1: raid set md0 active with 2 out of 2 mirrors after soft reboot (lost the log... it looked roughly like the following): md: array md0 already has disks!(only once!?! no bind messages before this!) md: could not bd_claim sd?2 (don't know which sd it was) md: unbindsd?2 (i'm unsure with the order of these 2 ) md: export_rdev(sd?2) md: bindsdc2 (this looks good...) md: bindsdb2 raid1: raid set md0 active with 2 out of 2 mirrors ok, after that i removed the ARRAY-entry from the mdadm.conf: DEVICE partitions #ARRAY /dev/md0 level=raid1 num-devices=2 UUID=. another soft-reboot: [ 46.255357] md: bindsdc2 [ 46.255572] md: bindsdb2 [ 46.811324] raid1: raid set md0 active with 2 out of 2 mirrors thats it! problem solved? just let it scan for arrays rather than specifying them? -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
I've also run into this. And there seems to be a fair number on the Ubuntu forums that have experienced it also. This bug can cause Ubuntu 8.04to hang (become completely unresponsive), presumably due to the logs getting filed with 'md: array md0 already has disks!' many times per second. Also, this error start appearing in the kernel log just after you the kernel states it has loaded symbols and it starts in mid error. So, you really don't know what is happening that leads up to this. I've tried every work around that I can find that has been suggested in the forums, e.g. reinstalling mdadm, rebuilding the array from scratch, etc. But none have worked. The only work around is to at the earliest opportunity, either in a busy box, if presented with one, or immediately after you log in you do the following: 1) sudo mdadm -S /dev/md0 ( mdadm -S /dev/md0, if in a busy box) 2) then check the log with dmesg | tail ( dmesg | /usr/bin/tail, if you are in a busybox) 3) if the error 'md: array md0 already has disks!' has not stopped, repeat steps 1 2 until it does. - I'm finding more and more that it takes repeating the steps 3-4 times before things settle down. 4) once the error stops, if the array is listed in the /etc/fstab, you can issue a sudo mount /dev/md0 (mount /dev/md0, if in a busy box) and things will then work until the next reboot. -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
Forgot one thing: hardware and configuration. I have and IBM InteliStation A Pro with 2 - 146 Gb SCSI drives, each on their own Adaptec controller, in a RAID0 array. -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188392] Re: mdam software raid fails to start up on reboot
I just experienced this problem. Through the md: array md0 already has disks! error. Through the spam, if you wait 60s (or whatever the timeout is), you will be dropped to the initramfs shell. You can't see it though through the already has disks error 100 times per second. But, I typed 'mdadm --stop /dev/md0' and this stopped the spam! Surprisingly, /dev/md0 existed, and was fine! (though degraded, but I expected that because one drive had failed) To repeat, I ran 'mdadm --stop /dev/md0' and *after* I ran that, /dev/md0 still existed and was fine. So, it appears that mdadm is trying to create /dev/md0 *twice* and obviously fails the second time (repeatedly). -- mdam software raid fails to start up on reboot https://bugs.launchpad.net/bugs/188392 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
