ClusterStorage Ghost Folders | Why They Appear and How to Check

In Windows Failover Clustering, you may sometimes notice extra folders like ClusterStorage.000 or ClusterStorage.001 on one host. These are ghost mount points created when the system couldn’t attach the shared volume to the usual C:\ClusterStorage path. They often appear after a failover, reboot, or storage hiccup, and remain even after the cluster stabilizes.

The important thing is: they don’t mean your cluster is broken. They’re just remnants of a past event. Still, it’s wise to verify that no workloads are tied to those ghost paths and that your Cluster Shared Volumes (CSV) are healthy.

🔍 What to Check

• Cluster Shared Volume health — confirm all shared volumes are online and coordinated by a healthy node.
• List all VM storage paths — review where your virtual disks (VHDX files) are stored.
• Check VM configuration files — inspect configs, snapshots, and paging files.
• Verify CSV mount points — ensure volumes are mounted under C:\ClusterStorage not ghost folders.
• Inspect cluster resources and logs — check disk resources and recent cluster events.
• Check redirected I/O state — confirm CSVs are in direct I/O mode.

🛠️ Testing Commands

# List all VM disk paths
Get-VM | Get-VMHardDiskDrive | Select-Object VMName, Path

# Check VM configuration, snapshots, and paging file locations
Get-VM | Select-Object Name, ConfigurationLocation, SnapshotFileLocation, SmartPagingFilePath

# Verify Cluster Shared Volume mount points
Get-ClusterSharedVolume | Select-Object Name, @{Name="Path";Expression={$_.SharedVolumeInfo.FriendlyVolumeName}}

# Run full cluster validation (storage, network, system health)
Test-Cluster

# Show physical disk resources and their status
Get-ClusterResource | Where-Object {$_.ResourceType -eq "Physical Disk"}

# Check cluster events/logs for recent disk or CSV issues
Get-ClusterLog -UseLocalTime -TimeSpan 1

# Show CSV I/O mode (Direct vs Redirected)
Get-ClusterSharedVolumeState

✅ Resolution

If ghost folders are empty and unused, they can be safely deleted. If they contain files, relocate them to the proper ClusterStorage\VolumeX path first. Use the above commands to confirm CSV health and ensure no VM references ghost paths.

🕯️ Kapothi Insight

Ghost doors remain when the shrine once faltered — but the true doorway is open and strong today.

Tags

Hyper‑V, Failover Clustering, ClusterStorage, Kapothi Legacy, Digital Forensics