update: new 5.1 cluster fails to start

From: Brandon Smith <brandon.smith_at_totaltec.com>
Date: Thu, 24 May 2001 10:51:24 -0400

i'm still working on this problem; here is an update.

i started form scratch again, this time going w/ failover and not multibus,
and not setting up a quorum disk. i figure i could setup the quorum disk
after the cluster is up. but the startup still stops, this time at the
message "TNC kproc_creator_daemon: Initialized and Ready." this message
was the message on the line before the "CNX QDISK" message i received while
having a quorum disk.

i've tried booting off genvmunix, and i've checked and double checked all
SAN devices to make sure i've set them up correctly at the SRM. also,
mysteriously, my SRM os_type was changed after my first attempt at a cluster
setup, to OpenVMS. i've never installed anything but Tru64 on this DS10, so
this is really puzzling, especially considering my following attempts to
setup a cluster have not set the os_type to OpenVMS.

also, on the HSG80 pair, the units i have created, the CFS disk, the first
member boot disk, and the quorum disk, all have access set to ALL.

--Brandon

> -----Original Message-----
> From: Brandon Smith
> Sent: Wednesday, May 23, 2001 4:30 PM
> To: 'tru64-unix-managers_at_ornl.gov'
> Subject: new 5.1 cluster fails to start
>
> i just setup a new 5.1 cluster w/ a DS10 (firmware 5.9), and a HSG80 pair
> (8.5F). the HSG80 pair is in multibus, and i have two fabrics. two HBAs
> in each server.
>
> the setup goes fine, and i take the reboot option after the member's
> kernel has been built. but during the startup, still at the blue screen,
> and after the message "CNX QDISK: Adding 1 quorum disk vote toward
> formation," everything just stops; i have my cursor flashing at a new
> line. this is the second time this has happened, and this time, i started
> w/ a new install of 5.1.
>
> --Brandon
Received on Thu May 24 2001 - 14:53:26 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:42 NZDT