I restarted the server after replacing the parity disk and added another ssd to the cache pool and now docker fails to start. my file is also 21.5gb. Changing the docker image size limit to 30gb didn't make a difference.

 

unraid-diagnostics-20241201-1042 10.43.44.zip

Dec  1 01:19:54 Unraid kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2508: errno=-5 IO failure (Error while writing out transaction)
Dec  1 01:19:54 Unraid kernel: BTRFS info (device loop2: state E): forced readonly

 

Docker image is corrupt, delete and recreate:

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Then:
https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

thanks this worked. everything is running again. Only my win 11 vm is broken
 

internal error: Could not create directory /var/lib/libvirt/swtpm/42c34252-c379-9108-f2b0-ce435557f5ce/tpm2 as 0:59

is this related to the above topic or should I open a new thread?

That should be unrelated, post new diags, libvirt.img may also be damaged, do you have a backup?

I have backups of the flash drive and appdata, I fear it won't help...

 

unraid-diagnostics-20241201-1636.zip

Look like libvirt is also corrupt, that's not saved in the flash drive, but if you don't have a backup, you can try recreating the image, then create a VM with the same settings and point to the existing vdisk.

The parity checked just finished so I rebooted the server and the VM is booting now again. 
I still wonder what I did wrong to cause all the mess...

@JorgeB Docker service failed again  

Stopped the array, added another disk to the pool, started array --> failed

 

I don't get what is causing it...

unraid-diagnostics-20241202-1223.zip

There's an issue with the shares spamming the log, reboot and post new diags after array start.

here you go

unraid-diagnostics-20241202-1459.zip

Cache pool is completely full, so it cannot write to the docker image.

 

I'm still seeing share related errors, do you have anything mounting under /mnt/user manually? That mountpoint is reserved.

with manually you mean not setup in the shares tab? not that I'm aware of...
I have linke the VM to a share to access the unraid folders.

Besides that I can't see anything suspicious

@JorgeB I found something suspiscious
My cache drive is 500GB but shows 1.3TB Size...

Pool has a missing device:

                  Data    Data      Metadata  System                              
Id Path           single  RAID1     RAID1     RAID1    Unallocated Total     Slack
-- -------------- ------- --------- --------- -------- ----------- --------- -----
 1 /dev/nvme0n1p1 1.00GiB 462.73GiB   2.00GiB 32.00MiB     1.02MiB 465.76GiB     -
 2 missing              - 462.73GiB   2.00GiB 32.00MiB     1.37TiB   1.82TiB     -
-- -------------- ------- --------- --------- -------- ----------- --------- -----
   Total          1.00GiB 462.73GiB   2.00GiB 32.00MiB     1.37TiB   2.27TiB 0.00B

 

You need to correct that, but still need to free up some space first.

I was able to free up some space and now docker is running again.
But I never had a second drive as cache. I have that drive setup as a second, independent pool


Any idea how to solve that issue? I also don't see a warning about a missing cache drive like in other posts on the forums.
weird...
 

Like mentioned, 

5 hours ago, JorgeB said:

still need to free up some space first.

You can then try to manually remove the missing the device

Updating to RC1 seems to have it fixed it by itself. Nice feature!  

👍