Operating System - HP-UX
1834935 Members
2221 Online
110071 Solutions
New Discussion

SAM reporting error message on vg00

 
Yogeeraj_1
Honored Contributor

SAM reporting error message on vg00

Dear experts,

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
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
5 REPLIES 5
Fred Ruffet
Honored Contributor

Re: SAM reporting error message on vg00

seems like your 4 drives have those devices :
/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.)
Yogeeraj_1
Honored Contributor

Re: SAM reporting error message on vg00

thanks fred for your reply!

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
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
Fred Ruffet
Honored Contributor

Re: SAM reporting error message on vg00

This may be residual effect from new year's celebration :)

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.)
T G Manikandan
Honored Contributor

Re: SAM reporting error message on vg00

The /etc/lvmtab file would not have the modified changes.



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..
Yogeeraj_1
Honored Contributor

Re: SAM reporting error message on vg00

Points noted and assigned ;) thanks
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)