HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Adding existing LVMs to new system after a rei...
Operating System - HP-UX
1837779
Members
3963
Online
110119
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
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
01-24-2002 09:04 AM
01-24-2002 09:04 AM
Hi
I had a C3000 boot disk died after a power outage. The disk has been replaced and HP-UX 10.20 ( ACE w/ patches applied ) has been reinstalled.
The C3000 previously had an AutoRaid array attached. It has been reattached, the array is recognized by ioscan and SAM. vgscan also sees the array disks, but how do I get these disk back into my physical volumes?
It is unknown exactly where they were mounted; there is no LVM mapping saved from the previous system.
Thoughts, instructions, ideas are all welcome!
THX,
Jay
I had a C3000 boot disk died after a power outage. The disk has been replaced and HP-UX 10.20 ( ACE w/ patches applied ) has been reinstalled.
The C3000 previously had an AutoRaid array attached. It has been reattached, the array is recognized by ioscan and SAM. vgscan also sees the array disks, but how do I get these disk back into my physical volumes?
It is unknown exactly where they were mounted; there is no LVM mapping saved from the previous system.
Thoughts, instructions, ideas are all welcome!
THX,
Jay
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 09:10 AM
01-24-2002 09:10 AM
Re: Adding existing LVMs to new system after a reinstall
Hi Jay,
You can do a vgscan and get info on the VG and lv you had on the disk array. jfs does not save any info about where the lv was last mounted so i guess you have to mount them manually and look at the files / data on it and decide where it should be mounted.
Hope this helps.
Regds
You can do a vgscan and get info on the VG and lv you had on the disk array. jfs does not save any info about where the lv was last mounted so i guess you have to mount them manually and look at the files / data on it and decide where it should be mounted.
Hope this helps.
Regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 09:11 AM
01-24-2002 09:11 AM
Re: Adding existing LVMs to new system after a reinstall
You could recover the map files from a previous backup and try to reimport them. The ideal situation would have been to use an ignte tape you created, which would have recovered the core vg00, including the old lvm inforamtion. Do you, by chance have an ignite tape?
Hope this helps
Chris
Hope this helps
Chris
It wasn't me!!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 09:15 AM
01-24-2002 09:15 AM
Solution
Hi,
Try this:
# vgscan ( this will report all disks which has LVM informations on it. Print this out and determine which disks are part of which VG)
Create VG group files:
# mkdir /dev/vg01
# mknod /dev/vg01/group c 64 0x010000 ( for creating group file for vg01.)
repeat this steps for each VG. for eg:
# mknod /dev/vg02/group c 64 0x020000 - for vg02
Import/activate volume groups:
# vgimport /dev/vg01 /dev/dsk/cxtxdx /dev/dsk/cxtxdx ( using information from vgscan)
# vgchange -a y vg01
# vgdiaplay -v /dev/vg01
find out LV information from this. Repeat this step for each VG
Mount LVs:
# mkdir /mount_dir ( create mount directories)
# mount /dev/vg01/lvol1 /mount_dir
repeat this step for all LVs. Do an 'fsck' if there is some file system error.
HTH,
Shiju
Try this:
# vgscan ( this will report all disks which has LVM informations on it. Print this out and determine which disks are part of which VG)
Create VG group files:
# mkdir /dev/vg01
# mknod /dev/vg01/group c 64 0x010000 ( for creating group file for vg01.)
repeat this steps for each VG. for eg:
# mknod /dev/vg02/group c 64 0x020000 - for vg02
Import/activate volume groups:
# vgimport /dev/vg01 /dev/dsk/cxtxdx /dev/dsk/cxtxdx ( using information from vgscan)
# vgchange -a y vg01
# vgdiaplay -v /dev/vg01
find out LV information from this. Repeat this step for each VG
Mount LVs:
# mkdir /mount_dir ( create mount directories)
# mount /dev/vg01/lvol1 /mount_dir
repeat this step for all LVs. Do an 'fsck' if there is some file system error.
HTH,
Shiju
Life is a promise, fulfill it!
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP