Has anyone ever seen this before?
My customer is installing TruCluster V5.1A with (2) ES45 systems and
FC storage. The customer has redundant MC adapters (already been checked)
with redundant MC Hubs.
The customer successfully installs TruCluster, and can add the 2nd
cluster member.
Then when booting the 2nd member, both systems lock up when the 2nd
system hits the quorum.
Each Member has 1 vote and the quorum has 1 vote.
See additional information below supplied by the customer.
Thanks,
Matt Morris
Technical Support Engineer
Avnet TECenter
7300 W. Detroit Street
Chandler, AZ 85226-2410
Matt,
And yes I'm booting the second system from the generic kernel, and yes I
have a shared storage subsystem (hsg80) that the quorum and cluster
filesystems reside on.
Node 1 comes up fine, I can log in cluster looks ok, I boot node 2 kernel
loads services are loading find till I get here
BEGIN
registering CMS Service
ics_mct: icsinfo set for node 2
ics_mct: Declaring this node 2
CNX QDISK: adding 1 quorum disk vote toward formation
#### OTHER SYSTEM LOCKS UP HERE
CNX MGR: Cluster cluster_name incarnation 0xe0b30 has been formed
CNX MGR: founding node is 2 csid is 0x10001
CNX MGR: membership configuration index: 1( 1 addition, 0 removed)
CNX MGR: node NODE2 2 incarn 0xe0b30 csid 0x10001 has been added to cluster
dlm: resuming lock activity
kch: resuming activity
CNX QDISK: successfully claimed quorum disk, adding 1 vote
CNX MGR: quorum (re)gained, (re)started cluster operations
joining versw kch set
clsm: checking peer configurations
clsm: initialized
waiting for cluster mount to complete
warning: cfs_perform_glroot_mount: cfs_mountroot_local failed to mount the
cluster root fs with error = 6
END
Thanks again,
Jason Hedden
Received on Thu Dec 20 2001 - 18:50:29 NZDT