trurl

Also possible your flash drive has disconnected. Use a USB2 port if you have one, they tend to be more reliable for booting.

I don't know if Vendor is required, but it must have a unique GUID.

Are you sure your server can reach the internet?

The syslog in your diagnostics is just after reboot. Go to Settings - Syslog Server and configure it so you can retain syslogs to try to capture more information before crash. Some other things I noticed, though unlikely to be the cause of crash. Why do you have 64G allocated for docker image? Have you had problems filling it? 20G should be more than enough and if it isn't you have one or more of your docker apps misconfigured. See below for more on this*** Your system and appdata shares have files on the array. This will impact the performance of your dockers. They should be cache-only or prefer, with no files on the array. ***In addition to misconfigured dockers filling docker image, it is also possible for them to fill memory, which could cause a crash. A docker application will fill docker image if it writes to a path that isn't mapped to Unraid storage. A docker application will fill memory if it is mapped to a path that is not actual storage since all other paths are in RAM.

The syslog in your diagnostics is just after reboot. Go to Settings - Syslog Server and configure it so you can retain syslogs to try to capture more information before crash.

Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

Unraid is NOT RAID. The parity array is not exactly like any standard RAID implementation, though it is similar in some ways. Each disk in the Unraid parity array is an independent filesystem. Each file exists completely on a single disk, there is no striping. Folders can span disks (User Shares), but files cannot. Various btrfs raid configurations are supported in the cache pool. See this Wiki Overview: https://wiki.unraid.net/UnRAID_6/Overview

Deleted XML due to inclusion of OSK

You can go directly to the correct support thread for any of your dockers by simply clicking on its icon in the Unraid webUI and selecting Support.

I have split your post into its own topic in the appropriate subforum. The thread you had posted in was not about Windows VMs at all, it was about accessing Unraid and its files over the network from Windows computers.

You are correct to be concerned that Unraid will not recognize the disks since their identifier will change. The very most important thing is to not accidentally assign a data disk to the parity slot. As long as you don't do that you should not experience any data loss. If you have enough of the actual serial number to work with, then that should be enough to allow you to reassign the drives correctly. Probably the actual serial number of each disk is printed on each disk label. When you first boot with the flash in the new system, Unraid will not attempt to start since the expected disk identifiers are not the same. You just need to go to Tools - New Config and assign the disks, check the box saying parity is already valid, and start the array. A non-correcting parity check would be a good way to confirm that things are working well.

Why have you allocated 40G to your docker image? Have you had problems with it filling up? 20G should be plenty and if it isn't you have misconfigured one or more of your docker apps. And your system share has files on the array. Disable docker service (Settings - Docker) and delete your docker image. Then do the fix johnnie.black mentioned. Then recreate your docker image (20G) and reinstall your dockers using the Previous Apps feature on the Apps page.

Now that you have been approved, go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.

I have discovered some XML posted as attachments in this thread that contain the OSK also. I am currently going through this thread and similar threads to delete those attachments. And in future, I will simply delete any XML that contains OSK rather than taking the trouble to redact the OSK myself. However, I would much rather not even look at these threads since their topic doesn't really interest me. If anybody sees further instances please report them because I am not planning to spend my time policing these threads.

@databaseland I have deleted 2 of your attachments because they contained OSK. If you want to post those, edit them so the OSK is not included. Henceforth, my policy with the numerous people who are posting OSK will be to simply delete the entire XML instead of taking the trouble to edit it for them.

And that post was reported to the moderators, so I guess I will take care of this for @rorton

SSDs are not recommended in the parity array. They can't be trimmed, they can only be written as fast as parity, and there is some question whether some implementations will invalidate parity.

Login (root with no password unless you have set one) and type shutdown and wait for it. Then put your flash in your pc and delete config/network.cfg to make it use default network settings.

Lots of people are running Unraid successfully. Do you need help?

It seems like you aren't talking about Unraid. Does your post have anything to do with our forum?

Sounds like a browser problem. Have you tried clearing cache?

Your "this guide" link just goes to your own post.

How exactly did you accomplish this?

You can probably do most of what you want with dockers instead of bothering with VMs.