Validate SCSI-3 fails on disk 0

Are you sure that it is failing on the local Disk 0 and not "Cluster Disk
0"? Believe it or not, there is usually a difference. I posted the details
about how to identify which disk is "Cluster Disk 0" in the following
thread:

http://social.technet.microsoft.com...10f09dffb7

Regards,
John


"SGoncalves" wrote in message
news:
Greetings everyone,

I'm trying to setup a Windows 2008 R2 x64 Cluster and run into a weird
error.

When it checks SCSI-3 Settings it goes through all the SAN Disks
without an issue.
However when it Scans Disk 0 (Local System Disk with the C:\ drive)
on Node 1 it fails. It passes on Node 2so now I'm trying to figure
out what is going on and why. Both nodes are on the exact same
hardware (purchased at the exact same time) (IBM Blades HS22) so I'm
not sure why I'm seeing this issue. I'm comparing the firmware/driver
versions on both servers but I have the feeling they are going to be
the same.

Is there a setting I can check on the local SAS bus to make sure
everything is good? Once again the SAN Storage (Blade Center S)
passes the SCSI-3 Reservation tests without a problem.

Thanks,

Sérgio.

Thank you for the answer.

I have indeed mixed the Disk 0 and the Cluster Disk 0, but still I
keep having the same error.

Regards.

On May 5, 10:34 pm, "John Toner [MVP]"
wrote:

Are you sure that it is failing on the local Disk 0 and not "Cluster Disk
0"? Believe it or not, there is usually a difference. I posted the details
about how to identify which disk is "Cluster Disk 0" in the following
thread:

http://social.technet.microsoft.com...ing/thr...

Regards,
John

"SGoncalves" wrote in message

news:
Greetings everyone,

I'm trying to setup a Windows 2008 R2 x64 Cluster and run into a weird
error.

When it checks SCSI-3 Settings it goes through all the SAN Disks
without an issue.
 However when it Scans Disk 0 (Local System Disk with the C:\ drive)
on Node 1 it fails.  It passes on Node 2so now I'm trying to figure
out what is going on and why.  Both nodes are on the exact same
hardware (purchased at the exact same time) (IBM Blades HS22) so I'm
not sure why I'm seeing this issue.  I'm comparing the firmware/driver
versions on both servers but I have the feeling they are going to be
the same.

Is there a setting I can check on the local SAS bus to make sure
everything is good?  Once again the SAN Storage (Blade Center S)
passes the SCSI-3 Reservation tests without a problem.

Thanks,

Sérgio.

You will likely need to work with your storage vendor for assistance with
this issue. Some SANs have special flags or settings that need to be enabled
in order to support SCSI3 PR.

Regards,
John

"SGoncalves" wrote in message
news:
Thank you for the answer.

I have indeed mixed the Disk 0 and the Cluster Disk 0, but still I
keep having the same error.

Regards.

On May 5, 10:34 pm, "John Toner [MVP]"
wrote:

Are you sure that it is failing on the local Disk 0 and not "Cluster Disk
0"? Believe it or not, there is usually a difference. I posted the details
about how to identify which disk is "Cluster Disk 0" in the following
thread:

http://social.technet.microsoft.com...ing/thr...

Regards,
John