After upgrading to SF 5.1SP1RP2 two disks of aix disk format changed to error state

book

Article ID: 100026180

calendar_today

Updated On:

Description

Error Message

02/03 01:14:32:  VxVM vxconfigd DEBUG  V-5-1-17951 vold_disk_check_udid_mismatch: Device hdisk882 not initialized, can't set attribute                                  >>>>>>>>>>
02/03 01:14:32:  VxVM vxconfigd DEBUG  V-5-1-5422 Did not find a disk in ddi_disk_list with either the same device number or same tag. tag = hdisk882          >>>>>>>>>>
02/03 01:14:49:  VxVM vxconfigd DEBUG  V-5-1-5346 devintf_add_autoconfig: RECORD: name : hdisk882, DEVNO: 0x1b0075
02/03 01:14:49:  VxVM vxconfigd DEBUG  V-5-1-18518 vold_get_udid_type: Found LIBNAME libvxemc.so for disk hdisk882 hdisk882
02/03 01:14:50:  VxVM vxconfigd DEBUG  V-5-1-17951 vold_disk_check_udid_mismatch: Device hdisk882 not initialized, can't set attribute                                   >>>>>>>>>>
02/03 01:15:01:  VxVM vxconfigd DEBUG  V-5-1-681 IOCTL NEW_DISK da=hdisk882 rid=1024.141 dm= dmrid=0.0 new_dmrid=0.0 dgiid=0.0 pub_dev=65535/65535 priv_dev=65535/65535 pub_len=9223372036854775807 priv_len=9223372036854775807 kflag=0x10 vflag=0x3000060: return 0(0x0)
02/03 01:15:50:  VxVM vxconfigd DEBUG  V-5-1-6059 thread 8822: running
02/03 01:15:51:  VxVM vxconfigd DEBUG  V-5-1-19859 Temporary registration may be needed if Sanvm on hdisk882
02/03 01:15:52:  VxVM vxconfigd DEBUG  V-5-1-24562 auto_info_get: vol_media_fmt failed with res=1, wp=/dev/vx/rdmp/hdisk882, vcds_dev=1769589
02/03 01:15:52:  VxVM vxconfigd DEBUG  V-5-1-5313 da_online failed, thread 8822: There is a request to a device or address that does not exist.                     >>>>>>>>>>


Thu Feb  2 07:26:34.924: SCSI error occured on Path hdisk882: opcode=0x28 reported illegal request (status=0x2, key=0x5, asc=0x21, ascq=0x0)
Thu Feb  2 07:26:34.924: I/O analysis done as DMP_PATH_FAILURE on Path hdisk882 belonging to Dmpnode hdisk882
Thu Feb  2 07:26:34.927: Disabled Path hdisk882 belonging to Dmpnode hdisk882 due to path failure
Thu Feb  2 07:26:34.928: Disabled Dmpnode hdisk882
Thu Feb  2 07:26:34.929: I/O error occured (errno=0x6) on Dmpnode hdisk882

However, we can read/write to the /dev/rhdisk882 and /dev/rhdisk873.

Cause

# /etc/vx/diag.d/vxmediadisc -p /dev/rhdisk882
vxmediadisc: Disk /dev/rhdisk882 is partitioned.
Partition Table Contents
Revision:                      1
Partition Table Type:          MBR         <<<<<=== VxVM recognizes this disk as MBR disk
Partition Table OStype:        Linux
Number of partitions:          4               <<<<<=== 4 partitions
Number of used partitions:     3
Partition Number 0:
     Partition Entry Type:          Linux
     Partition Entry Tag:           0x07 (Var)
     Partition Entry Start:         0x0000000000000040 (64)             <<<<<====
     Partition Entry Size:          0x0000000006525800 (106059776)
<>

VxVM (5.1SP1RP2) will traverse the 4 partitions to determine their format. However, there are only 3 available partitions in use and this is where the code fails.

Resolution

Workaround is to zero out the first sector (first 64 bytes is enough in this case) of the disks which contain the MBR (Master Boot Record)  partition. This will wipe out the MBR partition information.                                                                                                                                                                                                                  Disk will automatically come online with "auto:aixdisk" format and re-attach to the disk group after running "vxdctl enable". VxVM private region information will still be intact.

#dd if=/dev/zero of=/dev/rhdisk882 count=1 bs=512

#vxdctl enable

Code change is added to validate MBR partition. A valid MBR partition must start with 0x80 (active partition) or 0x00 (non-active). Contact Veritas technical support if additional details are needed.

 

Applies To

VRTSvxvm 5.1.112.0 5.1SP1RP2 for AIX  6.1

Issue/Introduction

After upgrading to SF (Storage Foundation) 5.1SP1RP2 from 5.0MP1RP3 a disk group could not be imported because its 2 devices were in error state.
These disks had data and we were un-able to reset the private region. - - ora20-84g DG1_ghrdev-ds1-d failed was:hdisk882
- - backups-59g DG1_ghrfpkd2-ds1-d failed was:hdisk873 #vxdisk -f init hdisk873
VxVM vxdisk ERROR V-5-1-2604 cannot open /dev/vx/rdmp/hdisk873
VxVM vxdisk ERROR V-5-1-5433 Device hdisk873: init failed:
Configuration daemon error 6