JonathanM

https://docs.unraid.net/unraid-os/manual/shares/user-shares/#moving-files-from-a-pool-cache-to-the-array

https://docs.unraid.net/unraid-os/manual/storage-management/#backing-up-the-pool-to-the-array @SpencerJ, could you put this on the list of things to be updated? It's still using old cache allocation terminology.

Then there is no way to do instant moves, because the data must copy from one disk to another.

What path do you have this set for?

A user share is a root folder on an array disk or a pool. To move instantly, the data must stay on the same disk and only rename the path. If the user share allocation method would dictate the data NOT stay on the same disk, a move needs to be a copy and delete action instead of a rename. Why?

Are you sure you didn't go to the legacy docs? The link to the official documentation is at the very bottom right of the GUI. https://docs.unraid.net/category/manual

Google "bathtub curve"

It would have been polite to ask the OP first if they mind if you hijack their thread. Normally you should start your own thread, since causes and fixes are rarely identical even if the symptoms match. If the OP has further issues and gets advice, it could be harmful to your situation to follow that advice. A read check at this point is pretty useless, but you didn't post enough info to really be helpful. You didn't post your diagnostics, and you cut off the part of the screenshot that shows whether the emulated drive is mounted correctly.

Take a look here. tldr: create a text file named stop in the config folder.

Having all files deleted is very much NOT empty, if that's what you were implying. Removing drives and keeping parity valid only works if you write zeroes to the whole partition while the drive is still part of the array. Typically that's more time and trouble than it's worth, so most people rebuild parity. Deleting a file simply updates the file system to allow new files to be written to that area, it doesn't actually remove the data.

Yep, on server OS the console has an id, and each user has their own id. If you use the user id, they have to have an active session to connect. That was why I asked whether or not you had the same version of windows on both machines, because server is treated differently and you said both were the same, so I didn't know what the issue could be if you had already configured the laptop server os successfully, there is no reason why the vm server os would act any differently. Glad you got it figured out!

https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/remote-control/use-teamviewer-remote-on-windows-servers/

Teamviewer must be configured differently on Windows Server. Have you followed the instructions specific to server editions?

Looks like your VM is using a private IP firewalled behind the Unraid IP. You need to change the network for the VM template so it gets an IP from your router instead.

Probably need to ask in the iscsi support thread, since iscsi is not built in to the Unraid.

that looks like a teamviewer version, not a windows version. https://en.wikipedia.org/wiki/List_of_Microsoft_Windows_versions#Server_versions

Do you have any ports forwarded and / or DMZ set to the server IP?

To clarify, you are running the same version of Windows Server on the laptop?

Did you do the steps in the order listed? It doesn't look like it to me.

Make sure you backup the license key file in the config folder and copy it back so the USB drive stays licensed.

Most do parity checks once a month, but if all your drives are active most of the time and you have notifications working so you can act on any errors, you can extend that if you wish. The biggest reason to do a parity check is to ensure all your drives are 100% healthy across the entire surface, which is what is required to do a recovery of 1 failed drive. Also, if you do ever see parity errors, it means that until parity is correct, a failed drive rebuild will not be fully accurate.

How is that different? It looks like they say exactly the same thing with different wording.

Yes, you can mount external shares using the Unassigned Devices plugin. As you suspect, it will complicate matters, but it's doable. Biggest issue I see on the forums when someone is using remote storage is disconnects, it's imperative that the remote storage is always available whenever Unraid is started. You must have a rock solid network.