Ask a questionAsk a question
 

AnswerCorrupt VHD in Hyper-V

  • Tuesday, May 27, 2008 8:29 PMDaniel vom Saal Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    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

     

Answers

  • Wednesday, May 28, 2008 3:14 PMMike Sterling [MSFT]MSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    If you copy it to another location, can you attach it from that new location? Try a separate physical disk or volume.

     

  • Thursday, May 29, 2008 11:29 AMChang Yin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    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:

     

    http://blogs.msdn.com/virtual_pc_guy/archive/2008/02/01/mounting-a-virtual-hard-disk-with-hyper-v.aspx

     

    If this cannot help, you may need to recreate the disk.

     

    Best regards,

    Chang Yin

  • Thursday, September 25, 2008 8:07 PMKyle iHost Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    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.
    • Edited byKyle iHost Thursday, September 25, 2008 8:10 PM
    • Marked As Answer byChang Yin Tuesday, September 30, 2008 2:56 AM
    •  

All Replies

  • Wednesday, May 28, 2008 3:14 PMMike Sterling [MSFT]MSFT, OwnerUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    If you copy it to another location, can you attach it from that new location? Try a separate physical disk or volume.

     

  • Thursday, May 29, 2008 11:29 AMChang Yin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    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:

     

    http://blogs.msdn.com/virtual_pc_guy/archive/2008/02/01/mounting-a-virtual-hard-disk-with-hyper-v.aspx

     

    If this cannot help, you may need to recreate the disk.

     

    Best regards,

    Chang Yin

  • Friday, July 11, 2008 7:57 PMjazztrumpet Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    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...
  • Thursday, September 25, 2008 8:07 PMKyle iHost Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    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.
    • Edited byKyle iHost Thursday, September 25, 2008 8:10 PM
    • Marked As Answer byChang Yin Tuesday, September 30, 2008 2:56 AM
    •  
  • Thursday, October 16, 2008 1:58 AMthelettere Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    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
    • Edited bythelettere Thursday, October 16, 2008 1:59 AM
    •  
  • Thursday, October 23, 2008 9:16 AMClasH1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    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