Hello Again
My original posting is attached at the bottom, thankfully the disk has now
been replaced and we have a happily mirrored (via LSM) system disk.
As is usually the case with LSM I received several responses with slightly
differing methods of reaching the same goal. It was good to hear that it is
not just me who thought the documentation was a little vague in this area.
Anyway all agreed that the general procedure is :
* 1. Disassociate the plexes on the failed disk from rootvol, swapvol
and any other volumes on the boot disk.
* 2. Remove the failed LSM disks from the diskgroup.
* 3. Re mirror the bootdisk volumes on to a replacement disk.
Nearly everyone agreed on how to do step 1.
# volplex -o rm dis rootvol-01 (rz0 had failed in our case)
# volplex -o rm dis swapvol-01
# volplex -o rm dis vol-rz0d-01
# volplex -o rm dis vol-rz0e-01
Carlos Chua suggested the above procedure using two steps i.e.
# volplex dis rootvol-01
and then
# voledit -r rm rootvol-01
for each plex, this will give the same result as the one line command above.
There were few variations in how to achieve step 2.
Most suggested :
- remove disk from the disk group
# voldg rmdisk rz0a
# voldg rmdisk rz0b
# voldg rmdisk rz0d
# voldg rmdisk rz0e
followed by :
- remove the disk access records
# voldisk rm rz0a
# voldisk rm rz0b
# voldisk rm rz0d
# voldisk rm rz0e
It was suggested (by Carlos) to remove rz0d (presumably rz0f in our case -
the priv disk) from volboot at this point :
# voldctl rm disk rz0d
Now step 3. Replace the faulty disk, label it, make the a partition the same
size as the a partition from which the mirror will be copied, and make the b
partition the same size plus 1024 blocks.
Then initiate the copy :
# volrootmir -a rz0
Thanks for all the responses. The procedure we actually followed was
provided by the Compaq support centre (center for those of you in the
U.S.)here in the U.K. reproduced here :
First disassociate the plexes
# volplex -o rm dis rootvol-01
# volplex -o rm dis swapvol-01
# volplex -o rm dis vol-rz0d-01
# volplex -o rm dis vol-rz0e-01
Remove the diskname and pointer from LSM (Can fail if done in one step so
two commands )
# voldg -k rmdisk rz0a
# voldg -k rmdisk rz0b
# voldg -k rmdisk rz0d
# voldg -k rmdisk rz0e
# voldg rmdisk rz0a
# voldg rmdisk rz0b
# voldg rmdisk rz0d
# voldg rmdisk rz0e
(N.B. We also got rid of rz0f the priv disk !! , as voldisk list was
displaying it)
Remove the device name from LSM
# voldisk rm rz0a
# voldisk rm rz0b
# voldisk rm rz0d
# voldisk rm rz0e
Replaced rz0.
Labeled it.
# volrootmir -a rz0
And everything worked fine - thank goodness !!!!
Kevin Jones
> -----Original Message-----
>
> Greetings Managers
>
> The scenario is :
>
> Alphaserver ES40
> Tru64 V4.0F
> 2 x 18Gb internal disks.
>
> The two internal (boot) disks DKA0 (rz0) and DKA100 (rz1) have been
> mirrored
> using LSM
> - volencap rz0
> - volrootmir -a rz1 (after various modifications to the rz1 disklabel)
>
> Everything was happy until a recent shutdown/power-off. After power on,
> error message on console stating that dka0 disabled via run/stop switch.
> Tried booting dka0 - no joy. Booted dka100 but problems further into the
> boot SCSI CAM errors. Removed DKA0 from system and booted DKA100 no
> problem.
>
> The question is : What is the cleanest way of replacing DKA0 (rz0) back
> into
> LSM control. The LSM manual is not exactly clear !!
>
> LSM does seem extremely complicated to configure/modify - hardware RAID
> controllers would be my first choice everytime !!
>
> Many thanks in advance
>
> Kevin Jones
>
> -------------------------------------------------------------------
> Standard Email disclaimer follows for legal reasons....
>
> The information in this e-mail is confidential and is intended for the
> addressee only. Copying or use by anybody else is not authorised. Its
> content does not necessarily represent the opinion of Hamilton Rentals
> PLC (part of the Compel Group) or any of its affiliates. If you are not
> the intended recipient, please advise the sender by return e-mail.
>
> This email was scanned for over 40,000 known viruses by
> kerberos.hamilton.co.uk. It was deemed clean for transmission.
> --------------------------------------------------------------------
-------------------------------------------------------------------
Standard Email disclaimer follows for legal reasons....
The information in this e-mail is confidential and is intended for the
addressee only. Copying or use by anybody else is not authorised. Its
content does not necessarily represent the opinion of Hamilton Rentals
PLC (part of the Compel Group) or any of its affiliates. If you are not
the intended recipient, please advise the sender by return e-mail.
This email was scanned for over 40,000 known viruses by
kerberos.hamilton.co.uk. It was deemed clean for transmission.
--------------------------------------------------------------------
Received on Mon Jan 24 2000 - 18:39:06 NZDT