11 hours ago, Hendrik112 said:

Hello, I would like to permanently disable the automatic docker update check. I have stopped using the unraid exclusive docker templates entirely for multiple years now in favour of docker compose.
The Fix Common Problems docker update check is just not working properly for containers not managed by dockerman and basically reports that any "3rd party container" has an update available. This is quite annoying and also makes it harder to see any relevant issues in the reports.

Is there any way to disable the update check in the plugin or could the check be fixed for all containers?

Echo this, also getting docker update warnings from Fix Common Problems all of the sudden. Verified Docker notifications are disabled in Notification Settings. Workaround right now is ignorning them, eventually the list is going to be about 30 warnings tall. Not sure if this is intended now, or if my broke updating to 7.0.

16 hours ago, coolman2170 said:

Verified Docker notifications are disabled in Notification Settings

FCP does not use the settings for docker notifications -> it uses it's own notifications on sending things (errors + warnings, warnings or none)

17 hours ago, coolman2170 said:

Echo this, also getting docker update warnings from Fix Common Problems all of the sudden. Verified Docker notifications are disabled in Notification Settings. Workaround right now is ignorning them, eventually the list is going to be about 30 warnings tall. Not sure if this is intended now, or if my broke updating to 7.0.

I tried to ignore them for some time, but the ignore functionality seems to be a bit broken with 7.0.0, I can't ignore any new warnings.

I came across this error while running fix common problems

 

Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the Unraid forum

 

Here is the diagnostics. Please help

 

herculeunraid-diagnostics-20250131-1918.zip

Hi,

 

I have run out of log space., with Fix Common Problems reporting that /var/log is getting full (currently 100 % used). Diagnostics attached. Server is at version 7.0.0, uptime around 25 days.

 

Please help!

whitey-diagnostics-20250205-0558.zip

@herculepirate

Lots of these in syslog

Jan 11 20:41:31 HerculeUnraid kernel: BTRFS warning (device sdb1): csum failed root 5 ino 68518 off 3991965696 csum 0x4ee7afb3 expected csum 0xd34723b1 mirror 1

This is almost certainly bad RAM.

 

You shouldn't even attempt to run any computer unless RAM 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.

 

After you fix RAM you will still have to deal with the damage it did to your data.

Been ~72 hours and can't connect to update plugins or docker containers, have ensured that DNS is set correctly, have rebooted both fiber modem and UDM PRO twice.  Fix Common Problems did finally run:

Reset your modem / router or try again later, or set your  to 8.8.8.8 and 8.8.4.4 Also make sure that you have a Gateway address set up (Your Routers IP address). Additionally, this may also mean that GitHub is currently down. This error means that you may not be able to update your OS or plugins  More Information

 

Diagnostics file attached

 

Edited February 8, 20251 yr by trurl
delete lots of attached files that should have been a single zip

Diagnostics is a single zip file. Find that single zip file wherever your browser downloads to and post the single zip file. Nobody is going to download all those separate files.

Idea/suggestion to add a plugin check please - the old version of the mover tuning plugin seems incompatible with unRAID v7.0.0 and stops working, causing cache pool to fill up. Simple fix is the remove the incompatible plugin then either run the stock built-in mover to empty the cache pool or install and configure the latest version of the plugin. Unfortunately when searching for the mover tuning plugin on the community apps there are two results returned and it isn't clear which version is which but I think the one with Reynald mentioned is the latest one with fixes for unRAID v7.0.0.

Edited February 8, 20251 yr by manfat
added link to relevant post

Apologies, single file as requested.

chimaera-diagnostics-20250207-2037.zip

I have no idea what this means or how to remedy it.

 

"Invalid folder cache contained within /mnt"

 

Any help is appreciated.

 

Regrads

tower-diagnostics-20250212-1830.zip

It almost certainly means you have a docker container configured to use /mnt/cache in a volume mapping.   Since you do not have a pool called ‘cache’ this creating a /mnt/cache folder which is only in RAM.

2 minutes ago, itimpi said:

Since you do not have a pool called ‘cache’ this creating a /mnt/cache folder which is only in RAM.

Not only is that host path not persistent storage for you, but that would be a folder in rootfs, the space the OS lives in. If you fill that up, all sorts of things are going to break.

On 2/7/2025 at 9:46 PM, norrismarine said:

have ensured that DNS is set correctly, have rebooted both fiber modem and UDM PRO twice.  Fix Common Problems did finally run:

Reset your modem / router or try again later, or set your  to 8.8.8.8 and 8.8.4.4 Also make sure that you have a Gateway address set up (Your Routers IP address)

Did you actually test this?

https://forums.unraid.net/topic/116516-problems-downloading-installing-apps-etc/

 

Your ifconfig has

eth0             UP             
eth1             DOWN           10.11.10.30/24 metric 1 

and also

br0              UP             192.168.1.50/24 

Have you tried renaming or deleting config/network.cfg on your flash drive so it will use defaults?

I encountered this error multiple times and ran ClamAV to remove some of the findings;  but I'm still wondering what we can do to secure and protect ourselves.   Prior, we had Connect enabled with SSL/TLS - nonetheless, we feel this caused us to be exposed as our password was plain text apparently?

 

I’m attaching our diagnostic as requested.

 

 

Edited February 12, 20251 yr by ich777
Deleted Diagnostics

Just a suggestion to add is to check if any controllers are in IDE mode and suggest changing to AHCI mode.

 

I either changed that myself by accident or one of my power tuning or boot issues caused it to change by itself and that caused issues spinning down drives.

 

Thank you for the plugin!

1 hour ago, Er1ck said:

I encountered this error multiple times and ran ClamAV to remove some of the findings;  but I'm still wondering what we can do to secure and protect ourselves.   Prior, we had Connect enabled with SSL/TLS - nonetheless, we feel this caused us to be exposed as our password was plain text apparently?

 

unraidserv-diagnostics-20250212-1052.zip 105.68 kB · 0 downloads

I'm attaching our diagnostic as requested.

 

 

You have your Unraid webgui exposed to the public internet. what do you expect? thats like leaving your car with keys unlocked along side a sign with "free ride"


Edit: Oh holy moly, everything is publicly rachable 💀

Edited February 12, 20251 yr by Mainfrezzer

On 2/5/2025 at 6:06 AM, Timski said:

Hi,

 

I have run out of log space., with Fix Common Problems reporting that /var/log is getting full (currently 100 % used). Diagnostics attached. Server is at version 7.0.0, uptime around 25 days.

 

Please help!

whitey-diagnostics-20250205-0558.zip 319.36 kB · 4 downloads

Bump!

I've recently replaced my array with a ZFS pool and now I'm getting a load of "Share XXX set to use pool cache, but files / folders exist on the YYY pool" warnings. I've gone through and checked all my shares, and all my files seem to be on the correct primary/secondary storage as defined in the share settings so I can't figure out why I'm getting this warning.

 

For example:

 

And here is the configuration for the share in question:

 

So based on the above, I would expect to have files on both Cache and on Deadpool, and certainly when I look at the share contents this holds true:

 

So as far as I can tell, I only have files for this share in the correctly configured configured locations - o why is FCP throwing these warnings? As far as I can tell, it looks like I'm getting this warning for all shares that are configured to use my ZFS pool as secondary storage.

 

Edit: Just to add, I noticed a few posts back that there were a few other reports of a similar issue. I've checked all of my docker mapping and every single one is mapped to /mnt/user/.... with one exception which is mapped to /mnt/cache (and the share in question is set to cache-only) so I'm not sure if that's related or not.

Edited February 16, 20251 yr by Lumpy_BD

Just like Lumpy_BD I also just converted my server to ZFS pools and finished migrating data back to it. All my shares set to cache primary array secondary are getting a warning in "fix common problems" about files/folders existing on the secondary. Looks like the checks aren't taking into account the secondary folder at all in the scan. 

 

 

alexandria-diagnostics-20250222-0723.zip

I can't wrap my head around why anyone who has switched to using ZFS pools INSTEAD of an Array is using a secondary location along with mover.

 

That's how you absolutely decimate your performance.

 

Make the ZFS pool your primary location and don't use a secondary. Set all shares to use Exclusive mode.

 

Edited February 23, 20251 yr by Espressomatic

because even with ZFS pools NVME is still faster

Ran into this alert stating I had flash drive corruption (exact alert/error pasted below) a while back and switched out my flash drive today yet still receive the notification from FixCommonProblems.  Attached are my diagnostics.  Are you able to advise?  Thanks.

 

/boot/config/flash.cfg corrupted    Your flash drive has possible corruption on /boot/config/flash.cfg. Post your diagnostics in the forum for more assistance

nas-1-diagnostics-20250302-1801.zip

2 minutes ago, emdee84 said:

/boot/config/flash.cfg

yes it is corrupt.

 

See if you can rewrite it by going to MAIN - Boot Device - flash - SMB Security Settings

8 minutes ago, trurl said:

yes it is corrupt.

 

See if you can rewrite it by going to MAIN - Boot Device - flash - SMB Security Settings

That seems to have fixed it.  Did not realize it was related to that setting.  Thank you!