Pre-clear error on new HDD

[Max3dmoon]

Hi,

 

Was pre-clearing a new HDD and got that:

 

 

What are my options please ?

Or should I just send back the HDD ?

 

[JorgeB]

Run memtest, disk could be good but bad RAM can make the post read fail.

[Max3dmoon]

5 minutes ago, JorgeB said:

Run memtest, disk could be good but bad RAM can make the post read fail.

Sorry I should have mentioned it, I did an extensive memtest and it came back with zero errors

[JorgeB]

No disk errors are logged, but post the complete diagnostics, maybe something will jump out.

[Max3dmoon]

Here it is, thanks JorgeB.

Really appreciate you putting the time 🙏

tower-diagnostics-20220923-1901.zip

[JorgeB]

Still nothing that suggests a disk problem, my best guess is still RAM related, or a plugin issue, you can run an extended SMART test on the disk confirm it's good.

[Max3dmoon]

13 hours ago, JorgeB said:

Still nothing that suggests a disk problem, my best guess is still RAM related, or a plugin issue, you can run an extended SMART test on the disk confirm it's good.

Interesting, thanks !

 

There has been a new development, a few hours after posting my last message I came back to find my unraid server completely unresponsive.

Had to do a hard reboot. Grabbed the diagnostic after the hard reboot, do you see anything that could explain what is going on ?

 

The server is currently doing a parity check and in // I also started a extended SMART test (still ongoing) on the unmounted drive that failed the pre-clear.

Once the parity and  the extended SMART is complete, I'll probably reboot and do another memtest.

 

[ I had an unraid build for years with not a single issue (with containers, VM etc.) and this new build is giving me so much headaches ! 🥴 ]

 

tower-diagnostics-20220923-2029.zip

[JorgeB]

Syslog starts over after every reboot, so everything normal so far, if it keeps crashing you can enable the syslog server to see if it catches something, though likely it won't if the problem is hardware related.

[Max3dmoon]

On 9/24/2022 at 3:42 PM, JorgeB said:

Syslog starts over after every reboot, so everything normal so far, if it keeps crashing you can enable the syslog server to see if it catches something, though likely it won't if the problem is hardware related.

Ok so I did that and ended up crashing a few minutes ago....the log is gibberish to me but I'm surprised to see tons of errors hours before the crash (Sept 27 AM but I crashed in PM)

 

Any idea what could be the culprit ?

syslog-192.168.1.175.log

[JorgeB]

Some issues but nothing obvious that explains the crashing, could be this issue: