HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- vgimport failure.
Operating System - Linux
1828413
Members
3465
Online
109977
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
Forums
Discussions
Discussions
Discussions
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
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-15-2008 11:42 AM
10-15-2008 11:42 AM
vgimport failure.
Red Hat Enterprise Linux AS release 3 (Taroon Update 9)
# pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/sdq" is associated to unknown VG "vghw_rds3_p1" (run vgscan)
pvscan -- inactive PV "/dev/sdr" is associated to unknown VG "vghw_rds3_p1" (run vgscan)
pvscan -- inactive PV "/dev/sdt" is in EXPORTED VG "vghw_rds3_p1_arcPV_EXP" [9.94 GB / 960 MB free]
pvscan -- ACTIVE PV "/dev/sda2" of VG "vg00" [418.86 GB / 321.83 GB free]
pvscan -- ACTIVE PV "/dev/sdb" of VG "vghw_rds1_d" [19.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdc" of VG "vghw_rds1_d" [19.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdd" of VG "vghw_rds1_d" [4.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sde" of VG "vghw_rds1_d" [4.94 GB / 768 MB free]
pvscan -- ACTIVE PV "/dev/sdf" of VG "vghw_rds1_d_arc" [7.94 GB / 960 MB free]
pvscan -- ACTIVE PV "/dev/sdg" of VG "vghw_rds3_s_db" [14.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdh" of VG "vghw_rds3_s_db" [14.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdi" of VG "vghw_rds3_s_bin" [9.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdj" of VG "vghw_rds3_s_bin" [4.94 GB / 192 MB free]
pvscan -- ACTIVE PV "/dev/sdk" of VG "vghw_rds3_s_db" [9.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdl" of VG "vghw_rds3_s_arc" [9.94 GB / 160 MB free]
pvscan -- ACTIVE PV "/dev/sdm" of VG "vghw_rds3_s_db" [19.94 GB / 32 MB free]
pvscan -- inactive PV "/dev/sdn" is associated to unknown VG "vghw_rds3_p1" (run vgscan)
pvscan -- inactive PV "/dev/sdo" is associated to unknown VG "vghw_rds3_p1" (run vgscan)
pvscan -- inactive PV "/dev/sdp" is associated to unknown VG "vghw_rds3_p1" (run vgscan)
pvscan -- total: 19 [626.87 GB] / in use: 19 [626.87 GB] / in no VG: 0 [0]
[root@exgld180n .sess_history]# strings /etc/lvmtab
vg00
vghw_rds1_d
vghw_rds1_d_arc
vghw_rds3_s_arc
vghw_rds3_s_bin
vghw_rds3_s_db
# vgimport -v /dev/vghw_rds3_ptest /dev/sdn /dev/sdo /dev/sdp /dev/sdq /dev/sdr
vgimport -- locking logical volume manager
vgimport -- checking volume group name
vgimport -- checking volume group "vghw_rds3_ptest" existence
vgimport -- trying to read physical volumes
vgimport -- checking for duplicate physical volumes
vgimport -- checking physical volume name "/dev/sdn"
vgimport -- reading data of physical volume "/dev/sdn" from disk
vgimport -- checking for exported physical volume "/dev/sdn"
vgimport -- ERROR: physical volume "/dev/sdn" doesn't belong to an exported volume group
vgimport [-d|--debug] [-f|--force] [-h|--help] [-v|--verbose]
VolumeGroupName PhysicalVolumePath [PhysicalVolumePath...]
i am surprised to see why the disks are showing associated with a vg prior to vgimport. Do you think a LUN initilise(pvcreate) will help? The data on the disks are restored from netaps snap volume which is a PROD data from vg vghw_rds3_p1. I tried importing with a different vg name and failed.
let ms know if you have any suggetion.
# pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/sdq" is associated to unknown VG "vghw_rds3_p1" (run vgscan)
pvscan -- inactive PV "/dev/sdr" is associated to unknown VG "vghw_rds3_p1" (run vgscan)
pvscan -- inactive PV "/dev/sdt" is in EXPORTED VG "vghw_rds3_p1_arcPV_EXP" [9.94 GB / 960 MB free]
pvscan -- ACTIVE PV "/dev/sda2" of VG "vg00" [418.86 GB / 321.83 GB free]
pvscan -- ACTIVE PV "/dev/sdb" of VG "vghw_rds1_d" [19.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdc" of VG "vghw_rds1_d" [19.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdd" of VG "vghw_rds1_d" [4.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sde" of VG "vghw_rds1_d" [4.94 GB / 768 MB free]
pvscan -- ACTIVE PV "/dev/sdf" of VG "vghw_rds1_d_arc" [7.94 GB / 960 MB free]
pvscan -- ACTIVE PV "/dev/sdg" of VG "vghw_rds3_s_db" [14.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdh" of VG "vghw_rds3_s_db" [14.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdi" of VG "vghw_rds3_s_bin" [9.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdj" of VG "vghw_rds3_s_bin" [4.94 GB / 192 MB free]
pvscan -- ACTIVE PV "/dev/sdk" of VG "vghw_rds3_s_db" [9.94 GB / 0 free]
pvscan -- ACTIVE PV "/dev/sdl" of VG "vghw_rds3_s_arc" [9.94 GB / 160 MB free]
pvscan -- ACTIVE PV "/dev/sdm" of VG "vghw_rds3_s_db" [19.94 GB / 32 MB free]
pvscan -- inactive PV "/dev/sdn" is associated to unknown VG "vghw_rds3_p1" (run vgscan)
pvscan -- inactive PV "/dev/sdo" is associated to unknown VG "vghw_rds3_p1" (run vgscan)
pvscan -- inactive PV "/dev/sdp" is associated to unknown VG "vghw_rds3_p1" (run vgscan)
pvscan -- total: 19 [626.87 GB] / in use: 19 [626.87 GB] / in no VG: 0 [0]
[root@exgld180n .sess_history]# strings /etc/lvmtab
vg00
vghw_rds1_d
vghw_rds1_d_arc
vghw_rds3_s_arc
vghw_rds3_s_bin
vghw_rds3_s_db
# vgimport -v /dev/vghw_rds3_ptest /dev/sdn /dev/sdo /dev/sdp /dev/sdq /dev/sdr
vgimport -- locking logical volume manager
vgimport -- checking volume group name
vgimport -- checking volume group "vghw_rds3_ptest" existence
vgimport -- trying to read physical volumes
vgimport -- checking for duplicate physical volumes
vgimport -- checking physical volume name "/dev/sdn"
vgimport -- reading data of physical volume "/dev/sdn" from disk
vgimport -- checking for exported physical volume "/dev/sdn"
vgimport -- ERROR: physical volume "/dev/sdn" doesn't belong to an exported volume group
vgimport [-d|--debug] [-f|--force] [-h|--help] [-v|--verbose]
VolumeGroupName PhysicalVolumePath [PhysicalVolumePath...]
i am surprised to see why the disks are showing associated with a vg prior to vgimport. Do you think a LUN initilise(pvcreate) will help? The data on the disks are restored from netaps snap volume which is a PROD data from vg vghw_rds3_p1. I tried importing with a different vg name and failed.
let ms know if you have any suggetion.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-15-2008 08:13 PM
10-15-2008 08:13 PM
Re: vgimport failure.
According to your output the physical volumes belong to the volume group named "vghw_rds3_p1" but your vgimport, you were referring to vghw_rds3_ptest.
The command you wanted to type should look something like this:
vgimport -v vghw_rds3_p1 /dev/sd[nopqr]
Perhaps you would like to run the vgscan first as suggested by the pvscan command ;)
The command you wanted to type should look something like this:
vgimport -v vghw_rds3_p1 /dev/sd[nopqr]
Perhaps you would like to run the vgscan first as suggested by the pvscan command ;)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2008 09:53 AM
10-17-2008 09:53 AM
Re: vgimport failure.
that was my second attempt with a different vg name. First tried with vghw_rds3_p1 only.
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP