IT Toolbox
Guide

How to diagnose Hyper-V AVHDX differencing disks

This BAOI guide provides a structured method for diagnosing a hyper-v avhdx chain.

TopicHyper-V →
⌚ About 2 min read
View my favorites
Virtualization Intermediate 15-30 min

This BAOI guide provides a structured method for diagnosing a hyper-v avhdx chain.

Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.

Étapes à suivre

  1. 1

    Collect

    To identify the exact error, time time and context.

  2. 2

    Limit

    Identify the systems and users involved.

  3. 3

    Test

    Use appropriate tools or commands to confirm cause.

  4. 4

    Correct

    Apply a targeted and reversible correction.

  5. 5

    Validate

    Play the full screenplay and check the logs.

Commands utiles

Get-VHD -Path disc.avhdx

À retenir

  • Keep the initial state.
  • Avoid multiple simultaneous changes.
  • Document the final result.
← All les guides
Technical deep dive

Virtualization: disk chains and quorum do not tolerate shortcuts

Technical checkpoints

  • An AVHDX belongs to a Hyper-V checkpoint chain; manually deleting or renaming it can break parent/child relationships.
  • Consolidation should use Hyper-V/PowerShell and be preceded by parent-chain and free-space checks.
  • Proxmox/corosync uses quorum to prevent split brain; forcing expected votes is only a controlled emergency measure.

State before action

For Hyper-V, read VHDX

Get-VHD <path.avhdx>
pvecm status
pvecm nodes

Topic-specific pitfalls

  • Copying/renaming an AVHDX in production without understanding its parent can make the VM unbootable.
  • Forcing quorum on multiple network partitions can create split brain and corruption.

How to validate

  • The Hyper-V chain is cleanly consolidated and the VM boots without orphaned checkpoints.
  • The Proxmox cluster regains quorum with expected nodes/links before further changes.

Operational context

AVHDX files are Hyper-V checkpoint differencing disks and should never be treated as ordinary orphan files based on filename or age alone. Map the checkpoint chain, VM disk attachment and parent relationships before any merge or storage cleanup.

Step-by-step checks

  1. Inventory the VM, configured virtual disks and visible checkpoints, including checkpoints that may have been created by backup software.
  2. For each attached VHDX/AVHDX, inspect parent-path relationships and verify every file in the differencing chain exists on storage.
  3. Check Hyper-V-VMMS/Worker and backup-product events for interrupted checkpoint merge, storage loss or failed backup cleanup.
  4. Measure free space on the volume before a merge operation is planned; merging can require significant temporary I/O and capacity.

Useful verification commands

Use commands only on systems you administer and capture the read-only output before making a configuration change.

Get-VMHardDiskDrive -VMName "VM01" | Format-List *
Get-VMSnapshot -VMName "VM01"
Get-VHD -Path "D:\VMs\VM01\disk.avhdx" | Format-List Path,VhdType,ParentPath,FileSize,Size

How to validate the result

The VM must have a consistent disk chain, no unexpected production checkpoint, and any approved merge must complete with the VM referencing the intended base/current disk and backup jobs operating normally.

Evidence to keep

Keep VM ID/name, Get-VMHardDiskDrive output, checkpoint list, each VHD/AVHDX parent path, file sizes, relevant VMMS/backup events and free-space measurements.

Frequently asked question

Can I delete an old-looking AVHDX file to recover space?

No. If it belongs to an active differencing chain, deletion can make the virtual disk unusable. Prove chain ownership first and use supported Hyper-V merge/checkpoint workflows.

Related BAOI resources: IT tools · procedures · IT dictionary.

♡ 0