Jump to content

Newly added disk is claiming to be faulty


joelrfernandes

Recommended Posts

Posted

Hello all,

 

So, I had this old parity disk that I recently replaced with a larger one, which left me with this old 4TB drive. I pre-cleared it and added it to the array yesterday. Today it looks like unRaid claims the drive to be faulty, although S.M.A.R.T. reports say otherwise. What am I missing?

 

The "faulty" drive is disk9

 

Diagnostics logs attached.

monster-diagnostics-20180301-0940.zip

Posted

It's not faulty, it's disabled.

 

unRAID disables a disk when a write to it fails. The failed write means the disk contents are invalid, but since parity was updated the array is able to emulate the valid contents.

 

So, the physical disk has invalid contents and is out-of-sync with parity. Check connections. You will have to rebuild the disk.

 

https://lime-technology.com/wiki/Troubleshooting#What_do_I_do_if_I_get_a_red_X_next_to_a_hard_disk.3F

Posted

Most likely disabled because of a very bad SATA cable:

 

ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
199 UDMA_CRC_Error_Count    -OSRCK   200   164   000    -    7313

Replace the cable and rebuild.

 

Also upgrade to v6.4.1 so you're warned about similar issues in the future.

Posted

Alright, so I now replaced the cable and unraid is rebuilding the drive.

 

I still have that UDMA_CRC_Error_Count of 7313 on the S.M.A.R.T. report, and now unRaid does mention it is a faulty drive:

5a9830af11ca7_CloudAppAnnotation2018-03-01at11_55_58AM.png.thumb.png.7bb330c08aefc30da520ecb1ddfa797d.png

 

Should I just acknowledge the error?

Posted
1 minute ago, joelrfernandes said:

quick question: if I acknowledge the current error, if that value increases in the future, will I get another alert or will it be silenced?

yes

Archived

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

×
×
  • Create New...