Server may freeze during startup when ALUA-capable storage is used in Windows Server 2012 R2 or Windows Server 2012

Symptoms

Assume that you have a storage configured to have multiple paths to an Asymmetric Logical Unit Access (ALUA)–capable storage array, and some of those paths are in a Standby state. This issue occurs when the first discovered path for a disk device is a Standby path, and the storage array responds to the host on this path with an error that is defined in the SCSI Primary Commands (SPC) specification.

Note Windows Server 2008 R2 also exhibits the behavior that is described in this article.

Workaround

To work around, change the state of the first connected path for a disk device from Standby to Active, or disconnect the path.

Resolution

To resolve this issue, we have released a hotfix for Windows Server 2012 R2 and Windows Server 2012.

Hotfix information

Important Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.

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 have update 2919355 installed in Windows Server 2012 R2.

Registry information

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

Restart requirement

You may 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 R2 file information and 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

    GDR

  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" 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

Mpio.sys

6.3.9600.17809

245,080

30-Apr-2015

00:25

x64

Msdsm.sys

6.3.9600.17809

182,104

30-Apr-2015

00:25

x64

Windows Server 2012 file information and notes

Important Windows 8 hotfixes and Windows Server 2012 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/Windows Server 2012" 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.17xxx

    Windows Server 2012

    RTM

    GDR

    6.2.920 0.21xxx

    Windows Server 2012

    RTM

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" 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

Mpio.sys

6.2.9200.17071

244,032

05-Aug-2014

09:00

x64

Mpio.sys

6.2.9200.21190

244,032

05-Aug-2014

01:19

x64

Msdsm.sys

6.2.9200.17362

184,152

06-May-2015

16:58

x64

Msdsm.sys

6.2.9200.21474

184,152

06-May-2015

17:19

x64

Additional file information

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_mpio.inf_31bf3856ad364e35_6.3.9600.17813_none_0e3bde8663137458.manifest

File version

Not applicable

File size

2,093

Date (UTC)

30-Apr-2015

Time (UTC)

00:29

Platform

Not applicable

File name

Amd64_msdsm.inf_31bf3856ad364e35_6.3.9600.17813_none_bb50449faf4ac667.manifest

File version

Not applicable

File size

2,099

Date (UTC)

30-Apr-2015

Time (UTC)

00:29

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_mpio.inf_31bf3856ad364e35_6.2.9200.17364_none_76120d1019085724.manifest

File version

Not applicable

File size

2,093

Date (UTC)

07-May-2015

Time (UTC)

22:42

Platform

Not applicable

File name

Amd64_mpio.inf_31bf3856ad364e35_6.2.9200.21476_none_7692da83322c458d.manifest

File version

Not applicable

File size

2,093

Date (UTC)

07-May-2015

Time (UTC)

22:42

Platform

Not applicable

File name

Amd64_msdsm.inf_31bf3856ad364e35_6.2.9200.17364_none_23267329653fa933.manifest

File version

Not applicable

File size

2,096

Date (UTC)

06-May-2015

Time (UTC)

17:02

Platform

Not applicable

File name

Amd64_msdsm.inf_31bf3856ad364e35_6.2.9200.21476_none_23a7409c7e63979c.manifest

File version

Not applicable

File size

2,096

Date (UTC)

06-May-2015

Time (UTC)

17:26

Platform

Not applicable



Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Need more help?

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

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×