Showing results for 
Search instead for 
Do you mean 

Trouble creating quroum disk

SOLVED
Go to Solution

Trouble creating quroum disk

I have a system runing Tru64 5.1B. The qeroum disk failed and I am trying to replace the disk. However I keep getting the following error:
disklabel -r -R -t ufs /dev/rdsk/rzE5c /ndbetc/vtocs/QUORUM RZ29 Collecting quorum data for Member(s): 1 2

070807093434B0109S Initializing cnx partition on quorum disk : dsk17h 070807093438B0109S 070807093438B0109SAdding the quorum disk could cause a temporary loss of quorum until the disk becomes trusted.
Do you want to continue with this operation? [yes]:y 070807093457B0109SThere appear to be non-voting member(s) in this cluster. If a non-voting cluster member is unable to access the quorum disk, it may lose quorum.
Do you want to continue with this operation? [yes]:y CNX MGR: aborting adjust qdisk: reason code: -17 subsystem error: Invalid argument

070807093507B0109S*** Error ***
Cannot update the cluster's running quorum configuration.

What does the error mean and how can I fix it?
7 REPLIES
Valued Contributor

Re: Trouble creating quroum disk

Only V4.0 releases use "rz#" device name conventions, V5.x releases use "dsk#". The replacement procedure from the cluster administration manual is as follows:

4.5.1 Replacing a Failed Quorum Disk

If a quorum disk fails during cluster operation and the cluster does not lose quorum, you can replace the disk by following these steps:

1. Make sure that the disk is disconnected from the cluster.

2. Use the clu_quorum command and note the running value of quorum disk votes.

3. Use the clu_quorum -f -d remove command to remove the quorum disk from the cluster.

4. Replace the disk. Enter the hwmgr -scan scsi command on each cluster member.

Note You must run hwmgr -scan scsi on every cluster member.

Wait a few moments for all members to recognize the presence of the new disk.

5. Use the hwmgr -view devices -cluster command to determine the device special file name (that is, the dsk name) of the new disk. Its name will be different from that of the failed quorum disk. Optionally, you can use the dsfmgr -n command to rename the new device special file to the name of the failed disk.

6. Use the clu_quorum -f -d add command to configure the new disk as the quorum disk. Make sure the new disk has the same number of votes as noted in step 2.

If a quorum disk fails during cluster operation and the cluster loses quorum and suspends operations, you must use the procedure in Section 4.10.1 to halt one cluster member and reboot it interactively to restore quorum to the cluster. You can then perform the previous steps.

Re: Trouble creating quroum disk

I have executed the replace quorum disk procedure before with no problem but now I am having issues.

I have two node cluster, one node is down at firmware prompt and the other one was booted up using: boot dke400 -fl "ia"
At vmunix prompt: vmunix clubase:cluster_expected_votes=1 clubase:cluster_qdisk_votes=0"

remove quorum disk and add it back after replacing disk.

It works fine on one two node cluster but I am having problems with another two node cluster.

Valued Contributor

Re: Trouble creating quroum disk

What patch kit are you running?

I assume from your description that the "add" is the failing command, not the "remove".

After you boot the 1st member, do "hwmgr v d" and you should see the new disk with a different dsk# than the old disk. Make sure you don't have a stale filesystem defined for that drive in /etc/fstab or /etc/fdmns.

What does "disklabel -r dsk#" report? If the dsk# does not report unlabeled, use "disklabel -z" to clear it.

Re: Trouble creating quroum disk

pk3
yes the add is failing.

197: 26 AS00-01 disk none 0 1 dsk25 [4/5/0]

disklabel: /dev/rdsk/rzE5c: No such device or address Collecting quorum data for Member(s): 1 2

070814090336B0109S
070814090336B0109S*** Error ***
Quorum disk is not configured.

070814090336B0109S*** Error ***
Cannot remove quorum disk.
disklabel: dsk17: No such file or directory
/sbin/hwmgr delete scsi -did 8
/sbin/hwmgr delete scsi -did 9
/sbin/hwmgr delete scsi -did 10
/sbin/hwmgr delete scsi -did 11
/sbin/hwmgr delete scsi -did 12
/sbin/hwmgr delete scsi -did 13
/sbin/hwmgr delete scsi -did 14
/sbin/hwmgr delete scsi -did 15
Resetting scsi device assignment.
/sbin/dsfmgr -vI
Moving dsk25 to dsk17
/sbin/dsfmgr -m dsk25 dsk17
Resetting scsi device assignment.
/sbin/dsfmgr -vI
disklabel -r -R -t ufs /dev/rdsk/rzE5c /ndbetc/vtocs/QUORUM RZ29 Collecting quorum data for Member(s): 1 2

070814090633B0109S Initializing cnx partition on quorum disk : dsk17h 070814090637B0109S 070814090637B0109SAdding the quorum disk could cause a temporary loss of quorum until the disk becomes trusted.
Do you want to continue with this operation? [yes]:y 070814090645B0109SThere appear to be non-voting member(s) in this cluster. If a non-voting cluster member is unable to access the quorum disk, it may lose quorum.
Do you want to continue with this operation? [yes]:y CNX MGR: aborting adjust qdisk: reason code: -17 subsystem error: Invalid argument

070814090648B0109S*** Error ***
Cannot update the cluster's running quorum configuration.

070814090648B0109S*** Error ***
Cannot configure quorum disk.


197: 26 AS00-01 disk none 0 1 dsk17 [4/5/0]


disklabel -r dsk17

070814090750B0109S# /dev/rdisk/dsk17c:
type: SCSI
disk: RZ29B
label: Quorum Disk

070814090750B0109Sflags:
070814090750B0109Sbytes/sector: 512
sectors/track: 113
tracks/cylinder: 20
sectors/cylinder: 2260
cylinders: 3708
sectors/unit: 8380080
rpm: 7200

070814090750B0109Sinterleave: 1
070814090750B0109Strackskew: 9
cylinderskew: 16
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0

070814090750B0109S8 partitions:
070814090750B0109S# size offset fstype fsize bsize cpg # ~Cyl values
a: 131072 0 unused 0 0 # 0 - 57*
b: 401408 131072 unused 0 0 # 57*- 235*
c: 8380080 0 unused 0 0 # 0 - 3707
d: 2623488 532480 unused 0 0 # 235*- 1396*
e: 2623488 3155968 unused 0 0 # 1396*- 2557*
f: 2600624 5779456 unused 0 0 # 2557*- 3707
g: 3936256 532480 unused 0 0 # 235*- 1977*
h: 2048 8378032 cnx # 3707*- 3707
Valued Contributor

Re: Trouble creating quroum disk

I think your problem is because this system has the obsolete V4.0 "rz" device names instantiated and this is confusing clu_quorum...

> disklabel: /dev/rdsk/rzE5c: No such device or address Collecting quorum

You should probably use "dsfmgr -p /dev" to delete all of them, but I have never used V4.0 so I have never seen either the problem or what happens as a result of deleting all "rz" devices.

So... here is the ugly unsupported way I would fix the quorum:

- boot the 1st member
- mount 2nd member's root disk locally as in:
# mount root2_domain#root /mnt
- identify the quorum disk major/minor numbers via:
# ls -l /dev/disk/dsk17h
brw------- 1 root system 19,319 Apr 25 17:30 /dev/disk/dsk17h
- here major==19 minor==319
- edit BOTH members' sysconfig as in:
# vi /etc/sysconfigtab /mnt/etc/sysconfigtab
- make both files have these clubase entries:
cluster_expected_votes=3
cluster_node_votes=1
cluster_qdisk_major=19 <<< your major
cluster_qdisk_minor=319 <<< your minor
cluster_qdisk_votes=1
- you should be able to reboot 1st member normally as in:
# reboot -q
Honored Contributor

Re: Trouble creating quroum disk

Solution from Jim should fix the problem.
But you must know what you are doing!

> disklabel: /dev/rdsk/rzE5c: No such device or address Collecting quorum

Try to create symbolic link to "missing" device.

# ln -s /dev/rdisk/dsk17c /dev/rdsk/rzE5c
In vino veritas, in VMS cluster

Re: Trouble creating quroum disk

Modifying the major and minor resolved the problem.
//Add this to "OnDomLoad" event