- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: After an Ignite B.4.1.61 boot my lvm config is...
Operating System - HP-UX
1753930
Members
9465
Online
108810
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
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
тАО10-03-2004 09:17 AM
тАО10-03-2004 09:17 AM
After an Ignite B.4.1.61 boot my lvm config is not correct
Server K580 runnning HPUX 11.0 using Ignite B.1.4.61. All VG's are mirrored. After booting from ignite tape the following errors appear in all other volume groups and they appear to be uncorrectable. Is this a known bug in Ignite 4.1.61
# vgdisplay -v /dev/vg03
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Volume groups ---
VG Name /dev/vg03
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 2
Open LV 3
Max PV 16
Cur PV 4
Act PV 3
Max PE per PV 8000
VGDA 6
PE Size (Mbytes) 4
Total PE 4216
Alloc PE 3366
Free PE 850
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg03/archive2
LV Status available/syncd
LV Size (Mbytes) 10000
Current LE 2500
Allocated PE 2500
Used PV 3
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg03/lvol2
LV Status available/syncd
LV Size (Mbytes) 0
Current LE 0
Allocated PE 0
Used PV 0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg03/test
LV Status available/syncd
LV Size (Mbytes) 4000
Current LE 1000
Allocated PE 1000
Used PV 1
--- Physical volumes ---
PV Name /dev/dsk/c3t5d0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 1023
Free PE 0
Autoswitch On
PV Name /dev/dsk/c3t6d0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 1023
Free PE 0
Autoswitch On
PV Name /dev/dsk/c5t14d0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 2170
Free PE 850
Autoswitch On
HELP!!!!!!!!!!!!!!!!!!!!!!
# vgdisplay -v /dev/vg03
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Volume groups ---
VG Name /dev/vg03
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 2
Open LV 3
Max PV 16
Cur PV 4
Act PV 3
Max PE per PV 8000
VGDA 6
PE Size (Mbytes) 4
Total PE 4216
Alloc PE 3366
Free PE 850
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg03/archive2
LV Status available/syncd
LV Size (Mbytes) 10000
Current LE 2500
Allocated PE 2500
Used PV 3
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg03/lvol2
LV Status available/syncd
LV Size (Mbytes) 0
Current LE 0
Allocated PE 0
Used PV 0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
LV Name /dev/vg03/test
LV Status available/syncd
LV Size (Mbytes) 4000
Current LE 1000
Allocated PE 1000
Used PV 1
--- Physical volumes ---
PV Name /dev/dsk/c3t5d0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 1023
Free PE 0
Autoswitch On
PV Name /dev/dsk/c3t6d0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 1023
Free PE 0
Autoswitch On
PV Name /dev/dsk/c5t14d0
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c1t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 2170
Free PE 850
Autoswitch On
HELP!!!!!!!!!!!!!!!!!!!!!!
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2004 09:32 AM
тАО10-03-2004 09:32 AM
Re: After an Ignite B.4.1.61 boot my lvm config is not correct
The reason you may have had to do an ignite recovery is because a disk failed.
Prior to doing an Ignite recovery if possible its always a good idea to check your disks.
diskinfo
dmesg
cstm mstm xstm look for and arrange replacement of any disks that have gone south.
Replace the disk and recovery your system again.
If this isn't a recovery the bad news here is you can't run a good ignite backup without all disks being present and accounted for. Follow the above steps, id and replace the bad disk and the make_tape_recovery will start to work.
Ignite's pickiness may have just done you a HUGE favor.
SEP
Prior to doing an Ignite recovery if possible its always a good idea to check your disks.
diskinfo
dmesg
cstm mstm xstm look for and arrange replacement of any disks that have gone south.
Replace the disk and recovery your system again.
If this isn't a recovery the bad news here is you can't run a good ignite backup without all disks being present and accounted for. Follow the above steps, id and replace the bad disk and the make_tape_recovery will start to work.
Ignite's pickiness may have just done you a HUGE favor.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-03-2004 09:37 AM
тАО10-03-2004 09:37 AM
Re: After an Ignite B.4.1.61 boot my lvm config is not correct
The reason for creating the reovery tape is the first place was to provide a clean recover point in case I had to use it, which I have. I appreciate that Ignite will not reover the mirrors and that I have to recover these manually, however the recovery tape has created the situation where I get these lvm errors and therefore cannot reduce the VG's to then create the mirror sets.
More help please
More help please
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