JonathanM

Try reformatting the drive with RUFUS
 

Try reformatting the new USB sticks with RUFUS, then follow the normal install instructions.

Have you tried SeaBIOS instead of OVMF?

Too many different goals have different requirements. No way to generalize except to set an upper limit that is rational for some situations, keeping a minimum free space of at least the size of the largest single file that is currently on the disk or a few multiples of that.
 
You need free space if you need to run file system checks, if you get corruption too little free space can keep the repair from completing.

If you stop VM and Docker services, so the menu items no longer appear in the GUI, you should be able to use Dynamix File Manager to move all the appdata folders onto a single disk. Then set the split level to manual, and it should stay on whichever disk you put it, and you can re-enable the Docker and VM services.

Semantics. The backup put the key file that belongs to the old USB stick onto the new stick, so you must obtain a new key file that matches the new stick. That's done with the replace key procedure.
 
I realize I'm saying the exact same thing that you said, just wording it differently, if I'm not clear reply back and I'll try to explain better.

nomachine

This guy has many videos encompassing pretty much all Unraid can do, have a poke around and see what you see.

What result do you get when you ping your duckdns name?

Can you log in with SSH if you set "Use SSH" to Yes on the Management Access page?

Assuming you have the file manager plugin, click on the "view" icon at the far right of disk1, select all, move, and select disk 2 as the destination.

Thank your lucky stars that you didn't blow up all your drives. Modular cables are not always compatible, EVEN from the same name brand.
 
Unless you know how to operate a volt meter and test the pinouts before powering your drives, NEVER reuse modular cables with the different PSU, just keep them together as a set.

Either
add more RAM
limit the amount of RAM your containers are allowed to use
quit using the containers that use too much RAM
set up a swap file on a pool disk (not officially supported, but has worked for some in the past)
 
Keep in mind that the OS unpacks into, and runs entirely from, a RAM disk, so killing processes that are consuming excessive RAM is the only defense against total crashes. It's also possible that you have something writing to RAM, since all the typical OS locations are in RAM instead of on a hard drive. If a file is being written to a location not mounted to one of your array or pool disks, it's writing to RAM.
 
Without you taking the steps to figure out which container(s) are causing the overflow it's tough to help. The VM reserves as much as it's assigned, and that chunk is untouchable to the OS, so even if the VM has free RAM the OS can't use it. Best to reduce the VM RAM to the smallest possible amount, and let the OS manage the rest.

Perhaps this?
https://www.gbmb.org/tib-to-tb

Update to 6.11.3

Upgrade to 6.11.3

Sure, just use BTRFS

Yes, if you set up a new flash drive with a trial, purchase the license, then copy the entire config folder to the newly licensed flash without the old *.key file.
 
Since you say you are having issues with the flash drive I'm assuming you are working with backup files from the drive, so just make sure you keep the key file with the physical key it was issued to, and overwrite the rest of the config folder's content with the active server config files. Probably should just remove the old dead *.key file from the backup you are working with, and make a separate copy of the newly issued key file and label it to correspond with the new physical USB stick.
 
I'm not sure how clear I was, so if you have questions just ask.
 
P.S. Are you using a USB 2.0 connection to the motherboard? Typically that results in less issues. My favorite USB drives are all metal and relatively large, for good heat dissipation.

USB enclosures sometimes alter ID's in unpredictable ways, for instance yours may be reporting for the first slot that responds, and subsequent drives aren't. Some USB cages are better than others, but all suffer from bandwidth issues for parity.
 
The only external hard drive cages that work comparable to internal SATA connections with Unraid is either ESATA with one port per drive, or SAS which allows multiple drives for a single cable.
 
USB suffers from poor connection stability under heavy load, which can cause Unraid to disable drives somewhat randomly.
 
You should be able to successfully use Unraid with USB connected array drives if you forego parity protection and just use data drives and single volume pools, any attempt to use parity with multiple USB data drives is going to be a frustrating experience compared to HBA sata internal connections.

I can't remember if there is a guide, but here it is in a nutshell.
 
1. Shut down the Windows 10 VM fully, hold down the shift key while clicking the Shut Down item.
2. On the VM page, click on the name text of the VM, it will drop down a list of the attached disks.
3. Click on the 70GB text in the capacity column, and change it to 90.
4. Boot the VM back up, go to disk management, and expand the partition to fit the new vdisk.

After a reboot, yes.

mirror is NOT backup.
 
Backups can be restored to fix things like file corruption and accidental deletion.
 
Mirror keeps the files identical in realtime, so if a file is deleted, it's gone everywhere.
 
mirror is NOT backup.
 
mirrors perform best with identical drives, but can be forced to use vastly different capacities and speeds, typically you will be restricted to the limits of the slower and smaller of the disparate drives.

👍

This.
You can attach as many additional drives as you want after the array has started, but the array will NOT start if the number of license limit devices are exceeded. Virtual devices don't count.
 
Why? All you really need to get started is the USB stick to set up a trial Unraid install, and a single drive that can be erased and used as Disk1 in the array. As long as you don't assign any of your current drives to Unraid, it won't touch them.

You can just remove the section of xml that you pictured.
 
Read this thread for more discussion.