A Cluster Disk Resource May Fail to Come Online and Run ChkDsk when an Invalid Character is used in the Resource Name


If the name of a Cluster disk resource has an invalid character in it from an NTFS perspective '\' '/' character and there is some file on the root of the drive where the cluster doesn't have READ permission or if the file is in use, then the disk resource fails to come online.


The name of the ‘Physical Disk’ resource has an backslash or forward slash character in the resource name. Example: "Disk G:\" and ‘Local System’ cannot open a handle to a file at root of drive (whether because it’s in use or permissions).


To fix this issue, install hotfix 3033918.


To work around this issue, either remove the invalid character(s) in resource names for ‘Physical Disk’ resource types OR have ‘Local System’ account at least ‘Read’ permission to files at the root of the drive. After making the changes you should be able to bring the disk resource online.

Note: It is not recommended to store files at the root of a clustered disk as the cluster needs to open handles to files and folders as part of the health detection mechanism used to determine possible access issues to storage. Since the cluster service runs in the context of the ‘Local System’ account, if that account does not have permission to files at the root of a drive, the health check may fail. 

More Information

Cluster tries to enumerate files on the disk during an Online event and if it is not able to enumerate files on the root of the cluster disk, it would fail the disk.

A snippet from the cluster logs:

00001668.00001f88::2011/08/02-12:04:00.366 WARN [RES] Physical Disk <G:\>: OnlineThread: Failed to get volume guid for device \\?\GLOBALROOT\Device\Harddisk2\Partition1\. Error 3
00001668.00001f88::2011/08/02-12:04:04.418 WARN [RES] Physical Disk <G:\>: OnlineThread: Failed to set volguid \??\Volume{aaeb0322-6921-11e0-a955-00155d50c903}. Error: 183.
00001668.00001f88::2011/08/02-12:04:04.418 INFO [RES] Physical Disk <G:\>: Found 2 mount points for device \Device\Harddisk2\Partition1
00001668.00001f88::2011/08/02-12:04:04.418 INFO [RES] Physical Disk <G:\>: VolumeIsNtfs: Volume \\?\GLOBALROOT\Device\Harddisk2\Partition1\ has FS type NTFS

00001668.00001f88::2011/08/02-12:04:04.426 ERR [RES] Physical Disk <G:\>: VerifyFS: Failed to open file \\?\GLOBALROOT\Device\Harddisk2\Partition1\kilo.docx Error: 5.
00001668.00001f88::2011/08/02-12:04:04.426 ERR [RES] Physical Disk <G:\>: VerifyFS: Failed to open file \\?\GLOBALROOT\Device\Harddisk2\Partition1\kilo.docx Error: 5.

00001668.00001f88::2011/08/02-12:04:04.426 ERR [RES] Physical Disk <G:\>: OnlineThread: Error 123 bringing resource online.
00001668.00001e3c::2011/08/02-12:04:52.772 ERR [RES] Physical Disk: Failed to get partition size, status 3
00001668.00001e3c::2011/08/02-12:04:52.773 ERR [RHS] Error 5023 from ResourceControl for resource G:\.
00001920.00000808::2011/08/02-12:04:52.773 WARN [RCM] ResourceControl(STORAGE_GET_DIRTY) to G:\ returned 5023.

The disk gets marked as dirty as the name had an invalid character and would run CHKDSK before the disk is brought online sucessfully next time. Following events may be noted in the system event log after you correct the problem and online the disk for the first time.

 Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 8/2/2011 5:23:11 PM
Event ID: 1066
Task Category: Physical Disk Resource
Level: Warning
Computer: XXXXXXXXXXX.com
Description: Cluster disk resource 'Cluster Disk 1' indicates corruption for volume '\\?\Volume{aaeb0322-6921-11e0-a955-00155d50c903}'. 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_ResCluster Disk 1_Disk2Part1.log'. Chkdsk may also write information to the Application Event Log.

Log Name: Application
Source: Chkdsk
Date: 8/2/2011 5:23:12 PM
Event ID: 26214
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Description: Chkdsk was executed in read/write mode.

This does not indicate actual corruption on the disk. What happened is that cluster set the dirty bit on the disk so chkdsk is run to verify an intact file system.

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

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

Windows Server 2008 R2 Service Pack 1, Windows Server 2008 R2 Datacenter, Windows Server 2008 R2 Datacenter without Hyper-V, Windows Server 2008 R2 Enterprise, Windows Server 2008 R2 Enterprise without Hyper-V, Windows Server 2008 R2 for Itanium-Based Systems

  • KB2590305