Hello,

I am looking for help troubleshooting several issues with my Unraid server. A few of these problems started around the same time, so I am not sure if they are related or separate issues.

System Information

Model: Custom
Unraid version: 7.1.4
Motherboard: MSI PRO B760-P WIFI DDR4 (MS-7D98) Version 1.0
BIOS: American Megatrends International, LLC. Version 1.60, dated 07/13/2023
CPU: 13th Gen Intel Core i5-13500
Memory: 32 GiB DDR4
Max memory capacity: 128 GiB
HVM: Enabled
IOMMU: Enabled
Network: eth0, 1000 Mbps, full duplex, MTU 1500
Kernel: Linux 6.12.24-Unraid x86_64
OpenSSL: 3.5.0
Case: Norco RPC-4220

Background

A few weeks ago, I came home from work and found that the Docker service had stopped. My 2 TB cache drive was completely full.

From what I could tell, it looked like one of my arr containers may have upgraded/replaced many existing media files and triggered a large number of downloads. I thought I had a minimum free space setting configured in SABnzbd, so I am not completely sure if that was the root cause.

I was able to manually start the mover and free up a large amount of space on the cache drive. However, Docker still would not start afterward. I eventually recreated the Docker image and reinstalled my containers, which got Docker working again.

I would like help figuring out what happened and how to prevent it from happening again.

Current Issues

1. Docker service stopped after cache drive filled up

The Docker service stopped when the cache drive became full. After freeing space with mover, Docker still would not start. I had to recreate the Docker image and reinstall my containers.

I would like help understanding:

• What logs/settings should I check to determine why this happened?

• How can I prevent downloads or Docker/appdata from filling the cache drive again?

• Should I be checking minimum free space settings in Unraid shares, SABnzbd, and the arr containers?

2. Pi-hole Docker failed around the same time

Around the same time the Docker service failed, my Pi-hole container also stopped working.

I tried reinstalling Pi-hole several times, but it gave an error each time. I have left Pi-hole uninstalled for now.

I can try reinstalling again and capture the exact error if needed.

3. Cache drive still has about 1.1 TB used

Since the incident, the cache drive stays around 1.1 TB used, even after running mover.

I am not sure what data is still on the cache drive or whether it is supposed to remain there.

I would like help confirming:

• What is currently using space on the cache drive?

• Whether my shares are configured correctly for cache usage

• Whether appdata, domains, system, downloads, or media files are stuck on cache

I have posted the output of:
du -h -d 1 /mnt/cache | sort -h

4. Server would not shut down cleanly

The server is currently very full and I need to add another drive.

I attempted to shut the server down so I could add a drive and begin a preclear, but the shutdown process hung. From what I remember, it appeared to be trying to spin down the drives, but the cache disk seemed to still be in use and would not spin down.

The server stayed in this loop and never completed the shutdown. I eventually had to hard power it off, which I would obviously like to avoid.

I would like help figuring out:

• How to identify what is keeping the cache drive busy during shutdown

• Whether a Docker container, VM, SMB connection, mover process, or plugin could be preventing shutdown

• What logs I should check after a forced shutdown

5. Docker image sometimes fills up

I have previously received warnings that my Docker image was filling up. I have not seen the warning recently, but I never figured out what was causing it.

I would like help checking whether one of my containers is writing data inside the Docker image instead of to a mapped appdata/downloads/media path.

6. Many old unused appdata folders

I have many old appdata folders from containers I have used over the years. For example, I have three different Plex appdata folders.

I am not sure which appdata folders are currently in use.

I would like to know:

• How to confirm which appdata folder each active Docker container is using

• The safest way to remove old unused appdata folders

• Whether there is a plugin or recommended process for appdata cleanup

7. Windows 10 File Explorer access issue

I do not think I have been able to reliably access the server from Windows 10 File Explorer for several years.

I usually rely on previously saved/recent folder shortcuts to access random folders on the server.

I would like help fixing normal SMB browsing/access from Windows File Explorer.

8. Persistent logs

I found and downloaded what appear to be my persistent syslog files:

• syslog-192.168.1.49.log

• syslog-192.168.1.49.log.1

These were stored on the cache drive.

I will attach both logs along with the diagnostics zip. I am not sure if they go back far enough to capture the original Docker/cache failure from a few weeks ago, but they may still help with recent shutdown/cache activity.

9. Power button/startup issue with Norco RPC-4220 case

When I shut down the server, I often have some kind of issue getting it started again.

The front power button appears to do nothing the first few times I press it. The case is a Norco RPC-4220.

I am not sure if this is just a case power button issue, a motherboard issue, a power supply issue, or something else.

Attached Files / Available Info

I have attached or can provide:

• Diagnostics zip from Tools → Diagnostics

• Persistent syslog files:

  • syslog-192.168.1.49.log

  • syslog-192.168.1.49.log.1

• Screenshots of the Main tab showing array, parity, cache/pool devices, usage, and filesystems

• Screenshots of share settings for appdata, system, domains, downloads, and media shares

• Screenshot of Settings → Docker showing Docker image location, size, and usage

• Docker container path mappings for SABnzbd, Sonarr, Radarr, Plex, Prowlarr, and others if needed

• SABnzbd settings for temporary folder, completed folder, and minimum free space

• Output from du commands showing what is using space on /mnt/cache

• Pi-hole reinstall error, if I try reinstalling again

Main Questions

I am mainly looking for help with:

1. Determining what caused the cache drive/Docker failure

2. Preventing the cache drive or Docker image from filling again

3. Finding what is still using 1.1 TB on cache

4. Fixing shutdown hangs

5. Cleaning up old appdata folders safely

6. Restoring normal Windows SMB access

Thanks in advance for any help.

syslog-192.168.1.49.log syslog-192.168.1.49.log.1 jesse-diagnostics-20260517-1349.zip

First thing you should do is set a Minimum Free Space setting on the 'cache' pool to stop it filling up in the first place.

In terms of looking to see what is using space on the 'cache' pool you can use Unraid's built-in File Manager to examine it. From the diagnostics it looks like 'appdata' is using around 724GB and 'system' around 14GB - not the total of 1.1TB you mentioned. You normally do want those 2 shares there for performance reasons.