On Tue, Oct 22, 2013 at 2:30 PM, Jogi Hofmüller <j...@mur.at> wrote: > Am 2013-10-18 12:42, schrieb Jogi Hofmüller: >> Am 2013-10-18 10:35, schrieb Jesse Molina: >>> >>> As previously noted, this was a bug in mdadm and has already been fixed >>> in the current version. Just update your mdadm package and then >>> re-build your initramfs file with the "update-initramfs" command. Be >>> sure to read the manpage for that command. Probably "update-initramfs >>> -u" alone will fix your problem. >>> >>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726237 >> >> Thanks for the hint. Read the bugreport before and figured it is not >> relevant since we are using mdadm 3.2.5 which is supposed to be working. >> >> Still, did the upgrade to 3.3-2: no change. >> >> BTW: all this happens on an Intel Serverbarebone (RZ1208GZ4GC) with >> SATA drives on C600/X79 series chipset SATA controler. >> >> A similar machine with Series/C200 Series Chipset SATA controler boots >> just fine with the same setup (linux-image-3.10-3-amd64 and mdadm 3.2.5). >> >> Does anyone have experience with Intel Serverbarebones? I figure it has >> something to do with the SATA controler ... > > I tried using linux-image-3.11-1 from sid today and got the same result. No > RAID is created. I really don't know where to start looking now. Any ideas? > Wrong list?
Feel free to find another list. At what point does your boot stop? Are you dropped to an initramfs shell? Is the array assembled? Are the by-uuid entries created? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=SxS02ocnJdGMvG8CbO5WW5nQSZsQYiSWbcOPXLj0=b...@mail.gmail.com
