Issue :
After system reboot vg failed to activate , manual activation show system is failed to query the disk. ioscan show the disk status are claimed and available on the system.
Error :
mountall: cannot mount /dev/vg_edwpsw/orasw01_11g
mountall: diagnostics from mount
UX:vxfs mount: ERROR: V-3-20003: Cannot open /dev/vg_edwpsw/orasw01_11g: No such device or address
UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version
mountall: cannot mount /dev/vg_edwpsw/orasw01
mountall: diagnostics from mount
UX:vxfs mount: ERROR: V-3-20003: Cannot open /dev/vg_edwpsw/orasw01: No such device or address
UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version
mountall: cannot mount /dev/vg_edwpsw/lv_apps
mountall: diagnostics from mount
UX:vxfs mount: ERROR: V-3-20003: Cannot open /dev/vg_edwpsw/lv_apps: No such device or address
UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version
[root@jupiterA:/etc/lvmconf]#
#-> grep -i "Wrong disk" /var/adm/syslog/syslog.log
Sep 1 16:42:42 jupiterA vmunix: LVM: VG 64 0x080000: PVLink 1 0x00009f Attach failed. Wrong disk!
Sep 1 17:14:45 jupiterA vmunix: LVM: VG 64 0x080000: PVLink 1 0x00009f Attach failed. Wrong disk!
Sep 1 17:14:45 jupiterA vmunix: LVM: VG 64 0x080000: PVLink 1 0x0000a6 Attach failed. Wrong disk!
Sep 1 17:14:45 jupiterA vmunix: LVM: VG 64 0x080000: PVLink 1 0x00011e Attach failed. Wrong disk!
Sep 1 17:14:45 jupiterA vmunix: LVM: VG 64 0x080000: PVLink 1 0x00011f Attach failed. Wrong disk!
Sep 1 17:15:13 jupiterA vmunix: LVM: VG 64 0x080000: PVLink 1 0x0000a6 Attach failed. Wrong disk!
[root@jupiterA:/etc/lvmconf]#
Recommendation Action :
Restore the vg cofinguration on the Disk , after verifying the disk and VG association.
#-> vgcfgrestore -f vg_edwpsw.conf.old -l
Volume Group Configuration information in "vg_edwpsw.conf.old"
VG Name /dev/vg_edwpsw
---- Physical volumes : 4 ----
/dev/rdisk/disk149 (Non-bootable)
/dev/rdisk/disk156 (Non-bootable)
/dev/rdisk/disk276 (Non-bootable)
/dev/rdisk/disk277 (Non-bootable)
vgcfgrestore -f /etc/lvmconf/vg_edwpsw.conf.old /dev/rdisk/disk149
vgcfgrestore -f /etc/lvmconf/vg_edwpsw.conf.old /dev/rdisk/disk156
vgcfgrestore -f /etc/lvmconf/vg_edwpsw.conf.old /dev/rdisk/disk276
vgcfgrestore -f /etc/lvmconf/vg_edwpsw.conf.old /dev/rdisk/disk277
[root@jupiterA:/home/ssingh45]#
#-> vgimport -sN -m vg_edwpsw.mapfile.ssingh45 vg_edwpsw
vgimport: Quorum not present, or some physical volume(s) are missing.
vgimport: Volume group "/dev/vg_edwpsw" has been successfully created.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating the volume group.
After system reboot vg failed to activate , manual activation show system is failed to query the disk. ioscan show the disk status are claimed and available on the system.
Error :
mountall: cannot mount /dev/vg_edwpsw/orasw01_11g
mountall: diagnostics from mount
UX:vxfs mount: ERROR: V-3-20003: Cannot open /dev/vg_edwpsw/orasw01_11g: No such device or address
UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version
mountall: cannot mount /dev/vg_edwpsw/orasw01
mountall: diagnostics from mount
UX:vxfs mount: ERROR: V-3-20003: Cannot open /dev/vg_edwpsw/orasw01: No such device or address
UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version
mountall: cannot mount /dev/vg_edwpsw/lv_apps
mountall: diagnostics from mount
UX:vxfs mount: ERROR: V-3-20003: Cannot open /dev/vg_edwpsw/lv_apps: No such device or address
UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version
[root@jupiterA:/etc/lvmconf]#
#-> grep -i "Wrong disk" /var/adm/syslog/syslog.log
Sep 1 16:42:42 jupiterA vmunix: LVM: VG 64 0x080000: PVLink 1 0x00009f Attach failed. Wrong disk!
Sep 1 17:14:45 jupiterA vmunix: LVM: VG 64 0x080000: PVLink 1 0x00009f Attach failed. Wrong disk!
Sep 1 17:14:45 jupiterA vmunix: LVM: VG 64 0x080000: PVLink 1 0x0000a6 Attach failed. Wrong disk!
Sep 1 17:14:45 jupiterA vmunix: LVM: VG 64 0x080000: PVLink 1 0x00011e Attach failed. Wrong disk!
Sep 1 17:14:45 jupiterA vmunix: LVM: VG 64 0x080000: PVLink 1 0x00011f Attach failed. Wrong disk!
Sep 1 17:15:13 jupiterA vmunix: LVM: VG 64 0x080000: PVLink 1 0x0000a6 Attach failed. Wrong disk!
[root@jupiterA:/etc/lvmconf]#
Recommendation Action :
Restore the vg cofinguration on the Disk , after verifying the disk and VG association.
#-> vgcfgrestore -f vg_edwpsw.conf.old -l
Volume Group Configuration information in "vg_edwpsw.conf.old"
VG Name /dev/vg_edwpsw
---- Physical volumes : 4 ----
/dev/rdisk/disk149 (Non-bootable)
/dev/rdisk/disk156 (Non-bootable)
/dev/rdisk/disk276 (Non-bootable)
/dev/rdisk/disk277 (Non-bootable)
vgcfgrestore -f /etc/lvmconf/vg_edwpsw.conf.old /dev/rdisk/disk149
vgcfgrestore -f /etc/lvmconf/vg_edwpsw.conf.old /dev/rdisk/disk156
vgcfgrestore -f /etc/lvmconf/vg_edwpsw.conf.old /dev/rdisk/disk276
vgcfgrestore -f /etc/lvmconf/vg_edwpsw.conf.old /dev/rdisk/disk277
[root@jupiterA:/home/ssingh45]#
#-> vgimport -sN -m vg_edwpsw.mapfile.ssingh45 vg_edwpsw
vgimport: Quorum not present, or some physical volume(s) are missing.
vgimport: Volume group "/dev/vg_edwpsw" has been successfully created.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating the volume group.
vgcfgrestore command not able to resolve the issue, finally it was decided to re-create the VG with new set of Disk as , old set of disk are always are problematic , after reboot and maintenance.
Size of disk in conf and in diskscan are different which causing the conflict. it seems something messy how it was happen. no clue , might someone imported with wrong mapfile.
#-> vgcfgrestore -vl -n vg_edwpsw
Volume Group Configuration information in "/etc/lvmconf/vg_edwpsw.conf"
VG Name /dev/vg_edwpsw
---- Physical volumes : 4 ----
PV Type Size (kb) Start (kb) PVkey
disk149 Non-Boot 104857920 21184 2
disk156 Non-Boot 104857920 21184 3
disk276 Non-Boot 39846720 21184 4
disk277 Non-Boot 39846720 21184 5
max_pv 255 max_pe 10000 max_lv 255 vg_version 1.0
SCSI describe of /dev/rdisk/disk149:
vendor: HP
product id: OPEN-V
type: direct access
size: 39846720 Kbytes
bytes per sector: 512
SCSI describe of /dev/rdisk/disk156:
vendor: HP
product id: OPEN-V
type: direct access
size: 39846720 Kbytes
bytes per sector: 512
SCSI describe of /dev/rdisk/disk276:
vendor: HP
product id: OPEN-V
type: direct access
size: 104857920 Kbytes
bytes per sector: 512
SCSI describe of /dev/rdisk/disk277:
vendor: HP
product id: OPEN-V
type: direct access
size: 104857920 Kbytes
bytes per sector: 512
Size of disk in conf and in diskscan are different which causing the conflict. it seems something messy how it was happen. no clue , might someone imported with wrong mapfile.
#-> vgcfgrestore -vl -n vg_edwpsw
Volume Group Configuration information in "/etc/lvmconf/vg_edwpsw.conf"
VG Name /dev/vg_edwpsw
---- Physical volumes : 4 ----
PV Type Size (kb) Start (kb) PVkey
disk149 Non-Boot 104857920 21184 2
disk156 Non-Boot 104857920 21184 3
disk276 Non-Boot 39846720 21184 4
disk277 Non-Boot 39846720 21184 5
max_pv 255 max_pe 10000 max_lv 255 vg_version 1.0
SCSI describe of /dev/rdisk/disk149:
vendor: HP
product id: OPEN-V
type: direct access
size: 39846720 Kbytes
bytes per sector: 512
SCSI describe of /dev/rdisk/disk156:
vendor: HP
product id: OPEN-V
type: direct access
size: 39846720 Kbytes
bytes per sector: 512
SCSI describe of /dev/rdisk/disk276:
vendor: HP
product id: OPEN-V
type: direct access
size: 104857920 Kbytes
bytes per sector: 512
SCSI describe of /dev/rdisk/disk277:
vendor: HP
product id: OPEN-V
type: direct access
size: 104857920 Kbytes
bytes per sector: 512
No comments:
Post a Comment