LSM Disk replacement

[David_854]

Is there a procedure to replace a lsm disk where the the disk number is rz8 and is a mirrored rootdg disk under 4.0f

TIA,

David

[Mark Poeschl_2]

There is a procedure using voldiskadm for removing and replacing a failed disk in sections 9.2.5.2 and 9.2.6 respectively in the doc at:

http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V40F_HTML/AQ3NCETE/TITLE.HTM

[David_854]

Thanks Mark, That is the procedure I was looking for.

David

[Ross Minkov · Accepted solution]

David,

Here is an LSM doc that I had. Just replace rz9 with rz8 in it.


LSM - Replacing a Failed Disk
=============================

· Delete the failed disk, for example rz9 from the disk group retaining the media
records. Use the disk media name.
# /sbin/voldg -g rootdg -k rmdisk disk09b
rmdisk
Removes the specified disk(s) from a disk group (rootdg by default).
The last disk cannot be removed from its disk group. It is not possible
to remove the last disk containing a valid disk group configuration or
log copy from its disk group.

Normally, the rmdisk operation will fail if subdisk records point to
the named disk media records. However, if the -k option is specified,
the disk media records will be kept, although in a removed state, and
the subdisk records will still point to them. The subdisks, and any
plexes that refer to them, are unusable until the disk is re-added
using the -k option to the adddisk operation. Any volumes that become
unusable, because all plexes become unusable, will be disabled.

Note

Use extra care with the -k option since this option can disable
active volumes.

· Remove the disk access records, using the disk access name.
# /sbin/voldisk rm rz9b
· Physically replace the failed disk with a new disk.
· Disk label the new disk.
· Initialize the new disk for use by LSM.
# /usr/sbin/voldisksetup -i rz9b nconfig=2 nlogs=2 privlen=1024
-i Normally, voldisksetup simply creates partitions for use with the Logi-
cal Storage Manager. If the -i (initialize) option is specified, a disk
header is added and an empty configuration is written on the disk. This
operation destroys any previous LSM database contents on the disk.

· Add the new disk to the disk group.
# /sbin/voldg -g rootdg -k adddisk disk09b=rz9b

· If this is a mirrored volume, attach the stale plex, start the volume, and start recovery.
# volrecover -sb vol-01

-s Starts disabled volumes that are selected by the operation. Volumes
will be started before any other recovery actions are taken. Volumes
will be started with the -o delayrecover start option. This requests
that any operations that can be delayed in starting a volume will be
delayed. In other words, only those operations necessary to make a
volume available for use will occur. Other operations, such as mirror
resynchronization, attaching of stale plexes and subdisks, and recovery
of stale RAID5 parity will normally be delayed.

-b Performs recovery operations in the background. With this option,
volrecover will put itself in the background to attach stale plexes and
subdisks, and to resynchronize mirrored volumes and RAID5 parity. If
this is used with -s, volumes will be started before recovery begins in
the background.



===========================================

[David_854]

Thank you to all your replies. This really helped alot.

David