Windows 10 VM starts then pauses and will not resume (SOLVED)

[joelkolb]

I am running Unraid v6.9.2 running on a Threadripper 1920X. I have a Windows 10 VM configured to pass through an Nvidia GTX 1660 Super and a USB 3.0 add in card. This setup has worked great for about 2 years. Most recently the array and the VM had been up for about 50 days. I went to work yesterday and when I came home the VM wasn't running. When I check the VMs section in Unraid it shows the VM as being paused.

The Windows environment in the VM is configured to be always on, not to sleep or hibernate or anything like that. I have no idea what caused it to pause. Now I can't get it to resume. When I try to resume the little status indicator icon spins for a split second and then goes right back to pause. If I force stop the VM and then start it again it appears to start up normally but a few seconds after the I get to the desktop everything freezes up. After that, when I check the status of the VM in Unraid again it shows as paused and will not resume. I don't know what caused this to happen out of the blue. I am attaching a diagnostic zip and a copy of the VMs xml config. Foolishly, I rebooted the server thinking it might help so I hope nothing was lost that can shed light on what's going on.

VM_config.xml kolbnet-nas1-diagnostics-20210819-0940.zip

Edited August 25, 2021 by joelkolb
SOLVED

[JorgeB]

Filesystem      Size  Used Avail Use% Mounted on
/dev/sdc1       224G  224G  168K 100% /mnt/disks/SSDSC2KB240G7R_BTYS83220MDP240AGN

 

Disk containing the vdisk is full.

[JorgeB]

Also this can help with that not happening in the future:

https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606

 

[joelkolb]

@JorgeB thanks for the quick response. That post that you linked to looks very helpful. I didn't know about the virtio-scsi controller with discard='unmap'. I did however try to prevent a situation like this from happening by setting the allocation for the virtual disk to be a bit smaller than the physical disk it lives on.

 

 

What did I do wrong? How was the vdisk still able to grow to fill the physical disk 100%? Should I have set the allocation size smaller? Most importantly, now that the damage is done and in the current state of things I can't get into Windows long enough to install the virtio-scsi driver, what I can I do to fix this? Thanks!

[JorgeB]

7 minutes ago, joelkolb said:

How was the vdisk still able to grow to fill the physical disk 100%?

It can still do that.

[JorgeB]

8 minutes ago, joelkolb said:

what I can I do to fix this? Thanks!

You can "resparsify" the vdisk, move it to somewhere else, then copy back with

cp --sparse=always /source /dest

 

[joelkolb]

@JorgeB thanks! Isn't is possible though that in the future the vdisk could actually become full and fill up the physical disk in a situation where TRIM won't help? Why isn't the vdisk allocation being respected and is there a way to lock the allocation size so that it won't grow beyond what is specified?

[JorgeB]

10 minutes ago, joelkolb said:

Isn't is possible though that in the future the vdisk could actually become full and fill up the physical disk in a situation where TRIM won't help?

It shouldn't happen with unmap enable.

[joelkolb]

@JorgeB It took me a few days to get everything situated but it all worked out following the information you provided. Thanks for your help.

[damnshaneisthatu]

On 8/19/2021 at 9:50 AM, JorgeB said:

You can "resparsify" the vdisk, move it to somewhere else, then copy back with

cp --sparse=always /source /dest

 

 

@JorgeB for those of us who are not as familiar with the CLI, is there another way to do this?

[JorgeB]

8 hours ago, damnshaneisthatu said:

for those of us who are not as familiar with the CLI, is there another way to do this?

Not that I know of, but this is very easy to do with the CLI, just need to specify the source/dest paths.