(SOLVED) So.....does this mean I need to return this hard drive... PreClear Failure

[Hobbes_Is_Real]

I will buy renewed hard drives and I have had pretty good luck, with only few easy to confirm out of the box opportunities that were swapped out easily with the seller.  They are upfront that these are enterprise level drives that have cycled out of use from a business or datacenter.  They scrub them, test them, and then they sell the used drives with their own 5 year warranty from the date of sale to me, no matter when the actual manufacturer warranty expires.  So I will get 10TB spinners for $60 to $79 this way.  Then I always make sure my dual parity drives are "new" drives, and I also buy new drives on Prime Day / Black Friday / Cyber Monday sales too.  Then I spread out the used drives as efficiently as possible so that if I make an XFS pool of drives, I only put 1 used drive and try to make sure majority are new ones along with RAIDs for extra protection, etc...  

 

This time the drive appeared to work with a brief overlook, could format / partition it, create folders, delete files, in both Windows and Unraid, etc...  But then as always I run 3 cycles of PreClear on these to make sure all is good.  But this one has failed every attempt.  Attached is the log of the last PreClear failed test. Can you offer any suggestions if it is something I can fix or do we simply need to replace it with another one?  I have already reached out to the seller with this issue and logs, but just wanted to see if anyone has experience with these similar errors.

 

Here are some examples of the failures in the attached last PreClear log..,..

 

Jun 23 07:12:46 preclear_disk_20230130_817: Zeroing: progress - 50% zeroed @ 209 MB/s
Jun 23 07:29:24 preclear_disk_20230130_817: Pause (smartctl run time: 26s)
Jun 23 07:29:24 preclear_disk_20230130_817: Paused
Jun 23 07:29:45 preclear_disk_20230130_817: killing smartctl with pid 10681 - probably stalled ...
Jun 23 07:30:06 preclear_disk_20230130_817: killing smartctl with pid 10681 - probably stalled ...
Jun 23 07:30:27 preclear_disk_20230130_817: Resumed
Jun 23 10:50:03 preclear_disk_20230130_817: Zeroing: progress - 75% zeroed @ 183 MB/s
Jun 23 15:28:52 preclear_disk_20230130_817: killing smartctl with pid 11261 - probably stalled ...
Jun 23 15:28:52 preclear_disk_20230130_817: Pause (smartctl run time: 34s)
Jun 23 15:28:52 preclear_disk_20230130_817: Paused
Jun 23 15:29:13 preclear_disk_20230130_817: killing smartctl with pid 11261 - probably stalled ...
Jun 23 15:29:35 preclear_disk_20230130_817: killing smartctl with pid 11261 - probably stalled ...
Jun 23 15:29:56 preclear_disk_20230130_817: killing smartctl with pid 11261 - probably stalled ...
Jun 23 15:30:17 preclear_disk_20230130_817: killing smartctl with pid 11261 - probably stalled ...
Jun 23 15:30:38 preclear_disk_20230130_817: killing smartctl with pid 11261 - probably stalled ...
Jun 23 15:30:59 preclear_disk_20230130_817: killing smartctl with pid 11261 - probably stalled ...
Jun 23 15:31:21 preclear_disk_20230130_817: killing smartctl with pid 11261 - probably stalled ...
Jun 23 15:31:42 preclear_disk_20230130_817: Resumed



Jun 23 15:31:46 preclear_disk_20230130_817: Post-Read: post-read verification started 1 of 5 retries...
Jun 23 15:31:46 preclear_disk_20230130_817: Post-Read: verifying the beginning of the disk.
Jun 23 15:31:47 preclear_disk_20230130_817: Post-Read: verifying the rest of the disk.
Jun 23 16:02:32 preclear_disk_20230130_817: Post-Read: cmp command failed - disk not zeroed
Jun 23 16:02:32 preclear_disk_20230130_817: Post-Read: elapsed time - 0:30:43
Jun 23 16:02:32 preclear_disk_20230130_817: Post-Read: dd command failed, exit code [141].



Jun 23 16:02:32 preclear_disk_20230130_817: Post-Read: post-read verification failed!
Jun 23 16:02:33 preclear_disk_20230130_817: ssmtp: Authorization failed (534 5.7.9 https://support.google.com/mail/?p=InvalidSecondFactor i9-20020aa78b49000000b00666e883757fsm50049pfd.123 - gsmtp)
Jun 23 16:02:33 preclear_disk_20230130_817: error encountered, exiting ...

 

preclear_disk_20230130_817.txt

Edited June 26, 2023 by Hobbes_Is_Real
Spelling / Grammar

[JorgeB]

Post the SMART report.

[Hobbes_Is_Real]

NM....the company is sending a replacement drive.  They are real easy to work with.

[JonathanM]

On 6/24/2023 at 2:50 AM, Hobbes_Is_Real said:

I always make sure my dual parity drives are "new" drives,

Arguably the parity drives are the LEAST valuable, as when they fail you have no data lost, and the chances of losing data then rests on the data drives.

 

Here is how to best visualize this. 2 parity drives allows for 2 simultaneous drive failures, the 3rd failure will cause the total data loss of all failed drives. So, no data loss until the 3rd failure. If the 2 parity drives fail, and then a data drive dies, you ONLY lose that single data drive's content. If 1 parity and 2 data drives die, you lose both data drives worth. If, and here is the takeaway, both your parity drives are fine, but you lose 3 data drives, ALL the data on ALL three drives is gone, and the 2 parity drives can do nothing to recover any of that data.

 

So, best case scenario, in a 3 drive failure, is for BOTH of the parity drives to die.

 

If you have less faith in a particular drive because it's not "new", then the best place for it is in a parity slot where it can do the least harm if it fails.

 

Now, the parity drives do get writes for every bit of data sent to any drive in the parity array, so I'm not saying use junk drives for parity, just statistically speaking you want the parity drive(s) to fail, not the data drives.

[Lolight]

8 hours ago, JonathanM said:

...so I'm not saying use junk drives for parity...

And certainly not of the SMR type.