JorgeB

For licensing issues, you shoudl contact support.

If it happens again, post the diagnostics before rebooting.

The wizard gives you two options: dedicated boot pool and boot+data pool. The default is dedicated

The copy is not logged, but it just uses rsync, look at the monitor output the next time you try it; it shows there, it's done just before the reboot.

There's a problem with the flash drive. Try recreating the flash drive, first backup the current one, then recreate it using the USB tool, confirm the flash drive boots with the stock install, and if yes, restore only the /config folder from the backup overwriting any existing files.

Post the output from btrfs dev stats /mnt/cache

The form is not showing all the extra fields in the bottom; try using a different browser.

These are old errors; they were not monitored before, please post the diagnostics

Post the diags after you get the errors.

It will make the current TPM key invalid, but you can still use the same TPM in the future for a new license, or even transfer this one from the flash drive back to the TPM (flash drives are permanently blacklisted).

These are errors reported by the btrfs filesystem, and they come from before, just that they weren't monitored, though I'm not sure why the buttons are greyed out, they work for me, will take a look Corruption errors mean that btrfs detected mismatched CRCs for some blocks on that device. The first step is to reset the stats, if you cannot do it using the GUI, open a terminal window and type btrfs dev stats -z /mnt/pool_name Then run a scrub and see if more errors come up btrfs scrub start -B /mnt/pool_name

You are able to use them for NBoot, but they do count for licensing.

Server is unable to reach the internet: Could not download current plugin versions This is typically a DNS problem.

Boot with a different flash drive, using a totally stock install, no key needed), and see if the GUI is still slow.

You should be able to copy the appdata share and also the docker user templates folder from the old flash drive (\config\plugins\dockerMan\templates-user) to the new one. Then go to Apps and restore the cotnainers 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 posted above what you can do to try and find out what is causing the array to not stop cleanly.

Have you done any other customizations? I cannot reproduce, and if this were a general issue, there would be infinite posts of users complaining. I would recommend retesting with a new stock installation.

TPM licenses are only blacklisted for the current key, meaning you can then still use it with another license.

Try rebooting in safe mode, if it still doesn't close, get the diagnostics from the CLI.

The problem was likely the reboot, due to the flash drive issues, not the upgrade itself.

Nope, they should all remain assigned after a reboot; it copies the complete configuration from the flash drive. Maybe there was an issue with the flash or some files.

Not sure what happened there, but you should be able to fix the pool by opening a terminal window and typing: zpool detach flash 9144051294089628447

All those FSCK files suggest the flash drive or its filesystem were having issues, you can try restoring only the config folder from one of the backups, all settings are there, if it doesn't work, try the other one.

That should be fine; you would need to see the logs if you still have them.

At the moment you can only use a single or dual drive pool for boot.