- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- problem with a logical volume
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
Forums
Discussions
Discussions
Discussions
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
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
01-21-2004 11:12 PM
01-21-2004 11:12 PM
When I try and run make_recovery -A I get:
save_config: error - cannot determine lv "/dev/vg00/monitor" usage via fstyp
And if I try and remove the UNUSED logical volume I get:
image1(root)/opt/ignite/bin> lvremove /dev/vg00/monitor
lvremove: Couldn't delete logical volume "/dev/vg00/monitor":
The supplied lv number refers to a non-existent logical volume.
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.con
f
Anyone know what I need to do to get rid of this lvol?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2004 11:15 PM
01-21-2004 11:15 PM
Re: problem with a logical volume
Does a lvreduce -f -k do the job?
Gideon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2004 11:17 PM
01-21-2004 11:17 PM
Re: problem with a logical volume
Check with "strings /etc/lvmtab" to see if this lvol is still in your lvmtab. If it is, make a new lvmtab:
mv /etc/lvmtab /etc/lvmtab.bak
vgscan -a
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2004 12:03 AM
01-22-2004 12:03 AM
Re: problem with a logical volume
Check /etc/lvmconf/vg00.conf and see wheather monitor logical volume is there ?
please check /dev/vg00/ for device file of monitor logical voulme.
post the o/p of
#ll /dev/vg00
Sunil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2004 12:08 AM
01-22-2004 12:08 AM
Re: problem with a logical volume
That should take care,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2004 12:08 AM
01-22-2004 12:08 AM
Re: problem with a logical volume
image1(root)/dev/vg00> ls -l *monitor*
brw-r----- 1 root sys 64 0x000010 Oct 29 11:12 monitor
crw-r----- 1 root sys 64 0x000010 Oct 29 11:12 rmonitor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-22-2004 12:14 AM
01-22-2004 12:14 AM
SolutionYou might even get a better error message.
If /etc/lvmtab is valid, the script I'm attaching should tell you which physical volume is giving you trouble.
Ignite is now a pretty good tool for finding missing disks because it won't work when one is messed up or turned off.
You may need to deactivate the volume groupo, vgexport the volume group and import it back in.
Then activate it and see if the problem is fixed. Any issues that come up during this process will help you identify and correct the actual problem.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com