JorgeB

Yes, that should work.

If the pool name started with mirror that is not allowed now, since it's reserved. Add a new pool with an allowed name, assign bot pool devices, leave the filesystem, set to auto, and start the array to import the pool.

Emulated disk1 is not mounting; check filesystem on it.

You can just use it as a normal pool.

Random reboots are almost always a hardware issue, start by running memtest from the boot menu, or because memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

Tailscale is also a good option IMO.

You can still share the pools using disk shares (if enabled)

That suggests a specific issue with that VM or vdisk, it may not be easy to troubleshoot. If you can, copy the data to the new VM and start using that one.

It should use TPM for licensing, no flash drive is required.

Do you see the same if you create a new VM using a new vdisk (same OS)

You can transfer the license from the old TPM to the new one, either yourself if you are under the limit or contact support if needed.

Disks just dropped offline, looks like a power/connection problem.

SMART for parity looks good, start the array to see if the emulated disk1 is mounting and post new diags.

That shoudl work. It's the same, it's still under /boot

Appdata should not be moved over SMB, either transfer the drive or make a local copy, docker image can be recreated (or also copied locally)

Emulated disk mounted, which is good, check contents to see if they look OK, also look for a lost+found folder.

FWIW, I just partitioned a flash drive with Windows 11, copied Unraid 7.2.6, booted, updated to 7.3.0, and it's still booting correctly, so it's not a general Windows issue; it could be with some specific flash drives, or there are other factors at play.

I would think that 50 GB would be more than enough, and you can expand it later if needed.

Try recreating the docker folder as a docker image. Many times I've seen strange errors with docker folders https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#re-creating-the-docker-image-file Then: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#reinstalling-docker-applications Also see below if you have any custom docker networks: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/docker-troubleshooting/#restoring-docker-custom-networks

I never used the plugin but you can still use the "boot device backup" function from the GUI, or the Connect cloud backup.

I'll test that because I think it should still work.

Yes, just need to have a copy of the current /config folder.

FCP doesn't yet support shares using two pools, you can report the issue in its support thread.

I assume the crash was between these timecodes May 18 20:43:29 UnRAID1 emhttpd: read SMART /dev/sdk May 18 20:59:54 UnRAID1 plugin-manager: dynamix.unraid.net.plg installed If, yes, there's nothing logged, suggesting a hardware issue, in this case my first suspect would be the CPU, since there have been dozens of cases with these CPUs, some users are on their 3rd and 4th CPU.

Please post the diagnostics.