From: Husemann, Harald (harald.husemann@Materna.DE)
Date: Fri Nov 15 2002 - 06:10:22 EST
(Original question below)
Hi all,
it seems we did something wrong during installation, seems to be a
metaroot-problem... We're currently installing all the stuff again, starting
with the OS.
It looks like it's not the right way to install SDS first, and then the
Cluster SW...
Hm, maybe we'd better read the entire installation guide before, :-)
Special thanks to:
Tony Jose who pointed us in the right direction
Casper Dik and Julie Peers for helpful hints
Michael Schulte for a real funny reply, :-))
Harald
-----Original Message-----
From: Husemann, Harald [mailto:harald.husemann@Materna.DE]
Sent: Thursday, November 14, 2002 4:37 AM
To: Sunmanagers Mailingliste (E-Mail)
Cc: Kupke, Detlev
Subject: Problems with SUN Cluster 3.0: System hangs after install
Hi gurus,
we're having a problem with a SUN Cluster 3.0 installation.
The server is a E420, with 2 CPU's and 2 GB RAM, running Solaris 8 Rev.
02/02 with latest recommended patch cluster (rev. -17) installed.
We've just installed SC 3.0 (newest release) on the first node, installed
the volume manager (Solstice DiskSuite), and started a reboot.
When the system comes up, the following msg. appears on the console:
================================/snip/======================================
===============================
Rebooting with command: boot
Boot device: disk File and args:
SunOS Release 5.8 Version Generic_108528-17 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
|
panic[cpu2]/thread=30001787360: mutex_enter: bad mutex, lp=0
owner=800000007d080030 thread=30001787360
000002a1000e58d0 unix:mutex_panic+5c (10415c48, 0, ffffffffffffffff,
7efefeff, 81010100, ff00)
%l0-3: 000003000002afc0 0000000000000000 0000030000a2dd40 0000030000a2dd18
%l4-7: 0000030000a2dd38 0000030000a2dd70 0000000000000000 0000000000000001
000002a1000e5980 cl_bootstrap:cluster+a8 (30001787360, 30001785138, 1,
104640b8, 10400000, 30001787360)
%l0-3: 0000000010464078 0000000000000000 46726f6d3a204a61 726b6b6f20486965
%l4-7: 74616e69656d6920 0000000010413b28 2e66693e0a202020 2020202020202020
00002a1000e5a40 genunix:cluster_wrapper+4 (0, 0, 300015be008, 30001783530,
16, 0)
%l0-3: 000000001010dac4 0000000000000000 0000030000a2df20 0000030001787620
%l4-7: 0000030000a2df18 0000030000a2df50 0000030000a2f808 000003000001c020
syncing file systems... done
skipping system dump - no dump device configured
rebooting...
Resetting ...
====================================/snap/==================================
====================================
That's it, the system won't boot. Booting it in non-cluster mode (with boot
-x) works fine...
We've tried to install the cluster patch (patch id 110648-23) directly after
installtion of SC 3.0, before the rebooting (as recommended), but the
patchadd fails with "one or more patch packages are not installed -
aborting..."
Anyone seen this before? What does "mutex panic" mean? I've also searched
docs.sun.com for it, but haven't found something useful...
Will summarize,
kind regards,
Harald
============================================
Harald Husemann
Systems Engineer
Teammanager Unix administration and Configuration Management
Materna Gmbh - Vo_kuhle 37 -
D-44141 Dortmund, Germany
Phone: +49-231-5599-8684
Mobile: +49-179-2300651
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:25:17 EDT