- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: LSM Disk replacement
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2005 08:08 AM
тАО06-03-2005 08:08 AM
TIA,
David
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2005 09:41 AM
тАО06-03-2005 09:41 AM
Re: LSM Disk replacement
http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V40F_HTML/AQ3NCETE/TITLE.HTM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2005 11:31 AM
тАО06-03-2005 11:31 AM
Re: LSM Disk replacement
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2005 06:57 PM
тАО06-03-2005 06:57 PM
SolutionDavid,
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.
===========================================
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-05-2005 01:29 PM
тАО06-05-2005 01:29 PM
Re: LSM Disk replacement
David