Parity read error, rebuilt parity, rebooted, error again

[dboris]

I had read errors on parity, probably because I had to shut down the system as it was frozen.
Did a parity rebuilt, no errors reported, rebooted, error came up again.

I'm including the diagnostic.

Could it be a bad SATA cable ? If it was the case I would expect parity rebuild to fail.
Just before this hapenning, as I said, system was frozing when I was trying to shut down my W10 VM.

I recently reinstalled unraid totally, as I couldn't start any VM.

 

I originally didn't took time to do the preclear of the 4 brand new seagate barracuda.

I REGRETED.
2 of the 4 drives had errors after a few days. I got them replaced.

I got to reconstruct parity and replace drive one by one MULTIPLE TIMES.
So every have already seen tons of data without giving any error on the SMART.

Every drive got precleared with success.

 

You may tell yourself it's a whole bunch of problems.
Sure it is, I play life in hard mode.

 

server-diagnostics-20200205-0924.zip

Edited February 5, 2020 by dboris

[JorgeB]

Diags are after rebooting so we can't see what happened, but the disk looks fine, replace/swap cables and re-sync parity, if it happens again grab diags before rebooting.

[dboris]

Thanks ! Acknowledged. Will keep you updated in the coming days. Launching parity repair tonight.

[dboris]

When I do a reboot (either manually from windows's UI or because there's an update), the VM crashes.

With the reset bug I have to reset the server.

When the VM crashes, and I observed this before reinstalling Unraid, it makes the parity rebuild fail.
It happening this morning, the Unraid's UI was kind of unresponsive until I stopped the array.

I saved the diag on an external SSD but it disapeared -_-.

 

Is this normal that the parity sync fails if the VM crashes ?
 

[JorgeB]

6 minutes ago, dboris said:

Is this normal that the parity sync fails if the VM crashes ?

No.

[dboris]

Oh hello
I got news.
So I had repaired the parity drive, and I was messing around with W10 + Ubuntu VM.
I stopped them both and wanted to edit their respective XML's.
But UI was frozen.
I got to hard reset the server.
Now DISK1 requires rebuild.

It drives me nuts because everytime the server crashes I have to spend hours with the server running while building.
It slows down my storage so I can't be really using it when rebuilding.
I saved the diagnostic.

At the moment of shooting the video Unraid's UI  was still frozen but W10 worked ok.
From the W10 VM I managaed to restart the Server "properly".
Usually when I have a problem with the VM, the server's UI crashes, then I have to hard reset, and rebuild parity...
 

 

server-diagnostics-20200208-2029.zip

Edited February 9, 2020 by dboris

[JorgeB]

You need to first find out what's making the server crash, could be related to hardware pass trough, try disabling them all then enabling one at a time, also make sure no CPU and/or RAM overclock.

[dboris]

So I did the rebuilt.
I tried to "reboot" Windows, on purpose, knowing it would make unraid crash.
I waited all night and server didn't stopped.
I had to hard reset.
I checked that nothing was overclocked.
If I want to "try to find" what makes W10 crashes the VM, I will have to hard reset it several times and risking to have to rebuild parity again hum 🥵

I'm pretty sure it's linked to the RX 5700 XT not reseting on W10 reboot.

Edited February 11, 2020 by dboris

[JorgeB]

2 minutes ago, dboris said:

I'm pretty sure it's linked to the RX 5700 XT not reseting on W10 reboot.

Possibly, there's a bug report about a similar issue, maybe post your experience there.

[dboris]

Wow thanks god, it's related, I'm passing through a similar device !

Edited February 11, 2020 by dboris