Replacing failed LSM mirrored disk

[Mihails Nikitins]

Hi,

Does anyone have a good procedure for replacing failed LSM mirrored disk?

I found a document here, but I'm not sure that this is optimal.

http://www.ornl.gov/cts/archives/mailing-lists/tru64-unix-managers/2001/05/msg00120.html

It supposes a lot of remove commands for all partitions like:

volplex dis vol-rz16g-02
voledit -fr rm vol-rz16g-02
voldg rmdisk rz17g
voldisk rm rz17g

Is it possible to remove disk and dependent LSM data structures with less commands?

Then single volrootmirr is supposed to do everything.

volrootmir -a rz17

I think "volmirror" should be used for non-root disks, like

/usr/sbin/volmirror disk_old disk_new

Thanks and points in advance for your comments!

BR,
Mihails

[Joris Denayer · Accepted solution]

Hi Mihails,

For non-boot devices, have a look in chapter 6.4.5 on

http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51B_HTML/ARH9BDTE/TITLE.HTM

Chapter 6.4.6 gives the explanations for bootdevices.


BTW: The complete documentation sets are at http://h30097.www3.hp.com/docs/pub_page/doc_list.html

Rgrds

Joris

[Mihails Nikitins]

Hi Joris,

Thank you for your reply!
I run Tru64 4.0F and it's LSM Manual was not so good and straightforward. That was the problem.

I hope LSM was mostly the same in 4.0F and I can use the commands with some exceptions (e.g. hwmgr is not available on my system).

BR,
Mihails

[Ralf Puchner]

1.) get disk access name and disk media name of the failed disk

# voldisk list
# volprint -Aht

2.) remove failed disk from lsm

# voldg -g -k rmdisk
wichtig: -k
# voldisk rm

3.) change disk

4.) write new disklabel

# disklabel -rw rzxxx

5.) init disk for lsm

# voldisksetup -i rzxxx

6.) link disk and diskgroup

# voldg -g -k adddisk =

7.) starting recovery of mirror

volrecover -g -sb

8.) additional work within ase:
# asemgr

m) Managing ASE Services -->
a) Advanced Utilities -->
r) re-reserve a service's devices (LSM only)

[Mihails Nikitins]

Hi,

Thanks for the replies. Procedure from v. 5.1. was OK.

In 4.0F one can use command "scu" instead of hwmgr
to detect SCSI devices.

scu scan edt all; scu show edt

BR,
Mihails