Hi Everyone,

 

I don't think I've ever gotten this error and reading a few posts from others on the same error seems to indicate I need your expert help in diagnosing my diagnostics.

 

I noticed people run Smart tests on the disks and according to what I saw in the Unraid GUI, I did not run a test or this disk, but there is a test log in the SMART folder of the diagnostics zip. 

 

• I'm running Unraid 6.8.3 and this disk is maybe half a year old..
• I'm currently trying to run an extended smart test. It's been stuck at 10% for at least 30 mins.
• I have a spare drive I can plop in if needed

 

I'm trying to learn as much as I can about unraid, but I'm not sure what my next steps should be.. whether i should rebuild this drive, replace it, or something else

 

Thank you kind souls for any help.

 

This is the error I'm seeing:

Unraid Disk 5 error: 10-07-2020 04:55

Alert [TOWER] - Disk 5 in error state (disk dsbl)
WDC_WD80EMAZ-00WJTA0_2SGD8S3J (sdf)

 

Edit: I added the extended smart test. After completion, the status said "Completed without error." Can anyone tell me what my next steps should be? Thanks!

 

tower-diagnostics-20200710-1856.zip

tower-smart-20200711-0838.zip

Edited July 11, 20205 yr by roobix
Added Extended Smart Test

1 hour ago, roobix said:

I'm currently trying to run an extended smart test. It's been stuck at 10% for at least 30 mins.

It should be normal, for a 8TB disk, need 16hrs to complete.

 

According current attach SMART record, Error just be CRC ( Interface relate ), anyway waiting for complete first.

 

0x06  0x018  4              20  ---  Number of Interface CRC Errors

ok thank you. I will attach once it's available

I just attached the Smart Report to the original post. 

 

Any suggestions on what my next steps should be? Thank you for any help!

Edited July 11, 20205 yr by roobix

The Smart Report indicated there were no errors so based on other folk's threads/suggestions, I decided to try and rebuild the drive back into my array by doing this:

 

Stop Array > Unassign Disk > Restart Array > Stop Array > Reassign Disk

 

About 2 mins into the parity check, i get a read error and the disk is disabled again. I replaced the disk with a brand new drive and still got the parity check error.

 

At this point, I'm thinking it's the bay or cable so I moved the drive into a different slot and it's currently allowing me to rebuild. The bay with the issue is using an IBM LSI SAS9220-8i M1015 46M0861 SAS/SATA PCI-e RAID Controller. The bay I'm currently testing with is also using that controller so I'm really hoping it's just a cable issue.

 

I just placed an order for a new cable via amazon in case the one I got off ebay was just really poorly made.

 

If I still continue to have the issue, I may look at the controller or PSU since someone in another thread mentioned it could be a PSU issue and I'm using an old 500 watt one right now..

 

If anyone thinks there is a better path or that I'm on the wrong track, please let me know and thanks!

 

 

Edited July 12, 20205 yr by roobix

2 hours ago, roobix said:

The Smart Report indicated there were no errors so based on other folk's threads/suggestions, I decided to try and rebuild the drive back into my array by doing this:

 

Stop Array > Unassign Disk > Restart Array > Stop Array > Reassign Disk

 

About 2 mins into the parity check, i get a read error and the disk is disabled again. I replaced the disk with a brand drew drive and still got the parity check error.

 

At this point, I'm thinking it's the bay or cable so I moved the drive into a different slot and it's currently allowing me to rebuild. The bay with the issue is using an IBM LSI SAS9220-8i M1015 46M0861 SAS/SATA PCI-e RAID Controller. The bay I'm currently testing with is also using that controller so I'm really hoping it's just a cable issue.

 

I just placed an order for a new cable via amazon in case the one I got off ebay was just really poorly made.

 

If I still continue to have the issue, I may look at the controller or PSU since someone in another thread mentioned it could be a PSU issue and I'm using an old 500 watt one right now..

 

If anyone thinks there is a better path or that I'm on the wrong track, please let me know and thanks!

 

 

Good work, at least you rule out not disk problem. Cable are 8087 to SATA ? Disk bay are some kind 3-to4 or 3-to5 enclosure ?

Thanks for checking in!

 

I'm using a Rosewill 4U RSV-L4412 as my enclosure and, yes, a Mini SAS to 4-SATA SFF-8087 Multi-Lane Forward Breakout Cable.

 

The one I ordered off Amazon seems to have a decent number of positive reviews (hoping they're not shill reviews lol). It might just be the same exact cable between eBay and Amazon, but I wasn't really sure where to find a better one.

25 minutes ago, roobix said:

I wasn't really sure where to find a better one.

Yes, hard to found quality one even you willing to pay more, most are China made and haven't qualify. Just well test it before put to production.

 

For your case, I think it may be the backplane ( disk slot ) issue, guess only.

Swap things should not hard to troubleshoot the fault.

Edited July 12, 20205 yr by Benson

Just wanted to give an update that I replaced the cable last night, reused the same bay and drive that was giving me issues and the drive was successfully rebuilt into my array without any errors. 

 

Thanks!