Moving vDisk results in Failed Boot / UEFI Interactive Shell

[baldsealion]

 

i have a new unraid setup i have been testing with for the last couple of days and I am having an issue where if I move a vdisk to another share (or even copy it into another subfolder inside the same share) and re-map it in the VM, it refuses to boot and goes to the uefi shell. It's happened on multiple VMs.

 

Is there a setting I am missing possibly?

 

I have confirmed that the vdisk order stays at 1 and the method for the disk is the same. It just simply seems to not accept any images that are copied.

 

For example, if I shut down VM through windows, wait until it said stopped. then went into settings > vm manager, turned off, then copied the file, then started everything back up and re-pointed the vdisk. Copied to the other share, which is on a data pool disk and not the array(a single nvme for now). When i go exit into the vbios, if i keep on virtio for disk, it shows as "UEFI Misc Device" in boot manager, but again if i press enter on it, nothing happens and returns me to same screen immediately(there is a brief "press any key to continue" behind it)

I don't want to passthrough the nvme as I want to use it for cache as well (its the only disk in the cache pool right now)

[baldsealion]

 

On Unraid 6.12.8 - new setup as of about 48 hours ago.

 

I have a vdisk provisioned (qcow2 img) as a brand new VM working perfectly fine(Windows 10), shut down VM through the guest, wait until it said stopped.

Then went into settings > vm manager, turned off, then copied the vdisk file to my new location, then started everything back up and re-pointed the vdisk.
 

When i go exit into the vbios, if i keep on virtio for disk, it shows as "UEFI Misc Device" in boot manager, but again if i press enter on it, nothing happens and returns me to same screen immediately(there is a brief "press any key to continue" behind it).

This has been repeated multiple times using several different VMs/vDisks, but it seems that my method for copying the vdisk is not working as expected. I use file explorer to just copy the vdisk img from one smb share to another and then modify the path in the VM, but this does not work as expected.

[trurl]

I merged your threads since they seemed to be about the same problem but the posts had additional information. 

[baldsealion]

7 minutes ago, trurl said:

I merged your threads since they seemed to be about the same problem but the posts had additional information. 

 

Thank you, I made the first one before creating my account, so I wasn't sure if it went through.

[JonathanM]

56 minutes ago, baldsealion said:

re-pointed the vdisk.

When you do that make sure the vdisk type is correct.

[baldsealion]

29 minutes ago, JonathanM said:

When you do that make sure the vdisk type is correct.

 

Well Ok so the share was on the array, but I changed the location to the nvme cache, so that new files would go on that, in the same share and that's what happened when I copied the vdisk into a new subfolder.

 

When I added to the VM, I did confirm before and after, it was using virtio with boot order of 1 -- this is something I did previously test, which sounds like what you are describing. I've also tried to use sata, scsi, ide, etc because yeah the first time the issue happened i thought that might be the case - or the wrong bios, but everything is correct, ive done this like 6 times now haha-- but I'm probably missing something still!

Here's the log when it boots into just the shell, not sure if this helps. I can repeat this on multiple vdisk types not just this Windows 10 VM, really bizarre behavior.

 

 

log.txt

[JonathanM]

[baldsealion]

21 minutes ago, JonathanM said:

Ok so, that was the culprit, when added in, it added as a raw, and after you add it in, the Form View removes that as a changeable option.

I modified the XML to qcow2 and it booted just fine. A suggestion, maybe leave the Primary vDisk Type option visible all the time?