Squid

The answer is the same as my original reply to your original question. IE: No, because it's a pointless section that bears no relationship to reality at all.

Not super easy, and definitely not worth the effort Yes Reason why the answer the the first question I listed is not worth the effort is because you simply stop the service (Settings - Docker), delete the Image (still on settings - Docker), re-enable the service and then hit Apps - Previous apps and check off what you want. Less than 5 minutes on even the slowest broadband connection and you're back in business with no thought process or recollection involved

Yeah, if you copy / paste via SMB (ie: Windows Explorer), the size will massively expand, especially if you use Plex Fastest method would be to make a backup via AppData backup plugin, then change the SOURCE of the backup to reflect the new cache pool and then restore. (And finally adjust the default appdata setting in Settings - Docker)

Reseat the cabling. SATA is not known for being a particularly robust connector.

Delete the contents of /ssh and /ssl on the flash drive and reboot

The diagnostics are after you rebooted, so we can't see what you saw... But to get the obvious out of the way, have you looked at https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-819173? Have you done a memtest? Also try disabling the XMP/AMP overclock on the memory...

Post your diagnostics and wait for @JorgeB to pipe in

Coming up on 5 years old. It all looks good except for those attributes, but if you've got one it won't hurt to replace it.

Probably HPA (or a shucked drive) https://forums.unraid.net/topic/61635-removing-hpa-from-drive/

Honestly, with any random motherboard if you're not going to be utilizing the component, it should get disabled in the BIOS (ie: Wifi, Bluetooth, serial ports, any lights etc if you can't see them etc). If nothing else, you save the power and in theory it's always a more stable system. And you should be able to do a BIOS update within the bios itself, but will need a monitor and keyboard attached.

Raw read error rate should ideally be 0 on WD smarts, yours is 2 Seek error rate should also I believe be 0 on WD, yours is 1 And 3 UDMA CRC errors (usually this indicates connection problems) of 3 The thresholds are all within limits, so not an urgent problem, but those attributes would all account for the read errors being listed within Main, and the system worked as designed and re-wrote the offending sectors with the correct values recalculated via parity.

Unlikely the syslog filling would directly cause a reset. But, your bluetooth dongle is giving the system a heart attack. Try a different USB port, ideally one of the 2.0 ports on the back of the board. Also, have you run a memtest yet? You might also considering disabling the overclock (XMP) on the memory within the BIOS Your BIOS is also out of date on the motherboard.

I've got 2 RSV-4411's -> My thoughts I've run across a drive one which it and it alone refused to work in one specific slot. Move it to another slot and everything was fine. Any other drive worked perfectly in that slot After inserting the sleds, always always give them another push. Whenever inside the case, always always give each of the 12 sata connections a push Since Molex tends to be rather rare nowadays, limit your use of adapters if at all possible. Always buy a supply that gives you the most amount of molex connectors (on different cables) rather than use adapters I've had nothing but trouble with using SSDs in the hotswap, even when they connect via the motherboard ports. I always instead just velcro them to the inside of the case and only use spinners on the hotswap. Certain drives will never light up the activity light on the sleds. Not an issue and nothing to worry about. All in all a great case, and absolutely insane value for the cost, but you do get what you pay for and the case has some quirks.

No

I've never had a problem with any container using SMB shares. but, I suppose it is entirely possible. I would try setting "slave" as the access mode on those path mappings when you edit the container

If you format the emulated drive, the rebuild will reflect a formatted drive. IE: You will lose data. Formatting is never part of any rebuild operation.

How is it connected? Also, not that this is the going to be the issue, but on permanently connected devices you're better off adding the drive as an additional cache-pool rather than mounting it via UD

Connect to the server's GUI via https://IP-Address (Note https not http) (and accept the browser warning that will appear) Then from settings, Management Settings, set Use SSL to be "No" But, you should still be able to even use that redirect/SSL. Probably all that needs to happen is the DNS record needs to be updated (which you can also do via Management Settings)

If Jon's got a picture of Tom in his office I'd be worried

The LSI is appearing 01:00.0 Serial Attached SCSI controller [0107]: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 [1000:0087] (rev 01) Subsystem: Hewlett Packard Enterprise H221 / 9207-8e [1590:0042] Kernel driver in use: mpt3sas Kernel modules: mpt3sas But, it's firmware is also I believe very out of date Dec 17 19:11:04 PinFish kernel: mpt2sas_cm0: LSISAS2308: FWVersion(11.10.07.00), ChipRevision(0x01), BiosVersion(07.20.10.00) I think that P20 is the version that you should be running.

If you're looking to run (for all intents and purposes) a VM as a container then I'd just install WebTop from apps. Turnkey solution

Just stop Docker (settings, docker) Then delete the image, then re-enable the service followed by Apps, Previous Apps. Check off what you want and you're done in 5 min

Which slot is the card in? Did you change the BIOS settings to effectively disable slot 2 by forcing slot 1 to be x16? Can you enter the "bios" of the LSI card? Post your diagnostics