Nothing useful in your syslog, it stops on October 3rd.

Probably that the spam from mover log prevented further logging or proper diagnostics generation.  

On 10/6/2021 at 7:29 PM, ChatNoir said:

Nothing useful in your syslog, it stops on October 3rd.

Probably that the spam from mover log prevented further logging or proper diagnostics generation.  

SO what should I generate for you?

Reboot and create a new diagnostic or?

I have paused the rebuild . Can't really let it run for 40 days for 8 %

10 hours ago, Profezor said:

Reboot and create a new diagnostic

yes

13 hours ago, trurl said:

yes

I stopped the rebuild of Disk 4 at 92%. Can’t wait 80 days.

galaxy-diagnostics-20211009-1351.zip

Edited October 9, 20214 yr by Profezor

parity disk disconnected

Ok, so I checked the hardware..

I recreated the parity.

I reformatted Disk 4. I can get the lost content later.

 

I rebooted and all the disk lights are green. Happy.

 

also I was able to start Dockers. But when I try to add the containers back I get the attached error.  If I can get over this maybe I can get my dockers working again.

 

UPDATE- A reboot after the fixing the hardware, re-adding the containers, the dockors are mostly back working. All except Nextcloud, but imam working on that. 
 

Thanks for all your help and good wishes.I know I will be back soon with another sad story. ;-0

Edited October 12, 20214 yr by Profezor

Kind of unrelated to OP's problem:

I just wanted to let you guys know that this thread helped me to track down a misconfiguration in my unRAID. I've set it up with ZFS, so my array is really just another thumb drive. Over night my appdata was moved to that array and thus configs went missing because I had the shares set up to Cache:Yes instead of Cache:Preferred. Thankful I had setup up my own cronjob rsync backup for the appdata so that I was able to get earlier versions of my appdata from the ZFS snapshots.

 

Cheers!