Squid

Should be noted ( *IF* I've got the model number of your RAM right ) that it is listed as being incompatible with your board in a 4 dimm configuration on MSI's QVL (But there are other 3000MHz 16GB dimms that MSI does list as being compatible in 4 DIMM configs) Oh, and a side note for the diagnostic pros out there. system/meminfo.txt does include the actual info on the sticks, including part numbers when running 6.8+

Yes No Yes All this assumes though that the HBA's are passing through the actual name of the drive as the device and not something specific to them (with HBA's in IR mode will tend to do)

ps command

Any long running commands will get aborted after they are finished. I've tried many ways of terminating, and I keep running into the same problem. I cant kill the PID of any long ru ing command (rsync)

Unassigned disks are not checked

Errors only are only cleared when they aren't found on a subsequent rescan

I don't believe that currently there is a way around the update available showing up constantly for the local repository. For a private repo, you could simply build it (docker build) on the local machine

Tags like "Branch" are unofficial additions created by CA and documented in the link provided in the OP. Beyond that, I consider the xml to be an internal data structure and not needed to ever be manually edited, as every thing that you can do by editing the xml can be done via the GUI (except of course for the additional CA tags if needed) https://forums.unraid.net/topic/57181-real-docker-faq/page/2/#comment-566100 You can't do it by default. Needs to be added to any given template

From the Main Tab, if you click on the hard drive icon next to the model it will bring up the error log for the drive, and then it'll be pretty obvious which one. One caveat though is that you may disturb other drive(s) cabling in the process of reseating the one thats needed, so you may / should do them all.

I would first try reseating the cabling to the drive and at the mobo. SATA connectors aren't exactly famous for making a good connection

With prefer if the cache drive gets full, then any new files in appdata will get written to the array and then when space frees up they'll get moved to the cache drive. With only the write will fail if the drive is full.

No queuing. At the time it runs, it checks the use cache settings on the share and moves appropriately. Sounds like after disabling the use cache, you never re-enabled it.

Post your diagnostics

Since it appears that 99% of the time "nobody cared" isn't a real problem, I'll just get rid of the test for the time being.

Check your boot order in the BIOS and make sure that the USB stick is the first listed.

As an aside, don't ever worry about making a backup of docker.img. It's so easy to recreate it that no one ever recommends to back it up.

Because the appdata share contains files on the cache drive. (Although generally for performance and hydro savings you would generally want appdata to be confined to the cache drive and then back it up) To fix (if you want it on the array), change the settings to use cache: Yes and then settings - Docker, disable the service. Main - Array Operations, run mover. After its done, change the settings back to "No" and then re-enable docker To have the share confined to the cache drive, do the above but set it to use Cache: Yes in the first step and disregard the last step

Yeah, as far as the Appdata Backup / Restore plugin is concerned, nothing changes. If you're changing the SSD, then you do that, create your appdata share appropriately and run the restore

A restore is the opposite settings of the Backup. IE: You set the plugin up for how to backup, and don't change anything when you want to restore. It'll figure it out.

And turn on mirror to flash drive in Settings - Syslog Server After it glitches, post the syslog file stored on the flash drive (logs folder)

It really appears that you did check off the box to format the drive.

Have you formatted the 2 disks you have attached to the system yet? Neither one is mounting Nov 22 00:38:47 Tower emhttpd: shcmd (35): mkdir -p /mnt/disk1 Nov 22 00:38:47 Tower emhttpd: /mnt/disk1 mount error: Unsupported partition layout Nov 22 00:38:47 Tower emhttpd: shcmd (36): umount /mnt/disk1 Nov 22 00:38:47 Tower root: umount: /mnt/disk1: not mounted. Nov 22 00:38:47 Tower emhttpd: shcmd (36): exit status: 32 Nov 22 00:38:47 Tower emhttpd: shcmd (37): rmdir /mnt/disk1 Nov 22 00:38:47 Tower emhttpd: shcmd (38): mkdir -p /mnt/disk2 Nov 22 00:38:47 Tower emhttpd: /mnt/disk2 mount error: Unsupported partition layout Nov 22 00:38:47 Tower emhttpd: shcmd (39): umount /mnt/disk2 Nov 22 00:38:47 Tower root: umount: /mnt/disk2: not mounted.

I'm assuming that its disk 7 your talking about It had file system corruption, and then it looks like you did format it instead of running the file system checks Nov 21 18:03:19 PlexServer emhttpd: shcmd (297): /sbin/wipefs -a /dev/md7 Nov 21 18:03:19 PlexServer root: /dev/md7: 4 bytes were erased at offset 0x00000000 (xfs): 58 46 53 42 Nov 21 18:03:19 PlexServer emhttpd: shcmd (298): mkfs.xfs -m crc=1,finobt=1 -f /dev/md7 You probably just need to stop / start the array to get access back to the shares.

Switch nerd pack to not install atop