Corrupt VHD in Hyper-V
When attempting to attach an existing virtual hard drive I get "Failed to open attachment 'C:\ directory \HV10001.vhd'. Error: 'The file or directory is corrupted and unreadable.'
The file itself seems OK (I can copy it from disk to disk on the host system). Is there any way to recover this thing? I'd really like to avoid rebuilding the whole darn thing from scratch...
Thanks,
DvS
Respostas
- If you copy it to another location, can you attach it from that new location? Try a separate physical disk or volume.
Hello,
You can also try creating a new disk in the same location and then attaching this new created vhd file to the virtual machine.
Unfortunately, this sounds like that the vhd file is corrupted, and I am sorry to say that we don't have any straightforward way to get this corrupted vhd file back.
Just for your reference, you can try mounting the vhd file to the parent partition, and then see if you can use chkdsk to repair it. Ben gives the method of mounting vhd files in his blog:
If this cannot help, you may need to recreate the disk.
Best regards,
Chang Yin
- Marcado como RespostaMike Sterling [MSFT]MSFT, Proprietáriosexta-feira, 30 de maio de 2008 22:44
- Daniel vom Saal said:
When attempting to attach an existing virtual hard drive I get "Failed to open attachment 'C:\ directory \HV10001.vhd'. Error: 'The file or directory is corrupted and unreadable.'
The file itself seems OK (I can copy it from disk to disk on the host system). Is there any way to recover this thing? I'd really like to avoid rebuilding the whole darn thing from scratch...
Thanks,
DvS
I was able to fix this error by deleting any snapshots that were listed, removing the .vhd from the virtual machine IDE settings, saving the settings by clicking OK, editing the virtual machine settings again and adding the .vhd back to the virtual machine IDE controller, and booting.
This problem was caused for me by expanding the .vhd while a snapshot existed. While the "right click / settings" of the virtual machine will grey out the option to edit the .vhd when a snapshot exists, the disk edit wizard in the main MMC UI will not and thus I was allowed to edit the .vhd while a snapshot existed and corrupted it.- EditadoKyle iHost quinta-feira, 25 de setembro de 2008 20:10
- Marcado como RespostaChang Yin terça-feira, 30 de setembro de 2008 2:56
Todas as Respostas
- If you copy it to another location, can you attach it from that new location? Try a separate physical disk or volume.
Hello,
You can also try creating a new disk in the same location and then attaching this new created vhd file to the virtual machine.
Unfortunately, this sounds like that the vhd file is corrupted, and I am sorry to say that we don't have any straightforward way to get this corrupted vhd file back.
Just for your reference, you can try mounting the vhd file to the parent partition, and then see if you can use chkdsk to repair it. Ben gives the method of mounting vhd files in his blog:
If this cannot help, you may need to recreate the disk.
Best regards,
Chang Yin
- Marcado como RespostaMike Sterling [MSFT]MSFT, Proprietáriosexta-feira, 30 de maio de 2008 22:44
- I had the same problem with a vhd while migrating from Virtual Server to Hyper-V.
I was sure the file was OK so I opened it in Virtual PC and it booted again.
I suspect Hyper-V has some issues with bigger disks / dynamicly expaning disks... - Daniel vom Saal said:
When attempting to attach an existing virtual hard drive I get "Failed to open attachment 'C:\ directory \HV10001.vhd'. Error: 'The file or directory is corrupted and unreadable.'
The file itself seems OK (I can copy it from disk to disk on the host system). Is there any way to recover this thing? I'd really like to avoid rebuilding the whole darn thing from scratch...
Thanks,
DvS
I was able to fix this error by deleting any snapshots that were listed, removing the .vhd from the virtual machine IDE settings, saving the settings by clicking OK, editing the virtual machine settings again and adding the .vhd back to the virtual machine IDE controller, and booting.
This problem was caused for me by expanding the .vhd while a snapshot existed. While the "right click / settings" of the virtual machine will grey out the option to edit the .vhd when a snapshot exists, the disk edit wizard in the main MMC UI will not and thus I was allowed to edit the .vhd while a snapshot existed and corrupted it.- EditadoKyle iHost quinta-feira, 25 de setembro de 2008 20:10
- Marcado como RespostaChang Yin terça-feira, 30 de setembro de 2008 2:56
- Kyle iHost said:
I was able to fix this error by deleting any snapshots that were listed, removing the .vhd from the virtual machine IDE settings, saving the settings by clicking OK, editing the virtual machine settings again and adding the .vhd back to the virtual machine IDE controller, and booting.
This problem was caused for me by expanding the .vhd while a snapshot existed. While the "right click / settings" of the virtual machine will grey out the option to edit the .vhd when a snapshot exists, the disk edit wizard in the main MMC UI will not and thus I was allowed to edit the .vhd while a snapshot existed and corrupted it.
I did the same thing... but is there a way to salvage the Snapshots?
(please say yes)
-e- Editadothelettere quinta-feira, 16 de outubro de 2008 1:59
- I hade the same problem,
what i did to be able to access the disk again was convert the disk to dynamicly size.
this made the disk accessable again.
however in the guest OS the disk now appers offline by default. you need to reactivatate it and then you can access the data again.
hope it helps
greetings
Clash
