Jump to content

Can't start array


Recommended Posts

I just turned off the machine to put a new drive in... Shut down cleanly, inserted drive, turned it back on... now the array won't start:

 


Dec 1 17:15:17 Tower emhttp: shcmd (116): /usr/local/sbin/set_ncq sdk 1 >/dev/null
Dec 1 17:15:17 Tower emhttp: shcmd (117): /usr/local/sbin/set_ncq sdj 1 >/dev/null
Dec 1 17:15:17 Tower emhttp: shcmd (118): /usr/local/sbin/set_ncq sdh 1 >/dev/null
Dec 1 17:15:17 Tower emhttp: shcmd (119): /usr/local/sbin/set_ncq sdd 1 >/dev/null
Dec 1 17:15:17 Tower emhttp: shcmd (120): /usr/local/sbin/set_ncq sdf 1 >/dev/null
Dec 1 17:15:17 Tower emhttp: shcmd (121): /usr/local/sbin/set_ncq sdg 1 >/dev/null
Dec 1 17:15:17 Tower emhttp: shcmd (122): /usr/local/sbin/set_ncq sdc 1 >/dev/null
Dec 1 17:15:17 Tower emhttp: shcmd (123): /usr/local/sbin/set_ncq sdb 1 >/dev/null
Dec 1 17:15:17 Tower kernel: mdcmd (90): start STOPPED
Dec 1 17:15:17 Tower kernel: md: do_run: lock_rdev error: -6
Dec 1 17:15:18 Tower emhttp: shcmd (124): rm /etc/samba/smb-shares.conf >/dev/null 2>&1
Dec 1 17:15:18 Tower emhttp: shcmd (125): cp /etc/exports- /etc/exports
Dec 1 17:15:18 Tower emhttp: shcmd (126): killall -HUP smbd
Dec 1 17:15:18 Tower emhttp: shcmd (127): /etc/rc.d/rc.nfsd restart | logger

 

Any ideas?

Link to comment

I didn't do anything with the drive besides plug it in - it was not part of the array.  I was planning on telneting in to preclear it.  My PSU should be sufficient, it's a 850W single-rail Corsair, this was only drive 10 to be plugged in.

 

I tried turning the machine off, removing the new drive, and turning it on again; still getting the same thing.

 

If I telnet it and manually create a directory in the mnt folder, and mount a disk into it, I can see all my data across the drives...

 

It's just clicking "start array" that gives me the error message above.

Link to comment

Thanks for the links mbryanr...

 

Looks like my disk5, aka sdf, isn't working...

 

If I "ls -l /mnt/sd*" then I see that all of my drives have sdX1 EXCEPT for sdf.

 

If I go to devices and unassign disk5 (it's a jumpered WD EARS), then the array starts fine in simulation mode.

 

I do have a precleared spare in the machine I could rebuild to... should I do that and RMA the WD drive? Or should I try some reisermagic on it first?

Link to comment

Thanks for the links mbryanr...

 

Looks like my disk5, aka sdf, isn't working...

 

If I "ls -l /mnt/sd*" then I see that all of my drives have sdX1 EXCEPT for sdf.

 

If I go to devices and unassign disk5 (it's a jumpered WD EARS), then the array starts fine in simulation mode.

 

I do have a precleared spare in the machine I could rebuild to... should I do that and RMA the WD drive? Or should I try some reisermagic on it first?

btw, -6 error indicates no partition (see 2nd link above).  I believe that matches what you are seeing.

 

I'm in no way an expert.  First, I would check all cabling, connections, etc. Then a smart test on disk 5; then ask for further assistance! Others with experience can guide you along the way.

 

Since disk 5 was working before the shutdown...it is unlikely something happened to it during that short period. Reisermagic should be performed as a last resort.

 

 

 

 

Link to comment

I think Limetech needs an official large facepalm icon...

 

I had just knocked a disc loose... after reseating it, it was redetected. 

 

It change the sdx assignment though... had to do that scary initconfig thing...  Now it is running okay, all my files are there... tonight I'll run a parity sync while the new drive preclears...

 

 

 

 

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...