On 10/12/2024 at 10:11 AM, Revan335 said:

Maybe can @Squids more say about this confusion message. Or he can change this for more clarify.

Looking at this more carefully, I think it's because the docker folder is on disk 4, which is at 13.1/14TB that rounds up to, 94%. That disk has been roughly at that usage since I changed to the docker directory a few months ago, because the array has been filling other lower disks the entire time.

 

However, given the share is set to split at any directory, and can use all disks, perhaps the error is wrong? If the directory couldn't be split to another drive, or it was only allowed on that Drive it would make sense. But in practice won't unraid split this directory to another disk at some point?

Split any directory split any directory. system/docker, system/libvirt, system/docker/the many many hundred/thousands subfolders.

 

You can see in the Filemanager on what's disks the system Share or his subfolders was located.

 

And yes, when only disk 4 was the disk for the system share, than was the message correct. He is 94% full.

Sorry not fully following, are you saying the error message is correct? I do have split any directory enabled, so the disk capacity should not matter.

6 hours ago, nerv said:

Sorry not fully following, are you saying the error message is correct? I do have split any directory enabled, so the disk capacity should not matter.

You can tested. Move the docker folder from disk 4 to another disk with more space and show the message persist. Or moved a few folders to another disk, removed temporaly one or more Docker Container to make more free space and show the warning changed his % message. Or moved other files/folders like music, multimedia from disk 4 to another disk. The disk have maybe not only the docker folder.

 

Only @Squid can bring light in the calculation or messages names/text/description of his Plugin.

On 10/6/2024 at 4:31 AM, L0rdRaiden said:

Could you please add a global setting to disable docker containers update warnings? Is quite annoying for those using docker compose with many containers.

 

 

Echoing this request, I'm managing these within compose myself with diun, watchtower, etc. Thank you for considering.

On 10/14/2024 at 4:46 PM, Revan335 said:

You can tested. Move the docker folder from disk 4 to another disk with more space and show the message persist. Or moved a few folders to another disk, removed temporaly one or more Docker Container to make more free space and show the warning changed his % message. Or moved other files/folders like music, multimedia from disk 4 to another disk. The disk have maybe not only the docker folder.

 

Only @Squid can bring light in the calculation or messages names/text/description of his Plugin.

got it. I'm a little terrified to move the folder 😂, but agreed that's a good way to confirm the issue.

On 7/26/2024 at 4:32 PM, bozzio said:

Hello

 

I'm getting Invalid folder ncdata contained within /mnt and I'm not sure why.  I'm running nextcloud aio and i have no variables pointing or mention ncdata.  I have NEXTCLOUD_MOUNT pointed to /mnt for the purpose of passing external media.  I cannot find what is causing this.  I have tried deleting the folder but it crashed nextcloud. Any help would be great!

diagnostics-20240726-1631.zip 285.09 kB · 0 downloads

Any help on this?

Generating this error:
"Macvlan and bridging has been found. This might cause issues with stability on your server.  More Information..."

And as I understand, this is no longer an issue. 

 

7 hours ago, The_Holocron said:

Generating this error:
"Macvlan and bridging has been found.

 

Yeah, one of the (few) things that drives me up the wall with the plugin, one other being the slave share warning. All ignored errors are duplicated twice on the screen and take up more space than the functional part of the UI on my systems.

 

I suppose I wouldn't have any issue if ignored issues were completely hidden from the UI - then I'd be able to truly ignore them.

 

 

 

 

Edited October 24, 20241 yr by Espressomatic

On 2/17/2024 at 8:56 AM, dopeytree said:

Noticed update assistant is proclaiming 'unbalanced.plg is not known to community applications'.

 

 

 

Still seeing this.  

Any reason or solution I am getting this error ?

I had this plugin working and when I tried to update as I well I got the same error.

I then uninstalled this app and now need to install it again.

 

plugin: installing: fix.common.problems.plg
Executing hook script: pre_plugin_checks
plugin: downloading: fix.common.problems.plg ... done

plugin: downloading: fix.common.problems-2024.10.02-x86_64-1.txz ...
plugin: fix.common.problems-2024.10.02-x86_64-1.txz download failure: Generic error
Executing hook script: post_plugin_checks

 

 

On 10/17/2024 at 11:11 AM, nerv said:

got it. I'm a little terrified to move the folder 😂, but agreed that's a good way to confirm the issue.

FYI I did move the docker folder to another disk with higher capacity and the error went away. So that pretty much confirms the check is looking at the disk's space rather than the share it belongs to.

 

Appreciate the help!

Hi guys,

 

I am using the Plugin for several months now, since now without problems. But today I wanted to start the plugin and, as usual, the scanning-windows pops up:

 

 

But unfortunately...that's it...the plugin does not start the scanning. I can leave the window open for minutes, nothing happens. No progression at all. I can go back and open the Unraid dashboard, so Unraid itself is still running. I can also re-open the plugin, but just to get the same result.

 

De-installation and re-installation of the plugin also hasn't changed the behavior.

 

Any hints?

 

Regards,

Stefan

 

Update: After a reboot plugin is working again. Problem resolved.

Looking to see if someone can view my diagnostics folder and tell me if this is a hack attempt, or something I've done to cause the error. I've never seen this error in 3 years.  I am running a Windows VM that was hacked on my Unraid server, and I completely reloaded Windows over the old one.  

tower-diagnostics-20241118-0701.zip

I guess nobody needs to look into your diagnostics, as you already know that you have been hacked.

And usually its not sufficient to "fix" the open door, but to clean up your whole LAN because the hack commonly dropped a malware that has infected every computer "in reach". And also every other LAN device like routers and so on.

Happy reinstalling EVERYTHING!

 

Hey All

 

Wonder if anyone can help - receiving the `Invalid folder appdata contained within /mnt` error. Be great if someone can point me in the right direction on how to resolve. 

 

Many thanks

unraid-diagnostics-20241125-0852.zip

On 11/25/2024 at 4:02 AM, K18LDP said:

Hey All

 

Wonder if anyone can help - receiving the `Invalid folder appdata contained within /mnt` error. Be great if someone can point me in the right direction on how to resolve. 

 

Many thanks

unraid-diagnostics-20241125-0852.zip 157.24 kB · 0 downloads

Look for a docker container that has a path mapping of /mnt/appdata instead of /mnt/user/appdata.  

On 11/26/2024 at 2:37 PM, Squid said:

Look for a docker container that has a path mapping of /mnt/appdata instead of /mnt/user/appdata.  

Thank you... I think 'glances' docker container may have been the issue... I had it mounted at /mnt

Is it possible to run Docker Safe New Perms from the command line or run it on a schedule?  I'd like to run it once a month or so just as a sanity check.

Use user scripts and set up a new script on whatever schedule you want.  Script will be:

#!/bin/bash
/usr/local/emhttp/plugins/fix.common.problems/scripts/newperms.sh

 

I have a strange problem, I used to have a docker i created called ubuntu-FFMPEG, and I also had the binhex-krusader app installed. I uninstalled those long ago and deleted any containers i found along with deleting the krusader folders on the appdata folder. But when ever fix common problems runs it keeps finding errors  one is that there is a update for ubuntu-FFMEPG , and the other is that binhex-krusader has volumes being passed that are normally mounted" I tried uninstalling fix common problems but the errors still show up. I dont just want to ignore them if there actually somewhere that hasent been cleaned up properly.

Docker Tab -> advanced view and look there.  Delete any orphans.  FCP only reports what the system says is there

Suggestion - can we somehow disable any alerts related to Nextcloud-aio-* for updates?

 

Because the AIO master container is the one handling the updates, unraid thinks there's always an update avaialble for these 10 containers on my system (others may have more) but they for sure all start with nextcloud-aio-* -- the only one that IS managed by unraid is nextcloud-aio-mastercontainer

 

It would be nice if we had a way to not have to manually ignore each of the 10, and either have these auto-ignored by fix common problems, or a checkbox to ignore items matching a text string, so we could put in "nextcloud-aio-" as the string or something? 

 

Just thinking out loud here  

 

Edited December 5, 20241 yr by CorneliousJD

4 hours ago, CorneliousJD said:

or a checkbox to ignore items matching a text string, so we could put in "nextcloud-aio-" as the string or something? 

The problem then would be that you want "nextcloud-aio-mastercontainer" which also would give you a match to your ignore string.

 

The real problem is that UNRAID says "ready for update" on these containers but if you ask to update it says "no configuration found, cannot update".

 

So this plugin better should check for the docker config.