Symptoms

Consider the following scenario:

  • You configure a Windows Server 2012 R2-based or Windows Server 2012-based computer to use Microsoft Multipath I/O (MPIO) and Microsoft Device Specific Module (MDSM).

  • You use a storage array as the cluster share storage.

  • You connect a storage device to the computer. The storage device is configured to use Asymmetric Logical Unit Access (ALUA).

  • You set up a failover cluster in the environment.

  • You disconnect all the paths between the storage and a passive node of the cluster which does not have the persistent reservation.

  • You reconnect the storage to the node through an Active/Unoptimized path.

In this scenario, some logical unit numbers (LUNs) from the storage cannot be used after the reconnection. Additionally, the pseudo-LUN stays in the "device not started (code 10)" status in the Device Manager.

Resolution

To resolve this issue in Windows Server 2012 R2, install update rollup 2955164, or install the hotfix that is described in this article.

To resolve this issue in Windows Server 2012, install the hotfix that is described in this article.

Update information for Windows 2012 R2

For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:

2955164 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: May 2014

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

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, submit a request to 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 R2 or Windows Server 2012. Additionally, you must first install the update 2919355 on Windows Server 2012 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must 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 R2 file information notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • 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.3.960 0.17 xxx

    Windows Server 2012 R2

    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 R2" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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 R2

File name

File version

File size

Date

Time

Platform

Msdsm.sys

6.3.9600.17088

181,080

03-Apr-2014

08:12

x64

Windows Server 2012 file information notes

Important Windows 8 hotfixes and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • 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, MANIFEST, and the associated security catalog (.cat) files, are very 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

Msdsm.sys

6.2.9200.16793

182,616

10-Jan-2014

05:19

x64

Msdsm.sys

6.2.9200.20912

182,616

10-Jan-2014

05:57

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

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.


Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2

File property

Value

File name

Amd64_msdsm.inf_31bf3856ad364e35_6.3.9600.17088_none_bb0 9876daf7f1f79.manifest

File version

Not applicable

File size

2,096

Date (UTC)

03-Apr-2014

Time (UTC)

08:26

Platform

Not Applicable

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012

File property

Value

File name

Amd64_msdsm.inf_31bf3856ad364e35_6.2.9200.16793_none_2305217b6558beaa.manifest

File version

Not applicable

File size

2,096

Date (UTC)

10-Jan-2014

Time (UTC)

05:24

Platform

Not applicable

File name

Amd64_msdsm.inf_31bf3856ad364e35_6.2.9200.20912_none_23e43f427e3662bc.manifest

File version

Not applicable

File size

2,096

Date (UTC)

10-Jan-2014

Time (UTC)

06:01

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,816

Date (UTC)

10-Jan-2014

Time (UTC)

11:47

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×