Squid

By itself, that error means the docker.img needs to be deleted and recreated https://forums.unraid.net/topic/57181-docker-faq/#comment-564309 But you have some other issues the Fix Common Problems is complaining about. Can you post your diagnostics

not currently

Yes, except that if I set up my system as 6.9.2 or 6.10 the scheduled time mover runs doesn't log that error (but will display it if I simply run mover at the command prompt)

They always have showed up in mine. Never even considered that they wouldn't since it only makes sense to me that they should be there....

Safe to ignore. Happened during processor initialization and is fairly common for some hardware combinations at that point in boot up

Settings - Disk Settings, Utilization Settings

That is the link for 6.8.3 You should be using the link for 6.9+ which is in the OP Everything else though implies something wrong with your settings. Post your diagnostics

You don't have user shares enabled in Settings - Global Share Settings. Using the server like that isn't an "issue" per se, but it is very oddball, especially since probably a lot of containers etc are going to reference /mnt/user/.... and if you're not careful and adjust every reference to instead be /mnt/diskX (or /mnt/cache) you're going to wind up in trouble.

It's not an error. Its simply a note the to actual devs of Linux so that they can see if you send them syslogs etc they can tell that it's not a stock linux kernel

Yeah, just uninstall it and then search for cAdvisor in CA and install that. It's simply a graphical way of showing what your system (in particular containers) as up to. Personally, I far prefer NetData though.

Yes

Dec 13 05:02:32 SimServer kernel: FAT-fs (sda1): error, corrupted directory (invalid entries) Dec 13 05:02:32 SimServer kernel: FAT-fs (sda1): Filesystem has been set read-only Try rebooting if the system during it's checks on bootup can't fix it, then pull the stick and run the file system checks on another computer. You might also consider restoring your backup (if you have one) onto the flash drive.

Its a USB2 adapter, but it will work

Very recently, as over the course of a month (every month), every single container in CA gets pulled to look for stuff like this Thanks

It supports XFS. You run the trial version first to confirm before actually purchasing.

Just in case anyone has installed Notepad++ from anywhere other than the official website, https://www.bleepingcomputer.com/news/security/malicious-notepad-plus-plus-installers-push-strongpity-malware/

@SpencerJ

That is a major surprise

Depends upon the value to you of the data. If it's 100% irreplaceable and your wife will never let you forget that the baby pictures are gone, then easeus is the way to go. But, in that case you should have a backup of it anyways, in which case do the repair. If it's simply media that can be redownloaded, then I'd do the repair. If you do the repair, then you can't do easeus as the filestructure will be changed. But if you rebuild onto another disk then you have the best of both worlds. You can run the repair against the replacement disk and still have the original to run with easeus.

Yes, but the devices still have to be isolated via one of the ACS override options in Settings - VM Settings

It was mentioned earlier in this thread. If you're attempting to passthrough the AMD card, you've got to isolate it. Those current devices in group 1 aren't conducive to passthrough, so you'd have to use one of the ACS override settings.

Post in the Unassigned Devices thread with your diagnostics

Did you fix this 2021-12-12 23:39:55.344+0000: 13274: error : qemuProcessReportLogError:2097 : internal error: qemu unexpectedly closed the monitor: 2021-12-12T23:39:55.300339Z qemu-system-x86_64: -device vfio-pci,host=0000:03:00.0,id=hostdev0,bus=pci.4,addr=0x0,romfile=/mnt/disk3/isos/Windows/Saphire.RX5708GB.8192.191031.rom: vfio 0000:03:00.0: group 1 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver. By isolating (Tools - system devices) what you're attempting to passthrough from the OS?

Those mini flash drives aren't particularly recommended primarily because they tend to run (very) hot, and heat is something which doesn't play well with any electronics. YMMV Personally, I have never had any problem with any flash drive (USB2 or USB3) I've ever thrown at Unraid (even generic ones), but I'd never purchase a mini one for any reason. If only because I'd probably lose it just after opening the package. If space is a major consideration, then https://www.amazon.ca/SinLoon-Female-Motherboard-Header-Adapter-Dual/dp/B0878S6BD5/ref=sr_1_28?keywords=internal+usb+adapter&qid=1639353920&sr=8-28 works wonders.

Just a comment (not that you're incorrect on any given point), But there is no such thing as LTS with regards to Unraid. 6.9.2 is the latest stable. 6.10 stable is just around the corner. It's always advised to keep your server up to date with the latest stable upon release (or soon thereafter) But, you are 100% right that certain things have changed in 6.10. eg: Under 6.9 to set a root password you go to Users and edit "root" Perhaps going forward @SpencerJ / @jonp could make sure that going forward historical documentation is available.