So, I've been getting an alert from my Unraid for the last day and a half about the Parity drive showing an error, and now the parity drive was disabled, I stopped the array, but in reading the diagnostic files I can't figure out why unraid disabled the disk. I'll post the SMART results, not sure what else to look at.

ST8000VN004-2M2101_WKD03SFK-20210919-2306 parity (sdh) - DISK_DSBL.txt

Please share your diagnostics.

9 hours ago, Varean said:

reading the diagnostic files I can't figure out

We probably can if we had the diagnostics. Almost certainly a connection problem. After we figure out the cause you will have to rebuild the disabled disk.

4 hours ago, trurl said:

We probably can if we had the diagnostics. Almost certainly a connection problem. After we figure out the cause you will have to rebuild the disabled disk.

I'm sorry, Diagnostics is general, I was under the impression it was the SMART results of the drive, I think you are looking for the attached below?

syslog.txt

1 minute ago, Varean said:

I'm sorry, Diagnostics is general, I was under the impression it was the SMART results of the drive, I think you are looking for the attached below?

syslog.txt 762.37 kB · 0 downloads

Actually is not general in an UnRaid context    It is specifically the system’s diagnostics zip file obtained via Tools->Diagnostics that contains a lot more files than the syslog which can help with diagnosing problems.

27 minutes ago, itimpi said:

Actually is not general in an UnRaid context    It is specifically the system’s diagnostics zip file obtained via Tools->Diagnostics that contains a lot more files than the syslog which can help with diagnosing problems.

Sorry, I haven't had a point where I needed to upload files, and when I tried to upload the ZIP folder last night it came up with an error, but not when I uploaded a single file. So I just made some bad assumptions.

Tower-diagnostics-20210919-2306.zip

59 minutes ago, Varean said:

I think you are looking for the attached below?

Every time we said Diagnostics the forum turned that into a link to instructions for getting them. Diagnostics contains syslog, SMART for all attached disks, and many other useful things about your configuration and hardware all in one single zip file.

Not sure if that is a disk problem, or controller or connection. Which controller is that disk using?

 

Disable spindown on parity and run an extended SMART test.

48 minutes ago, trurl said:

Not sure if that is a disk problem, or controller or connection. Which controller is that disk using?

 

Disable spindown on parity and run an extended SMART test.

Disabled Spin-down, and i'm running the extended test now.

 

It is using one of the mini SAS 8087 connectors, running on the LSI 2308 that I believe is built into the board.

I have them on SAS to SATA breakout cables

17 hours ago, trurl said:

Not sure if that is a disk problem, or controller or connection. Which controller is that disk using?

 

Disable spindown on parity and run an extended SMART test.

I ran the extended SMART test, and it shows as passed 

ST8000VN004-2M2101_WKD03SFK-20210921-0735.txt

See here:

 

17 minutes ago, JorgeB said:

See here:

 

 

Thanks for sharing, when I get a chance i'll have to try this to see if it resolves the issue for me.

 

Currently running 6.9.2, but as the poster says it might need a firmware update to the drive to fix the issue. 

Do you know if I need to have my Array up in order to perform the steps? Or can I leave it off (I stopped the array as a precaution to avoid further issues)

Since parity is disable you can do it with the array started, then you'll need to re-sync parity.

So, I haven't been able to test the previous suggestion, but so far the MAIN section of Unraid shows 221 errors on the Parity drive, previously before my SMART test it was showing 100.