KZPCC drives not accessible with 5.1B/PK4 & TruCluster
From: Lee Wen, Sheldon (sheldon.leewen_at_cgi.com)
Date: 05/19/05
- Previous message: rahul bhatnagar: "upgrading patches on Netscape Mesasaging server ver 4.15"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 19 May 2005 07:44:48 -0400 To: tru64-unix-managers@ornl.gov
Hi Guys,
I have a strange problem. I have a cluster of 2 ES45 machines. Previously
they were running 5.1A PK3 and without problems were able to access the
KZPCC drives. However, for various reasons we rebuilt the cluster. This
involved first upgrading the firmware (6.9 I believe). Then I installed
Tru64 5.1B and TruCluster (but didn't create the cluster yet) with the new
hardware delivery which brought me up to PK4. The KZPCC devices were still
accessible, and everything seemed ok. However, then I ran clu_create on one
of the machines to make a 1 member cluster. As soon as I rebooted (and
before running clu_add_member) I realized that I could no longer access the
volume I had on my kzpcc. When I try to access it from diskconfig I get the
message that the hardware is lock, removed or unavailable. Since all of my
swap space for my oracle databases is on this volume it's rather urgent I
get it working again. Any ideas anyone?
Thank you for your time.
Cheers,
Sheldon Lee-Wen
Unix Systems Engineer
Ottawa Data Center, Unix Services
CGI Information Systems and Management
Phone: 613-740-5900 ext 5363
Fax: 613-749-2201
Email: sheldon.leewen@cgi.com
- application/x-pkcs7-signature attachment: smime.p7s
- Previous message: rahul bhatnagar: "upgrading patches on Netscape Mesasaging server ver 4.15"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
