Symptoms
Consider the following scenarios:
-
You have two Windows Server 2012-based or Windows Server 2012 R2-based computers that have the Hyper-V role installed.
-
You install a virtual machine on one of the Hyper-V hosts.
-
You set up a guest failover cluster, and then you make the virtual machine a cluster node.
-
The virtual machine is configured to access logical unit numbers (LUNs) over a Synthetic Fibre Channel.
-
You try to perform live migration to move the virtual machine to another Hyper-V host.
In this situation, the virtual machine on the target Hyper-V host cannot access the LUNs over the Synthetic Fibre Channel.
Cause
This issue occurs because the target Hyper-V host cannot restore the Synthetic Fibre Channel LUN on behalf of the virtual machine during live migration.
More Information
You might receive the following error event and warning event when this issue occurs:
-
On the target Hyper-V host:
Error event: Hyper-V SynthFC-Admin ID 32214 with description like Failed to reserve LUN with Instance Path '\\?\SCSI#VMLUN&Ven_HP&Prod_HSV360#5&17efa605&0&070002#{6f416619-9f29-42a5-b20b-37e219ca02b0}' to virtual machine 'WS2012-1' with error: The data is invalid. (0x8007000D). (Virtual machine ID C799C113-B153-4E49-B0C5-F9E24774EB9A) Hyper-V SynthFC-Admin ID 32216 with description like Failed to register LUN with Instance Path '\\?\SCSI#VMLUN&Ven_DGC&Prod_RAID_5#5&378d83c&0&080200#{6f416619-9f29-42a5-b20b-37e219ca02b0}' to virtual machine 'SERVER2012R2-STD-64-1' with error: The data is invalid. (0x8007000D). (Virtual machine ID 86FA60B1-8B40-45C5-A88F-1F024BECA8F0)
-
On the virtual machine:
Warning Event: Microsoft-Windows-Ntfs ID 140 The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume82. (A device which does not exist was specified.) Event ID:50 {Delaled Write Failed} Windows was unable to save all the data for the file. The data has been lost. This erorr may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
Resolution
Windows Server 2012 R2 update information Â
To resolve this issue in Windows Server 2012 R2, install update rollup 2903939. For more information about how to obtain this update rollup package, click the following article number to go to the article in the Microsoft Knowledge Base:
2903939 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: December 2013
Windows Server 2012 Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running Windows Server 2012.
Registry information
To apply this hotfix, you do not have to make any changes to the registry.
Restart requirement
You might have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2012 file information notesImportant Windows 8 and Windows Server 2012 hotfixes are included in the same packages.
-
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.2.920 0.20 xxx
Windows Server 2012
RTM
LDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Synthfcvdev.dll |
6.2.9200.16729 |
317,440 |
2-Oct-13 |
22:19 |
x64 |
|
Synthfcvdev.dll |
6.2.9200.20840 |
317,440 |
2-Oct-13 |
22:19 |
x64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional files for all supported x64-based versions of Windows Server 2012
|
File property |
Value |
|---|---|
|
File name |
Amd64_bf06e1a0da30b4763466562a28b26a78_31bf3856ad364e35_6.2.9200.20840_none_ae9234d34a7170fd.manifest |
|
File version |
Not applicable |
|
File size |
710 |
|
Date (UTC) |
3-Oct-13 |
|
Time (UTC) |
9:13 |
|
Platform |
Not applicable |
|
File name |
Amd64_c561e47297677ee2478df76962e76d7d_31bf3856ad364e35_6.2.9200.16729_none_62a718630908eba6.manifest |
|
File version |
Not applicable |
|
File size |
710 |
|
Date (UTC) |
3-Oct-13 |
|
Time (UTC) |
9:13 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-hyper-v-vstack-synthfcvdev_31bf3856ad364e35_6.2.9200.16729_none_97e6ebe468e72d2d.manifest |
|
File version |
Not applicable |
|
File size |
53,582 |
|
Date (UTC) |
3-Oct-13 |
|
Time (UTC) |
2:12 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-hyper-v-vstack-synthfcvdev_31bf3856ad364e35_6.2.9200.20840_none_9851e63d821d20ca.manifest |
|
File version |
Not applicable |
|
File size |
53,582 |
|
Date (UTC) |
3-Oct-13 |
|
Time (UTC) |
3:23 |
|
Platform |
Not applicable |
