- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - OpenVMS
- >
- %VMScluster-I-MSCPCONN
-
-
Categories
- Topics
- Hybrid IT with Cloud
- Mobile & IoT
- IT for Data & Analytics
- Transformation
- Strategy and Technology
- Products
- Cloud
- Integrated Systems
- Networking
- Servers and Operating Systems
- Services
- Storage
- Company
- Events
- Partner Solutions and Certifications
- Welcome
- Welcome
- Announcements
- Tips and Tricks
- Feedback
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- Converged Data Center Infrastructure
- Digital Transformation
- Grounded in the Cloud
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- Networking
- OEM Solutions
- Servers: The Right Compute
- Telecom IQ
- Transforming IT
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Categories
-
Forums
-
Blogs
-
InformationEnglish
%VMScluster-I-MSCPCONN
SOLVED- 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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-09-2008 12:51 PM
12-09-2008 12:51 PM
jasper is boot node for jasvms and jasvsm is having 0 vote in quorum.
jasvms boots perfectly fine from jasper out of cluster, when I try to boot jasvms in cluster with jasper, it crashes with PROCGONE bugcheck
please see the attachment for details
please help
"Ignorance more frequently begets confidence than does knowledge."
Regards
Bjay
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-09-2008 01:16 PM
12-09-2008 01:16 PM
SolutionCheck your system disk used on and used for the (satellite?) node that is booting (and crashing).
You're running OpenVMS Alpha V8.3, huh? You might want to check that version again as the crash that was attached was from an OpenVMS Alpha V8.2 system. Not V8.3.
Might not be the system disk you think it is?
As for the crash itself, check the system disk configuration, as a start. Here's the error you're hitting:
$ x=f$message(%x00728334)
$ show sym x
X = "%MOUNT-F-DEVSHAMEM, device is already mounted as a shadow set member"
$ help /message devshamem
DEVSHAMEM, device is already mounted as a shadow set member
Facility: MOUNT, Mount Utility
Explanation: The device you attempted to mount as a nonshadowed device
is already mounted elsewhere in the cluster as a shadow set
member.
User Action: Mount the device as a member of a shadow set. You can use DSA:
to specify a generic virtual unit if you do not know which
virtual unit contains the device.
--
As a general rule, satellites should be non-voting members of the cluster, as well. Votes are typically assumed to hosts with non-served access to the system disk and/or to the quorum disk, or the votes are assigned to the quorum disk. (It's *very* easy to clobber a cluster with shared storage if you're not *very* careful with this. Don't try to "game" the votes and expected_votes settings, too.)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-09-2008 02:38 PM
12-09-2008 02:38 PM
Re: %VMScluster-I-MSCPCONN
Re: %VMScluster-I-MSCPCONN
thank you for quick response
you are right with your diagnose. I did
$ana /crash sys$sysdevice:[sys1.sysexe]sysdump.dmp
sda>clue register
R0 value reads the same "device is already mounted as a shadow set member"
well the mistake I made was on the satellite node:
Jasper(boot node) has a system disk shadow set and the shadowing parameters in Jasvms(satellite node) were
shadowing 0
shadow_sys_unit 0
shadow_sys_disk 0
I believe the last one tells the system to create a system disk shadow set.
so what was happening when jasvms(satellite) node boots up it tries to mount $4$dka0 where as it is already mounted as a member of DSA0 that give rise to conflict
thanks for your response
Regards
Bjay
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-09-2008 02:41 PM
12-09-2008 02:41 PM
Re: %VMScluster-I-MSCPCONN
Re: %VMScluster-I-MSCPCONN
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2018 Hewlett Packard Enterprise Development LP