February 20, 20242 yr I'm running a server with an Unraid VM on it. After a couple of hours, the VM pauses and stops running a Helix Core host (file sharing and revision history service). I believe this is due to the vdisk reaching it's capacity (as shown in the screenshot below). When it pauses, I have to power cycle the server to get it running again. 1) Is there any easier way to get it off of the paused state? 2) How can I avoid getting to a paused state? Thanks in advance for the help.
February 20, 20242 yr Solution 12 minutes ago, lwintz said: How can I avoid getting to a paused state? Use a larger storage device for the vdisk? Also make sure the vdisk is being trimmed: https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606
February 20, 20242 yr Author 1 hour ago, JorgeB said: Use a larger storage device for the vdisk? Also make sure the vdisk is being trimmed: https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606 Thanks for the help! I think I'm on the right path for trimming the disk but I'm not sure where to find the SCSI driver. I navigated to E:\vioscsi\w10 but don't have a driver there. I assume my issue is in step 1 of the link you sent me "First we need to install the SCSI controller". I tried moving on anyway with the steps as if an SCSI driver was already installed. When I tried to reboot, Windows would crash. I made sure beforehand have fast startup off to avoid that but still had problems. Any guidance?
February 20, 20242 yr 9 minutes ago, lwintz said: Thanks for the help! I think I'm on the right path for trimming the disk but I'm not sure where to find the SCSI driver As of lately you don't need the SCSI driver, it's mentioned in the FAQ entry, just add the unmap=discard option, that should be enough.
February 20, 20242 yr Author 9 minutes ago, JorgeB said: As of lately you don't need the SCSI driver, it's mentioned in the FAQ entry, just add the unmap=discard option, that should be enough. Windows still crashes whenever I try to run the VM after adding that. Specifically the stop code is "INACCESSIBLE BOOT DEVICE". This is the current set up Edited February 20, 20242 yr by lwintz
February 20, 20242 yr If you don't change the controller type you should not get that error, were you using virtio?
February 20, 20242 yr It's visible on your first screenshot, change back to virito, but leave the unmap=discard option
February 20, 20242 yr Author 3 hours ago, JorgeB said: It's visible on your first screenshot, change back to virito, but leave the unmap=discard option changed the bus for vdisk1 back to virtio with the unmap=discard. Had another capacity and allocation = 100G pause as described in my first screenshot. Also, just want to thank you again for helping. EDIT Started sending them again and am now stuck at this. The capacity is much larger than the allocation but it still paused itself automatically. Edited February 20, 20242 yr by lwintz
February 21, 20242 yr Author 7 hours ago, JorgeB said: Did you trim the vdisk by running Windows defrag? yep, redid it again just to be sure today
February 21, 20242 yr How is the available space of the actual storage device where the vdisk resides?
February 23, 20242 yr Author On 2/21/2024 at 11:00 AM, JorgeB said: How is the available space of the actual storage device where the vdisk resides? There are 3 8 TB disks that have parity to each other. I'm not sure how I would find the location of the vdisk. I know that "mnt/" refers to the location it's mounted on the drive, but I don't know how to find where that actually is.
February 23, 20242 yr Author 57 minutes ago, JorgeB said: Post the output of: find /mnt -name <vdisk name> /mnt/user/domains/Windows 10/vdisk1.img
February 23, 20242 yr Community Expert 3 hours ago, lwintz said: There are 3 8 TB disks that have parity to each other. I'm not sure how I would find the location of the vdisk. I know that "mnt/" refers to the location it's mounted on the drive, but I don't know how to find where that actually is. getfattr --absolute-names --only-values -n system.LOCATION /mnt/user/domains/vm name/vdisk1.img should tell you the physical location
February 23, 20242 yr Author 1 hour ago, JorgeB said: It should output more results. Misread your comment 14 minutes ago, SimonF said: getfattr --absolute-names --only-values -n system.LOCATION /mnt/user/domains/vm name/vdisk1.img should tell you the physical location Edited February 23, 20242 yr by lwintz
February 26, 20242 yr Author On 2/23/2024 at 12:58 PM, JorgeB said: You do that on the Unraid CLI, not the VM ah
February 26, 20242 yr Author 1 minute ago, JorgeB said: So it's on cache, post the diagnostics please. solidworksnas-diagnostics-20240226-0940.zip
February 26, 20242 yr Cache has plenty of space, I'm afraid that if it's still pausing, there may be an issue with the vdisk.
February 26, 20242 yr Author 1 minute ago, JorgeB said: Cache has plenty of space, I'm afraid that if it's still pausing, there may be an issue with the vdisk. Meaning how it's been set up? How the data is allocated? Would I need to recreate my VM if I wanted to change my vdisk?
February 26, 20242 yr You could create a new vdisk and then if you need to copy something from the old one try assign it as disk2.
February 26, 20242 yr Community Expert 4 hours ago, lwintz said: Meaning how it's been set up? How the data is allocated? Would I need to recreate my VM if I wanted to change my vdisk? Have you increase the partition within the disk also? Also check you have set power options not to suspend etc.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.