(SOLVED) - Drive shows with red X, device is disabled.

[calypsocowboy]

I have a drive showing with a red X, device is disabled.  About my system, I'm running Unraid 6.2 on an older Supermicro PDSMi board with a RR1U-ELi riser card with a SuperMicro AOC-SASLP-MV8 card. The drive that is having problems is connected to that card. It's a 4TB Seagate drive. I got it from a schucked enclosure a number of years back from Costco. I have two of those drives in the computer. I believe my mobo bios is up to date, I'm not sure what bios the card is running. 

 

This first happened about 3 months ago. At the time, I stopped the array, powered down the server, pulled and reset the power and data cables, restarted the server, checked the smart report, it came back clean on the drive, so went through the process of adding the drive back into the array, Things seemed to be working well for a bit.

 

About a week ago, I noticed the same thing, I took the same steps only this time, I connected the drive to a different end of the breakout cable, the one I had it connected to looked a little suspect, same process, clean smart report, added drive back in. 

 

And now, back comes the red x, same drive. 

 

No now trying to figure out what's next. I'm not sure the drive is bad because after each reboot, it come back clean. I've tried different ends on the breakout cable (Monoprice). I could try ordering a new cable to see if that might be the issue. I'm not sure if it's the expansion card or maybe the riser or the combo. I don't think my mobo supports just the card without the riser. 

 

Any thoughts or am I too the point where I need to look for a new expansion card, or maybe a mobo that supports more SATA connections, or supports the card I have directly instead of via riser. 

 

Current Diagnostics - cascade-diagnostics-20170527-1408.zip

Last Weeks Diagnostics - cascade-diagnostics-20170521-0812.zip

Edited June 1, 2017 by calypsocowboy

[JorgeB]

Disk4 problems appear to be caused by the SASLP, is a somewhat common issue with unRAID v6, bigger problem is that your disk3 is failing:

 

Device Model:     WDC WD20EARS-00MVWB0
Serial Number:    WD-WMAZA0310325
197 Current_Pending_Sector  0x0032   200   199   000    Old_age   Always       -       171
198 Offline_Uncorrectable   0x0030   200   200   000    Old_age   Offline      -       48

 

I'm guessing you don't have notifications enable and didn't notice all the errors during disk4 rebuild:

 

May 21 16:57:58 CASCADE kernel: md: disk3 read error, sector=1850849464
May 21 16:57:58 CASCADE kernel: md: recovery thread: multiple disk errors, sector=1850849464
May 21 16:57:58 CASCADE kernel: md: disk3 read error, sector=1850849472
May 21 16:57:58 CASCADE kernel: md: recovery thread: multiple disk errors, sector=1850849472
May 21 16:57:58 CASCADE kernel: md: disk3 read error, sector=1850849480
May 21 16:57:58 CASCADE kernel: md: recovery thread: multiple disk errors, sector=1850849480
May 21 16:57:58 CASCADE kernel: md: disk3 read error, sector=1850849488
May 21 16:57:58 CASCADE kernel: md: recovery thread: multiple disk errors, sector=1850849488
May 21 16:57:58 CASCADE kernel: md: disk3 read error, sector=1850849496
May 21 16:57:58 CASCADE kernel: md: recovery thread: multiple disk errors, sector=1850849496
May 21 16:57:58 CASCADE kernel: md: disk3 read error, sector=1850849504

Due to these errors the rebuilt disk will have corrupt files.

Edited May 27, 2017 by johnnie.black

[calypsocowboy]

Okay, at this point, I've copied off most of what I think my (non-replaceable) files off the array. I haven't checked all the files to see if they are okay. At this point on the array is mostly music and movies about 8.8TB worth that I can replace but would prefer not to. I've shut down the array to prevent further writes to it. 

 

My current array is 4TB parity, 4TB, 3x2TB data drives. As it sits right now, I'm using 8.8TB, so I don't have room to pull the failing 2TB drive out now. In a week, I'll have a new motherboard and/or a new controller card and a new 8TB drive I was planning on for parity. What's the best way to bring things back up as it sounds like at this point, it sounds like trusting parity to rebuild the drive wouldn't be a good idea. 

 

My initial thought was some what around clearing my 4TB parity drive, bringing up all 4 other discs, copying the data from the failing drive over to a good one and removing it from the array. All of this would I'm assuming be done with the array unprotected. Then once the failing 2TB drive is out and the 4TB drive is in, Put the 8TB drive and rebuild parity. Lastly, hope that I didn't lose too much data. 

[JorgeB]

This is the type of situation that having checksums would be very helpful, In my view you have 2 options, none is perfect:

 

1) replace disk3 with a new one and rebuild, some files will be corrupt due to corruptions on disk4, then copy all readable files from old disk3 and replace the rebuilt files, all copied files should be OK, all those that you aren't able to copy may or not be corrupt, most should be fine though.

 

2) do a new config without disk3 and copy all readable files from it  (some corrupt files will remain on disk4).

 

 

[calypsocowboy]

So i think I'm going to go with option 2 and do the new config.  I'll then mount disk3 up to another machine and see what data I can get off it and copy it back to the server.

 

I believe these are correct procedures https://wiki.lime-technology.com/UnRAID_6_2/Storage_Management#Reset_the_array_configuration 

 

One additional question, I'm assuming that resetting the array rebuilds the parity drive. So I'm guessing it makes sense to wait to do this until I get my new larger parity drive. Is that correct?

 

Once that all completes, then I'll preclear my old parity drive and add it back in. 

 

BTW, thanks for the help.  I definitely need to get notifications setup on the server. 

[JorgeB]

7 hours ago, calypsocowboy said:

 

I believe these are correct procedures https://wiki.lime-technology.com/UnRAID_6_2/Storage_Management#Reset_the_array_configuration 

 

Yes

 

7 hours ago, calypsocowboy said:

One additional question, I'm assuming that resetting the array rebuilds the parity drive. So I'm guessing it makes sense to wait to do this until I get my new larger parity drive. Is that correct?

 

Correct

 

 

[calypsocowboy]

Thanks!