I need some help figuring out if a disk in my array is bad or if a "device disabled" error and red X next to the disk is caused by something else.

 

The problem seemed to start yesterday when I noticed that a parity check which usually takes 8 hours was reporting 13 days.  I also noticed that on the main screen there was reports of errors next to Disk 2 (the one offline now).  I went and ran the SMART check on all the drives and everything said that they all passed.

 

Fast forward to this morning when I logged on and noticed that Disk 2 has a red X and when I go to check the SMART status it says that it is disabled.  Also, I am unable to start my Windows 10 VM because it says a USB device is not attached.  I'm not sure if that is related, but that has never happened before.

 

I have attached the diagnostics file.  Can anyone help??

server-diagnostics-20161218-1510.zip

Shut down and check the cables to disk 2 then power up and grab diagnostics again so that we can see the SMART report on that disk.

 

I shut down the server, swapped the cable out with a new one and rebooted.  The disk still shows that SMART is disabled, but I went ahead anyway and re-grabbed the diagnostics file and attached it.  Thanks for your help!

server-diagnostics-20161218-1558.zip

You need to enable SMART first:

 

smartctl -s on /dev/sdd

 

Then grab and post new diags.

 

Syslog from when the disk got disable could help, if you saved it attach it also.

Done.  I ran that command which re-enabled SMART and then grabbed the new diag file.  It was the drive ending in 2834 that is giving me the error BTW.  Thanks!

server-diagnostics-20161218-1614.zip

SMART looks fine, since we can't see what happened try rebuilding to the same disk, if it happens again grab the diagnostics before rebooting.

SMART looks fine, since we can't see what happened try rebuilding to the same disk, if it happens again grab the diagnostics before rebooting.

OK, thank you very much.  I'll get on it and report back when it's done.

 

Sent from my Pixel XL using Tapatalk

 

 

So, I finally started the rebuild of the drive and it's telling me that it is going to take over 100 days to rebuild this.  Any idea what is going on here, because I'm sure it shouldn't take that long to rebuild.  I figured it was just something that happens when you start and lowers quickly as time goes on but the estimate is not getting any shorter, in fact it's getting longer.

Grab you diagnostics while it's being a problem and post them.

 

I've attached current diagnostic logs.

 

Except for a few short bursts of around 11MB/sec the speed always seems to hover around 2MB/sec.  This seemed to be the problem a few days ago when I noticed the parity check was going to take forever as well.

server-diagnostics-20161218-2213.zip

Don't see anything in the logs, do you have a spare disk you could use?

Unfortunately I don't have one on hand (now i know better) but I did buy one yesterday and it should be here by tomorrow or Friday.

 

Should I let the rebuild continue running or should I stop it and wait for the new drive?

You can do the following:

 

-cancel the rebuild

-stop the array

-unassign that disk

-start array

 

You'll have an option to do a read check (although I think unRAID still calls it a parity check), if the speed is normal there's something wrong with that disk, if it's not then it could be another disk (or another issue).

Ok, so here is what is going on so far.

 

I stopped the rebuild, stopped the array and then shut down.  I then switched sata ports on that HD to see if it was the problem.  After a reboot and attempted rebuild the max speed never exceeded 11 MB/sec and hovered around 2 MB/sec.

 

I also noticed that my Win 10 VM (which worked before this issue) now wouldn't start because it had an "internal error: Did not find USB device 5a4:1700" I found out that this is my USB3 card which does show up but now has a different ID of 1b73:1100.  When I disabled then re-enabled the card in the VM manager the VM started working again.

 

My new drive is scheduled to be here Wednesday so I guess I'll find out then if this is a drive issue or a motherboard issue.  Is there anything else I can try in the meantime to problem solve this?

Is there anything else I can try in the meantime to problem solve this?

 

You can do the following:

 

-cancel the rebuild

-stop the array

-unassign that disk

-start array

 

You'll have an option to do a read check (although I think unRAID still calls it a parity check), if the speed is normal there's something wrong with that disk, if it's not then it could be another disk (or another issue).

My apologies, I didn't quite understand what you meant at first..I get it now.

 

I just tried what you suggested: cancelled rebuild, stopped array, unassigned disk, started array.  However, the only option I have after that is to run a Parity-Sync and/or Data-rebuild and, when I press the "sync" button the screen refreshes and nothing happens.

It should start a read check, post the syslog after pressing sync.

Pressed "Sync" again and then grabbed the syslog (attached)

server-syslog-20161219-1556.zip

Only thing I can think of is that there's a bug and it doesn't work because a rebuild was canceled, so try this, stop the array, leave the disk unassigned, reboot and try again, it has to work.

Good call, after a reboot I was able to run a parity check with the suspect disk unassigned and am now getting speeds between 40-50 MB/sec.  I think that's where it should be, correct?

 

Should I let this parity check continue or stop and wait for my new disk to arrive and rebuild?

 

Thank you so much for all your help!!

 

 

OK, so since you already tried a different port it should be a problem with that disk, you can cancel the read check and wait for the spare.