From: Surinder S. Dio (S.S.Dio@gre.ac.uk)
Date: Fri Nov 08 2002 - 13:07:45 EST
Hi,
We're fairly wet behind the ears on trucluster and stuff - we just
got a 5 node es45 - running tru cluster V5.1A and are getting into it.
It has been working pretty fine up until now in it's installed mode
(by compaq) but today I had to reboot it to register some changes I
made to /etc/sysconfigtab (to increase per proc stack size) and
after the reboot we can not get the cluster up again.
When each node boots - it sits around waiting for the cluster quorum
(3 in this case) and when it reaches quorum the nodes dump with a
message:
"CNX MGR: Another node has already booted from this disk
Warning no disk available for dump"
And we're dumped back at the >>>
I've tried to get each node up individually - in single user,
without the cluster software kicking in - but we're not really sure
what we're doing here.
Alas we're not even sure of how the disks are laid out - each node
has local disk and they all connect thru to a shared storage device
as well.
We check the boot device (>>>show dev_boot) and tried booting from
that with:
>>> boot -fl ia dka100
But that just boots it into a prompt that doesnt accept my vmunix
clubase commands (I was trying to do this from the notes I made
while the machine was being installed).
(each node has a different boot device so I'm assuming they boot
from the shared storage).
I have a set of dkaXXX devices and a set of dkbXXX devices - but I'm
not sure which is the local disk or which is the shared ones.
Ideally I'd like to be able to get around/fix the "another node has
already booted from this disk" error - failing that I'd like to get
each node up in single user mode - so that I can at least reverse my
changes to /etc/sysconfigtab - just in case my entries are
responsible for this whole mess happening.
It's all become a bit of a nightmare today :-)
Any advise would be gratefully received.
TIA
Surinder
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:59 EDT