Windows-based MSDSM doesn't handle sense code 02/04/03 (LUN Not Ready – Manual Intervention Required)

Van toepassing: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 EssentialsWindows Server 2012 R2 Standard

Symptoms


Consider the following scenario:
  • You have a Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 R2 Service Pack 1 (SP1) Failover Cluster that is attached to a storage array.
  • This configuration is running native Microsoft Multipath I/O (MPIO) and Microsoft Device Specific Module (MSDSM) functionality.
  • The storage array returns a "02/04/03" (LUN Not Ready - Manual Intervention Required) error.

In this scenario, cluster disks and Cluster Shared Volumes (CSV) disks fail.

Resolution


To resolve this issue, we have released an update rollup for Windows Server 2012 R2, and we have released an hotfix for Windows Server 2012, Windows 7, or Windows Server 2008 R2.

Note This hotfix enables MSDSM to handle the sense code 02/04/03 (LUN Not Ready – Manual Intervention Required). After the hotfix is applied, MSDSM retries I/O through an alternative path to the LUN.

Get the update rollup for Windows Server 2012 R2

To resolve this issue, install the update rollup that is dated November 2014.

Get the November 2014 update rollup for Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2

Get the hotfix information for Windows Server 2012, Windows 7, or Windows Server 2008 R2

A supported hotfix is available from Microsoft Support. 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 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, go to the following Microsoft website: Note 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 on Windows 7 or Windows Server 2008 R2, you must have Service Pack 1 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

Status


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

References


Learn about the terminology that Microsoft uses to describe software updates.