- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- LVM/MirrorDisk UX help
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
тАО03-18-2008 10:21 AM
тАО03-18-2008 10:21 AM
Is there someway to change the volume group so that it no longer looks for the failed drive without crashing the system through vgchange.
The failed disk is c4t6d0 in the volume group vgarray.
Here is the volume group layout...
# strings /etc/lvmtab
/dev/vg00
/dev/dsk/c3t6d0
/dev/dsk/c3t5d0
/dev/vgarray
/dev/dsk/c4t5d0
/dev/dsk/c4t6d0
Drive c4t6d0 is missing from ioscan
# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 0 10/0/14/0.0.0 sdisk CLAIMED DEVICE TEAC CD-532E-B CDROM
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 10/0/15/1.5.0 sdisk CLAIMED DEVICE QUANTUM ATLAS10K-18LVD
/dev/dsk/c3t5d0 /dev/rdsk/c3t5d0
disk 2 10/0/15/1.6.0 sdisk CLAIMED DEVICE QUANTUM ATLAS10K-18LVD
/dev/dsk/c3t6d0 /dev/rdsk/c3t6d0
disk 3 10/4/3/0.5.0 sdisk CLAIMED DEVICE SEAGATE ST318275LC
/dev/dsk/c4t5d0 /dev/rdsk/c4t5d0
dd fails.
# dd if=/dev/dsk/c4t6d0 of=/dev/null bs=512 count=1
/dev/dsk/c4t6d0: No such device or address
dd: cannot open /dev/dsk/c4t6d0
Any help is greatly appreciated.
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-18-2008 10:41 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-18-2008 10:44 AM
тАО03-18-2008 10:44 AM
Re: LVM/MirrorDisk UX help
#vgreduce -l /dev/vgarray
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-18-2008 03:11 PM
тАО03-18-2008 03:11 PM
Re: LVM/MirrorDisk UX help
Normally, a failed drive will not cause any problems to the running system. Check to see that you have disk mirroring software installed:
swlist -l product | grep -ie mirror
If not, then the disk is not mirrored and you'll have to remove the entire volume group and re-create it, followed by a data restoration. Otherwise, I would check lvdisplay on one of the lvols on this disk just to verify that it is mirrored. To avoid errors caused by the bad drive, just pull it out. The system should boot and recover without any problem (if the disks are mirrored).
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-22-2008 07:06 AM
тАО03-22-2008 07:06 AM
Re: LVM/MirrorDisk UX help
# mv /etc/lvmtab /etc/lvmtab.bkp
# vgscan -v
### If the volume group vgarry is still showing then. . .
# vgchange -a n /dev/vgarry
# vgexport -m /dev/vgarry.map vgarry
# mkdir /dev/vgarry
# mknod /dev/vgarry/group c 64 0x010000
# vgimport /dev/vgarry /dev/dsk/c4t5d0
# vgchange -a y /dev/vgarry
# mountall
It's going to work !!!
Regards,
Piyush Mathiya