Admins,
I have created a problem for myself. In the process of adding a new disk to my
system, I typed
disklabel -z dsk5
instead of disklabel -z dsk53...
dsk5 is my cluster boot disk for member2. In particular....
I have a two member GS160 cluster, the cluster root and boot disks are located
on a SAN via HSG80 controllers, I'm using TruCluster 5.1 on Tru64 5.1 patch kit
3... Member one is down currently for Hardware failures.
The in memory copy is fine... A disklabel -p produces the correct vaules. I
tried editing the label, but as I thought I can't because its in use... dsk5
conatins the boot block for loading.... Any one have any suggestions?
Lee Brewer
Received on Thu Jan 31 2002 - 21:00:22 NZDT