JonathanM

USB is problematic for array drives, inconsistent identification and random disconnects are just a couple of the issues that are prevalent with USB enclosures. If you can't use internal SATA connections, the next best option is SAS, it's much more suitable for external drive connections. Some people have successfully used USB, but figuring out which controllers and drive bays work at all, let alone consistently, is a real problem.

Diagnostics taken after the error has occurred may hold a clue.

While we are discussing the new notifications viewing system, I'd like to propose a small tweak. Instead of only changing the color of the bell, why not change from a green bell to a yellow exclamation point to a red asymmetric star, like a cartoon splat or crash symbol? That way colour blind people can still tell at a glance which type of notification is showing. The highest level of unread notification would determine which icon was shown on the header. (BTW, I find it amusing that last year's "ditch ALL the color and go to flat white icons" is slowly going away)

Can't speak specifically to that card, but typically RAID cards with batteries are there to keep power interruptions from corrupting data in flight, as they typically have a not insignificant amount of RAM on the controller for caching writes. If the card is in IT mode and all transactions are handled by the host, I don't think it's needed. Question is, can the card really be put in IT mode, or is it always going to be "in the way" of Unraid managing the drives?

nomachine works well for me.

Lots of little changes, but the major 6.12 feature was ZFS, because there was a small but very vocal group that insisted ZFS was the solution to all their issues. In reality, very few people currently using Unraid really benefit much from ZFS, and it brings with it a good deal of complexity and adds more issues. It will take a while to get things calmed down.

Another thing to try would be a different VGA cable. Some cables don't have the pins connected that transmit the monitor ID back to the board.

Does it still act up with 6.12.2 in safe mode?

This looks like it may be useful to you. https://fohdeesha.com/docs/perc.html

See here or here Depending on which container you are running.

Disable docker service.

Try here, that's where the template support link leads. https://github.com/monicahq/monica/issues

I think adding a warning requiring typing YES to acknowledge before the wipe command is executed would be sufficient. Maybe it would be a good idea to add a new section to the "New Config" area to manage the resetting of pools. Limit the current new config reset to parity array only, and add individual line items for each currently defined pool.

Arguably the parity drives are the LEAST valuable, as when they fail you have no data lost, and the chances of losing data then rests on the data drives. Here is how to best visualize this. 2 parity drives allows for 2 simultaneous drive failures, the 3rd failure will cause the total data loss of all failed drives. So, no data loss until the 3rd failure. If the 2 parity drives fail, and then a data drive dies, you ONLY lose that single data drive's content. If 1 parity and 2 data drives die, you lose both data drives worth. If, and here is the takeaway, both your parity drives are fine, but you lose 3 data drives, ALL the data on ALL three drives is gone, and the 2 parity drives can do nothing to recover any of that data. So, best case scenario, in a 3 drive failure, is for BOTH of the parity drives to die. If you have less faith in a particular drive because it's not "new", then the best place for it is in a parity slot where it can do the least harm if it fails. Now, the parity drives do get writes for every bit of data sent to any drive in the parity array, so I'm not saying use junk drives for parity, just statistically speaking you want the parity drive(s) to fail, not the data drives.

Safe mode

Not necessarily that specific adapter, but yes, a wireless game adapter, or some other piece of equipment that translates WIFI into wired ethernet. Some routers can be reprogrammed to serve that function, and they typically work better than the game adapters.

I realize this isn't what you are asking, but just saying, "nothing beats the bandwidth of a station wagon full of tape backups". Have you considered getting the system initially synced locally, then just doing differential syncs over WAN?

Why?

So did the domains share move to the vm_machines pool?

Move the vdisk from the array to the pool using dynamix file manager or mc at the console or whatever your favorite file manager is, then change the VM XML to point to the new location. Or, to make it even simpler, assign the pool as the primary location for the domains share, assuming the vdisk is in the domains share, and the array as the secondary location with the mover set to move from the array to the pool. This assumes your pool is big enough for all the content of the domains share.

You can encrypt just a single drive in the array if you wish, and any shares on that drive will be encrypted. You would need to copy all data off of that drive before changing it to encrypted.

Because the boot drive for Unraid has to match the license file.

If you leave it attached I think it will still be detected as a pool member, whether it's in the logical slot or not. Wait for @JorgeB to confirm, but I think you should probably be able to substitute wiping the mbr / partition table instead of physically removing it, but I'm pretty sure you can't allow it to be found as a former pool member.