But would I much rather be able to just run and update and reboot? You bet ya. Now this sounds like a long process but it's not. Since the changes are all written to the USB drive and not the boot vmdk, after doing an update I have to power down the server, detach the USB drive from the VM, attach it and the vmdk to a Windows VM, recopy the data from the USB to the boot disk, detach the USB and vmdk from the Windows VM, reattach the USB to the UnRAID VM, and power back on. This works fine, until you need to do an upgrade. The VM boots off that, but once loaded, all config changes are written to the passed through USB. So to mitigate this I created a 1GB boot vmdk that is just a copy of the USB flash drive. I run UnRAID inside of a VM and booting off the passed through USB drive is VERY slow.
I very well may wind up sticking with it and I'd be mostly happy to do so. Well since this topic has veered where I didn't want it to go and can't help that, I'll chime in.įirst off I'm not in any way disgruntled about UnRAID.
0 kommentar(er)
