- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SAM reporting error message on vg00
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
Forums
Discussions
Discussions
Discussions
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
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
01-03-2005 07:43 PM
01-03-2005 07:43 PM
SAM reporting error message on vg00
My RP5400 has 4 internal disks. The OS has been installed on /dev/dsk/c2t2d0 with hardware path 0/0/2/0.2.0.
Two other disks have been striped into VG01.
0/0/1/1.0.0 and 0/0/2/0.0.0.
Now, i am trying to use the last disk (0/0/1/1.2.0) to create a new volume group VG02.
SAM is reporting the fllowing errors:
The Logical Volume Manager shows this device file, /dev/dsk/c2t2d0, with hardware path, 0/0/2/0.2.0, as belonging to Volume Group, vg00. SAM has determined that this hardware path is not currently active because either the device is disconnected, or this is not the primary path to a multiple path physical volume. This results in incorrect disk utilization information in the Disk Devices and Volume Group lists.
and then:
SAM could not retrieve any information about the disk whose device file is /dev/dsk/c2t2d0". Check to make sure the disk is properly attached to the system.
The disks are all properly attached!!
Below the output of my ioscan:
# ioscan -FknC disk
scsi:wsio:T:T:F:31:188:65536:disk:sdisk:0/0/1/1.0.0:0 0 3 18 0 0 0 0 178 134 208
172 170 203 248 70 :2:root.sba.lba.c720.tgt.sdisk:sdisk:CLAIMED:DEVICE:SEAGATE
ST318404LC:1
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
scsi:wsio:T:T:F:31:188:73728:disk:sdisk:0/0/1/1.2.0:0 0 3 18 0 0 0 0 178 134 208
172 159 42 72 227 :3:root.sba.lba.c720.tgt.sdisk:sdisk:CLAIMED:DEVICE:SEAGATE ST318404LC:1
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
scsi:wsio:T:T:F:31:188:131072:disk:sdisk:0/0/2/0.0.0:0 0 3 18 0 0 0 0 194 236 36
35 28 130 248 206 :4:root.sba.lba.c720.tgt.sdisk:sdisk:CLAIMED:DEVICE:SEAGATE ST318404LC:2
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
scsi:wsio:T:T:F:31:188:139264:disk:sdisk:0/0/2/0.2.0:0 0 3 18 0 0 0 0 194 236 36
35 181 98 211 190 :0:root.sba.lba.c720.tgt.sdisk:sdisk:CLAIMED:DEVICE:SEAGATE ST318404LC:2
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
scsi:wsio:T:T:F:31:188:204800:disk:sdisk:0/0/2/1.2.0:5 128 2 66 0 0 0 0 204 34 1
87 47 0 0 0 0 :1:root.sba.lba.c720.tgt.sdisk:sdisk:CLAIMED:DEVICE:HP DVD-ROM 304:3
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
#
how do i proceed?
thank you in advance for your replies!
best regards
Yogeeraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2005 07:53 PM
01-03-2005 07:53 PM
Re: SAM reporting error message on vg00
/dev/dsk/c1t0d0
/dev/dsk/c1t2d0
/dev/dsk/c2t0d0
/dev/dsk/c2t2d0
your say your vg00 is configured on c2t2d0. Error messages you post shows errors on c2t2d0. Seems like you *really* want to reuse vg00 disk. use
vgdisplay -v | grep "PV Name"
to know what disks are already in use, then use the fourth disk to create new vg.
Regards,
Fred
"Reality is just a point of view." (P. K. D.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2005 08:32 PM
01-03-2005 08:32 PM
Re: SAM reporting error message on vg00
below the output of the vgdisplay command:
# vgdisplay -v | grep "PV Name"
PV Name /dev/dsk/c2t2d0
PV Name /dev/dsk/c1t0d0
PV Name /dev/dsk/c2t0d0
hence, /dev/dsk/c1t2d0 is free for utilization.
what was worrying me was that error message. When i ran SAM again, i didn't get the same error mesages, except when creating the new vg:
Although the disk(s) you have chosen are not currently part of any active volume group, at least one of these disks contains old LVM data structures. If the disks are added, the old LVM structures will be overwritten and it will not be possible to recover the data currently on them.
This is probably because the disk contained some old data.
I have been able to create the VG successfully now. This has been a short moment of panic ;)
thanks again
regards
Yogeeraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2005 10:00 PM
01-03-2005 10:00 PM
Re: SAM reporting error message on vg00
This message appear when you try to pvcreate on a disk and an old LVM structure exists on it.
Regards,
Fred
"Reality is just a point of view." (P. K. D.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2005 10:05 PM
01-03-2005 10:05 PM
Re: SAM reporting error message on vg00
A vgscan would have refreshed the file for /etc/lvmtab.
You should have done a scan again from the SAM which would have refreshed the /etc/lvmtab file and now it is giving you the right information.
Thanks..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2005 11:18 PM
01-03-2005 11:18 PM