Disk resource does not come online in Windows Server 2012 R2 or Windows Server 2008 R2-based failover cluster

This article describes an issue that occurs when a disk resource name contains unauthorized file system characters in a Windows Server 2012 R2 or Windows Server 2008 R2-based failover cluster. A hotfix is available to resolve this issue. The hotfix has a prerequisite.
Symptoms
Consider the following scenario:
  • A disk resource name contains unauthorized file system characters, such as colon (:) or backslash (\), in a Windows Server 2012 R2 or Windows Server 2008 R2-based failover cluster.
  • The disk requires that chkdsk be run.
In this scenario, the chkdsk command doesn't run as expected, and the disk resource can't come online.
Cause
The name of the "Physical Disk" resource has an backslash or forward slash character in the resource name. Example: "Disk G:\".
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: 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, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.Or, install Service Pack 1 for Windows 7 or Windows Server 2008 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.

File information

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:
    VersionProductMilestoneService branch
    6.3.960 0.17xxxWindows Server 2012 R2RTMGDR
  • 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 nameFile versionFile sizeDateTimePlatform
Clusres.dll6.3.9600.176671,997,31227-Jan-201503:11x64

Windows Server 2008 R2 file information and notes

Important Windows 7 hotfixes and Windows Server 2008 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 7/Windows Server 2008 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:
    VersionProductMilestoneService branch
    6.1.760 1.22 xxxWindows Server 2008 R2SP1DR
  • 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 2008 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 2008 R2
File nameFile versionFile sizeDateTimePlatform
Clusres.dll6.1.7601.229401,294,33622-Jan-201504:27x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Clusres.dll6.1.7601.229402,140,67222-Jan-201503:16IA-64

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 propertyValue
File nameAmd64_f53c9357603e6fc57585f203685c795d_31bf3856ad364e35_6.3.9600.17667_none_cbaa6e3bdbb4c758.manifest
File versionNot applicable
File size715
Date (UTC)27-Jan-2015
Time (UTC)23:49
PlatformNot applicable
File nameAmd64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.3.9600.17667_none_b1b18ed670df74b5.manifest
File versionNot applicable
File size2,732
Date (UTC)27-Jan-2015
Time (UTC)05:24
PlatformNot applicable
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2
File propertyValue
File nameAmd64_541d0ff217b2f4ab7cd1d0d577c747ad_31bf3856ad364e35_6.1.7601.22940_none_5bf763685885d152.manifest
File versionNot applicable
File size715
Date (UTC)22-Jan-2015
Time (UTC)22:13
PlatformNot applicable
File nameAmd64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.1.7601.22940_none_1f65bf63ccd472a0.manifest
File versionNot applicable
File size2,693
Date (UTC)22-Jan-2015
Time (UTC)04:49
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File propertyValue
File nameIa64_798a522590839423af97f8986a8256aa_31bf3856ad364e35_6.1.7601.22940_none_1f4a3ae09dd5002a.manifest
File versionNot applicable
File size713
Date (UTC)22-Jan-2015
Time (UTC)22:13
PlatformNot applicable
File nameIa64_microsoft-windows-f..overcluster-clusres_31bf3856ad364e35_6.1.7601.22940_none_c348c7d614750a66.manifest
File versionNot applicable
File size2,691
Date (UTC)22-Jan-2015
Time (UTC)04:28
PlatformNot applicable

Workaround
To work around this issue, rename the cluster disk resource so that it has no characters that are invalid in a file name, such as colon (:), backslash (\), slash (/), asterisk (*), question mark (?), quotation mark ("), left angle bracket (<), right angle bracket (>), or vertical bar (|).
More information
On Windows Server 2008 R2, the following entries may be logged in the cluster log when the issue occurs and the resource will not come online:

00000e20.00000a58::2014/10/29-02:59:09.844 ERR [RES] Physical Disk <Disk X:>: OnlineThread: Error 123 bringing resource online.
00000e20.00000a58::2014/10/29-02:59:10.282 INFO [RES] Physical Disk <Disk X:>: stop reserve succeeded on device 7 (sig e18d90fc)
00000e20.00000a58::2014/10/29-02:59:10.282 INFO [RES] Physical Disk <Disk X:>: HardDiskpCloseSVIHandles: Exit
00000e20.00000a58::2014/10/29-02:59:10.282 ERR [RHS] Resource <Disk X:>: has indicated that it cannot come online on any node.


On Windows Server 2012 R2, the resource will come online. However, the chkdsk command will not run. The following event will be logged in the System event log, However, there is no corresponding event from the chkdsk command in the Application event log:

Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: Date & Time
Event ID: 1066
Task Category: Physical Disk Resource
Level: Warning
Keywords:
User: SYSTEM
Computer: Computer
Description:
Cluster disk resource 'Disk X:' indicates corruption for volume '\Device\Harddisk13\ClusterPartition2'. Chkdsk is being run to repair problems. The disk will be unavailable until Chkdsk completes. Chkdsk output will be logged to file 'C:\Windows\Cluster\Reports\ChkDsk_ResF:\Resource_Disk13Part2.log'.
Chkdsk may also write information to the Application Event Log.

Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
See the terminology that Microsoft uses to describe software updates.
Properties

Article ID: 3033918 - Last Review: 07/15/2016 06:00:00 - Revision: 5.0

Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows Server 2008 R2 Service Pack 1

  • kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB3033918
Feedback