Moved to a separate Thread: https://forums.unraid.net/topic/192895-cache-setup-help/

Where is plugin source code? I want to translate it into Chinese and update some old links.

GitHub

GitHub - unraid/fix.common.problems

Contribute to unraid/fix.common.problems development by creating an account on GitHub.

Because of how wordy it is it's never been revamped to be translation compliant within the OS. But, that'll probably happen post 7.2.0 in time for 7.3

I just stumbled upon what I believe is the same issue that has been described here before:

The Fix Common Problems Plugin keeps telling me that "Error: Out Of Memory errors detected on your server".

Because a malfunctioning container once actually caused a runaway memory issue and ultimately crashed my server, I had set up generous memory limits for each and every container.

It turns out that one of them wasn't generous enough after experimenting with npmplus over npm:

Aug 31 23:56:16 Server kernel: Memory cgroup out of memory: Killed process 3724576 (nginx) total-vm:718840kB, anon-rss:660372kB, file-rss:15968kB, shmem-rss:0kB, UID:99 pgtables:2172kB oom_score_adj:0

Aug 31 23:56:16 Server kernel: nginx invoked oom-killer: gfp_mask=0xcc0(GFP_KERNEL), order=0, oom_score_adj=0

Given that the server did not run out of memory and the container's memory limit worked like it should, I feel like this is warning is at the very least misleading.

It would be nice to have different warnings for actual server out of memory issues and simply having a container hit a predefined limit.

I have updated my Nextcloud AIO container on my Unraid 7.1.4 (screenshots attached). I did it from the container itself (for child containers) and the unraid Docker dashboard (for AIO master container).

Yet even after doing so, the CA plugin "Fix Common Problem" says the container has updates available. Again, screenshot attached.
Upon going through a lot of forums and Reddit doom scrolling, I got to know that CA FCP fetches update data from somewhere else, and Child containers, when updated via AIO Master Container, are not recognised. Hence, the warnings. It's better to leave it as is, else we can break the Official Update path of AIO updates.
I believe the only solution for this is to find a way for CA FCP to recognise 3rd Party updates. And if I am not wrong, it has been an issue for a really long time now. Can we expect a fix for this?
PS: I might not have an idea of what I am talking about as a Mechanical Engineer; these things are usually beyond me.
Thank you.

Woke up to an improper shutdown message with the docker service failing to start and "mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead." in the log. Thought it may have been due to a nearby earthquake overnight but I'm now guessing it was a coincidence, any help would be appreciated.

node804-diagnostics-20250922-1117.zip

Fix Common Problems surfaced this warning -

Event: Fix Common Problems - Unraid

Subject: Warnings have been found with your server.(Unraid)

Description: Investigate at Settings / User Utilities / Fix Common Problems

Importance: warning

* Share backups is set for both included (disk2) and excluded (disk1,disk3) disks

I've been working on my backups strategy. I have a "backups" share where my critical Unraid array files are backed up as well as several external computers. I want to copy that share to an unassigned drive for redundancy. I was having problems backing up because some of the backup streams would occur during the main rclone backup of the share. This would cause the rclone process to never finish.

So, the new strategy is to install a new drive (disk2) dedicated to the backups share. That new drive is formatted as btrf so it can be snapshotted. The unassigned drive is formatted as exFAT because I want to be able to grab that drive (it's an external drive) and run with it in a disaster, in any available machine.

Anyway, the new setup seems to be working properly to backup the share to the external drive using the snapshot capability of rclone.

However, I wonder if I set up the included / excluded drives for the share properly. My intent is that the backups share only lives on disk2 and is not spread out across any other drives (for the proper snapshot). I tried to set it up so that disk2 is the sole home of any backups share files, and no other array files live there. Is there a better way to set up the share?

Yes, I also back up the backups share to Backblaze using Duplicacy.

Edited September 23, 2025Sep 23 by WalkerZ

If you have included drives, then you don't need exclusions and vice versa.

Hello,

I have this Error on FCP.

How do i fix this?

tower-diagnostics-20251002-1141.zip

Out of memory errors could probably be upgraded with a bit more info or advice how to obtain the extra info:

grep -i "oom-killer\|killed process" /var/log/syslog

On 10/2/2025 at 3:44 AM, gevsan said:

Hello,

I have this Error on FCP.

How do i fix this?

tower-diagnostics-20251002-1141.zip

I had the same issue come up today, except it was /mnt/Media:

I used mc (Midnight Commander) from the Unraid terminal and navigated to the /mnt/Media folder. I found it to be empty, so I deleted the folder. That gave me a few seconds of a heart attack, as I couldn't immediately see my actual /Media share!! I did find it intact in /mnt/user/Media, but it made my heart stop for a second. :)

So, it might be that the/mnt/cache folder is empty (are you using /cache_doc, /cache_ssd, /cache_vm, and /cache_protected now instead of /mnt/cache?). Perhaps if that folder is empty, it's left over from a previous configuration you used and now you could delete it?? If it is just an empty folder and not being written to, then it might also be okay to leave it as is and ignore the error. I'm not really sure, just sort of guessing. For me (at least for now!), deleting the empty folder removed the error from FCP for me.

I'm getting a message telling me /var/log/ is getting full and my up time is only a few weeks. Any idea what's causing the issue?

hoth-diagnostics-20251011-1415.zip

12 minutes ago, Kliszaj said:

I'm getting a message

On 5/8/2016 at 4:01 PM, Squid said:

Any support for problems this plugin finds, should be posted in the General v6 section of these forums.

there may an issue with using ghcr.io repos? I noticed even when you use them such as ghcr.io/chrisbenincasa/tunarr it still adds https://dockerhub infront sometimes but maybe thats a template authoring mode bug, but doesn't seem to affect function except it's saying this has been blacklisted because its not on docker hub when the url is GHCR.io (GitHub repos)

perhaps this ties into a wider community app issue? not really sure

If possible would like to see DATE & TIME of detection too.

Edited October 23, 2025Oct 23 by dopeytree

Hey, FCP reported a warning today that I don't understand...

“Invalid folder cache contained within /mnt”

Can someone help me?

diagnostics-20251102-2255.zip

Regards

8 minutes ago, nzane said:

Hey, FCP reported a warning today that I don't understand...

“Invalid folder cache contained within /mnt”

Can someone help me?

diagnostics-20251102-2255.zip

Regards

It's the (1) Share a Duplicate?

Do you have a Docker Container, VM, Script, ... that have cache in his Template? And created this after his Start.

When I see its right, its your Cache Drive Cache-Pool.

Edited November 2, 2025Nov 2 by Revan335

23 minutes ago, Revan335 said:

It's the (1) Share a Duplicate?

Do you have a Docker Container, VM, Script, ... that have cache in his Template? And created this after his Start.

When I see its right, its your Cache Drive Cache-Pool.

Sorry, but what do you mean by “(1) Share”?

I don't have any duplicate shares.

I found an appdata config that pointed to “cache.” I fixed that. Unfortunately, the error is still there. What I don't understand is why the “media-*” shares are located on the cache pool. There are only a few folders/files in there.

Edited November 2, 2025Nov 2 by nzane

I mean this:

We fixed this?

Change the Docker Template?

Do you deleted the empty/wrong Appdata Folder?

And than Rescan the Fixed Common Problems to check is the Message persist.

Maybe you write to the Cache Pool and than moved the Mover this (for Example the media Folders) to the Array.

Edited November 2, 2025Nov 2 by Revan335

12 minutes ago, Revan335 said:

I mean this:

Unfortunately, I cannot identify this share.

12 minutes ago, Revan335 said:

We fixed this?

Change the Docker Template?

Do you deleted the empty/wrong Appdata Folder?

And than Rescan the Fixed Common Problems to check is the Message persist.

Maybe you write to the Cache Pool and than moved the Mover this (for Example the media Folders) to the Array.

I changed the docker template from /mnt/cache/... to /mnt/user/...

Wrong appdata folder disappears with this step.

Yes. Message persists.

I would understand that with the mover if I had a share with second storage. But in my case, the shares are either only on cache or only on array.

You have a ZFS Cache Pool.

When the media Folders not created through a Docker Container or others and not up-to-date for example today or so, than this maybe relics from the past.

Was this Folders or Shares in the past a Part for example Cache = preferred?

You can tried with the mover to moved this Folders to the Array. You can change the Share Settings temporary for that and than start the mover.

When the mover don't moved this completed to Array than its that maybe ZFS Datasets.

You can removed/destroyed this for example with the ZFS Master Plugin or the Terminal Commands for ZFS.

Checked before that this Empty! Than after that its deleted with all Content!

Or you can try to moved this Folders manually to Array for example to a Test Folder. When the Folders or Datasets on Cache are empty then it doesn't matter and can be removed/destroyed when the Mover/Manually Way not working.

Its the Problem new?

Its the Cache Pool or ZFS New?

Maybe this have more Informations:

Edited November 3, 2025Nov 3 by Revan335

Hello, the server has been up and running for four days. I first configured the cache and array and then set up the shares. I have no idea how this could have happened. I then installed all the Docker containers.

I have now set the affected shares to cache -> array and moved the folders using the mover. In the end, I changed everything back.

Now the cache is clean and only contains the 4 shares that should be there. However, the error is still there. Attached is a new report.

nzaunraid01-diagnostics-20251103-1254.zip

You have no media Folders under Appdata or on the Cache?

All Cache Shares are only on the Cache?

All Array Shares are only on the Array?

Only the Shares that have Cache > Array, have Folders on Cache/Array?

In VMs, Docker Templates, Scripts, ... is no incorrect Folder Locations are set? For example a Folder Path to Cache directly but Cache is not exist than his Name was Cache-Pool for Example.

5 hours ago, Revan335 said:

You have no media Folders under Appdata or on the Cache?

No.

5 hours ago, Revan335 said:

All Cache Shares are only on the Cache?

Yes.

5 hours ago, Revan335 said:

All Array Shares are only on the Array?

Yes.

5 hours ago, Revan335 said:

Only the Shares that have Cache > Array, have Folders on Cache/Array?

I don't have any shared folders that are tiered or moved from cache to array. Cache-only and array-only shares.

5 hours ago, Revan335 said:

In VMs, Docker Templates, Scripts, ... is no incorrect Folder Locations are set? For example a Folder Path to Cache directly but Cache is not exist than his Name was Cache-Pool for Example.

I don't have any VMs or scripts (yet). I've just gone through all the Docker templates. All paths point to /mnt/user/...

EDIT: Rebooted Unraid and error is gone... Thanks for your help.

Edited November 3, 2025Nov 3 by nzane

3 hours ago, nzane said:

No

And its not correct that the Folders are there?

3 hours ago, nzane said:

EDIT: Rebooted Unraid and error is gone... Thanks for your help.

Awesome!

I'm seeing this issue when I run the scan:

Share docker is an implied array-only share, but files / folders exist on the cache

Set Use Cache appropriately, then rerun this analysis.

I looked at the post in https://forums.unraid.net/topic/120220-fix-common-problems-more-information/ however it doesn't shed any light on how to fix. If I look at the 'docker' share, which docker auto creates when it runs, it's set to Cache and secondary is set to None, also Exclusive Shares = yes. I can see the symlink from /mnt/user/docker to /mnt/cache/docker

lrwxrwxrwx 1 root root 168 Nov 8 07:37 docker -> ../cache/docker/

What am I missing here?

If I run Compute All on Shares - it shows just utilising the cache as expected:

docker - - Cache 246 KB 1.93 TB

Cache 246 KB 1.93 TB

In Docker settings, the paths are set as follows:

Docker directory:

/mnt/user/docker/

Default appdata storage location:

/mnt/user/appdata/

Edited November 8, 2025Nov 8 by flashback