Squid

Dec 31 13:48:58 Tower kernel: BTRFS info (device sdc1): using crc32c (crc32c-intel) checksum algorithm Dec 31 13:48:58 Tower kernel: BTRFS info (device sdc1): using free space tree Dec 31 13:48:58 Tower kernel: BTRFS info (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 3, gen 0 Dec 31 13:48:58 Tower kernel: BTRFS info (device sdc1): enabling ssd optimizations Dec 31 13:48:58 Tower kernel: BTRFS error (device sdc1): incorrect extent count for 583105773568; counted 1348, expected 1338 This is causing the cache pool to be read-only, with the result of docker failing to start Since it mentions "corrupt 3", best to initially start with running memtest from the boot menu for at least a couple of passes, since bad memory can and will cause corruption

It's not that it's overclocked. The RAM is actually running at it's SPD speeds. But rather that at those speeds its greater than what your CPU supports. You need to underclock the RAM to match what is in the graphs FWIW, The QVL for the motherboard shows that RAM you have as only being supported for two sticks.

The system will never do that for you. Monthly suffices. Single or dual parity drives are entirely up to you and your own level of confidence. Actual drive failures are exceedingly rare. And additionally, a URE does not constitute a drive failure in Unraid (rightfully so) unlike a traditional RAID system.

What does that mean? What shows in the browser when you try to hit it via the IP address. Note: use http not https Can you access the webUI via one of the webGUI boot modes and a locally attached monitor / mouse?

The picture shows that they aren't exported. The share you need to export via it's settings. Also, FWIW you've created a top level directory (ie: share) via a docker container called AppData and appdata. Not an issue per se, but rather confusing. You should see which contaiiner has the "appdata" share and fix it to match the case of the default one (it's going to be one that does not have a "/config" for one of its container paths.

Your other post says SATA connections are not (and have never been) known for being a robust connector and most times the non-locking connectors work better than the so-called locking ones. But assuming that your original posting is correct and not this one, then you slightly dislodged the sata cabling to the other drive when replacing the parity drive. Reseat all the cabling at both ends.

The top right display sometimes takes a bit to update itself and ultimately may require a reboot or a simple sign out / sign in. However, if Tools - Registration shows that you are NOT running the trial version then you're effectively good to go no matter what

Dec 26 18:40:49 Odin mcelog: Corrected memory errors on page b5571b000 exceed threshold 10 in 24h: 10 in 24h Dec 26 18:40:49 Odin mcelog: Location SOCKET:0 CHANNEL:1 DIMM:? [] I didn't notice originally that you were running ECC memory, so Memtest on the boot menu wouldn't find anything. But, even if you did replace the memory, the new memory is also toast. You should run memtest from memtest86.com (set up a new boot flash for this), and investigate via your system event log

run check filesystem against disk 5

You need to post your diagnostics @ds246 You should try in SafeMode or remove Appdata Backup as a test to see if it continues, since the errors started immediately after it was installed on the reboot

I'd try it by disabling Wireguard and then go from there.

You must have slow internet. Unless the hour included the reading / finding of instructions. I do this constantly in the course of testing, and usually average about 10 minutes start to finish...

Which Plex App? Any VPN / firewalls involved in your network?

I'm running Sonoma and have zero problems. I'd check that in Finder under locations that you are connected as your specific username. Disconnect the open shares and the location, then on the location reconnect and ensure that it's connected as the user in question

Nothing to fix. You just need to enable it

You would have set it up in the template when you installed it. If you don't remember, edit the container from the docker tab and scroll down In my case, it's saving it to /mnt/user/Downloads/. In otherwords, to my Downloads share

Curious if you also have an issue with the dashboard not populating CPU usage etc correctly. Upshot with FCP is that if you just let it sit for a couple of minutes and then reload the page it should populate everything that it found. FWIW, probable fix to these issues for a small minority of users are probably in the soon to be released 6.13

Because the template repository no longer exists. Only if the application in question has been previously installed can it then be reinstalled. Getting further results from dockerHub will however bring up the raw applications and CA will then assist in creating a template for you to install

Unfortunately, many routers for some weird unknown issues have problems resolving requests from clients. This can result in what you're seeing. Unraid does not force anyone to use Google's DNS (8.8.8.8 / 8.8.4.4) as the resolver. You can set the addresses in Network Settings to be anything you want (I'm a fan of OpenDNS - 208.67.222.222 / 208.67.220.220) including CloudFare (1.1.1.1) Another issue that does come up from time to time is that on occasion (this seems to lately happen to ghcr repositories) is that the checksums reported by ghcr when checking for updates are actually incorrect. This results in ghcr telliing Unraid / Docker that an update is available, but there may not actually be one (Resulting in a 0 byte pull). This issue is purely GitHub's (owned by Microsoft) and nothing to do with Unraid at all.

Nothing to do with changing the DNS addresses. You should post your diagnostics

FWIW I've switched to a complete Mac / Apple environment and cannot see any fundamental difference on a stock MacOS (Sonoma) install vs a Windows environment. Not saying that there isn't any, but in how I have my server organized I don't see any real difference

There's probably 2 options on that boot menu UEFI and Legacy. Which one are you using? Make sure that the boot order set in the BIOS matches what you're actually selecting.

If you are using either Network Type as Host or assigning the container a specific IP address, then any and all port mappings are ignored because in those 2 settings they make no sense. The docker run command for one of the apps which you're having issues on would be very helpful

Are the apps from Community Applications. The question marks for icons however speaks volumes if they are from CA. It basically means that most likely your server cannot reach the internet properly (Try setting static DNS addresses in Settings - Network settings) or could also be a corrupt docker image