Recently I was involved in a Private Cloud project and as part of the project, we were migrating some virtual machines from one Hyper-v cluster to another. The VM was apparently successfully live migrated to second cluster but after few seconds, the VM crashes and then cannot boot and gave below error:

clip_image002

After doing some research, we found that the storage that clusters were using were not supporting ODX, hence we disabled to ODX in the registry, by changing the registry key HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\FilterSupportedFeaturesMode from 0 to 1.

Once the ODX was disabled, the live migration of virtual machines between Hyper-V clusters worked perfectly and no disk read errors were encountered.

Hope this helps for people encountering similar situation.

Read my favorites blogs:

Assigning File Share permissions using Power Shell

Designing a backup less Exchange 2010 Architecture

Step by step guide for upgrading Active Directory from Microsoft Windows 2003 to Microsoft Windows Server 2008

Microsoft Exchange 2010 CAS Array – Steps and Recommendations

Appear Offline in Microsoft Office Communicator Server 2007

Microsoft Exchange 2010 Test cases

Microsoft Exchange Server 2010 Disaster Recovery

Microsoft Exchange Server 2010 Upgrade Guide