Provisioning Server “Corrupt VHD” When Mounting in Windows Disk Management or Hyper-V 3

Today I was hit with a rather precarious scenario:  I wanted to test my VDI image, which is streamed via PVS, with MCS on Atlantis ILIO.  The plan to accomplish this was relatively straightfoward:  Create a merged base of the PVS image, copy the VHD, create a VM in Hyper-V, boot, uninstall PVS target device, rearm windows, shutdown then snapshot.  It was going to be awesome… however…

Upon trying to deploy the VHD to Hyper-V, SCVMM reported that the disk was corrupt.  Knowing that I was just booting from this device, I stubbornly tried again but I was not successful.  Upon failing again, I remembered I had a similar issue when resizing my XenApp VHD previously and I recalled I had worked around the issue by using VHD Resizer.  I mirrored this file for easy access.

I don’t know what the cause is yet of these corrupt VHD’s, however both VHD’s were created with the PVS imaging utility.

Leave a comment

Your email address will not be published.

3 thoughts on “Provisioning Server “Corrupt VHD” When Mounting in Windows Disk Management or Hyper-V

  • justjeff

    From another website

    We utilize PVS and when we were attempting to update the target device software utilizing Hyper-V we got several error messages saying the VHD is corrupted. The actual root of the issue is that PVS makes 16MB block size VHD files (thanks SAMAN!) and Windows 2008 only reads VHD files that are 512KB or 2MB block sized files.

    • Atum Post author

      Thanks for the tip Justjeff! I wonder what the implications are for PVS for using a Hyper-V created VHD with the smaller blocksize or if Server 2012/2012R2 can read them.