- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- quorum disk
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2009 09:35 PM
тАО08-19-2009 09:35 PM
quorum disk
%sysinit- volume already mounted on a differently-named device, stauts = 007280b4
i get the above error when i boot my machine. i want to change the disk_quorum value. I boot form cd and do a mc sysgen
after that i type as follows
sysgen> use current
sysgen> set disk_quorum "$2$dka100"
sysgen> write current
after that i get a error as " sysgen-e-creparfil, unable to create parameter file.
-rms-e-wlk, device currently write locked.
i want to know if iam on the right track in solving this problem and also how can i change the disk_quorum value.
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2009 10:26 PM
тАО08-19-2009 10:26 PM
Re: quorum disk
You may mount the real systemdisk and do a SYSGEN> WRITE disk:[sys0.sysexe]alphavmssys.par
(replace disk and the systemroot with your values)
or do a conversational boot into SYSBOOT and set your parameters. When exiting from SYSBOOT VMS continues to boot.
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2009 11:38 PM
тАО08-19-2009 11:38 PM
Re: quorum disk
Do you really need a quorum disk vote to be able to get your environment running? Can you set he quorum disk name to be blank, then reset and reboot?
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2009 03:30 AM
тАО08-20-2009 03:30 AM
Re: quorum disk
%sysinit- volume already mounted on a differently-named device, stauts = 007280b4
Status 007280b4 = %MOUNT-F-VOLALRMNT, another volume of same label already mounted
Teh disk you designed as the quorum disk bears the wrong label; given it's location (sysinit) I think you desigend the system disk being the quorum disk, or you have given it the wrong label.
It has nothing to do with the disk quorum.
Boot minimal, mount the disk designed to be the quorum disk and relabel it. Modify MODPARAMS and specify the wrong disk, label and diskquorum, and execute AUTOGEN. Then reboot normally.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2009 09:29 AM
тАО08-20-2009 09:29 AM
Re: quorum disk
Steve you have a really good question here:
>>>Do you really need a quorum disk vote to be able to get your environment running?
You need to have quorum to create quorum.dat on the quorum disk. Until this file is created, the quorum disk isn't voting. Do not create or copy this file on the fly. So, the answers depends on your cluster voting configuration. In a two node cluster with 1 vote on each node and 1 quorum disk vote, you need to start one node with temporarily inflated votes allowing quorum.dat to be created. Changing the quorum disk will require attention to quorum.
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2009 10:48 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2009 10:41 PM
тАО08-20-2009 10:41 PM
Re: quorum disk
"Steve you have a really good question here:
>>>Do you really need a quorum disk vote to be able to get your environment running? "
I got the impression that the OP had an environment that was already working which is why I asked the question. All nodes available shouldn't need the QD vote but it needs to be quorate to boot in the first instance as you say Andy.
Steve