You dont have javascript enabled! Please enable it!

There was an error during move operation: Data error (cyclic redundancy check) (0x80070017)

2 Min. Read

Hello Folks,

Let’s continue the migration project from Hyper-V 2012 to 2012 R2, if you didn’t read my previous posts, you can find them here Post1 and Post2.

The very simple migration process from Hyper-V 2012 Host to another Hyper-V 2012 R2 Host using Cross-Version (Shared Nothing) Live Migration.

Another issue that I came across while moving a particular VM with the following error: Data error (cyclic redundancy check) (‘0x80070017’).


Mmmm interesting, Data error for a specific Virtual Hard Disk.

This Virtual Machine has two Virtual Hard Disks, one under IDE controller and the second one under SCSI controller:


Let’s compare and check the report if there are any incompatibilities between Host A and Host B using the Compare-VM cmdlet.


What Compare-VM does? a PowerShell equivalent of the fix-up GUI wizard you can use before you register, import, or move a Virtual Machine.

You can read more about it here explained in detail by Mr. Ben Hyper-V Program Manager.


As you can see a lovely nice error shows that the Virtual Hard Disk File not found :) and the VM is still happily running on Host A.

We will try to check the disk for the guest OS (VM):


Try to move the VM again, but unfortunately still the same error:


This Virtual machine has a Dynamic Virtual Hard Disk, is it could be broken?

Let’s try to shrink and convert the Dynamic .vhdx to a Fix virtual disk.




Start the conversion, and here is another error (Failed to convert the virtual disk) with the same Data error.


What we left off is to check the physical disk for that host where the Virtual Hard disk is located:


Ohhhh! very interesting we have bad sectors on the physical disk as we can see for two different virtual machines.

Attempt to move the VM again and we succeeded this time :)


So let’s finalize the migration for all Virtual Machines on that host before a freak bad sector strikes or hard drive failure.

Hope this will help someone facing the same issue.

Until next time… Enjoy your day!


Related Posts


Monitor Hyper-V Server with Perfmon View

Understanding Processor, NUMA, Core, Logical Processor and Virtual Processor in Hyper-V


Let me know what you think, or ask a question...

error: Alert: The content of this website is copyrighted from being plagiarized! You can copy from the 'Code Blocks' in 'Black' by selecting the Code. Thank You!