- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Missing volume groups
Operating System - HP-UX
1753785
Members
7637
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО08-24-2001 12:28 AM
тАО08-24-2001 12:28 AM
Hi folks
My server crashed and upon reboot it appears some of the volume groups are missing (spanning different disks).
I tried renaming lvmtab and running vgscan -v.
It listed the missing volume groups as "The volume group /dev/vgxx/group was not matched with any Physical Volumes."
Any help is greatly appreciated
My server crashed and upon reboot it appears some of the volume groups are missing (spanning different disks).
I tried renaming lvmtab and running vgscan -v.
It listed the missing volume groups as "The volume group /dev/vgxx/group was not matched with any Physical Volumes."
Any help is greatly appreciated
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2001 12:52 AM
тАО08-24-2001 12:52 AM
Re: Missing volume groups
Terry,
seems to me your volume groups are not activated. You have to activate VG's at boot time in /etc/lvmrc.
Put your VG in there; reboot and you will see your missing groups.
to activate the VG not permanently at boot time issue the command
vgchange -a /dev/vgxx
Regards
Rainer
He's a real UNIX Man, sitting in his UNIX LAN making all his UNIX plans for nobody ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2001 12:58 AM
тАО08-24-2001 12:58 AM
Re: Missing volume groups
Thanks for your help
I was able to get it sorted.
I was able to get it sorted.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2001 01:06 AM
тАО08-24-2001 01:06 AM
Solution
Move back your lvmtab to the original position or else the vgchange won't work.
vgchange -a y vgname
ll /etc/lvmconf/
and look for vgname.conf
vgcfgrestore -n /dev/vgname -l
to list what pvs are associated to the vgname and recorded in the /etc/lvmconf/vgname.conf
strings /etc/lvmtab to verify they are the same
From the device file for the vgname pv
issue and ioscan -fnkCdisk
and verify that the device for the PV is showing up as CLAIMED.
If it is not there, the hardware has probably failed and you should interrogate via ioscan -fnk exactly what has gone missing.
If it is claimed, the h/w has not failed and you probably have a vg not activating for some reason or other.. /etc/lvmrc customised activation is one reason.
vgchange -a y vgname
will manually activate.
Note any warnings.
Quorum errors mean that less than 51% of the disks are available in the vg, you can force activation to see what remains with
vgchange -a y -q n vgname
vgdisplay -v vgname
vgdisplay -v vgname will give you much information about the health of the vg, once it activates that is.
Have a look in your
/etc/shutdownlog
and
/var/adm/syslog/syslog.log
and OLDsyslog to see what happened prior to and after shutdown.
Later,
Bill
vgchange -a y vgname
ll /etc/lvmconf/
and look for vgname.conf
vgcfgrestore -n /dev/vgname -l
to list what pvs are associated to the vgname and recorded in the /etc/lvmconf/vgname.conf
strings /etc/lvmtab to verify they are the same
From the device file for the vgname pv
issue and ioscan -fnkCdisk
and verify that the device for the PV is showing up as CLAIMED.
If it is not there, the hardware has probably failed and you should interrogate via ioscan -fnk exactly what has gone missing.
If it is claimed, the h/w has not failed and you probably have a vg not activating for some reason or other.. /etc/lvmrc customised activation is one reason.
vgchange -a y vgname
will manually activate.
Note any warnings.
Quorum errors mean that less than 51% of the disks are available in the vg, you can force activation to see what remains with
vgchange -a y -q n vgname
vgdisplay -v vgname
vgdisplay -v vgname will give you much information about the health of the vg, once it activates that is.
Have a look in your
/etc/shutdownlog
and
/var/adm/syslog/syslog.log
and OLDsyslog to see what happened prior to and after shutdown.
Later,
Bill
It works for me (tm)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP