If you suspect a timing issue then add the ARRAY line, it might not be waiting long enough to for all the drives to become visible before it tried to assemble the array. and be sure to update your initrd so that your initrd has the new mdadm.conf as well. On Thu, Mar 21, 2013 at 12:41 PM, Yaron <tclug at freakzilla.com> wrote: > this is a brand new setup - brand new machine, brand new OS install, brand > new RAID array and drives, so nothing can really be out of date (: > mdadm.conf does not have an "ARRAY" line, but from what I've heard it > doesn't need to have one. > > Like I said, you reboot enough times and it works fine. I really think > it's some kind of timing issue. I do hear the drives spin up and the > correct LEDs on the array box DO light up. I'm not seeing any error > messages, nor do I know where to look for them, is the problem. > > > > On Thu, 21 Mar 2013, Mike Hicks wrote: > > Is your /etc/mdadm.conf file up to date? There should be an "ARRAY" line >> in >> there with the correct UUID for your RAID set. It might also be pointing >> at >> devices that have been renamed or be excluding devices that should be >> used. >> >> -- >> Mike Hicks | hick0088 at umn.edu | Saint Paul, MN >> >> >> On Thu, Mar 21, 2013 at 8:19 AM, Yaron <tclug at freakzilla.com> wrote: >> I'm not using a partition table on the RAID device at all, but >> that's moot since I'm not booting off it. It gets mounted well >> after the OS is done booting... but it makes the boot process >> hang for random reasons. >> >> On Thu, 21 Mar 2013, Mike Miller wrote: >> >> On Wed, 20 Mar 2013, Yaron wrote: >> >> Ok, I've been running a software RAID5 >> on one of my older systems for a while. >> Almost every time I reboot, it claims >> the RAID is degraded and dumps me into >> busybox, where all I can really do is >> exit and HOME it'll see the drives next >> time I reboot. This is solved by >> rebooting anywhere from 2 to 20 times. >> >> I figured it was this system or these >> harddrives or this SATA controller or... >> whatever. But I just set up a brand new >> RAID array on a brand new machine using >> brand-new drives and a brand-new array, >> etc, etc. Same exact issue. >> >> Anyone have ANY idea if this is ME doing >> something wrong, or what? >> >> >> >> I don't really know anything except that the tricky >> part of making my RAID 1 work was figuring out how >> the boot partition is supposed to be set up. I >> didn't get that right and then after a kernel update >> it wouldn't reboot unless I went back to the earlier >> kernel. That might be irrelevant, but judging from >> things I was reading on web forums and advice I was >> getting, this is a tricky issue. With larger drives >> (more than 2.2 TB) we have to use GPT instead of MBR >> and then all kinds of little annoyances come along. >> Are you using GPT? >> >> Mike >> ______________________________**_________________ >> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota >> tclug-list at mn-linux.org >> http://mailman.mn-linux.org/**mailman/listinfo/tclug-list<http://mailman.mn-linux.org/mailman/listinfo/tclug-list> >> >> >> >> >> -- >> ______________________________**_________________ >> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota >> tclug-list at mn-linux.org >> http://mailman.mn-linux.org/**mailman/listinfo/tclug-list<http://mailman.mn-linux.org/mailman/listinfo/tclug-list> >> >> >> >> >> > > > -- > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20130321/a99f235b/attachment.html>