Hi. Using Unraid 6.8.3 (see signature), I wanted to create a gaming vm on unassigned disk.  I did the usual, created a new VM, haven't assigned GPU yet, since the box is headless, will assign gpu later, started installation, but after loading viator drivers, I can see the drive, I went on to next, and keeps stuck there.  I tried changing virt-io to older version, with the same result.  My XML is below.  Can someone please help?

 

xml.txt

Try changing the vdisk bus to sata. Or delete the old vdisk and create a new one. Also ensure your unassigned device mounted disk has enough free space and is not having problems or high io etc.

hi @testdasi

Changing vdisk bus to sata didn't help.  I also deleted the the VM, and recreated it, this time, changing vdisk bus to sata.  Still didn't work.

It's not deleting the VM. Deleting the vdisk file. Once vdisk file is deleted and you open the VM on the VM GUI, it will go back to creating a new vdisk mode. Take a screenshot of what you use for that.

Hi.  Deleted vdisk1.img, entered new settings, turned it on, it started, with the same results.  Still stuck at the same place.

2 minutes ago, jang430 said:

Hi.  Deleted vdisk1.img, entered new settings, turned it on, it started, with the same results.  Still stuck at the same place.

You haven't taken the screenshot of your new vdisk settings.

So, I tried exactly the same thing again, deleted vdisk1.img, and this time, instead of using /mnt/disks/Windows, I selected my cache drive, an hdd, and didn't change the rest, it went through.  

 

Is there an issue if it's an NVME drive?  Or because it's it's an unassigned disk?

9 minutes ago, jang430 said:

So, I tried exactly the same thing again, deleted vdisk1.img, and this time, instead of using /mnt/disks/Windows, I selected my cache drive, an hdd, and didn't change the rest, it went through.  

 

Is there an issue if it's an NVME drive?  Or because it's it's an unassigned disk?

maybe silly question but are you sure your NVMe is mounted at /mnt/disks/Windows?

If it's not then your /mnt/disks/Windows would be in RAM which would cause issues.

 

NVMe and UD are certainly not the problem by themselves. I have 2 VM's currently running out of vdisks stored on an NVMe UD.

Edited March 18, 20206 yr by testdasi

I went to /mnt/disks/Windows to delete the vdisk1.img.  /Windows being the folder I wanted to place the image.  

 

This is a screenshot of my unassigned drive.

 

Do I need to do anything?  Mount it or anything?

13 minutes ago, jang430 said:

I went to /mnt/disks/Windows to delete the vdisk1.img.  /Windows being the folder I wanted to place the image.  

 

This is a screenshot of my unassigned drive.

 

Do I need to do anything?  Mount it or anything?

Your SSD is not even formatted so definitely wasn't mounted. So your /mnt/disks/Windows was in RAM.

You need to first format the UD (you might need to install Unassigned Devices Plus plugin to be able to enable destructive mode in the UD settings to allow formatting - otherwise, the Format button is greyed out). Pick either xfs or btrfs depending on your needs.

Then change the mount name to Windows and mount the formatted UD. Only then it will show up in /mnt/disks/Windows.

Thanks a lot. Understood. Will do that.


Sent from my iPhone using Tapatalk