(SOLVED) Hard Drive Post-Read Verification FAIL (Part 2)

[B Train]

Greetings UnRaid community.

I am adding an HDD to my UnRaid setup and I receivd a Post-Read Verification after running a 'Pre-Clear'.

 

My plan for the new HDD is to add it to my existing setup as a second parity.

After running the PRE CLEAR steps described in a video by SpaceInvader One (linked at the bottom of this post) I get a message saying:

"Post-read verification - - - - FAILED".

 

Further information specific to my case is shown below.

 

For future reference, a similar thread was created but was not helpful to me.

The thread is located on the link below, by a user named 'Twisted'.

 

The S.M.A.R.T. report for my disk in question is attached as a .txt file

I have the following report, facilitated by the UnRaid GUI by clicking on 'Preclear Disk Log':

 

######################################################

Unraid Server Preclear of disk WD-WCC4E5X4NS26

Cycle 1 of 1, partition start on sector 64.

 

Step 1 of 5 - Pre-read verification: [9:20:32 @ 118 MB/s] SUCCESS

Step 2 of 5 - Zeroing the disk: [9:39:37 @ 115 MB/s] SUCCESS

Step 3 of 5 - Writing Unraid's Preclear signature: SUCCESS

Step 4 of 5 - Verifying Unraid's Preclear signature: SUCCESS

Step 5 of 5 - Post-Read verification: FAIL

 

Cycle elapsed time: 19:06:40 | Total elapsed time: 19:06:40 #

 

S.M.A.R.T. Status (device type: default)

 

ATTRIBUTE INITIAL STATUS

 

Reallocated_Sector_Ct 0 -

Power_On_Hours 75262 -

Temperature_Celsius 26 -

Reallocated_Event_Count 0 -

Current_Pending_Sector 0 -

Offline_Uncorrectable 0 -

UDMA_CRC_Error_Count 0 -

######################################################

 

Can someone please help me decipher or diagnose what is the error here and how to go about correcting the error?

 

The video I mentioned above is from Youtube.

Author: SpaceInvaderOne

Tile: 'How and why to PreClear your hard drives before adding to your array'

 

Thank you for your help!

WDC_WD40EFRX-68WT0N0_WD-WCC4E5X4NS26-20231231-1406.txt

[ChatNoir]

1 hour ago, B Train said:

Can someone please help me decipher or diagnose what is the error here and how to go about correcting the error?

 

Well, that does not look so good for the drive.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    3
197 Current_Pending_Sector  -O--CK   200   200   000    -    1
200 Multi_Zone_Error_Rate   ---R--   200   200   000    -    2

Those attribute values are not great.

 

But that is quite bad too (even it the test seems super old).

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       80%      9747         146290080

 

Try to run an extended SMART test and see if those get better somehow.

 

But in your place, I'd replace. The drive seems quite old anyway at 75k+ hours (8.5 years).

[B Train]

Thank you very much for your response.

I did run an extended SMART test, which I believe is attached to my original post.

Hoping I provided the right thing, if not, I will check and provide an updated SMART test

[ChatNoir]

6 hours ago, B Train said:

I did run an extended SMART test, which I believe is attached to my original post.

Hoping I provided the right thing, if not, I will check and provide an updated SMART test

OK, my bad. It seems that the lifetime hours in the SMART tests are not coded the same way as the lifetime in the attributes. The first one reached its max value, started back from 0 and incremented from that at some point.

I missed that.

 

The result of the SMART test is Completed: read failure

You should replace the drive.

[B Train]

Thank you very much ChatNoir.

Do you recommend running this test several times?

Is the result of 'read failure' always terminal for a hard drive?

Could the 'read failure' be due to any other factor, such as a loose cable?

 

Thank you once again for your help!

[ChatNoir]

2 hours ago, B Train said:

Do you recommend running this test several times?

Not really, I initially misunderstood the situation. One complete Extended SMART test should be enough to have a clear picture of the drive status.

 

2 hours ago, B Train said:

Could the 'read failure' be due to any other factor, such as a loose cable?

I don't think so. It would manifest as UDMA_CRC_Error or perhaps as read error.

 

2 hours ago, B Train said:

Is the result of 'read failure' always terminal for a hard drive?

In my (limited) experience, it is. If a drive cannot be reliably be read, then you cannot trust it with your data.

Especially in the context of an Unraid Array where the Parity protection is not only handled by the Parity drive(s) but also by every Data drives for parity calculations and rebuild.

[B Train]

ChatNoir thank you so much for that information. It is very very helpful to me.

I guess it is time to throw that HDD away!