JonathanM

Unraid must have direct access to your licensed USB stick. Running Unraid virtualized is unsupported, it's intended to be run bare metal and used to host VM's, docker containers, and storage pools. It's not forbidden, you are certainly welcome to experiment with it, but just know that any issues you encounter will need to be demonstrated to happen when running bare metal, as no official support is offered for running Unraid as a VM. There are plenty of folks virtualizing Unraid, so look around this section of the forum for tips and tricks discovered by other users.

Normally the docker.img file would be on a pool, not on a parity array disk, and mover should not be attempting to move it. Does that docker.img file exist both on disk1 and on a pool, /mnt/<poolname>/system/docker/docker.img? If so, only one would be actually in use, so the latest dated file should be kept and the older file should be deleted.

Did you happen to mean tps63070? I couldn't find a reference to your number.

I've had better luck doing a disk image backup from the running bare metal machine, then doing a restore to the VM. Acronis has some advanced migration options that help with moving a windows install to what is basically new hardware.

So the new VM worked fine up until the point you overwrite the img file? Maybe the disk format type is set incorrectly in the template?

Try setting up a new VM with the same version of Ubuntu, once that is working overwrite the vdisk file with the migrated copy.

Have you tried nomachine?

Some motherboard models won't allow the groups to be changed. Small chance BIOS upgrade or changes may help. If not, different model motherboard may be required.

Does this help?

Why not use the "stop" file? Doesn't exist by default, but if you create a file formatted the same as the go file in the same location (USB boot stick) it will be run on shutdown.

Would it be worth adding an automated check with a warning, so people unaware of the situation would get a heads up when they first install said disk in Unraid?

Parity can only replace a drive if all other data drives are good. Parity drives by themselves are worthless, they contain no data. To rebuild a data drive all the other data drives are needed, plus parity. Consider this scenario. 2 Parity drives, 10 data drives. For some reason, doesn't matter how for this example, 3 drives die. If all three dead drives are data drives, you just lost all the data on all three drives. If, however, both parity drives died, and only 1 data drive, you only lost that single drive of data. If data loss is inevitable, as it is when you exceed the failure tolerance of a RAID or Unraid array, only Unraid gives you the opportunity to keep the data on the drives that didn't fail. I'd rather lose the parity drives than the data drives.

Why? I'd rather lose 2 parity drives than 2 data drives. Losing parity means recalculating it from known good data drives, losing data drives means trusting that parity was perfectly in sync when the data drives dropped, which is not always a sure bet.

Assuming you already made the allocation larger and want to expand the partition to fill it, the easiest way is to create a "utility" VM with all your management tools like gparted and such, then add the Ubuntu Server virtual disk as a second disk to the utility VM. Obviously the server VM must not be running while you work on it. I'm sure there are command line utilities to accomplish it inside the server itself, but it's easier for me to just mount it to another VM.

What are you seeing on the monitor directly plugged in to the video card?

Try installing nomachine in the VM and access it using nomachine on your desktop to see if it's actually unresponsive.

Probably because you didn't find the correct thread. Read through the support thread, your issue is covered there. DON'T DELETE /mnt/user/appdata

Keep in mind that your license key file on your USB stick is still valid for current versions, so what you could do is build your new system, get it running with a trial key, migrate your data, then when you are done with the old system you can use the old key and license with the new install. As long as you make good labeled copies of the USB sticks each time you make changes, we can help you accomplish pretty much any end goal configuration you desire. I don't think it's fair to expect information from an almost 10 year old thread to still be perfectly valid. Technology has moved a long way since then. When you get ready to move forward, I recommend you create a new post in the main general support area, briefly outlining where you are and where you want to end up. Include the details of the hardware you are currently using and are willing to purchase for your updated setup.

What devices are in group 9?

binhex I don't see that you asked in the support thread for that container.

As JorgeB said, migrating just the license key file and super.dat to a fresh install would be best to accomplish an upgrade. Also keep in mind that the file system used in V5, reiserfs, is no longer being updated, doesn't support very large disks, and is going to be removed in the not too distant future. You will need to copy your data to disks with current filesystems. Perhaps it would be better to set up a new install with fresh disks, then copy the data from the old drives using the Unassigned Devices plugin.

Opinions vary. If your budget is limiting, a good backup strategy is more important, but if you can afford it, ECC is an insurance policy.

https://docs.unraid.net/unraid-os/release-notes/7.0.0/ Read the first bit, probably should read the whole thing before updating anyway.

Contact support.

Did you get your uniform yet?