Squid

from the terminal, cp /var/log/syslog /boot and then upload the syslog file that will get stored in the root of the flash drive here.

I just replaced a server that did the same thing. Although mine was ~10+ years old Any reboot or powerdown and then a turn on would not show anything on the monitor at all unless after waiting a bit I hit the restart button. Assuming yours is the same and nothing happens on the monitor at all then it's hardware related. What is a different story and would take some time investigation on your part. In my case, I just couldn't be bothered. as it was scheduled for replacement anyways

/dev/loop2 40G 23G 18G 57% /var/lib/docker If you keep having trouble, I'd suggest using a folder instead of an image for the docker (Settings - Docker and switch to folder)

By pulling the drive and running it outside of Unraid you just invalidated parity. With the drive still "missing" from unraid, run the check filesystem against disk #1. Then you reinstall the drive and rebuild the contents onto itself

Huh? As stated multiple times in multiple places by multiple people (including official Limetech representatives), only the trial ever phones home and that is simply to validate the time remaining on the trial. Paid licences do not phone home if you're not logged into the UPC. ever The only reason you need to ever actually log into the UPC is to replace a licence key. Zero reason to log into it if you're not taking advantage of the other features of MyServers. The entire OS is even designed around not having to have an internet connection running unless you're installing software on it.

Have you run a memtest lately? Same errors within the docker.img

The % isn't RAM. It's the % of the image being used. You can see the RAM usage on the Docker Tab and switching to Advanced View

Try switching your boot type in the BIOS from Legacy to UEFI / vice-versa

For one reason or another you enabled Debugging in CA's Settings. disable it. It's simply a warning because of the massive amount of data that gets logged by CA

Because a write to it never actually failed, and the drive is still there, even though there is corruption on it. Corruption would appear to be caused by a piss-poor cable connection to the drive. Reseat and/or replace Because it's not missing or red-balled Nope. Run check filesytem against disk 1

It would appear from the project link on the UI that you need to run both to have the UI.

Try setting static DNS addresses in Settings - Network settings (208.67.222.222 / 208.67.220.220) If no difference, then create a new thread in General Support and include your diagnostics

Oct 30 00:03:11 Executor kernel: verify_parent_transid: 7967 callbacks suppressed Oct 30 00:03:11 Executor kernel: BTRFS error (device loop2): parent transid verify failed on 17584734208 wanted 1640023 found 1639989 By far the easiest way for this to happen is when the image fills up. Either way, the solution is the same. Delete the image, then reinstall from Apps - Previous Apps. 5 minutes and you're done

appdata, D-------b are both set to use cache: Prefer. No idea if D-------b should be using it or not. domains is set to use cache No, but files exist on the cache drive. Mover won't touch those files since you've said not to move them. Change it to use cache: yes (although generally you want the domains to be on the cache drive) What are you expecting to move, and what is taking up the space (hit calculate on the shares tab. If the spinner doesn't go away after 2 minutes, refresh the page)

Advanced View. (Docker you also have to stop the service in order to change them)

And removed the incompatible flag in CA / FCP

You need to post your diagnostics. But, since it says "Share Cache Full", the implication is that mover is trying to move onto the cache drive not from it

The mce looks like it's nothing, and if anything I'd guess its from the system reconfiguring due to the nvidia drivers

Settings

It's most likely not your log actually filling up, but rather the image itself due to a misconfigure of the various paths? What does Container Size show on the Docker tab? A number of entries in the Docker FAQ here about the image filling up.

Hit Add Pool.

Realistically, the problem with this forum and containers is that a ton of the questions aren't even relevant. Any question related to the container itself (why doesn't it install? What do I change on the template?) belongs here. Questions related to bugs, questions regarding the app itself belong on the app's own forum (ie: Project pages). Since these are possibly the majority of the support problems, CA and the dashboard / docker tabs now list (6.10+) Project first followed by Discord, and then Support on all the dropdowns.

Anecdotal evidence that tdarr is causing this https://forums.unraid.net/bug-reports/stable-releases/683-shfs-error-results-in-lost-mntuser-r939/?tab=comments

/config/go on the flash drive At some point, you did add it for one reason or another. @binhex what is this?