Hyper-V failed checkpoint merge (low disk space). VM Export fails at 99% and additional avhdx files created with each attempt

IN 1 Reputation point
2022-04-02T18:15:21.033+00:00

Hello, hopefully someone can shed some light on my issue. I will do my best to describe the situation and provided applicable information

Hyper V host running Server 2012 r2
3x Server VMs running (2x AD, 1x Files server)

The files server is the VM giving me the issues. I embarrassingly did not notice a checkpoint had been created ages ago. This server has a dynamic c: for the server installation, and a 300gb fixed data drive for file shares. The checkpoint file had grown to ~135 gb before I noticed, leaving only about 10-15gb of free space on the partition housing the VM Hard Drives. It was suggested to delete the checkpoint to merge the data drive to regain some storage capacity, unfortunately the merge process used up the remaining space and all 3 of the VMs paused.

I was able to clear up some space on that partition by moving the 2 smaller VMs data drives to another partition so all 3 VMs are running. Since the failed checkpoint deletion/merge attempt, no checkpoints are showing up in the Hyper V GUI. When looking at the folders, I see the main C: vhdx files and now 3 avhdx files. The same for the data drive (1x vhdx, 3x avhdx). The timestamps of the recently created 2 avhdx files correspond with attempts to export this Files Server from Hyper V.

When looking at the event logs for Hyper-v-vmms, I see two errors

  1. Error 1
    Event 18350, Hyper-V-VMMS
    The description for Event ID 18350 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

VFiles
6BAD1461-C721-44DD-8CA2-24EF2B166EAA
%%2147943065
0x80070299

The locale specific resource for the desired message is not present

  1. Error 2

Event 18350, Hyper-V-VMMS
The description for Event ID 19100 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

VFiles
6BAD1461-C721-44DD-8CA2-24EF2B166EAA
%%2147942512
0x80070070

The locale specific resource for the desired message is not present

I am able to successfully export the two ADs to an external USB hard drive (2tb) without any issue. The Files server has given me a generic error the two times I have tried as well as creating the new avhdx files.

189443-hyper-v-export-failed-4222.jpg

Currently all 3 servers are up and running, the partition currently housing the files server hard drives has 52gb of the total 558gb capacity. Rebooting the VM files server has not resulted in any of the avhdx files to merge automatically

I appreciate any help. Please let me know if I need to provide any additional information, thank you

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,603 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 39,481 Reputation points
    2022-04-07T10:44:51.77+00:00

    Hi @IN

    Event 18350 means the export operation failed for the VM. Shutting down the VM with the un-merged AVHD files and then restarting the Hyper-V Management Service will always successfully merge the AVHD file and reset the VSS error.

    How did you configure permissions for the share on the storage?
    Is it accessible from other Windows clients?
    Have you tried to grant read/write access to everyone?

    Below threads discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue.

    Backup problem of Hyper-V machine
    https://learn.microsoft.com/en-us/answers/questions/205978/backup-problem-of-hyper-v-machine.html

    Error 0x80070005 when exporting Hyper-V VMs
    https://social.technet.microsoft.com/Forums/en-US/40ca9109-ed78-4f4b-abf1-ad67b7f2172a/error-0x80070005-when-exporting-hyperv-vms-to-a-remote-linux-nas?forum=winserverhyperv

    Hope this resolves your Query!!

    --
    --If the reply is helpful, please Upvote and Accept it as an answer–

    0 comments No comments