- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Model 20 help
Disk Enclosures
1753338
Members
5343
Online
108792
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-13-2008 06:55 AM
тАО10-13-2008 06:55 AM
Model 20 help
Our G70 server crashed (drive failure). After replacing drives and getting the server operational, we couldn't mount our RAID volumes on the Model 20. Actually two of the three volumes show. If I go into sam I get:
Disk Devices 0 of 7 selected
------------------------------------------------------------------------------
Hardware Number Volume Total
Path of Paths Use Group Mbytes Description
/---------------------------------------------------------------------------\
| 16.0 1 -- -- -- HP Model 20 Disk Array ^
| 16.0.0 1 LVM vg02 16026 HP Model 20 LUN (RAID
| 16.0.1 1 Unused -- 33646 HP Model 20 LUN (RAID
| 16.1 1 -- -- -- HP Model 20 Disk Array
| 52.3.0 1 Unused vg00 8683 SEAGATE ST19171N
| 52.4.0 1 LVM vg00 2033 HP C2490 SCSI Disk Dri
| 52.6.0 1 LVM vg00 4095 Quantum XP34361S
I select the "unused" disk (16.0.1) and try to add the volume group but the response is "volume group already exists, adding will delete all data". Obviously I don't want to lose the data. How do get this lv to show up again?
FYI
Model G70 hpux 10.20
Model 20 w/ 2 storage processors + bpu +
(10) 9gb drives
Disk Devices 0 of 7 selected
------------------------------------------------------------------------------
Hardware Number Volume Total
Path of Paths Use Group Mbytes Description
/---------------------------------------------------------------------------\
| 16.0 1 -- -- -- HP Model 20 Disk Array ^
| 16.0.0 1 LVM vg02 16026 HP Model 20 LUN (RAID
| 16.0.1 1 Unused -- 33646 HP Model 20 LUN (RAID
| 16.1 1 -- -- -- HP Model 20 Disk Array
| 52.3.0 1 Unused vg00 8683 SEAGATE ST19171N
| 52.4.0 1 LVM vg00 2033 HP C2490 SCSI Disk Dri
| 52.6.0 1 LVM vg00 4095 Quantum XP34361S
I select the "unused" disk (16.0.1) and try to add the volume group but the response is "volume group already exists, adding will delete all data". Obviously I don't want to lose the data. How do get this lv to show up again?
FYI
Model G70 hpux 10.20
Model 20 w/ 2 storage processors + bpu +
(10) 9gb drives
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-13-2008 09:31 PM
тАО10-13-2008 09:31 PM
Re: Model 20 help
Some things to try:
Do a preview of vgscan
# vgscan -p -v
and check the array status either with stm or gridmanager.
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!
Do a preview of vgscan
# vgscan -p -v
and check the array status either with stm or gridmanager.
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
тАО10-14-2008 05:13 AM
тАО10-14-2008 05:13 AM
Re: Model 20 help
Here's the output of vgscan:
vgscan -p -v
vgscan: Warning: couldn't query physical volume "/dev/dsk/c1t3d0":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query all of the physical volumes.
vgscan: The physical volume "/dev/dsk/c0t0d0" is already recorded in the "/etc/l
vmtab" file.
vgscan: The physical volume "/dev/dsk/c0t1d0" is already recorded in the "/etc/l
vmtab" file.
vgscan: The physical volume "/dev/dsk/c1t3d0" is already recorded in the "/etc/l
vmtab" file.
vgscan: The physical volume "/dev/dsk/c1t4d0" is already recorded in the "/etc/l
vmtab" file.
vgscan: The physical volume "/dev/dsk/c1t6d0" is already recorded in the "/etc/l
vmtab" file.
Current path "/dev/dsk/c0t1d0" is an alternate link, skip.
reading LVMREC, please wait....
Couldn't stat physical volume "/dev/dsk/c1t2d0":
Invalid argument
/dev/vg02
/dev/dsk/c0t0d0
/dev/dsk/c0t1d0
reading VGDA, please wait....
reading VGDA, please wait....
filling VGDA, please wait....
Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c0t0d1
/dev/dsk/c0t1d1
Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c1t3d0
/dev/vg00
/dev/dsk/c1t4d0
/dev/dsk/c1t6d0
Gridmgr shows:
SP A:
Prom Revision 1.73
Micro Code Revision 8.60
All 10 drives show ENA
SP B:
Prom Revision 1.73
Micro Code Revision 8.60
All 10 drives show RDY
vgscan -p -v
vgscan: Warning: couldn't query physical volume "/dev/dsk/c1t3d0":
The specified path does not correspond to physical volume attached to
this volume group
vgscan: Warning: couldn't query all of the physical volumes.
vgscan: The physical volume "/dev/dsk/c0t0d0" is already recorded in the "/etc/l
vmtab" file.
vgscan: The physical volume "/dev/dsk/c0t1d0" is already recorded in the "/etc/l
vmtab" file.
vgscan: The physical volume "/dev/dsk/c1t3d0" is already recorded in the "/etc/l
vmtab" file.
vgscan: The physical volume "/dev/dsk/c1t4d0" is already recorded in the "/etc/l
vmtab" file.
vgscan: The physical volume "/dev/dsk/c1t6d0" is already recorded in the "/etc/l
vmtab" file.
Current path "/dev/dsk/c0t1d0" is an alternate link, skip.
reading LVMREC, please wait....
Couldn't stat physical volume "/dev/dsk/c1t2d0":
Invalid argument
/dev/vg02
/dev/dsk/c0t0d0
/dev/dsk/c0t1d0
reading VGDA, please wait....
reading VGDA, please wait....
filling VGDA, please wait....
Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c0t0d1
/dev/dsk/c0t1d1
Following Physical Volumes belong to one Volume Group.
Unable to match these Physical Volumes to a Volume Group.
Use the vgimport command to complete the process.
/dev/dsk/c1t3d0
/dev/vg00
/dev/dsk/c1t4d0
/dev/dsk/c1t6d0
Gridmgr shows:
SP A:
Prom Revision 1.73
Micro Code Revision 8.60
All 10 drives show ENA
SP B:
Prom Revision 1.73
Micro Code Revision 8.60
All 10 drives show RDY
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