Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. When you move a resource group from one node to another in a Windows Server 2003 cluster, disk resources remain in an online pending state for a long time

When you move a resource group from one node to another in a Windows Server 2003 cluster, disk resources remain in an online pending state for a long time

View products that this article applies to.

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986� (http://support.microsoft.com/kb/256986/ ) Description of the Microsoft Windows registry

↑ Back to the top

Symptoms

You move a resource group that contains physical disk resources from one node to another in a Microsoft Windows Server 2003 cluster. After you do this, the disk resources remain in an online pending state for a long time on the second node.

Additionally, the following message is logged in the System log:

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: Date
Time: 04:12:34
User: N/A
Computer: ComputerName
Description: Application popup: Windows - Delayed Write Failed : Windows was unable to save all the data for the file X:\$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

This problem occurs when the nodes in the cluster are connected to an EMC PowerPath shared storage device.

↑ Back to the top

Resolution

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, follow these steps on the node where event ID 26 is logged.
  1. Start Notepad.
  2. Copy and then paste the following text into Notepad.
    Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EmcpBase\Parameters]
"MpPagingIoTimeout"=dword:00000000
  3. Save the text file as MpPagingIoTimeout.reg.
  4. Locate and then right-click the MpPagingIoTimeout.reg file that you saved in step 3.
  5. Click Merge.
  6. Click OK.
  7. Restart the computer.

↑ Back to the top

More information

More information about cluster operations is available in the Cluster.log file. For example, the Cluster service may generate the following log information when this problem occurs. 
924:020.11/10[04:12:06.069](062938) INFO Physical Disk <Disk X:>: Online, waiting for notification from PnP thread that all volumes exist...
924:020.11/10[04:12:08.069](062949) INFO Physical Disk <Disk X:>: Online, wait for PnP notification returns 258. 
924:020.11/10[04:12:08.069](062949) INFO Physical Disk: [PnP] AddVolumes: Volume list update in process, skipping update 
924:020.11/10[04:12:08.079](062949) INFO Physical Disk <Disk X:>: Online, call MountMgr to check for new, unprocessed volumes.
924:020.11/10[04:12:08.079](062949) INFO Physical Disk <Disk X:>: Online, waiting for notification from PnP thread that all volumes exist...
924:020.11/10[04:12:10.079](062949) INFO Physical Disk <Disk X:>: Online, wait for PnP notification returns 258. 
924:020.11/10[04:12:10.079](062949) INFO Physical Disk: [PnP] AddVolumes: Volume list update in process, skipping update 
924:020.11/10[04:12:10.089](062949) INFO Physical Disk <Disk X:>: Online, call MountMgr to check for new, unprocessed volumes.
924:020.11/10[04:12:10.089](062949) INFO Physical Disk <Disk X:>: Online, waiting for notification from PnP thread that all volumes exist...
924:020.11/10[04:12:12.090](062949) INFO Physical Disk <Disk X:>: Online, wait for PnP notification returns 258. 
924:020.11/10[04:12:12.090](062949) INFO Physical Disk: [PnP] AddVolumes: Volume list update in process, skipping update 
924:020.11/10[04:12:12.100](062949) INFO Physical Disk <Disk X:>: Online, send IOCTL to mark all volumes online.

## Here is a one-minute gap in the thread.

924:020.11/10[04:13:07.130](062957) INFO Physical Disk <Disk X:>: Online, call MountMgr to check for new, unprocessed volumes.
924:020.11/10[04:13:07.130](062957) INFO Physical Disk <Disk X:>: Online, waiting for notification from PnP thread that all volumes exist...
924:020.11/10[04:13:09.130](062957) INFO Physical Disk <Disk X:>: Online, wait for PnP notification returns 258. 
924:020.11/10[04:13:09.480](062957) WARN Physical Disk: [PnP] GetVolumeInfo: Skip update:   \??\Volume{29fcba9f-cb3a-11d8-b911-505054503030}
In this example, a one-minute gap occurs around the time when event ID 26 is logged.

↑ Back to the top

Keywords: KB929269, kbprb, kbexpertiseinter, kbtshoot

↑ Back to the top

Article Info
Article ID : 929269
Revision : 5
Created on : 12/29/2006
Published on : 12/29/2006
Exists online : False
Views : 227