vgchange returns errors

[Victor_101]

# vgchange -a y /dev/vg01
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk
/c4t0d0":
Cross-device link
vgchange: Warning: couldn't query physical volume "/dev/dsk/c4t0d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "/dev/vg01":
Quorum not present, or some physical volume(s) are missing.


i cannot contact the disk array.. its showing in the ioscan.. i went to IRM initially theyy were sayin failed state.. then i forced the online state.. still same respond to vgchange ..help plss

[Bharat Katkar]

Hi Victor,
try doing this and see the status of c4t0d0:

# pvdisplay -v /dev/dsk/c4t0d0

Look like some problem with this PV.

# ioscan -fnC disk
See if the device /dev/dsk/c4t0d0 is listed.

Regards,

[Sanjay Kumar Suri]

can you check with following command:

diskinfo /dev/dsk/c4t0d0

sks

[Victor_101]

# pvdisplay -v /dev/dsk/c4t0d0
pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c4t0d0":
The specified path does not correspond to physical volume attached to
this volume group
pvdisplay: Warning: couldn't query all of the physical volumes.
pvdisplay: Couldn't retrieve the names of the physical volumes
belonging to volume group "/dev/vg01".
pvdisplay: Cannot display physical volume "/dev/dsk/c4t0d0".



# diskinfo /dev/rdsk/c4t0d0
SCSI describe of /dev/rdsk/c4t0d0:
vendor: I2O
product id: RAID5
type: direct access
size: 215058432 Kbytes
bytes per sector: 512



and finally what caught my eye....

# diskinfo /dev/dsk/c4t0d0
diskinfo: Character device required

pls advise.. will assing points when we sort it out




# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
disk 2 0/0/1/0.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c0t2d0 /dev/rdsk/c0t2d0
disk 0 0/0/1/1.15.0 sdisk CLAIMED DEVICE HP 36.4GMAS3367NC
/dev/dsk/c1t15d0 /dev/rdsk/c1t15d0
disk 1 0/0/2/1.15.0 sdisk CLAIMED DEVICE HP 36.4GMAS3367NC
/dev/dsk/c3t15d0 /dev/rdsk/c3t15d0
disk 3 0/4/0/1.0.0.0 sdisk CLAIMED DEVICE I2O RAID5
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
#

[Dietmar Konermann]

The "Cross-device link" error means that the device is available and readable... but the Volume Group ID (VGID) found on the device does not match the VGID listed in /etc/lvmtab.

Please check the VGID with:

echo "0d8208?UY" | adb /dev/dsk/xxxxx

It should return the date when the VG has been created... 1970 would mean that the VGID is 0. Either because the device has been wiped our because it is not part of any VG. Restoring the LVM structures using vgcfgrestore could be a possible next step then.

Best regards...
Dietmar.

[Bharat Katkar]

Hi,
I think you have lost /dev/dsk/c4t0d0.
# cd /dev/dsk
# ls -la c4t0d0

Now hopefully you need to do pvcreate. LVM info on the disk seems to be lost.

Regards,

[Bharat Katkar · Accepted solution]

Hi,
Don't do pvcreate direclty as it may wipe of the data on that disk. Instead try doing vgcfgrestore as suggested earlier by dietmar.

Regards,

[Victor_101]

briliant u guys...


just one prob still.. chck this


# vgcfgrestore -n /dev/vg01 /dev/rdsk/c4t0d0
Volume Group configuration has been restored to /dev/rdsk/c4t0d0
# vgchange -a y /dev/vg01
Activated volume group
Volume group "/dev/vg01" has been successfully changed.
# mountall
mountall: /dev/vg01/vol1 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: not a valid vxfs file system
mountall: cannot fsck /dev/vg01/vol1
mountall: diagnostics from fsck
invalid super-block
file system check failure, aborting ...
itialize aggregate
mountall: /dev/vg01/vol1 failed in fsck
mountall: /dev/vg01/vol1 cannot be mounted



were almost there.. its ok if i have to lose that volume.. its still empty.. test servers.. want to know though how do i get rid of that volume ?? through sam ?? will be better yet if i can restore..

that was quick guys.. all 3

[Naveej.K.A]

hi,

remove the volume?
lvremove /dev/vg01/lvol1

regds
Naveej

[Victor_101]

hi ther..

Dietmarr.. im sorry i mistakely assigned u only 6 points. should have mde it 10.. maybe next time.. unless u can show me how to change that.. will be glad to...






deleted and created the new volumee. all fine

thanx a million guys

[Victor_101]

one last thing guys.. why did this thing happen... how do i avoid in the future.. meanin what do i take care not to repeat again ?

[Bharat Katkar]

Hi victor,
Some precautions that i take care are:

1. create map files of all VG's and keep them safe. # vgexport -p ...
2. Remember group file major/minor no. of all VG's

As far as problem with VG's are concerned.

vgcfgbackup/vgcfgrestore is also a good thing to do.

Regards,

[Fabio Ettore]

Hi Victor,

it can happen for more reasons:

- substituted disk and configured it in a not good LVM configuration for example with different device files than before;
- suddenly any physical volume (disks) fail.

Do you work on any disks of VG01 recently?

Best regards,
Ettore

[Naveej.K.A]

hi,

a power outage??
a failing disk??

could be some of the reasons!!!

regds
Naveej