Admins,
In my previous post I had the following problem:
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?
Solution: Provided by Dr. Blinn:
If you save the "disklabel -p" output to a file and if in fact it is
correct for the disk in question (TruCluster setup USUALLY uses non-
standard partitioning), then you should be able to write it back to
the disk through the "c" partition with disklabel -w -R and the rest
of the needed flags (e.g., -t advfs since it's an AdvFS boot disk).
Doing it through the "a" partition probably won't work because it's
a mounted disk through the "a" partition. If that fails, you'll have
the ASCII file with the label, and you should be able to apply it by
shutting down that cluster member and writing the label using some
other member that can access the disk.
This worked. My problem was using the "a" partition. Using the "c" partition
did the trick...
Thanks for all of the other responses...
Lee Brewer
Received on Wed Feb 13 2002 - 15:14:42 NZDT