- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Couldn't access the list of physical volumes f...
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
тАО04-02-2014 03:25 AM
тАО04-02-2014 03:25 AM
Couldn't access the list of physical volumes for volume group "/dev/test".
Hi,
I cant import volume group to another node
the following error come:---
Couldn't access the list of physical volumes for volume group "/dev/test".
NODE 1
uatdata4#ll /dev/*/group
crw-r----- 1 root sys 64 0x010000 Mar 26 12:22 /dev/asd/group
crw-r----- 1 root sys 64 0x030000 Apr 2 10:43 /dev/test/group
crw-r----- 1 root sys 64 0x000000 Mar 14 19:07 /dev/vg00/group
crw-rw-rw- 1 root sys 64 0x020000 Mar 31 14:12 /dev/vglock/group
gexport -p -v -s -m /test.map test
NODE 2
ioscan -m dsf
/dev/rdisk/disk13 /dev/rdsk/c4t0d1
/dev/rdsk/c2t0d1
/dev/rdisk/disk14 /dev/rdsk/c2t0d2
/dev/rdsk/c4t0d2
uatdata2#mkdir /dev/test
uatdata2#pvcreate -f /dev/rdsk/c2t0d2
Physical volume "/dev/rdsk/c2t0d2" has been successfully created.
uatdata2#mknod /dev/test/group c 64 0x030000
uatdata2#vgimport -p -v -s -m /test.map test
Beginning the import process on Volume Group "test".
Couldn't access the list of physical volumes for volume group "/dev/test".
Please help me......
Thanks
aamir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-02-2014 03:34 AM
тАО04-02-2014 03:34 AM
Re: Couldn't access the list of physical volumes for volume group "/dev/test".
>> uatdata2#pvcreate -f /dev/rdsk/c2t0d2
In this case you just deleted it.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-02-2014 03:45 AM
тАО04-02-2014 03:45 AM
Re: Couldn't access the list of physical volumes for volume group "/dev/test".
Hi,
Please ignore last message.
again i do but still shown same error:
uatdata2#
uatdata2#rm -rf /dev/test
uatdata2#vgexport test
vgexport: Volume group "/dev/test" does not exist in the "/etc/lvmtab" file.
vgexport: Volume group "/dev/test" does not exist in the "/etc/lvmtab_p" file.
vgexport: Couldn't export volume group "test".
uatdata2#
uatdata2#pvcreate -f /dev/rdsk/c2t0d2
Physical volume "/dev/rdsk/c2t0d2" has been successfully created.
uatdata2#ll /dev/*/group
crw-r----- 1 root sys 64 0x000000 Mar 25 15:47 /dev/vg00/group
crw-rw-rw- 1 root sys 64 0x020000 Apr 2 12:30 /dev/vglock/group
uatdata2#mkdir /dev/test
uatdata2#mknod /dev/test/group c 64 0x030000
uatdata2#vgimport -p -v -s -m /test.map test
Beginning the import process on Volume Group "test".
Couldn't access the list of physical volumes for volume group "/dev/test".
uatdata2#strings test.map
VGID 3a9be234533bb629
uatdata2#
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-02-2014 03:50 AM - edited тАО04-02-2014 06:46 AM
тАО04-02-2014 03:50 AM - edited тАО04-02-2014 06:46 AM
Re: Couldn't access the list of physical volumes for volume group "/dev/test".
Why pvcreate???
You wiped the disk!
You may try to restore the LVM information with vgcfgrestore on node1, but this information is wiped too if you used vgexport without "p" for preview.
Re-create the VG and restore the data from backup.
In case of doubt, first ask, then do.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2015 03:51 PM
тАО12-15-2015 03:51 PM
Re: Couldn't access the list of physical volumes for volume group "/dev/test".
Hello, i have the next problem:
i migrated the san disks of hpux 11.31 server to a vm running hpux 11.31 too. But when i execute the vgimport command on the vm for activate the volume groups i receive the next messages:
vgimport -p -s -v -m /sort/MAPAS/vguspv2softempfian2.map /dev/vguspv2softempfian2
Beginning the import process on Volume Group "/dev/vguspv2softempfian2".
Couldn't access the list of physical volumes for volume group "/dev/vguspv2softempfian2".
when i checked the disks status, i saw the next:
a) running the "ioscan" command:
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
disk 36 64000/0xfa00/0x27 esdisk CLAIMED DEVICE HITACHI OPEN-V
/dev/disk/disk36 /dev/rdisk/disk36
disk 37 64000/0xfa00/0x28 esdisk CLAIMED DEVICE HITACHI OPEN-V
/dev/disk/disk37 /dev/rdisk/disk37
disk 38 64000/0xfa00/0x29 esdisk CLAIMED DEVICE HITACHI OPEN-V
/dev/disk/disk38 /dev/rdisk/disk38
disk 39 64000/0xfa00/0x2a esdisk CLAIMED DEVICE HITACHI OPEN-V
/dev/disk/disk39 /dev/rdisk/disk39
disk 40 64000/0xfa00/0x2b esdisk CLAIMED DEVICE HITACHI OPEN-V
/dev/disk/disk40 /dev/rdisk/disk40
disk 41 64000/0xfa00/0x2c esdisk CLAIMED DEVICE HITACHI OPEN-V
/dev/disk/disk41 /dev/rdisk/disk41
b) By smh utility:
Size 16.0007 GB
Block Size (bytes) 512
Capacity (blocks) 33555840
Use LVM
VG Name -
Device Type direct access
Instance Number 39
Total Path Count 1
Device Class disk
Driver esdisk
State UNOPEN
Vendor "HITACHI "
Product "OPEN-V "
Serial Number "45688 "
Firmware Revision "5001"
SCSI Protocol Revision 2
c) By lunpath:
LUN PATH INFORMATION FOR LUN : /dev/rdisk/disk226
Total number of LUN paths = 1
World Wide Identifier(WWID) = 0x60060e8005b278000000b27800000eb5
LUN path : lunpath249
Class = lunpath
Instance = 249
Hardware path = 0/0/2/0/0.0x50060e8005b27870.0x40be000000000000
SCSI transport protocol = Virtual Storage HBA
State = UNOPEN
Last Open or Close state = ACTIVE
LUN PATH INFORMATION FOR LUN : /dev/rdisk/disk227
Total number of LUN paths = 1
World Wide Identifier(WWID) = 0x60060e8005b278000000b27800000640
LUN path : lunpath250
Class = lunpath
Instance = 250
Hardware path = 0/0/2/0/0.0x50060e8005b27870.0x40c0000000000000
SCSI transport protocol = Virtual Storage HBA
State = UNOPEN
Last Open or Close state = ACTIVE
Questions:
1) If all disks for this volume group are CLAIMED, why cant activate the volume group ??
How can fix this issue ??
Regards