Compartir a través de

Event ID 1034 — Cluster Storage Functionality

  • Artículo

Applies To: Windows Server 2008

In a failover cluster, most clustered services or applications use at least one disk, also called a disk resource, that you assign when you configure the clustered service or application. Clients can use the clustered service or application only when the disk is functioning correctly.

Event Details

Product: Windows Operating System
ID: 1034
Source: Microsoft-Windows-FailoverClustering
Version: 6.0
Symbolic Name: RES_DISK_MISSING
Message: Cluster physical disk resource '%1' cannot be brought online because the associated disk could not be found. The expected signature of the disk was '%2'. If the disk was replaced or restored, in the Failover Cluster Management snap-in, you can use the Repair function (in the properties sheet for the disk) to repair the new or restored disk. If the disk will not be replaced, delete the associated disk resource.

Resolve

Confirm disk availability

Confirm that the affected disk is available. For more information, see "Reviewing hardware, connections, and configuration of a disk in cluster storage." If the disk has failed, see "Assigning a functioning disk to a clustered service or application if the previously assigned disk has failed."

If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering."

To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.

Reviewing hardware, connections, and configuration of a disk in cluster storage

To review hardware, connections, and configuration of a disk in cluster storage:

  1. On each node in the cluster, open Disk Management (which is in Server Manager under Storage) and see if the disk is visible from one of the nodes (it should be visible from one node but not multiple nodes). If it is visible to a node, continue to the next step. If it is not visible from any node, still in Disk Management on a node, right-click any volume, click Properties, and then click the Hardware tab. Click the listed disks or LUNs to see if all expected disks or LUNs appear. If they do not, check cables, multi-path software, and the storage device, and correct any issues that are preventing one or more disks or LUNs from appearing. If this corrects the overall problem, skip all the remaining steps and procedures.

  2. Review the event log for any events that indicate problems with the disk. If an event provides information about the disk signature expected by the cluster, save this information and skip to the last step in this procedure.

  3. To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

  4. In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.

  5. If the console tree is collapsed, expand the tree under the cluster you want to manage, and then click Storage.

  6. In the center pane, find the disk resource whose configuration you want to check, and record the exact name of the resource for use in a later step.

  7. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

  8. Type:

    CLUSTER RESOURCE DiskResourceName /PRIV >path\filename.TXT

    For DiskResourceName, type the name of the disk resource, and for path\filename, type a path and a new filename of your choosing.

  9. Locate the file you created in the previous step and open it. For a master boot record (MBR) disk, look in the file for DiskSignature. For a GPT disk, look in the file for DiskIdGuid.

  10. Use the software for your storage to determine whether the signature of the disk matches either the DiskSignature or DiskIdGuid for the disk resource. If it does not, use the following procedure to repair the disk configuration.

Assigning a functioning disk to a clustered service or application if the previously assigned disk has failed

To assign a functioning disk to a clustered service or application if the previously assigned disk has failed:

  1. To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

  2. In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.

  3. If the console tree is collapsed, expand the tree under the cluster you want to manage.

  4. To determine whether the replacement disk that you want to use is already configured as a clustered disk in available storage, in the console tree, click Storage, and see whether the disk is listed under Available Storage.

  5. In the console tree, click Services and Applications.

  6. Perform this step only if the replacement disk is already configured as a disk in the clustered storage. Right-click the service or application that uses the disk that failed, click Add Storage, and add the replacement disk. Then, in the center pane, right-click the disk that failed, and then click the Remove from command.

  7. Perform this step only if the replacement disk is not configured as a disk in the clustered storage. Expose a LUN to each node, but do not use Failover Cluster Management to add that LUN to the cluster. Then, with Services and Applications still selected, in the center pane, click the service or application that uses the failed disk, right-click the failed disk resource, click Properties and then, on the General tab, click Repair.

    With the Repair button, you can assign a different disk to this service or application. The disk that you assign must be one that can be used for clustering but is not yet clustered.

    Caution   The Repair button does not recover data.

    You can restore the data to the disk before or after using the Repair button.

To open Event Viewer and view events related to failover clustering:

  1. If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
  3. To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
  4. To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.

Verify

Confirm that the disk resource can come online. If there have been recent problems with writing to the disk, it can be appropriate to monitor event logs and monitor the function of the corresponding clustered service or application, to confirm that the problems have been resolved.

To perform the following procedures, you must be a member of the local Administrators group on each clustered server, and the account you use must be a domain account, or you must have been delegated the equivalent authority.

Confirming that a disk resource can come online

To confirm that a disk resource can come online:

  1. To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.
  3. If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications.
  4. In the console tree, click a clustered service or application.
  5. In the center pane, expand the listing for the disk resource. View the status of the resource.
  6. If a disk resource is offline, to bring it online, right-click the resource and then click Bring this resource online.

To perform a quick check on the status of a resource, you can run the following command.

Using a command to check the status of a resource in a failover cluster

To use a command to check the status of a resource in a failover cluster:

  1. On a node in the cluster, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

  2. Type:

    CLUSTER RESOURCE ResourceName /STATUS

    If you run the preceding command without specifying a resource name, status is displayed for all resources in the cluster.

Cluster Storage Functionality

Failover Clustering