Possible File System Corruption about volume that seems not exist

DZ 21 Reputation points

I have a 2 node cluster and one of the guest VM is showing the following errors which prevents my backup jobs to run properly.

""The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \?\Volume{03499d9b-dd46-11eb-94a9-00155d0a6e01}, DeviceName: \Device\HarddiskVolume20.
(A device which does not exist was specified.)"

"The shadow copies of volume \?\Volume{03499f08-dd46-11eb-94a9-00155d0a6e01} were aborted during detection because a critical control file could not be opened."

I can't seem to located \Device\HarddiskVolume20, which it may not exist nor I can find out which drive is associated with VolumeId: \?\Volume{03499d9b-dd46-11eb-94a9-00155d0a6e01.

I ran Get-Volume PowerShell command on the VM and 2 hosts, but still can't find any drive with that volume ID. Any advise and tips would highly be appreciated.

Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,526 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,104 questions
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,530 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
958 questions
{count} votes

2 answers

Sort by: Most helpful
  1. JiayaoZhu 3,911 Reputation points


    Thanks for posting on your forum!

    Based on your description, it seems that your Volume 20 has been lost while it is still automatically mounted in your system. You can start wbadmin, enter into command prompt and run Mountvol /R , to removes volume mount point directories and registry settings for volumes that are no longer in the system. You can learn more about this command from this article:

    Besides, [HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices] is used to store some information about each drive (device) that was plugged into a Windows system. Among this information is the drive letter that was assigned to this drive. Thus, if a drive is used again, it ensures that the same drive letter is assigned to the drive.

    Then you can retry to operate your backup.

    Thanks for your support! Hope to hear your good news soon!

    Besides, would you please help me Accept Answer. An accepted blog can be put on top of our forum, so that people who have a similar issue can get access to their solution more quickly. I would really appreciate it if you could support my work.


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. DZ 21 Reputation points

    Thanks for your reply. Strangely, when I delete old volume shadow copies from an active volume, then I can run my backup without any issues.

    can this issue be related to corrupt shadow copies or maybe the shadow copies storage location is getting full? but it appears that I have enough storage!