vgchange -a y vgdb7 --> Cross-device link -> Quorum not present

[Nikee Reddy]

Hello,

When I tried to activate the following VG the system is generating the following error message:
----------------------------------------------
vgchange -a y vgdb7
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c15t1d2":
Cross-device link
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c16t1d3":
Cross-device link
vgchange: Warning: couldn't query physical volume "/dev/dsk/c15t1d2":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c16t1d3":
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 "vgdb7":
Quorum not present, or some physical volume(s) are missing.
-----------------------------------------------
Under this VG, we have only 2 CX-600 disks.
1>/dev/dsk/c15t1d2
2>/dev/dsk/c16t1d3

When I ran the ioscan -fnC disk, I see both the disks.

Also I did ran the diskinfo:
----------------------------------------------
DISK 1:
-------
diskinfo /dev/rdsk/c15t1d2
SCSI describe of /dev/rdsk/c15t1d2:
vendor: DGC
product id: CX600WDR10
type: direct access
size: 100663296 Kbytes
bytes per sector: 512

Disk 2:
-------
diskinfo /dev/rdsk/c16t1d3
SCSI describe of /dev/rdsk/c16t1d3:
vendor: DGC
product id: CX600WDR10
type: direct access
size: 100663296 Kbytes
bytes per sector: 512
----------------------------------------------
Which means, both the disks are present and I do not see any logs other than the following under /var/adm/syslog/syslog.log

"vmunix: LVM: VG 64 0x0a0000: Unable to initialize the latest status information."
----------------------------------------------
root@titan:/etc/lvmconf# strings /etc/lvmtab
/dev/vg00
/dev/dsk/c2t0d0
/dev/dsk/c1t2d0
/dev/dsk/c2t2d0
/dev/dsk/c1t0d0
/dev/vgdb1
/dev/dsk/c16t0d3
/dev/vgdb2
/dev/dsk/c15t0d0
/dev/vgdb3
/dev/dsk/c15t0d4
/dev/vgdb4
/dev/dsk/c16t0d1
/dev/vgdb5
/dev/dsk/c16t0d5
/dev/vgdb6
/dev/dsk/c15t0d2
/dev/vgnfs
/dev/dsk/c16t1d1
/dev/vgcomm
/dev/dsk/c15t1d0
/dev/vgdb
/dev/dsk/c15t0d6
/dev/dsk/c16t0d7
/dev/vgdb7
/dev/dsk/c15t1d2
/dev/dsk/c16t1d3
----------------------------------------------
vgcfgrestore information:
-------------------------
root@titan:/etc/lvmconf# vgcfgrestore -l -f vgdb7.conf.old
Volume Group Configuration information in "vgdb7.conf.old"
VG Name /dev/vgdb7
---- Physical volumes : 2 ----
/dev/rdsk/c15t1d2 (Non-bootable)
/dev/rdsk/c16t1d3 (Non-bootable)

root@titan:/etc/lvmconf# vgcfgrestore -l -f vgdb7.conf
Volume Group Configuration information in "vgdb7.conf"
VG Name /dev/vgdb7
---- Physical volumes : 2 ----
/dev/rdsk/c15t1d2 (Non-bootable)
/dev/rdsk/c16t1d3 (Non-bootable)
----------------------------------------------
When I tried to export the colume group vgdb7, it did identified the correct disks;
root@titan:/root# vgexport -v -p -s -m vgdb7.map vgdb7
Beginning the export process on Volume Group "vgdb7".
/dev/dsk/c15t1d2
/dev/dsk/c16t1d3

Based on the above information, looks like we have corrupted the LVM headers by use of pvcreate on the failover node.

FYI - vgdb7 is a brand new volume group and no data in it.

Please let me know how to resolve this issue.

Thank you,
Nikee

[Mridul Shrivastava · Accepted solution]

Based on the inputs.. no data and its a new VG..
I would go for vgexport and recreate the vg from scratch..

After recreating remember not to do vgcreate on other nodes only vgexport in preview mode then vgimport is required.

[Robert-Jan Goossens]

Hi Nikee,

---
FYI - vgdb7 is a brand new volume group and no data in it.
---

If there is no data inside vg start over again.

# ll /dev/vgdb7/group
note the minor number
# vgexport vgdb7
# mkdir /dev/vgdb7
# mknod /dev/vg01/group c 64 0xyy0000
# vgcreate /dev/vgdb7 /dev/dsk/c15t1d2
# vgextend /dev/vgdb7 /dev/dsk/c16t1d3

Robert-Jan

[Nikee Reddy]

Hello All,

I have found the other way and was able to resolve it.

This is what I have done:
vgcfgrestore -n /dev/vgdb7 /dev/rdsk/c15t1d2
vgcfgrestore -n /dev/vgdb7 /dev/rdsk/c16t1d3

Then I was able to activate the vgdb7 volume group.

Thank you for all you help and response.

Thank you,
Nikee