Okay, so I wiped the flash and tried again. It now hangs on array startup. The webui will load pages, but is not responsive to any commands.

New Diagnostics attached.

lovenest-diagnostics-20260120-2135.zip

Disable Docker and VM Manager, setup syslog server.

Boot in SAFE mode and see if you can start the array.

Did that and it looks like the array came up without issue.

lovenest-safemode-diagnostics-20260121-1811.zip

Let it run like that for a few hours. If no problems appear, try booting in normal mode but leave dockers and VMs disabled.

Will do.. It seems fine when I run it without Docker or VMs, but as soon as I turn either on that's when I run into issues.

A common way for a misconfigured container to make your system unstable is if it has a host volume mapping that isn't actual mounted storage. When this happens, the container creates a folder at that path in rootfs (RAM) where the OS keeps its files and it writes its data there instead of to a user share, etc. If you fill up rootfs, the OS has no room to work in.

When you have this problem, what do you get from command line with this?

df -h /

So.. I paused the parity check, and tried to start docker. The screenshot below is what I see once I hit apply to start docker and it just sits there forever (I left it last night and it was the same when I got back home this evening.) I can refresh the page, and it will say that docker is stopped, but the docker tab shows up in the webui and shows "docker service failed to start".

The cli shot is one before I did anything and then two while docker "was starting" and then one after I refreshed the page.

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/

What permissions should the docker and libvirt folders have? They're currently set as root.

I'm not sure it matters since the processes that use those will be root anyway

Okay, well I asked because now it's not creating the docker.img file when attempting to start docker.

It should be OK to do New Permissions on the system share. Just make sure you only run it on system share. Probably won't help but mine is owned by nobody:users

Didn't make a difference. I did find this in the syslogs though:

Jan 21 19:10:54 Lovenest nginx: 2026/01/21 19:10:54 [error] 2955#2955: *2695 upstream timed out (110: Connection timed out) while reading upstream, client: IP-REDACTED, server: , request: "POST /update.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.sock:", host: "IP-REDACTED", referrer: "http://IP-REDACTED/Settings/DockerSettings"
Jan 21 19:27:17 Lovenest ool www[46289]: /usr/local/emhttp/plugins/dynamix/scripts/emcmd 'cmdStatus=Apply'

Delete docker.img from the Settings - Docker page.

Reboot

Try again

45 minutes ago, trurl said:

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/

Reboot wouldn't work, had to unclean shutdown. This time it created a new docker.img file, but Docker still failed to start. New diagnostics attached.

lovenest-safemode-diagnostics-20260121-1957.zip

Looks like there were problems with cache

Jan 21 19:51:37 Lovenest kernel: PANIC: zfs: rt={spa=cache vdev_guid=9190427880482758334 ms_id=12 ms_allocatable}: removing nonexistent segment from range tree (offset=400003009d08000 size=3000)

https://docs.unraid.net/unraid-os/troubleshooting/common-issues/data-recovery/

No errors showing up with a scrub or SMART test.

Ended up having to wipe and format the cache drive. Thanks @trurl for all the help.