Hi there,

fix common problem detected /var/log is getting full (currently 100 % used).

i cannot find the rootcause of it. please help

Greetings,

Arie

diagnostics-20260127-1248.zip

Not much left of your syslog after I remove all the mover errors.

First thing, remove the Mover Tuning plugin. Then reboot to clear your logs.

Then post new diagnostics. We need to do a lot of work on the configuration of your shares.

Oke thank you for your assistance! im sorry if i messed up. restarting now

i restarted and generated new diagnostic logs

moker-vet-diagnostics-20260127-1407.zip

Many of the things we need to discuss are in your FCP warnings:

Jan 27 14:07:04 Moker-Vet root: Fix Common Problems: Warning: Share docker is an implied array-only share, but files / folders exist on the cache
Jan 27 14:07:04 Moker-Vet root: Fix Common Problems: Warning: Share DockerImage is an implied array-only share, but files / folders exist on the cache
Jan 27 14:07:04 Moker-Vet root: Fix Common Problems: Warning: Share media is an implied array-only share, but files / folders exist on the cache
Jan 27 14:07:04 Moker-Vet root: Fix Common Problems: Warning: Share Media is an implied array-only share, but files / folders exist on the cache
Jan 27 14:07:04 Moker-Vet root: Fix Common Problems: Warning: Share Plex-Transcode is an implied array-only share, but files / folders exist on the cache
Jan 27 14:07:04 Moker-Vet root: Fix Common Problems: Warning: Share transcode is an implied array-only share, but files / folders exist on the cache
Jan 27 14:07:04 Moker-Vet root: Fix Common Problems: Warning: Share Admin set to cache-only, but files / folders exist on the array
Jan 27 14:07:05 Moker-Vet root: Fix Common Problems: Warning: Share domains set to cache-only, but files / folders exist on the array
Jan 27 14:07:05 Moker-Vet root: Fix Common Problems: Warning: Share isos set to cache-only, but files / folders exist on the array
Jan 27 14:07:05 Moker-Vet root: Fix Common Problems: Warning: Plugin Update Check not enabled
Jan 27 14:07:05 Moker-Vet root: Fix Common Problems: Warning: Docker Update Check not enabled
Jan 27 14:07:05 Moker-Vet root: Fix Common Problems: Error: Same share (media) exists in a different case
Jan 27 14:07:05 Moker-Vet root: Fix Common Problems: Error: Same share (Media) exists in a different case
Jan 27 14:07:05 Moker-Vet root: Fix Common Problems: Warning: Docker application FreeFileSync has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option
Jan 27 14:07:05 Moker-Vet root: Fix Common Problems: Warning: Docker application FreeFileSync-VNC has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option
Jan 27 14:07:08 Moker-Vet root: Fix Common Problems: Warning: Deprecated plugin plexstreams.plg
Jan 27 14:07:13 Moker-Vet root: Fix Common Problems: Error: File pgid present within /mnt
Jan 27 14:07:13 Moker-Vet root: Fix Common Problems: Error: File puid present within /mnt
Jan 27 14:07:18 Moker-Vet root: Fix Common Problems: Other Warning: Mover logging is enabled
Jan 27 14:07:20 Moker-Vet root: Fix Common Problems: Other Warning: Background notifications not enabled
Jan 27 14:07:21 Moker-Vet root: Fix Common Problems: Warning: Share Admin set to use pool moker-vet, but files / folders exist on the cache pool
Jan 27 14:07:21 Moker-Vet root: Fix Common Problems: Warning: Share appdata set to use pool cache, but files / folders exist on the moker-vet pool
Jan 27 14:07:21 Moker-Vet root: Fix Common Problems: Warning: Share mokervet set to use pool moker-vet, but files / folders exist on the cache pool

Possibly a lot of that about cache is from you trying to fix your problems with mover.

Let's take these in smaller bites.

This is an easy one:

Jan 27 14:07:08 Moker-Vet root: Fix Common Problems: Warning: Deprecated plugin plexstreams.plg

Remove it

Done

This one is potentially serious, but maybe not a lot of data has been put there (yet). Might take some work to track this down.

Jan 27 14:07:13 Moker-Vet root: Fix Common Problems: Error: File pgid present within /mnt
Jan 27 14:07:13 Moker-Vet root: Fix Common Problems: Error: File puid present within /mnt

I suspect you have somehow created volume mappings - pgid and puid - in one or more of your containers. Usually, these would be environment variables instead of volumes. Not sure how they wound up with a host volume of /mnt, but that path isn't actual mounted storage so is in rootfs, the space the OS lives in. The reason I said potentially serious is if you fill that space up, the OS has no room to work in and can become very unstable.

How many containers do you have?

47, i dont use all but 27 of them are usually running

What do you get from command line with this?

ls -lah /mnt

See attached image. I also have found that my plex media server container is very slow loading in libraries. But i dont know if that is related or not..

Not taking up much space then (as expected) but still not good

26 minutes ago, Moker-Vet said:

47, i dont use all but 27 of them are usually running

You will have to examine each of your containers and see if any have a host path of /mnt

47 minutes ago, trurl said:

Jan 27 14:07:05 Moker-Vet root: Fix Common Problems: Error: Same share (media) exists in a different case
Jan 27 14:07:05 Moker-Vet root: Fix Common Problems: Error: Same share (Media) exists in a different case

Linux is case-sensitive. Media and media are different. You should be able to see on the User Shares page that you have both of these user shares.

You probably have some containers using /mnt/user/Media and others using /mnt/user/media. These are not the same. You need to decide which of these you want to use, fix the containers so they refer to the one you intend to use, consilidate the files into the one you want to keep, then delete the other share.

I'm concentrating on your containers first because if we don't fix them first, they will just recreate the problems. Then we can move on to the way your shares are configured. Probably we will need to disable Docker in Settings eventually to get some of that cleaned up, but you wouldn't be able to fix your containers with Docker disabled so we are doing that first.

Hi Trurl!

I appreciate your help, apologies it took awhile for me to reply. i have done as you asked and i noticed indeed the Media and media folder was present in several containers. i also noticed the PGID and PUID was for 1 container set to 0. i have changed those to 99 and 100. after that i deleted the media and Media folder and i deleted the PGID and PUID file in the mnt. i ran the fixcommon problems again and it didnt showed the issue.

i think we are ready to move to the next points

Post new diagnostics

moker-vet-diagnostics-20260130-0906.zip

What is the intended purpose of your moker-vet pool, and why do you have a share named mokervet?

Hi!, i have created the moker-vet pool out of neccasairity because my 20tb hdd where shrinked to 10tb when added to the array. my intention was to add them to the array but i would lose to much terabytes by doing that. And then i had to chose between btrfs and zfs. i chose btrfs because i have worked with btrfs before and not zfs. i couldnt really determine if zfs was the right choice for me. the naming of the pool and the share was just because i needed a name and i liked moker-vet.

- the array is using my 4tb drives.

-the moker-vet pool is using my 4tb ssd's, and 14tb+ hdd's

both storage pools are used for the same purpose -> storing video files. i use mover between them to prevent them from getting full.

its not ideal but its the solution i found while trial and error this issue.

the reason why my share is named moker-vet is simply because i liked the name and its my production storage share for my video files.

1 minute ago, Moker-Vet said:

the moker-vet pool is using my 4tb ssd's, and 14tb+ hdd's

Probably be better if SSDs and HDDs were in separate pools.

that i can do, it will take some time because i would have drag and drop alot of video files haha

7 minutes ago, Moker-Vet said:

20tb hdd where shrinked to 10tb when added to the array. my intention was to add them to the array but i would lose to much terabytes by doing that

Don't understand what you mean there. That isn't how the Unraid array works. There is 1 or 2 parity disks that don't contribute to storage capacity, but all other array disks use the full size of each disk and the total capacity of the array is the sum of the array data disks.

When i added a 22tb hdd to my xfs array it became a 10tb. i was not talking about parity in my example because i tested it without a parity. but i dont want my 22tb hdd to be shrinked.

2 minutes ago, Moker-Vet said:

When i added a 22tb hdd to my xfs array it became a 10tb. i was not talking about parity in my example because i tested it without a parity. but i dont want my 22tb hdd to be shrinked.

Then it problably already had a partition that should have been deleted before adding to array.

The only thing I can think of that might be going on there is if the disks were configured by another system to have multiple partitions. Unraid will only use one partition on each array disk. If Unraid prepares an unpartitioned disk, it will only have a single partition and it will use the whole disk.

What do you get from command line with this? May take a little while for the complete output since you have so many disks.

lsblk