Farily new to unraid here, so this kind of caught me. I had two warnings to the effect of this file here is set to cache only but is also on the array. Likely due to newbness during the initial setup of the system. I easily resolved the errors by just removing the offending folders from their old location points.

I was pointed to this thread by the error as a solution: https://forums.unraid.net/topic/120220-fix-common-problems-more-information/?tab=comments#comment-1098686

The thing that was slightly confusing is both warnings, or at least one of them, indicated I should use Dynamix File Manger to help fix my issue. So I go looking for it etc, finally check the DFM thread and read that DFM is built in to my 7.3.0 unraid.

Basically, does that warning need to be updated or removed? I resolved my issue with CLI,. I was just confused by some things I wasn't aware of as unraid has evolved.

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

Importance: warning

* The plugin usb_manager_usbip_addon.plg is not known to Community Applications and is possibly incompatible with your server

Is that correct or a Bug again?

The Maintainer Answer: https://forums.unraid.net/topic/100511-plugin-usb_manager/page/24/#findComment-1627484

And the Discussion about this.

For your consideration, I have two suggestions to add to check for FCP. I just recovered from an incident where the default postgresql17 install created /mnt/cache/appdata/postgresql17, but my server doesn't have a cache pool, so it mounted the database into an unintended RAM disk. Full mechanics: https://product.unraid.net/p/7-3-1-mover-moves-array-data-into-ram-rootfs-when-a-share-s-configured-pool-doesn-t-exist-but-mnt-pool-is-a-plain-directory

Suggested behavior: Warn the user when a share has shareUseCache of yes/prefer/only and shareCachePool names a pool that isn't defined (regardless of what exists under /mnt), — especially when the system has zero pools. I've also asked for stock Unraid to surface this proactively (https://product.unraid.net/p/proactively-surface-share-references-to-nonexistent-pools-and-flag-legacy-prefer-cache-configs-on-upgrade), but FCP fixing the test would protect people today.

Two suggested COAs in the "share references non existent pool" test include/tests.php, version 2026.05.16):

1. The test builds $pools[] from defined Cache-type disks, then if ( ! isset($pools) ) return; — so on a system with no pools at all, the whole test is skipped. Poolless systems are exactly where legacy prefercache share settings are dangerous: if a plain directory appears at /mnt/cache (Docker auto-creates one from any stale template host path), the mover could move array data into it — i.e. into RAM.

2. The existence test is !is_dir("/mnt/$sharePool") — mountpoint -q (or checking the pool config) would be more robust.

On 7/17/2026 at 7:18 AM, Revan335 said:

And again!

Any Information about that?

Other Dynamix Plugins too:
* The plugin dynamix.password.validator.plg is not known to Community Applications and is possibly incompatible with your server

With Internal Boot introduced in unraid 7.3.0 this is not necessarily valid?