Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
1. Download Fortect and install it on your computer
2. Launch the program and click "Scan"
3. Click "Repair" to fix any issues that are found
Home »Virtualization» Microsoft Hyper-V » Recovering a completely damaged virtual hard disk
In the Windows XP era, Microsoft had ambitious plans for technologies to integrate these types of PCs.Products into their exceptional desktop operating system, which happens to be Vista. Among the things that Microsoft considered was a completely new computer file system, in which all files would be grouped together in some kind of database-like structure. In the end, this particular feature never made it to Windows, but at the time I said that some editorials shouted that I considered a new data system a bad idea because encapsulation could easily become a serious flaw right now. If the encapsulation should get corrupted, the entire folder structure can be lost, mainly because of this.
Close a few decades ago and your current idea will prove to be reliable. SharePoint document libraries, for example, for storing files in a SQL Server blob storage area. Likewise, Hyper-V virtual machines store files over the Internet on hard drives, which are essentially a fully encapsulated file system. Despite the full use of encapsulation, Hyper-V virtual hard disks are so reliable that they are usedThey are found in countless production systems. Even things that are absolute can sometimes go wrong. I’ve seen several cases of VHD problems over the years, especially in VMs that rely on checkpoint chaining. If that happens, you can restore a backup, you may have one, but sometimes you can just as easily restore a damaged dedicated hard drive, and voila.
Why Is Data Corruption Happening?
Before showing you how to prepare a corrupted VHD, you are probably wondering how the corruption currently occurs. Sometimes damage to equipment can lead to malfunction. I once had a wonderful external RAID device that messed up quite a bit of data due to the wrong cable. However, in the case of enclosure-bound Hyper-V virtual disks, the damage mainly occurs as a result of the interruption of the hard disk chain.
When the virtual machine is not actually protected and is not running, the operating system Windows usually allows you to secure a virtual hard disk and access its own content from the host operating system. I use this method all the time when setting up laboratory conditions. However, if there are checkpoints on the virtual disk, installing the virtual disk outside of Hyper-V will destroy the checkpoint archipelago at this point. This also applies if you are not making any changes to the contents of the user-friendly hard drive. The next time you try to start the virtual server, you will receive an error message similar to the number below.
Repair Damaged Virtual Hard Disk
When it comes to testing extreme virtual disks, conventional wisdom often dictates the use of the Test-VHD cmdlet in PowerShell. However, from my actual experience, I found that the test-vhd cmdlet is actually not that useful. The cmdlet returns True if the virtual disk is considered healthy, and false if any of our virtual disks are bad. The problem is that the Test-VHD cmdlet with It reports True if a virtual disk checkpoint is broken in the chain due to the installation of a virtual disk that contains checkpoints, even if the virtual disk is actually damaged in the chain. See the illustration below to see what I mean. The Test-VHD cmdlet usually returns True, even if the error message specifically states that the vDisk string has always been corrupted.
The key to solving this problem is the problem highlighted at the end of the error draft shown in the image above. The error indicates a mismatch between the parent VHD IDs and the disk differentiation. This means that if you can fix the current break in the disc label, it might seem possible to reconnect the virtual disc or DVD chain to remove the damage. Figure
Typically the least visible Hyper-V manager and personal computer that is experiencing problems is selected. Although the Hyper-V Coordinator continues to display the full VM gateway tree, the chain of controlx points is broken at the disk level.
If you continue to see the image above, you will notice that there is a Check Disk option in the Actions panel. When you click the Inspect Disk button, a dialog box displays a Windows screen where you must select a virtual disk to check. If I had selected the Client.VHDX file, in the resulting window, which you can see below, it should appear as if the particular virtual hard disk is completely healthy. In fact, if I mounted the main hard drive according to the host OS size, I could view its contents without any problem.
In the following case, the root vDisk appears to be healthy, and just like the problem is obviously related to the connection between the root vDisk, the first checkpoint, currently. Since the root network hard drive doesn’t seem to notice anything behind the checkpoint tree, let’s see what happens if you keep clicking on the Check Disk option in the Hyper-V Manager and select this time: AVHDX file (differential drive, linked with checkpoint) as opposed to the main VHDX file.
This time, Hyper-V Manager displays an error indicating that the exclusive disk chain is broken. However, as you can see better in the image below, I also have a button that allows you to reconnect the drive chain.
Clicking the Reconnect button launches the Change VHD wizard, prompting you to select the parent directory of the VHD. Depending on how the damage occurred, the person may need to check the “Ignore ID Mismatch” checkbox as shown in the image for this article. In my case, this confirmed the error message that people mentioned the ID mismatch, so the checkbox was necessary for the search. After that, each virtual machine started without any problems, and the specific issue of virtual hard disk or DVD corruption was resolved.
Of course, it is best to try to prevent disk corruption in Hyper-V environments, but if something goes wrong, someone canDon’t use your own tools to repair a damaged virtual hard disk. However, we recommend that you avoid directly mounting checkpoint virtual disks.
Run CHKDSK: By running the Windows PowerShell script, you can mount the VHD file in the root folder and then run CHKDSK on it.Using Windows PowerShell: You need to get some simple commands to use this device.Create a virtual server:Microsoft VHD Tool:
However, Hyper-V virtual disks are usually damaged due to a corrupted disk chain. When a virtual machine is usually unsecured and down, any Windows operating system will allow you to mount a virtual disk and easily access its contents using a high-level method of operation.
VHD / VHDX and file system corruption VHD and VHDX files eliminate the necessary Being physically discovered by a vulnerable system. If the user simply double-clicks on a VHD or VHDX file containing a specially crafted reporting system, there is a risk of Windows crash or more, as described below.
