Cypher01

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

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...

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

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

here you go unraid-diagnostics-20241202-1459.zip

@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

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...

I have backups of the flash drive and appdata, I fear it won't help... unraid-diagnostics-20241201-1636.zip

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?

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

here's my diagnostics file unraid-diagnostics-20241201-1042.zip

Same here, 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.

@Goulasch I had also a lots of trouble install nextcloud until I deactivated internal ssl on unraid. I assume it prevented the container talking to the db. I'm not an expert on this though. Might have also been a coindicence but right after disabling ssl it worked.

@JorgeBThe error just accured again copied log.txt

I see. If it will happen again, I know what to do. Thanks for your advice