Squid

Definitely strange. Your BIOS thinks that your flash drive is also a CDROM drive, and reporting it as such. TBH, my first suggestion would be to restore the factory defaults in the BIOS.

Try closing all open browsers / tabs that are open to the GUI, and reboot the system.

From during the bootup sequence: Jun 25 19:55:14 Tower-NAS kernel: FAT-fs (sda1): error, clusters badly computed (450 != 449) In theory, a reboot *should* fix you up, but for the best success, shut down the server, pull the flash and toss it into a Windows / Mac box and run it's file system checks on it (Win: right click on drive, properties, tools, Check) and then try the server again. Worst case scenario, replace the flash https://wiki.unraid.net/Manual/Changing_The_Flash_Device

Download the zip https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/stable/unRAIDServer-6.9.2-x86_64.zip and then overwrite all of the bz* files and the changelog.txt file on the flash drive with those on the zip

Look on the flash drive within the /logs folder. There should be a zip file dated with the time of when you more or less started the diagnostics collection.

SATA is one of the worst connectors ever designed. What you're seeing is due to a poor connection (or excess use of power splitters) a drop off and continual reset of the drive until finally the system gave up and simply disabled the drive. Reseat the connectors (both ends) and rebuild the drive, taking care not to breathe too heavily on any other connections and then rebuild the drive. This can also be caused in some rare cases by EMI interference from trying to make the system pretty inside by cable management. Data (sata) cables shouldn't in an ideal world ever be tied together (so that any EMI is random and not continuous) and never ever ever use tie straps to perform any cable management -> use velcro.

The mce error is more or less a very badly worded message saying that the default driver doesn't work and that edac is being used instead. For the VM issue, you'd want to create a new thread, and include your diagnostics as it's not particularly relevant to this thread.

If you want the file browser to be able to bypass /mnt, then it winds up being a feature request. Similarly with the libvirt.img file being able to be stored as a directory instead of as an image. You're already using the docker as a folder because zfs won't mount it correctly as a btrfs image. If because of the limitations imposed by 6.10 (aka security over convenience), the downgrade until such time as ZFS is incorporated into the system.

You're still bypassing the system. The appropriate place to mount any additional volumes would be within /mnt/disks. The GUI has controls within it to prevent users from installing a VM to RAM etc. And, as the OS evolves and the developers notice errors that they never thought of that users make, controls will be put into place to prevent that from happening.

Offset - Visual thing only, and a bug report already posted about it. Paths - You're bypassing the system and using ZFS to store all of your files, and the GUI doesn't take that into consideration, so you have to type everything in -> by design The mounting issue -> Personally, I'd disable the VMs from running and then try moving the libvirt image onto the array and point it at that and see what happens. (ZFS has issues mounting libvirt volumes as btrfs). If that's not an option, then your best bet is to ask in the ZFS thread, as this isn't particularly an OS issue.

Yes

Jun 25 14:29:53 Deadpool zed[8747]: zed_udev_monitor: skip /dev/loop2 (in use by btrfs) Jun 25 14:29:53 Deadpool kernel: BTRFS info (device loop2): enabling ssd optimizations Jun 25 14:29:53 Deadpool root: Resize device id 1 (/dev/loop2) from 1.00GiB to max Jun 25 14:29:53 Deadpool zed[8747]: zed_udev_monitor: skip /dev/loop2 (in use by btrfs) Try rebooting

You need to post your diagnostics

Configured Memory Speed: 4800 MT/s First thing to do on any crashing issues is to not overclock memory and run things at SPD speeds, not overclocking or using XMP profiles. IE: Run the memory at stock speed of 2400

Is the VM stopped?

The above still applies - Within same share, the file stays on the same disk. Different shares the destination will follow the use cache rules on the destination. Using a rootshare file stays on the same disk

Depends on what you mean by "move" and how you're moving them. If you're moving them between shares, and the destination share is use cache yes / prefer then it will wind up on the cache pool If you're moving within the same share, then the move is instantaneous and the file will stay on the exact same hard drive as the source. If you're using a so-called "rootshare", then the file will also always stay on the same drive.

Yes Via Dynamix File Manager (or alternatively Krusader). If you have a parity drive, then under Settings - Disk Settings turn on Write Method: Reconstruct Write

Segfaults are rather common with Plex. You could run a memtest to rule out any memory issues, but the best place to complain about it is on Plex's forum

You probably added /downloads as a root folder within Radarr (ie: where it stores movies),

It's supposed to IIRC

All of the "games" in Apps aren't games, rather Game Servers (as the Category says). You're not downloading the game (which you have to buy on Steam), but rather a game server which allows you and your friends to connect to to play in your own separate world separated from the rest of the players online (along with other things)

If you already have a parity drive, then the data on D2 will be lost. Without a parity drive installed, data on D2 will be lost if it's not formatted as XFS / BTRFS / ReiserFS Presumably this drive has data on it from Windows (formatted NTFS), so you'd need another drive to add as D2 and then transfer the data over to it either through the network or by mounting the disk with the Unassigned Devices plugin

Plex isn't running (nor is tautuli). Until they are running they effectively don't have an IP address

That doesn't help. If you're passing through the gpu, then you shouldn't be using it for anything else at all. The 2 are incompatible with each other, and the GPU should also be isolated from the rest of the system via Tools - System Devices (same as with any other devices which get passed through).