Windows Server TechCenter >
Windows Server Forums
>
Clustering
>
Cluster Manager test fails on Storage Section
Cluster Manager test fails on Storage Section
- Running the test for cluster failover and I am not sure if I can proceed to create the cluster with the error that I have. I understand that there is no failover for the local machine's C: Drive (boot), all other tests pass. Or is there a way to remove the local drive from the test or from mpio?
StorageName Result Description List All Disks 
Success List Potential Cluster Disks Success Validate Disk Access Latency Success Validate Disk Arbitration Success Validate Disk Failover 
Failed Validate File System 
Canceled Validate Microsoft MPIO-based disks Success Validate Multiple Arbitration Success Validate SCSI device Vital Product Data (VPD) Success Validate SCSI-3 Persistent Reservation Success Validate Simultaneous Failover Canceled
Here is the detailed section:
List All Disks
List all disks visible to one or more nodes (including non-cluster disks).Prepare storage for testingPreparing storage for testing on node tluxhs1.tluxvm.orl.comPreparing storage for testing on node tluxhs2.tluxvm.orl.com
tluxhs1.tluxvm.orl.comGetting information on PhysicalDrive 0 from node tluxhs1.tluxvm.orl.comGetting information on PhysicalDrive 1 from node tluxhs1.tluxvm.orl.comGetting information on PhysicalDrive 2 from node tluxhs1.tluxvm.orl.comGetting information on PhysicalDrive 3 from node tluxhs1.tluxvm.orl.comGetting information on PhysicalDrive 4 from node tluxhs1.tluxvm.orl.comGetting information on PhysicalDrive 5 from node tluxhs1.tluxvm.orl.comGetting information on PhysicalDrive 6 from node tluxhs1.tluxvm.orl.comDisk Number Disk Identifier Disk Bus Type Disk Stack Type Disk Address (PORT:PATH:TID:LUN) Adapter Description Eligible for Validation Disk Characteristics PhysicalDrive0 fceb8fb7 Bus Type SAS Stor Port 2:0:0:0 Dell SAS 6/iR Integrated Controller False Disk is a boot volume. Disk is a system volume. Disk is used for paging files. Disk is used for memory dump files. Disk is on the system bus. Disk partition style is MBR. Disk partition type is BASIC. PhysicalDrive1 871348a8 Bus Type iSCSI Stor Port 3:0:0:0 Microsoft Multi-Path Bus Driver True Disk partition style is MBR. Disk partition type is BASIC. Disk is Microsoft MPIO based disk PhysicalDrive2 871348bc Bus Type iSCSI Stor Port 3:0:3:1 Microsoft Multi-Path Bus Driver True Disk partition style is MBR. Disk partition type is BASIC. Disk is Microsoft MPIO based disk PhysicalDrive3 871348a4 Bus Type iSCSI Stor Port 3:0:3:2 Microsoft Multi-Path Bus Driver True Disk partition style is MBR. Disk partition type is BASIC. Disk is Microsoft MPIO based disk PhysicalDrive4 a9429ada Bus Type iSCSI Stor Port 3:0:3:3 Microsoft Multi-Path Bus Driver True Disk partition style is MBR. Disk partition type is BASIC. Disk is Microsoft MPIO based disk PhysicalDrive5 87134890 Bus Type iSCSI Stor Port 3:0:0:4 Microsoft Multi-Path Bus Driver True Disk partition style is MBR. Disk partition type is BASIC. Disk is Microsoft MPIO based disk PhysicalDrive6 <Unknown> Bus Type iSCSI Stor Port 3:0:2:31 Microsoft Multi-Path Bus Driver False Disk partition style is RAW. Disk is Microsoft MPIO based disk Any help would be greatly appreciated.
Robert Ramos
Answers
- Actually, it says "Cluster disk 0" which is different than Disk 0.
Under the "List Potential Cluster Disks" section, it should have a section similar to the following:
Disks eligible for cluster validation: Disks will be referred to by the following cluster disk numbers in subsequent tests Cluster disk 0 has disk identifier f2891a82 Cluster disk 1 has disk identifier f289197d Cluster disk 2 has disk identifier f289197c Cluster disk 3 has disk identifier f289197f Cluster disk 4 has disk identifier f289197e
You would use the identifier value listed here to line up the Disk Identifier value from the List All Disks section of the report to figure out which physicaldrive number cluster is using for Cluster disk 0.
Basically, this report is stating that the node is having issues with the volume on the disk identified as Cluster Disk 0. You might try re-formatting this disk to see if this helps. If this doesn't help, you might consider contacting your storage vendor for further support.
Visit my blog about multi-site clustering - http://msmvps.com/blogs/jtoner- Marked As Answer byEdwin vMierloMVP, ModeratorFriday, November 06, 2009 5:05 PM
- Proposed As Answer byEdwin vMierloMVP, ModeratorFriday, November 06, 2009 12:12 PM
All Replies
Cluster knows about your boot drive...in the "Eligible for Validation" column it lists PhysicalDrive0 as not eligible for validation, so it would not test this disk.
The validation error appears to be occurring during the failover testing. Post the "Validate Disk Failover" section of the validation test.
Visit my blog about multi-site clustering - http://msmvps.com/blogs/jtoner- Thanks for the help. Here is the "Validate Disk Failover" section. It refers to disk 0, which I thought should be exempt.
Validate Disk Failover
Validate that a disk can fail over successfully with data intact.Getting partition table for cluster disk 0 from node tluxhs1.tluxvm.orl.comArbitrating for cluster disk 0 from node tluxhs1.tluxvm.orl.comBringing online cluster disk 0 on node tluxhs1.tluxvm.orl.comWriting file data on cluster disk 0 partition 1Failed to write file data on cluster disk 0 partition 1, failure reason: The disk structure is corrupted and unreadable.Failed to write file data on cluster disk 0 partition 1, failure reason: The disk structure is corrupted and unreadable. - Actually, it says "Cluster disk 0" which is different than Disk 0.
Under the "List Potential Cluster Disks" section, it should have a section similar to the following:
Disks eligible for cluster validation: Disks will be referred to by the following cluster disk numbers in subsequent tests Cluster disk 0 has disk identifier f2891a82 Cluster disk 1 has disk identifier f289197d Cluster disk 2 has disk identifier f289197c Cluster disk 3 has disk identifier f289197f Cluster disk 4 has disk identifier f289197e
You would use the identifier value listed here to line up the Disk Identifier value from the List All Disks section of the report to figure out which physicaldrive number cluster is using for Cluster disk 0.
Basically, this report is stating that the node is having issues with the volume on the disk identified as Cluster Disk 0. You might try re-formatting this disk to see if this helps. If this doesn't help, you might consider contacting your storage vendor for further support.
Visit my blog about multi-site clustering - http://msmvps.com/blogs/jtoner- Marked As Answer byEdwin vMierloMVP, ModeratorFriday, November 06, 2009 5:05 PM
- Proposed As Answer byEdwin vMierloMVP, ModeratorFriday, November 06, 2009 12:12 PM
- This guided me down the right path. Thanks. Paid close attention to the message stating the disk structure is corrupt or unreadable. Newly formatted hard drives with a VHD on them but for whatever reason there was corruption. I ran chkdsk and found directory structure issues and orphaned files. I can't believe it. Directory structure is simple...
Hyper-V/Tluxhs1 or Hyper-V/Tluxhs2
and whatever Hyper-V Manager puts in there for the configuration. As far as files the VHD and again whatever Hyper-V Manager puts in there.
All good after the chkdsk /f.
