Having a lot of trouble with a server that was running great for a while. Attempted to update a docker container and everything went down hill. I grabbed some diagnostics and attempted a restart.

Issue 1: Web UI being laggy. Can log in on restart, but attempting to access VM or Docker tabs causes web GUI to freeze. Thought it might be errors being thrown by one of the GPUs based off the diagnostics. It has been removed. Also saw issues with NVIDIA driver plugin, loaded up safemode and removed that, pulled new diagnostics at that time.

Issue 2: Docker is now giving "Docker Service Failed to start". Attempted to remove and rebuild dockerimg, but Web UI froze again.

Attempted to pull a third set of diagnostics via SSH but it's also stuck at "Starting diagnostics collection..."

Any help would be greatly appreciated.

lovenest-diagnostics-20260119-1900.zip lovenest-safemode-diagnostics-20260119-2014.zip

Check filesystem on cache.

Why do you have docker.img set to 200G?

10 hours ago, trurl said:

Check filesystem on cache.

The filesystem check revealed my docker.img and one of my vm img files were both corrupt. I've removed them but docker still fails to start.

I'm also still getting severe lag after I start my VM's even with the one that was causing problems disabled.

Can I ask what it was in the diagnostics that pointed you to that? I'd like to be able to diagnose it in the future.

10 hours ago, trurl said:

Why do you have docker.img set to 200G?

If I remember correctly I couldn't get one of the containers to access my shares, so I added some space to the docker.img file.

Edited January 20Jan 20 by kal-el681
updated info

1 hour ago, kal-el681 said:

If I remember correctly I couldn't get one of the containers to access my shares, so I added some space to the docker.img file.

No conceivable reason for larger .img to make any difference at all with that. Almost certainly something to do with the volume mappings.

1 hour ago, kal-el681 said:

Can I ask what it was in the diagnostics that pointed you to that?

syslog starting here:

Jan 19 19:58:52 Lovenest emhttpd: mounting /mnt/cache

1 hour ago, kal-el681 said:

The filesystem check revealed my docker.img and one of my vm img files were both corrupt. I've removed them but docker still fails to start.

Post new diagnostics

I have noticed that now when I try to access the VMs tab, even after disabling the problem vm, everything stalls. I was able to grab new diagnostics this morning. The result of zpool scrub is:

scrub results

pool: cache

state: ONLINE

status: One or more devices has experienced an error resulting in data

corruption. Applications may be affected.

action: Restore the file in question if possible. Otherwise restore the

entire pool from backup.

see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A

scan: scrub repaired 0B in 00:20:54 with 2 errors on Tue Jan 20 00:41:03 2026

config:

NAME STATE READ WRITE CKSUM

cache ONLINE 0 0 0

nvme0n1p1 ONLINE 0 0 4

errors: Permanent errors have been detected in the following files:

/mnt/cache/system/docker/docker.img

/mnt/cache/domains/Windows 10 - VMS/vdisk1.img

lovenest-diagnostics-20260120-1052.zip

4 minutes ago, kal-el681 said:

errors: Permanent errors have been detected in the following files:

/mnt/cache/system/docker/docker.img

/mnt/cache/domains/Windows 10 - VMS/vdisk1.img

Did you delete and recreate these?

1 minute ago, trurl said:

Did you delete and recreate these?

I suggest recreating docker.img as 50G. Really that is more than should be necessary for most.

I deleted the VM vdisk as I'm not going to use it anymore anyway, and used the delete docker.img tool in the docker settings, I'll do the docker.img file again and set it to 50G once I get the UI back from the 500 error I have right now.

Still seeing corruption on cache after that scrub. See cache mount entries starting here:

Jan 20 10:02:59 Lovenest emhttpd: mounting /mnt/cache

Have you done memtest recently?

I did have to replace some RAM a few months ago and had run memtest on all the individial sticks in the system seperately. Everything was fine after the replacement. I'll run a couple cycles and see what it says.

Welp, there's the problem.. Two of these are basically new sticks. I'm wondering if there's an issue with my MB causing it.

Have you taken care of these Ryzen recommendations?

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

If you are overclocking, fix that and try memtest again.

But (and I've been saying this a lot recently)

On 1/18/2026 at 10:02 PM, trurl said:

You must never attempt to run any computer unless memory is working perfectly. Everything goes through RAM. The OS and other executable code, your DATA. EVERYTHING. The CPU can't do anything with anything until it is loaded into RAM.

I did see that and adjusted the "Power Supply Idle Control". I'll remove the xmp profile and run it again.

I reset the profile to default and am still getting the same thing.

Test each stick individually in each slot.

Alright, so here's where I stand, I ran memtest on all the sticks, found a dead one and in the process of RMA. Installed two of the good sticks and started up. It booted fine as before, but still hangs/kills the web UI when I try to access the VM's tab or VM settings. If I don't navigate away from the dashboard, I can still see all the information (RAM/CPU usage, network graph) updating as it should. It's even showing the parity % working at the bottom. If I try to navigate away from the dashboard the pages won't load, also tried to SSH, and I can access it, but running any commands hang.

59 minutes ago, kal-el681 said:

Installed two of the good sticks and started up

Does that configuration pass memtest?

It does, yes.

Edited January 20Jan 20 by kal-el681
Image

Perhaps something got corrupted when you were running with bad RAM.

Do you have a flash backup?

I do, could you link me the steps to restore it please?

The config folder from your flash backup is all you need to get your configuration going again on a new install.

Oh, you're saying to wipe the whole thing, or just the USB drive?