Squid

Probably best to ask in the project link (ie plex's own forums)

You were running the appdata backup plugin, and if you had it set, then there's also a backup of your flash drive made (Although I recommend using the MyServers plugin even without remote access to make flash backups)

Post your diagnostics

It's all based upon what the dockerfile itself reports. When you're on br0 or host it's all pretty much pointless

Aug 22 18:52:40 Unraid kernel: BTRFS info (device nvme0n1p1): forced readonly Personally, I am not a fan of using BTRFS on single device cache pools (Only use it on multi-device pools) and would much rather use XFS. I'm going to leave it up to @JorgeB to help as he is without question the resident guru.

https://forums.unraid.net/bug-reports/stable-releases/683-unnecessary-overwriting-of-json-files-in-dockerimg-every-5-seconds-r1079/?do=getNewComment&d=2&id=1079

What you want to do is either make a multi-device cache pool so that there's redundancy without any performance loss, or backup the vdisks periodically.

Can your server even hit the internet? EG: After a reboot does the Apps tab work?

My opinion: You purchased ECC memory and are using it so that if/when one starts going bad you can replace it. Sure the errors are currently being corrected, but that is simply the stick telling you "replace me". If you have ECC memory and chose to not replace the memory when errors begin to happen then I'd question why you even bought ECC memory and a compatible CPU / motherboard in the first place.

I didn't say that. I said the mce happens on certain hardware combinations when initializing the cpu cores and is nothing to worry about. Its on the boot menu. If you're booting via UEFI, then you'll have to temporarily switch to Legacy in order to run it (or download a new stick from https://www.memtest86.com/)

Nope. There is definitely something wrong with de_DE somewhere, and what you were seeing in CA (and what I fixed - in retrospect didn't need to be fixed, but the solution actually makes sense) were simply a symptom on the root cause elsewhere. @ich777 @bonienl?

You should determine why its slowly filling up (eg: Container Size on the docker tab) and then fix that (eg: limit the logging, etc)

The mce listed happened during core initialization, and isn't anything to worry about and happens on certain hardware combinations I would start with running a memtest for a pass or two

Your parity drive is ready for the scrap yard 5 Reallocated_Sector_Ct PO--CK 073 073 005 - 7456 Disk 1 is above my comfort level 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 952 Disk 2 actually looks good, but simply a connection issue. Reseat everything to it, then rebuild it. Only after a successful rebuild should you replace the parity drive. Because of the massive amounts of reallocated sectors on the parity drive, you may have some corruption And also, make sure you have notifications enabled so you'll get an email / push notification if your drives degrade further (and if any replacement begins to degrade)

Those diagnostics show that the docker image is empty. Apps - Previous Apps, check off whatever you want and hit install.

The new controller is reporting the SNs differently. Take a note of all the disk assignments and then Tools - New Config. Then reassign the drives accordingly anf check off parity is already valid when starting the array

Never mind. Got the chain of events down to replicate this. Errors occur if you update the active language. (although I couldn't replicate via updating nl_NL while it was active) Fixed next release. Solution in the meantime is to simply reload the Apps tab. Thanks for reporting.

Any other German users having problems within CA?

What version of Unraid? I tried installing German on 6.10-rc series, 6.9.2 and I don't get any error at all.. (And the error directly relates to either the translation itself or Unraid's translation routine not Community Applications specifically) Try removing the language (you'll have to switch to English first), then reinstalling it and switching back. Perhaps @bonienl can determine what's wrong

Interesting that the drive doesn't even appear in the smart section of the diagnostics. Turn off the server Replace the drive Turn on server Assign the drive to disk 1 (the one that will show as being missing) Start the array If anything comes up as unmountable, do not click format Contents will rebuild onto the drive.

Does accessing via the IP address work? Does the server have internet connectivity?

@ljm42 you will want to read this thread and investigate accordingly

Known issue. Global share settings, enable user shares

You'd need to post your diagnostics

Settings - Docker - Advanced View with the service stopped