[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

no activity for long assuming fix released ** Changed in: mdadm (Ubuntu) Status: Confirmed => Fix Released -- mdadm causes boot to hang for 4 minutes https://bugs.launchpad.net/bugs/67299 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ub

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Having had a very similar problem (see ) which was gone after a fresh gutsy install, perhaps this does ``solve'' this issue here as well? -- mdadm causes boot to hang for 4 minutes https://bugs.launchpad.net/bugs/67299 You

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

** Changed in: mdadm (Ubuntu) Status: Incomplete => Confirmed -- mdadm causes boot to hang for 4 minutes https://bugs.launchpad.net/bugs/67299 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubun

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

cat /etc/mdadm/mdadm.conf DEVICE partitions cat /proc/mdstat Personalities : [raid5] [raid4] md0 : active raid5 hda6[0] hdd1[2] hdc1[1] 390700544 blocks level 5, 32k chunk, algorithm 0 [3/3] [UUU] unused devices: cat /etc/fstab # /etc/fstab: static file system information. # #

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Hi Richard, If you can post a copy of your /etc/mdadm.conf (or is it /etc/mdadm/mdadm.conf), the output of cat /proc/mdstat, your /etc/fstab and an ls -l of /dev/disk/by-uuid that might give something to help with. Dave -- mdadm causes boot to hang for 4 minutes https://bugs.launchpad.net/b

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

This scenario is also happening to me, for me the wait can be over 10 minutes. I also use evms and have lvm2 on md in a raid 5. I have the updated mdadm package from edgy-updates installed. If there's any info that I can provide to help debug this issue please let me know. -- mdadm causes boot

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

It depends how you do clone the disks. Note that the initramfs is updated on each machine for the very good reason that some raid information are stored there. If the wrong information are cloned in the initramfs of another machine, that one will suffer of the problem again and you will need to re

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

ok. Thanks for the fix (Well. Almost fix) . We have been suffering from this now for three months. In our case, we have Edgy on Software RAID which we disk cloned and use it in three other machines of the same configuration. Prior to the fix, in each cloned disk machine will take over 10 mins (sa

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

All bugs marked as duplicates of this one have been reassigned to #74346 as suggested by https://wiki.ubuntu.com/StableReleaseUpdates point 1 ("If more than one bug is being addressed, it is better to file a bug to track the SRU itself and refer to all of the relevant bugs.") This bug is still rel

Re: [Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Dave Gilbert wrote: > Hi Fabio, That deb seems to work fine for me (reporter of 6); some > comments: > > 1) The /etc/mdadm/mdadm.conf you create in the initrd is now very different > from the mdadm.conf you would find in your running system - perhaps it should > have a different name (mdadm.uu

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Hi Fabio, That deb seems to work fine for me (reporter of 6); some comments: 1) The /etc/mdadm/mdadm.conf you create in the initrd is now very different from the mdadm.conf you would find in your running system - perhaps it should have a different name (mdadm.uuids ?) (Incidentally that

Re: [Bug 67299] Re: mdadm causes boot to hang for 4 minutes

On 01/12/06, Fabio Massimo Di Nitto <[EMAIL PROTECTED]> wrote: > I will upload mdadm now to solve the timeout issue for all the others but i > will > need some more help from you to solve your problem in edgy. That sounds good. I'm happy to help however I can to sort this out. Thanks, Oliver

Re: [Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Oliver Payne wrote: > On 30/11/06, Fabio Massimo Di Nitto <[EMAIL PROTECTED]> wrote: >> Are you running RAID over LVM? > > Yes. Ok.. this change totally the issue. lvm and evms are always executed after mdadm. > >> and are you actually using evms for your disk management for real? > > Yes, I u

Re: [Bug 67299] Re: mdadm causes boot to hang for 4 minutes

On 30/11/06, Fabio Massimo Di Nitto <[EMAIL PROTECTED]> wrote: > Are you running RAID over LVM? Yes. > and are you actually using evms for your disk management for real? Yes, I use evms for managing my filesystems. All my non-root filesystems are lvm volumes. I also have a backup filesystem, w

Re: [Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Oliver Payne wrote: > Unfortunately, no joy here with the new version :-( Output from mdadm > -D /dev/md0: > Number Major Minor RaidDevice State >0 25380 active sync > /dev/evms/.nodes/lvm2/30G_container/backup1 >1 253 111

Re: [Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Istvan Botka wrote: > Hi Fabio! > > I've tried the http://people.ubuntu.com/~fabbione/67299/ package on my amd64 > box (it runs amd64). > It's working but complains on debug section (log_begin_msg and log_end_msg > not found) > My RAID is an raid5 level array built from sd[a-d]. > Oh i see.. i

Re: [Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Alan Tam wrote: > Any reason the loop max lasts for 180 seconds? I guess 15 or 30 seconds > are pretty much enough (bug 73710). > Unfortunaly 15/30 seconds are not enough for all systems. In one of my test cases I have devices appearing after a minute. The problems that we are addressing here ar

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Unfortunately, no joy here with the new version :-( Output from mdadm -D /dev/md0: /dev/md0: Version : 00.90.03 Creation Time : Thu Jun 29 22:56:50 2006 Raid Level : raid1/dev/md0: Version : 00.90.03 Creation Time : Thu Jun 29 22:56:50 2006 Raid Level : raid1 Ar

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Hi Fabio! I've tried the http://people.ubuntu.com/~fabbione/67299/ package on my amd64 box (it runs amd64). It's working but complains on debug section (log_begin_msg and log_end_msg not found) My RAID is an raid5 level array built from sd[a-d]. -- mdadm causes boot to hang for 4 minutes https

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Hi Fabio, tried your patched mdadm and it works fine for me. (I reported to bug 6) Edgy upgraded from dapper on i386 with kernel 2.6.17-10-generic. mdadm.conf: DEVICE /dev/hd[eg]1 /dev/md0 ARRAY /dev/md0 level=raid0 num-devices=2 auto=md UUID=de8de1a1:92bd24ff:71f87519:4adf71fd Thank you f

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Any reason the loop max lasts for 180 seconds? I guess 15 or 30 seconds are pretty much enough (bug 73710). -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

I uploaded a new mdadm that should address all the issues (at least i really hope so) described in all bugs here: http://people.ubuntu.com/~fabbione/67299/ I would be really glad if you could please test it in your environment (make sure your initramfs is updated) and let me know if it works. If

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Ok to all submitters: thanks a lot for the reports. Clearly i fucked this up and I am working on a proper fix. Stay tuned because i will need your help to test some cases like the one with sdv and so on. Fabio -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubun

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

too much handwaving.. eh.. ** Changed in: mdadm (Ubuntu) Importance: Undecided => High Assignee: (unassigned) => Fabio Massimo Di Nitto -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubu

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Hi Oliver! Could you send the output of mdadm -D /dev/md0 command also? -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

I have a RAID1 array built from two lvm2 regions (via EVMS). /proc/mdstat shows: Personalities : [raid1] md0 : active raid1 dm-11[1] dm-8[0] 15335360 blocks [2/2] [UU] unused devices: and /etc/mdadm/mdadm.conf contains: DEVICE partitions ARRAY /dev/md0 level=raid1 num-devices=2 U

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

You're right. My fix works work in my and the two other reported case. It is a quick and dirty fix for some special cases. I have spent ~4-5 hours to catch this bug. (A reboot takes up to 10 minutes on my box when patch not included) It would have been take less time if the script would have so

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Ok, I found out how to rebuild the initrd, I can confirm this fixes the bug for me. -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Do I need to rebuild the initrd for this? If so, how do I do it? I did patch that script, but boot still took a long time so I assume there is another step. -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com htt

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Be careful - while indeed this does seem a fix for this problem, this script needs a lot more work. Hard coding that fairly arbitrary list of devices is going to break again for someone with a more obscure device. (As a first example, when there are more than 26 scsi devices - and I've seen a syste

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

** Changed in: mdadm (Ubuntu) Status: Confirmed => Fix Committed -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

** Attachment added: "Scan whole disks not only the partitions for raid members at boot time." http://librarian.launchpad.net/5173804/md.patch -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Here is my patch for /usr/share/initramfs-tools/scripts/local-top/md --- md.orig 2006-09-26 14:36:43.0 +0200 +++ md.fixed2006-11-26 10:13:12.0 +0100 @@ -23,7 +23,7 @@ # Detect raid level while [ "$configureduuids" ] && [ ${slumber} -gt 0 ]; do - for x in /dev/hd[a

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

The wait for me is more than 3 minutes, though. Any chance of a fix for this though? -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

** Changed in: mdadm (Ubuntu) Status: Unconfirmed => Confirmed -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

There is a script /usr/share/initramfs-tools/scripts/local-top/md in the mdadm package. It scans only the hda1, hda2, sda1, sdb2, etc but no the hda, hdb, sda, sdb. There is a cycle in this script that wait 180 seconds on every boot for timeout of the scanning the possibly raid member disks to de

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

There is a script /usr/share/initramfs-tools/scripts/local-top/md in the mdadm package. It scans only the hda1, hda2, sda1, sdb2, etc but no the hda, hdb, sda, sdb. There is a cycle in this script that wait 180 seconds on every boot for timeout of the scanning the possibly raid member disks to de

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

OK, it doesn't look quite the same problem I've got - for me that sed is producing rubbish and hence it never finds it (but I've not tried fixing that to see if the problem then goes away). I'd suggest adding some debug to the beginning and end of that scripts and then rebuilding the initrd and

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

It should be noted that I also have a card reader, as in bug #6 but I unplugged it, and disabled USB boot in BIOS the problem remained. Also, as you requested: [EMAIL PROTECTED]:~$ cat /etc/mdadm/mdadm.conf | grep "UUID" | sed -e 's/.*=//g' 3dcc3d57:4499d301:a27ac102:cf8ea623 [EMAIL PROTECTED

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Hmm, maybe its not exactly the same problem as mine then - can you try: cat /etc/mdadm/mdadm.conf | grep "UUID" | sed -e 's/.*=//g' and add on here what it says - in principal it should be just the UUID -- mdadm causes boot to hang for 4 minutes https://launchpad.net/bugs/67299 -- ubuntu-bug

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Hiya Dave, Here's the info you asked for. [EMAIL PROTECTED]:~$ cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb[0] sdc[1] 244198464 blocks [2/2] [UU] unused devices: [EMAIL PROTECTED]:~$ [EMAIL PROTECTED]:~$ sudo mdadm --examine /dev/sdb /dev/sdb: Magic :

[Bug 67299] Re: mdadm causes boot to hang for 4 minutes

Hi Tom, It looks like I'm falling over a similar problem to you in bug 6; in my case I think the problem is it doesn't like the format of my mdadm.conf; but could you add to your report; the output of : cat /proc/mdstat and then for each of the partitions with the RAID on the output of md