Unsolved
This post is more than 5 years old
4 Posts
0
15805
September 24th, 2012 13:00
Persistent reservation , windows 2003 sp2
All,
Good day.
We had outage couple of days ago and our cluster disk went offline. When analyzing the logs with Microsoft, they said we need to diasble Persistent Reservation flag.
Microsoft comments “This mostly happens due to a persistent reservation present on the disks which does not allow the clusdisk.sys to perform I/O operation on the cluster disks and blocks it. This also prevents failover to other nodes.
Action Plan:
- Engage the Storage vendor and ask them to remove the persistent reservations on the cluster disks.”
Microsoft keep saying to engage Storage vendor and storage vendor saying is done from host.
Any thoughts would be appreciated!
Thanks,
Naveen
No Events found!
Mich
86 Posts
0
March 29th, 2016 17:00
Hi dynamo, I am talking about removing old persistent reservations that have been left on a device due to a cluster issue, power outage or abnormal cluster removal.
henkvisser
5 Posts
0
March 30th, 2016 03:00
After clearing the Cluster Persistent reservation, Cluster Validation came up with another issue which does not make sense to me:
"The wrong diskette is in the drive. Insert %2 (Volume Serial Number: %3) into drive %1"
The way I managed to get the cluster to work now:
1) Stop presenting the Luns to both Cluster Servers at the same time.
2) Now the validation works and the cluster can be configured.
3) present the Luns to the second server.
4) Configure the quorum.
Now I got a working w2k8R2 cluster.
However...... if I run now "Validate a Configuration" it still shows :
"The wrong diskette is in the drive.Insert %2 (Volume Serial Number: %3) into drive %"
So by getting bypassing the cluster validation, I can get it to work. Not very elegant. Could it cause any problem?
Mich
86 Posts
0
March 30th, 2016 20:00
Sounds like something is still not right. I would be identifying the cause before placing any servers into production without passing validation.
Are these physical servers or VMs?
See also KB https://support.emc.com/kb/379359
If you google the error you will see a link to a Microsoft forum that discusses the issue as well.
henkvisser
5 Posts
0
April 1st, 2016 06:00
I am running on physical dell PowerEdge M600 blades.
Just to be on the save site, and identifying the cause, I reiterated the process and presented the LUNs to both servers before running the Cluster validation.
I did run the Clear-ClusterDiskReservation command for all the disks. But the "Validate a configuration" keeps coming back with:
"Cluster Disk # does not support Persistent Reservations. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters."
And it repeats this error for all the presented LUNs.
Mich
86 Posts
0
April 4th, 2016 19:00
I think it best that you log a service request for this issue. Will need EMCReports from the servers in the cluster.
Regards, Michel.
henkvisser
5 Posts
0
April 5th, 2016 02:00
http://wintelguy.com/2011/20110514_scsicmd.html
I did run the SCSI-3 test on all the cluster disks, and they all passed!
So it looks like the CX4-120 is behaving well.
However W2K8R2 cluster validation still fails with:
"Successfully accessed cluster disk 0 from node cg-srv02.testbed.pmic while it should have failed
Cluster Disk 0 does not support Persistent Reservations. Some storage devices require specific firmware versions or settings to function properly with failover clusters. Please contact your storage administrator or storage vendor to check the configuration of the storage to allow it to function properly with failover clusters."
Here is the result of the SCSI-3 test:
Example of disk 1:
C:\>scsicmd -d1 -sscsi3_test
********************** SCSI-3 SUPPORT TEST ***********************************
* The SCSI-3 SUPPORT TEST performs a set of SCSI-3 PR on disk(s) specified in *
* -d option. *
* SCSICMD uses the predefined '1234567812345678' key in SCSI-3 support test. *
* *
* Make sure that the testing shouldn't be under the cluster resource. *
* *
* If SFW DMP (5.0 DDI-3/5.1 GA/5.1 DDI-1 or a newer DDI version) hasn't been *
* installed nor claim the disk, make sure that there is only one HBA path *
* connected to the disk(s) from the testing host before running SCSICMD tool. *
*******************************************************************************
Harddisk1
Scsi Address
------------------
Length : 0x8
PortNumber : 0x1
PathId : 0x0
TargetId : 0x0
Lun : 0x0
******** PERFORM SCSI-3 PR OPERATION TESTS ON Harddisk1 *************
===>Test #1: Clean up any SCSI-3 keys left on harddisk1
Test #1 - **** PASSED. There is no SCSI-3 key left on the disk: #1.
===> Test #2: Perform SCSI-3 Register action on harddisk1 with SCSI-3 key: 785
6341278563412
Test #2 - Successfully issued SCSI-3 Register action.
Test #2 - Checking...There should be a registered key on harddisk1
SCSI3 registered keys on harddisk1
Key: 7856341278563412
Test #2 - *** PASSED. Successfully performed SCSI-3 Register Service Action.
===> Test #3: Perform SCSI-3 reservation action on harddisk1 with SCSI-3 key:
7856341278563412
Test #3 - Successfully issued SCSI-3 reservation action.
Test #3 - Checking...Reading the SCSI-3 reservation holder
SCSI3 reservation holder key on harddisk1
Key: 7856341278563412
Test #3 - *** PASSED. Successfully performed SCSI-3 Reservation Action.
==> Test #4: Perform SCSI-3 release action on harddisk1 with SCSI-3 key: 7856
341278563412
Test #4 - Successfully issued SCSI-3 release action.
Test #4 - Checking...There should be none SCSI-3 reservation holder left on the
Test #4 - There is no SCSI-3 reservation holder left on harddisk1.
Test #4 - Checking...There should be a SCSI-3 registered key left on the disk.
SCSI3 registered keys on harddisk1
Key: 7856341278563412
Test #4 - *** PASSED. Successfully performed SCSI-3 Release Action.
==> Test #5: Perform a part of SCSI-3 preempt action test on harddisk1.
Test #5 - Testing the support of SCSI-3 preempt PR.
Test #5 - *** PASSED. Successfully performed a part of SCSI-3 Preempt Service A
ction test.
===> Test #6: Perform SCSI-3 Register Ignore Existing action on harddisk1.
Test #6 - Perform SCSI-3 Register Ignore Existing key action on harddisk1 with t
he new SCSI-3 key: 8344838F997E1DB9
Test #6 - Checking...There should be a new SCSI-3 registered on the disk. The re
gistered key:
8344838F997E1DB9
SCSI3 registered keys on harddisk1
Key: 8344838F997E1DB9
Test #6 - *** PASSED. Successfully performed SCSI-3 Register Ignore Existing Se
rvice Action.
===> Test #7: Perform SCSI-3 Unregister Service Action on harddisk1.
Test #7 - Checking...There should be no SCSI-3 key left on the harddisk1.
Test #7 - *** PASSED. Successfully performed SCSI-3 UnRegister Service Action.
===> Test #8: Perform SCSI-3 Clear Service Action on harddisk1.
Test #8 - Performing SCSI-3 Register action on harddisk1 with SCSI-3 key: 78563
41278563412
Test #8 - Performing SCSI-3 Reservation action on harddisk1 with SCSI-3 key: 785
6341278563412
Test #8 - Performing SCSI-3 Clear Service Action
Test #8 - Checking...There should be no SCSI-3 key left on the disk
Test #8 - *** PASSED. Successfully performed SCSI-3 UnRegister Service Action
====> SCSI-3 PERSISTENT OPERATION TESTS: All tests are PASSED on harddisk1.
C:\>
henkvisser
5 Posts
0
April 6th, 2016 04:00
Guys,
The issue "Cluster Disk # does not support Persistent Reservations" has been solved by installing PowerPath 6.0 SP1 (build 175) at both my W288R2 cluster servers.
Now the cluster validation verification passes.
Thanks for your contributions in this thread. I learned a lot from you guys.
Kind regards,
Henk