Squid

Port mapping has no effect on containers with a custom IP address. The ideal place to ask about any issues with the app is within their dedicated support threads. which you can get via clicking on the icon and selecting Support

Enable the syslog server (mirror to flash) and after the next crash post a new set of diagnostics and the syslog that was saved in /logs on the flash drive

Yes CA thinks that it's installed due to the folder existing What you should be doing is submitting the base english files here: https://github.com/unraid/lang-en_US And then you can also include the Spanish translations here https://github.com/unraid/lang-es_ES That way the base translations will propagate to all the languages for someone to (hopefully) translate, and your Spanish ones will be there on the next update of the languages

You should post your diagnostics.

To be expected. The docker system ignores all port mappings when network type is a custom IP (or host)

Is this a brand new system? Have you ever formatted the drives for use in Unraid?

Put the stick into another computer (eg: Windows) and run chkdsk on it

Thanks. Will be fixed next release. But, Tools - PHP Settings set it back to no errors / default.

It's one of the built-in safe guards to stop the feed from getting trashed if GitHub has issues. In this case, a repository was deleted by the maintainer so the feed aborts until an investigation happens. All by design and I try to look for this daily.

From the locally attached monitor / keyboard can you enter in at a command prompt diagnostics It'll get saved onto the flash drive in the /logs folder. Then powerdown powerdown and from another computer you can move the contents of /previous into the root of the flash drive and power everything back on and you'll be back running

You should post your diagnostics, what share in particular you're attempting this, and also ensure that you are properly connected to the server as the applicable user you created in Unraid

Looks like an issue with corruption on the flash drive and the boot files. Try moving the files from /previous to the root of the flash drive and then attempt the upgrade again.

Because it's not completely obvious, you're doing transfers when the system is running Windows and when it's running Unraid from the same source computer? Also, what share are you writing to when using Unraid?

It's showing that it has a 2.5G connection. Where are you seeing that its only running at 1G?

First things you should always do in any situation like this is run Memtest from the boot menu for at least a couple of passes. To roll back though, all you have to do would be to download the appropriate .zip file from https://unraid.net/download Shutdown the server, pull out the flash and replace all of the bz* files in the root of the flash drive with those in the archive. Power back up. Alternatively you can also create a folder on the flash drive named "previous" and put all of the files in the root of the archive into that folder and then Update OS will offer you a rollback option

From Main, Boot Device, Click on Flash then Syslinux Configuration Add this to the Append line on which ever entry you have as default (the "radio" button that's selected) pci=noaer It should look something akin to this after the fact Reboot and see if that fixes you up

Is the nvidia plugin installed?

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