jcarreiro21

Hey all, Saw a couple instances that match but usually resolved with users running Pihole. I do not have Pihole running in my home so hopefully there are further suggestions. My Plugins tab never loads, just sits there with the Unraid logo as if it is thinking about it but never does anything. Left if for a couple hours at times and nothing Made some DNS changes on both Unraid and my UDM Pro but same case every time. No Threat Detection, etc. etc. enabled on the UDM Pro. Attached my diagnostics if that helps! TIA! jaycustomnas-diagnostics-20210628-2113.zip

Replaced the default value from 10000000000 to 10GB and the error has cleared in Fix Common Problems app I am now able to mkdir in /mnt/user/appdata! Thanks @Squid!!!

You mean under Global Settings? It is set to 10000000000 which I believe is 10GB? Even though the Fix Common Problem app states the following...

jaycustomnas-diagnostics-20190903-2149.zip

@Squid should I just upload the ZIP folder? @BRiT Interesting as I have not seen this before but seems to only be my LSIO containers.

Any time I now try to install a new docker container or update an existing container that uses the /mnt/user/appdata directory it either fails the install or the upgrade claims to complete but the version is the same. To test I can create a new folder in the /mnt/user directory but cannot within /mnt/user/appdata as it states there is no space even though terminal shows 3629G free of 3948G Any ideas anyone? Pihole is an example of trying to install a container that uses the /mnt/user/appdata directory and fails each time

Also have docker update notifications that when I hit update they claim they are updated to the latest I noticed this issue with pihole so I changed the directory from /mnt/user to /mnt/cache

Seems to be any time Unraid wants to write to /mnt/user/appdata it fails stating that there is no space even though its essential to my disk array with almost 3.5TB of space available I try to terminal in and try to create just a folder to that location and states the same error in terminal too

Oh thanks @jonathanm attached now diagnostics-20190829-2230.zip

Hopefully this helps? This is the read out I get after "installing" PiHole. Docker container claims to be there but directory does not exist

Can no longer install anymore docker containers as it states that there is no space. I check via terminal and using mc to navigate and when I enter the /mnt/user/ directory I see 3631G/3948G although the Dashboard shows 273GB used and 3.73TB available and I know for a fact that I do not have near 4TB of data on my array. Can anyone help? I have dug around but not much stands out as to why I am getting this error. I have 50GB allocated for the Docker image and only 12GB is used. My SSD cache pool has plenty of space. When anything is written to /mnt/user/ is it suppose to then offload somewhere? All that I add to the array can be seen in /mnt/user. Perhaps my Shares are set up incorrectly? All are marked High-Water. I have noticed a /mnt/user0 folder but not sure what that's about.

@helin0x @david279 Well jumping back to good old F6 from January 2019 has fixed the issue!! 970 passes on to the VM just fine in slot 1 while the 710 is used for UNRAID in slot 3 Thanks for the tips!

@helin0x I tried the most recent BIOS version F42a and no joy. Also tried going back to F30 and same issue. Going back to F6 and going to try that now as the BIOS is currently downgrading to F6 @david279 Thanks for the for this thread! Tried the ABB BIOS for my board version F42a and dooes not fix the issue for me. Going back to a January 2019 BIOS now to try that

As soon as I apply a rom file I get that error "unknown pci header type 127" Error is persistent after removing the rom path so a reboot more than likely is required now

It would only give me that error if I were to set VLC as primary and the 970 as secondary. No matter what changes are made after that, only a reboot will correct the error. I will try the BIOS update and see how that goes. Will reply shortly I have tried applying a rom file but have the same issue as the monitor not detecting any signal from the 970