Docker & Share corrupted after Parity-Check(?)

[Marcez]

Hello Helpers!, 

 

I have a problem with my unraid server after a Parity-Check, and I can't figure out what happened and what the solution is.

Last 31st my scheduled parity check was performed. During this parity check all my docker containers stopped. Which normally doesn't happen. Now it seems that my docker image is "gone". In the docker settings I get the message that the path to the docker image is incorrect.

Now 3 weeks ago I transferred the system to a new motherboard and an AMD processor. I also removed 1 SSD with SMART errors from my Cache pool (which consisted of 3 SSDs now 2).

But the path that would no longer exist does not refer to the Cache pool. So I don't think it can be done here.

Also, after adjusting the system, it worked well for several weeks until the 31st.

 

I'm missing some shares under "Domains" and my VMs don't work anymore.

Can you tell me what went wrong and what the solution is?

This is the error i get when i open the Docker tap:



This is the Error in the Docker settings:




 

the path to which the Doncker refers:


VM:


Array: 

tower-syslog-20230403-1723.zip tower-diagnostics-20230403-1924.zip

Parity Check settings:

 

Edited April 3, 2023 by Marcez
Added VM/Shares & Parity Check settings

[itimpi]

It looks as though a lot of the drives dropped offline as there is no SMART information for them in the diagnostics.    It might be worth power-cycling the server to see if that brings them back.   Also carefully check any power cabling, and anything else common to multiple drives.   Post new diagnostics after that so we can see what (if anything) has changed. 

 

 

[Marcez]

Hi, 

I Did a reboot of the server and these are the results i added the log.

This the overview before the restart, I have Smart data..


 

 

tower-diagnostics-20230403-2031.zip

Edited April 3, 2023 by Marcez

[Marcez]

Morning,

Now suddenly my shares are back & and my docker.img/ VM locations work again. 

If i take a look at /mtn/disk2/ there are now different files as in the other example. 
As seen in this screenshot this is how my /mnt/disk2/ should be. 

When i went over to the new systemboard i added this one: https://www.amazon.nl/dp/B0BL3GS323?ref_=pe_28126711_487767311_302_E_DDE_dt_1
Can it be this is giving problems?

I took it from this post: