- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- VGSCAN errors:
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
04-12-2001 01:58 PM
04-12-2001 01:58 PM
VGSCAN errors:
when I try to vgscan, i get the following: How do i fix it?
Physical Volume "/dev/dsk/c2t6d0" contains no LVM information
Couldn't stat physical volume "/dev/dsk/c7t2d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c7t3d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c7t4d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c7t5d0":
Invalid argument
Couldn't stat physical volume "/dev/dsk/c7t6d0":
Invalid argument
Physical Volume "/dev/dsk/c7t6d2" is not part of a Volume Group
Physical Volume "/dev/dsk/c7t6d6" is not part of a Volume Group
Couldn't stat physical volume "/dev/dsk/c7t7d0":
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2001 02:24 PM
04-12-2001 02:24 PM
Re: VGSCAN errors:
I'd try this after (re)reading the man pages for 'vgscan':
Make a good backup copy of your current /etc/lvmtab before you start.
# cp /etc/lvmtab /etc/lvmtab.old
Now, remove the file and issue the 'vgscan' to rebuild it. The idea is that if /etc/lvmtab exists, the information contained in it is used to assist in rebuilding the file, and/but the existing file is updated with the new corrected configuration. So:
# rm /etc/lvmtab
# vgscan -a -v > /tmp/vgscan.log 2>&1
Again, pay attention to the guidelines in the man pages for 'vgscan' regarding alternate links and/or boot devices. Also note from the man pages that after 'vgscan' completes successfully, you should run 'vgimport' on each set of unmatched physical volumes.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2001 01:00 AM
04-13-2001 01:00 AM
Re: VGSCAN errors:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2001 04:34 AM
04-13-2001 04:34 AM
Re: VGSCAN errors:
vgscan is designed to scan all disks in numerical order looking for LVM headers in order to recreate the lvmtab. Unfortunately the command relies on you knowing what you're doing and being able to examine the /etc/lvmtab
in order to correct thing to do bus traffic management better... using vgreduce and vgextend.
a pvdisplay on the device files showld also give some info.. but only use vgscan if something is screwed up with your /etc/lvmtab.
Later,
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2001 09:16 AM
04-19-2001 09:16 AM
Re: VGSCAN errors:
Now there are 2 related posts with not enough background info to properly advise. What are we trying to accomplish? Has there been a hardware failure? HBA or storage frame? Have devices been reconfigured, changed Target/LUN, or something like that? Disks added, removed or relocated?
There may be old device files out there that no longer are associated with real hardware and need to be cleaned up? Also, the system may need to discover new device addressing if there have been changes? This would require a reboot or a plain ioscan.
More info of this nature would be helpful in deciding whether your situation requires vgscan, vgimport, or possibly vgreduce -f and then vgextend. Bottom line would be is there data on some devices that needs to be recovered, or are you just trying to get some disks into a volume group?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2001 04:24 AM
05-07-2001 04:24 AM
Re: VGSCAN errors:
Had you change the disk? if you have done this, you must be restore the LVM configuration whit vgcfgrestore and make the new FS