Squid

Always a chance of stuff moving to lost & found when there's corruption. An alternative would be to pull the disk, connect it to a Windows box and run https://www.easeus.com/data-recovery-software/ (you'll probably want to buy it). You will need enough storage space available on another drive connected the the box to save the recovered info.

vDisks without that change in the XML will always increase in size and never decrease. You download a file (say 2G) to the VM, and the vdisk will increase in size by ~2G. Delete that file and the vDisk will not decrease. Do that enough times (or just use the VM for normal purposes where tmp files are created and deleted all the time) and the vdisk will always eventually increase in space to the maximum you've specified. You're probably seeing the total maximum size when you're looking at it, and not what it actually takes up on the drive.

You don't worry about it and reinstall from Apps - Previous Apps

(and docker.cfg has issues too)

Changed Status to Solved

Yeah, but we're talking kilobytes here. A single byte smaller is enough to toss that error. Reason I brought up shucked is that a ton of times a shucked drive also has an HPA partition which very slightly lowers the capacity.

When it doesn't show, you would have to post the diagnostics before typing the above and after

Some module within Grafana (zfs related?) would be my best guess.. You'd have to correlate the PID (55009) against the output of ps -aux The other hex numbers etc only are meaningful to the devs themselves after a ton of diagnosis involving de-compilers etc.

Wait a couple of minutes before trying to log in. -> It's a quirk and a bit pet peeve of mine that if you're sitting in front of that screen and you see the login screen and immediately log in you will see exactly what you're seeing. Try again in a few minutes. Or, From the start menu (the "lime"), go to the terminal and type in diagnostics and then powerdown and after the system has shut off, post the resulting zip file that was stored within /logs on the flash drive (pull the flash drive and put it into another computer)

That shouldn't matter. The only thing is to try and wait a couple of minutes longer than what you've been doing. Quirk of the GUI is that until everything is started up it won't respond. Myself, I've got user scripts installed with a script set to run at array start that is nothing but beep beep beep so that I know after a reboot when the system "thinks" it's up and running and then I know to wait a minute or two after those beeps before trying the WebUI The troubleshooting from here is a pita, but it's renaming all the .plg files to be .plg1, reboot, then rename one of them back to .plg and reboot until the problems start again. The last one renamed is the culprit. (It's on a mental todo list to kinda automate this via a plugin at some point)

https://forums.unraid.net/topic/51703-vm-faq/?tab=comments#comment-557606

@atribe ^^^^

It's 100% a manual run. Nothing automatic

Changed Status to Retest

Did you stop and start the array after making that change? Known issue (fixed next rev) where the use cache setting doesn't take effect without stopping and starting

I continually have "Server Execution Errors" whenever I try and start a container If you're running 6.9.2 or greater, then look at your "go" file (/config/go on the flash drive) and if this line is present curl -o '/usr/bin/runc' -L 'https://github.com/binhex/arch-packages/raw/master/static/x86-64/runc' && chmod +x '/usr/bin/runc' then remove it and reboot. (This line was apparently necessary for some @binhex containers on older versions of Unraid.) If this line isn't present in your go file (or via user scripts), then this error usually means that there is a port conflict between the app you're attempting to start and another app already running (or a service in the OS itself)

unable to retrieve OCI runtime error..... Remove this line from /config/go on the flash drive and reboot curl -o '/usr/bin/runc' -L 'https://github.com/binhex/arch-packages/raw/master/static/x86-64/runc' && chmod +x '/usr/bin/runc'

Post your diagnostics and additionally, pick one of them and do hit "Edit" on it, make a change (any change), then revert that change and then hit Apply. Then post the docker run command that appears.

Possible. Change the extension on user.scripts.plg to be something else and reboot. My next guess would be dynamix.unraid.net.plg

Is the new 4TB a shucked drive?

If this stuff doesn't work, what happens if you boot in safe mode?

Delete this line from the /config/go on the flash drive It's a remnant from unmenu cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c What is this in the same file? unraid_notify start

Then diagnostics

Not according to the diagnostics. It shows you're on F7 and a crititcal update F8 is available.

Make sure you uninstall it / remove the package from /extra or /packages on the flash drive