- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: physical volume not attached
Operating System - HP-UX
1753469
Members
5320
Online
108794
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
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
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
09-10-2003 01:48 PM
09-10-2003 01:48 PM
Re: physical volume not attached
That disk always has belonged to that volume group.
No, I haven't changed anything lately, I guess the disks are SCSI2... how can I know that?
If the i/o cables had moved, I guess all the disk that belong the array would be as NO_HW...
Could be a possibility the disk's path is confused to the OS?
I mean It's been moved. Could I set it online (the disks are hot pluggable)?
Before I didn't have any problem like this.
What are EMC disks?
No I don't have the inq utility, what does the inq utility do?
No, I haven't changed anything lately, I guess the disks are SCSI2... how can I know that?
If the i/o cables had moved, I guess all the disk that belong the array would be as NO_HW...
Could be a possibility the disk's path is confused to the OS?
I mean It's been moved. Could I set it online (the disks are hot pluggable)?
Before I didn't have any problem like this.
What are EMC disks?
No I don't have the inq utility, what does the inq utility do?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2003 03:52 PM
09-10-2003 03:52 PM
Re: physical volume not attached
Hi Hunan,
Do a
vgdisplay -v > /tmp/vg.out 2>&1
vi /tmp/vg.out
This should list the disk that the system is complaining about. If you search with that disk device name in the same file, you will find the corresponding volume group.
This message tells that the VG headers on that disk do not match with VG that it belongs to. Either someone did a "pvcreate -f" on it by mistake or you lost that disk.
Try running ioscan,diskinfo,lssf etc., commands to make sure the disk is physically there. If you confirm that it is there and it is in fact the same disk, then do a vgcfgrestore on it to put back the VG headers.
vgcfgrestore -n vgname /dev/rdsk/cxtydz
vgchange -a y vgname
This should fix your issue if the data on that disk is not already overwritten.
-Sri
Do a
vgdisplay -v > /tmp/vg.out 2>&1
vi /tmp/vg.out
This should list the disk that the system is complaining about. If you search with that disk device name in the same file, you will find the corresponding volume group.
This message tells that the VG headers on that disk do not match with VG that it belongs to. Either someone did a "pvcreate -f" on it by mistake or you lost that disk.
Try running ioscan,diskinfo,lssf etc., commands to make sure the disk is physically there. If you confirm that it is there and it is in fact the same disk, then do a vgcfgrestore on it to put back the VG headers.
vgcfgrestore -n vgname /dev/rdsk/cxtydz
vgchange -a y vgname
This should fix your issue if the data on that disk is not already overwritten.
-Sri
You may be disappointed if you fail, but you are doomed if you don't try
- « Previous
-
- 1
- 2
- Next »
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