<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>+1 on Munir's comprehensive answer. </div><div><br></div><div>I'd also advocate using UUID references rather than /dev/sdX for portability. </div><div><br></div><div>It sounds like you might have a failing drive. If the motor is having issues spinning the drive up in time or, less commonly, keeping it going, then the drive won't respond to the kernel's raid probing in time and the result will match the symptoms you're reporting. (There are other causes, though. One of my PCIe SATA controller cards times out with two drives attached; it is reliably fine with one drive. )</div><div><br></div><div>Thomas</div><div><br></div><div><br></div><div><br>On Mar 21, 2013, at 10:28 AM, Munir Nassar <<a href="mailto:tclug@beitsahour.net">tclug@beitsahour.net</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">on modern systems there is little need for an mdadm.conf to configure the array.<div><br></div><div style="">a couple of things to look for,</div><div style="">if you are using linux-md/partitions, are the partitions marked linux raid autodetect? if not, then you may want to so that you do so that the linux kernel can build the array automatically.(note that do not below, but i also have an entry in mdadm.conf) </div>
<div style="">ARRAY /dev/md/datastore metadata=1.2 UUID=ce33ff1a:82c18dff:ef8d5149:60e9281e name=snakeman:datastore<br></div><div style=""><br></div><div style="">you can get the UUID from the mdadm command below</div><div style="">
<br>
</div><div style="">also, what is the md version that you are using? you can use mdadm --detail to find out:</div><div style=""><div>$ sudo /sbin/mdadm --detail /dev/md127</div><div>/dev/md127:</div><div> Version : 1.2</div>
<div> Creation Time : Sat May 26 17:55:25 2012</div><div> Raid Level : raid5</div><div> Array Size : 5128012288 (4890.45 GiB 5251.08 GB)</div><div> Used Dev Size : 732573184 (698.64 GiB 750.15 GB)</div><div> Raid Devices : 8</div>
<div> Total Devices : 8</div><div> Persistence : Superblock is persistent</div><div><br></div><div> Update Time : Thu Mar 21 10:23:59 2013</div><div> State : clean</div><div> Active Devices : 8</div><div>
Working Devices : 8</div>
<div> Failed Devices : 0</div><div> Spare Devices : 0</div><div><br></div><div> Layout : left-symmetric</div><div> Chunk Size : 512K</div><div><br></div><div> Name : snakeman:datastore (local to host snakeman)</div>
<div> UUID : ce33ff1a:82c18dff:ef8d5149:60e9281e</div><div> Events : 2114</div><div><br></div><div> Number Major Minor RaidDevice State</div><div> 0 8 0 0 active sync /dev/sda</div>
<div> 1 8 16 1 active sync /dev/sdb</div><div> 2 8 32 2 active sync /dev/sdc</div><div> 3 8 48 3 active sync /dev/sdd</div><div>
4 8 64 4 active sync /dev/sde</div><div> 5 8 80 5 active sync /dev/sdf</div><div> 9 8 96 6 active sync /dev/sdg</div><div> 8 8 112 7 active sync /dev/sdh</div>
<div><br></div><div style="">also, does the array finish building before you reboot? /proc/mdstat should show you the status of the rebuild, do not power down the system before it has finished rebuilding.</div><div style=""><br>
</div><div style="">finally, check the smart status on the drives, it could be that one of the drives is failing without you even knowing it, check with smartctl -a /dev/sdX, maybe run a long scan on each drive in turn: smartctl -t long /dev/sdX</div>
<div style=""><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 21, 2013 at 9:57 AM, Yaron <span dir="ltr"><<a href="mailto:tclug@freakzilla.com" target="_blank">tclug@freakzilla.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There are no commented out options that indicate delaying mdadm, but I will try and google for that.<div class="im HOEnZb">
<br>
<br>
On Thu, 21 Mar 2013, gregrwm wrote:<br>
<br>
</div><div class="im HOEnZb"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
could be that mdadm.conf ought to wait for an event it isn't waiting for<br>
<br>
<br>
</blockquote>
<br>
<br>
<br></div><div class="HOEnZb"><div class="h5">
--<br>
______________________________<u></u>_________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org" target="_blank">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/<u></u>mailman/listinfo/tclug-list</a><br>
</div></div></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>TCLUG Mailing List - Minneapolis/St. Paul, Minnesota</span><br><span><a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a></span><br><span><a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a></span><br></div></blockquote></body></html>