[Bug 252365] Re: mdadm does not add spares to arrays on boot
Many years later I can no longer reproduce this ** Changed in: mdadm (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/252365 Title: mdadm does not add spares to arrays on boot To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/252365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252365] Re: mdadm does not add spares to arrays on boot
Does Bug #550131 "initramfs missing /var/run/mdadm dir (loosing state)" fix this? -- mdadm does not add spares to arrays on boot https://bugs.launchpad.net/bugs/252365 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 252365] Re: mdadm does not add spares to arrays on boot
I'd consider the missing modules issue as fix released, right? Christian Reis, does the race still occur in recent releases? Why is initramfs udev killed instead of transitioned to the rootfs? https://wiki.ubuntu.com/ReliableRaid ** Changed in: initramfs-tools Status: New => Fix Released ** Changed in: mdadm (Ubuntu) Status: New => Incomplete -- mdadm does not add spares to arrays on boot https://bugs.launchpad.net/bugs/252365 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 252365] Re: mdadm does not add spares to arrays on boot
MNLipp, sbrady69: I think we are actually having a different problem than this bug. Jan's issue is that the spare he has comes from a separate controller (which isn't available in the stock initramfs he was using). I spent a lot of time researching this yesterday, and found that it's actually a race condition: the md devices are assembled too early, before the spare drive has been scanned. I had an additional issue in that I was referring to the drives in mdadm.conf explicitly instead of via UUIDs. I worked around this reliably by using UUIDs in mdadm.conf and by adding a custom sleep script in /etc/initramfs-tools/scripts /local-premount/ ; I'm posting an entry in my diary in case people are interested: http://async.com.br/~kiko/diary.html?date=09.12.2009 -- mdadm does not add spares to arrays on boot https://bugs.launchpad.net/bugs/252365 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 252365] Re: mdadm does not add spares to arrays on boot
change amount of spares if this happens on debian lenny after update for RAID 1 config. for some reason 2 devices, and 1 spare did not return emails before, but now is. I have to change spares=1 to spares=0 -- mdadm does not add spares to arrays on boot https://bugs.launchpad.net/bugs/252365 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 252365] Re: mdadm does not add spares to arrays on boot
I confirm this same problem on Debian Lenny. I was not able to fix the problem by adding: DEVICE /dev/hd[abcdef][12] or DEVICE /dev/sd[abcdef][12] to mdadm.conf this is for IDE hard drives, I assume support has degraded for such devices -- mdadm does not add spares to arrays on boot https://bugs.launchpad.net/bugs/252365 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 252365] Re: mdadm does not add spares to arrays on boot
I can confirm the problem (for 9.04) and I have all disks on the same controller (raid5 with 3 + 1 spare). The spare is recognized sometimes, but not always. Looking at the boot messages, I strongly suspect that it depends on the sequence in which the disks become available to mdadm. Disks are /dev/sd?5 with ?=[abcd], spare is /dev/sdd5. If the sequence is "bind" with ?=[abc] then the spare is not recognized. If one or more of the [abc] binds show up after "bind", then the spare is recognized. Seems like spares are not added after the raid has been set active. -- mdadm does not add spares to arrays on boot https://bugs.launchpad.net/bugs/252365 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 252365] Re: mdadm does not add spares to arrays on boot
I have this same symptom, but all my disks are on the same controller, so the issue is likely to be different. I wonder what is causing the spares to not be picked up -- could it be mdadm --scan is not doing the right thing? -- mdadm does not add spares to arrays on boot https://bugs.launchpad.net/bugs/252365 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 252365] Re: mdadm does not add spares to arrays on boot
I have been advised on the linux-raid mailing list [1] that this problem is more likely to be caused by mkinitrd than by mdadm, and that I should therefore file a bug against initramfs-tools. [1]: http://marc.info/?l=linux-raid&m=123421650832520&w=2 ** Also affects: initramfs-tools Importance: Undecided Status: New -- mdadm does not add spares to arrays on boot https://bugs.launchpad.net/bugs/252365 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 252365] Re: mdadm does not add spares to arrays on boot
JanCeuleers: Your solution works! My setup is similar to yours. I have a nVidia mainboard SATA controller with the system disk and spare connected, and a Promise TX4 SATA PCI card with four disks hosting a RAID5 volume. I added the modules sata_nv and sata_promise to /etc/initramfs-tools/modules, rebuilt initrd, rebooted, and now it works as intended. Thank you for finding a solution. I hope the Ubuntu devs can find a way to automate this or inform users about it. -- mdadm does not add spares to arrays on boot https://bugs.launchpad.net/bugs/252365 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 252365] Re: mdadm does not add spares to arrays on boot
I'm sorry for having let this bug linger for such a long time. I think I have now found the proper solution to this problem. Restating the problem: I have six disks, four of which are served by a sata-sil24 controller, the other two being served by a sata-via controller. The active partitions of my raid5 set live on the first four disks, the spare partitions live on one of the other two disks (the other being used for backup). With the above setup, the active members of the raid set would come up fine upon boot, but the spares would not be added automatically, so that I had to add them from /etc/rc.local On my system, this problem has been solved by including both sata modules in the initrd image. That is: I added sata-via and sata-sil24 to /etc/initramfs-tools/modules , rebuilt the initrd images using update- initramfs -u -k all, and everything is now activated automatically on boot. Bjorn Ruud: can you let us know whether your spare disk is also served by a controller that requires a different module from the one serving your active disks? If so, would you give the above a go and report back? -- mdadm does not add spares to arrays on boot https://bugs.launchpad.net/bugs/252365 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 252365] Re: mdadm does not add spares to arrays on boot
I can confirm this problem on Ubuntu Server 8.04. I have the same RAID5 configuration as the reporter (4 active disks, 1 spare). In my case the spare isn't added to the array on boot no matter what changes are made to mdadm.conf. Stating the devices explicitly doesn't help. $ cat /etc/mdadm/mdadm.conf [snip] DEVICE partitions [snip] ARRAY /dev/md0 level=raid5 num-devices=4 spares=1 UUID=d7ae6761:1abc675c:6e03419f:9b214e6e $ sudo mdadm --detail --scan ARRAY /dev/md0 level=raid5 num-devices=4 spares=1 UUID=d7ae6761:1abc675c:6e03419f:9b214e6e $ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active raid5 sdf1[4](S) sda1[0] sdd1[3] sdc1[2] sdb1[1] 2197715712 blocks level 5, 64k chunk, algorithm 2 [4/4] [] unused devices: $ sudo mdadm --detail /dev/md0 /dev/md0: Version : 00.90.03 Creation Time : Thu Aug 9 15:29:00 2007 Raid Level : raid5 Array Size : 2197715712 (2095.91 GiB 2250.46 GB) Used Dev Size : 732571904 (698.64 GiB 750.15 GB) Raid Devices : 4 Total Devices : 5 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Fri Nov 28 15:06:38 2008 State : clean Active Devices : 4 Working Devices : 5 Failed Devices : 0 Spare Devices : 1 Layout : left-symmetric Chunk Size : 64K UUID : d7ae6761:1abc675c:6e03419f:9b214e6e Events : 0.76 Number Major Minor RaidDevice State 0 810 active sync /dev/sda1 1 8 171 active sync /dev/sdb1 2 8 332 active sync /dev/sdc1 3 8 493 active sync /dev/sdd1 4 8 81- spare /dev/sdf1 -- mdadm does not add spares to arrays on boot https://bugs.launchpad.net/bugs/252365 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
