The best practice to fix the problem with "VxVM vxconfigd NOTICE V-5-1-13788 Data Corruption Protection Activated

Description

Error Message

[ ERROR MESSAGES ]

# vxdisk scandisks

VxVM vxconfigd NOTICE V-5-1-0 LUN serial number of the OS device path with device number 118/41640 has changed from 60000970000592600022533031463645 (c40t5000097A08005920d103) to 60000970000592600022533032313134 (c40t5000097A08005920d103)

VxVM vxconfigd NOTICE V-5-1-0 LUN serial number of the OS device path with device number 118/41712 has changed from 60000970000592600022533031463645 (c39t5000097A0800591Cd103) to 60000970000592600022533032313134 (c39t5000097A0800591Cd103)

VxVM vxconfigd NOTICE V-5-1-0 LUN serial number of the OS device path with device number 118/41648 has changed from 60000970000592600022533031463645 (c46t5000097A08005928d103) to 60000970000592600022533032313134 (c46t5000097A08005928d103)

VxVM vxconfigd NOTICE V-5-1-0 LUN serial number of the OS device path with device number 118/41656 has changed from 60000970000592600022533031463645 (c45t5000097A08005914d103) to 60000970000592600022533032313134 (c45t5000097A08005914d103)

VxVM vxconfigd NOTICE V-5-1-13788 Data Corruption Protection Activated - User Corrective Action Needed:

VxVM vxconfigd NOTICE V-5-1-0 To recover, first ensure that the OS device tree is up to date (requires OS specific commands). Then, execute 'vxdisk rm' on the following devices before reinitiating device discovery using 'vxdisk scandisks'

VxVM vxconfigd NOTICE V-5-1-0 emc0_2114, emc0_2114, emc0_2114, emc0_2114

VxVM vxconfigd ERROR V-5-1-13790 No device configuration changes have been applied to DMP kernel database.

VxVM vxconfigd ERROR V-5-1-13791 Please consult the documentation for correct procedure to replace disk/path.

VxVM vxconfigd ERROR V-5-1-13992 open failed on path: /dev/vx/rdmp/emc0_2114

VxVM vxdisk ERROR V-5-1-0 Data Corruption Protection Activated - User Corrective Action Needed

VxVM vxdisk INFO V-5-1-0 To recover, first ensure that the OS device tree is up to date (requires OS specific commands).

VxVM vxdisk INFO V-5-1-0 Then, execute 'vxdisk rm' on the following devices before reinitiating device discovery:

emc0_2114, emc0_2114, emc0_2114, emc0_2114

Cause

[ CAUSE ]

1. In general, when there are problem with discrepancy showing up disk devices between OS and DMP level,

2. Rebuilding disk devices tree at OS and DMP level helps solve the problem.

3. However, in some cases this does not fix the problem through the way above, thereby requiring to bring System Vendors an attention on this matter.

---------------------------------------------------------------------------------

# devfsadm -Cv

=

# hasys -freeze

# cd /dev/vx/dmp

# rm -rf *

# cd /dev/vx/rdmp

# rm -rf *

# cd /etc/vx

# rm -rf *.info

# vxconfigd -k

---------------------------------------------------------------------------------

4. To fix the problem on the spot, the advanced way followed is probably helpful when the similar issue may incur.

Resolution

[ FINDINGS AND SUGGESTION ]

1. Check to see if there are any disk devices "unusable" at OS level.

---------------------------------------------------------------------------------

# cfgadm -al -o show_SCSI_LUN | grep -i unusable

c39::5000097a0800591c ,103 disk connected configured unusable

c40::5000097a08005920 ,103 disk connected configured unusable

c45::5000097a08005914 ,103 disk connected configured unusable

c46::5000097a08005928 ,103 disk connected configured unusable

2. Remove the disk devices above.

---------------------------------------------------------------------------------

#cfgadm -c unconfigure -o unusable_SCSI_LUN c39::5000097a0800591c

#cfgadm -c unconfigure -o unusable_SCSI_LUN c40::5000097a08005920

#cfgadm -c unconfigure -o unusable_SCSI_LUN c45::5000097a08005914

#cfgadm -c unconfigure -o unusable_SCSI_LUN c46::5000097a08005928

3. Recheck the disk devices "unusable"

---------------------------------------------------------------------------------

#cfgadm -al -o show_SCSI_LUN | grep -i unusable

~ Nothing returned.

4. Rescan and rebuild the disk devices at OS level.

---------------------------------------------------------------------------------

#devfsadm -Cv

5. Recan and rebuild the disk devices at DMP level.

---------------------------------------------------------------------------------

#vxdisk scandisks

--> If this fixes the problem, not required to do the next steps.

--> If not, there are further steps to go further as follows.

6. As one of two disk devices is still not visible at OS level.

---------------------------------------------------------------------------------

#devfsadm -Cv

#format

--> It will be turned out that executing the command line “devfsadm” ended up with failing to discover the one disk at OS level.

So therefore, here is the last attempt to rescan disk devices at OS level by forcing to update disk devices on controller c39, c40, c45 and c46 where the issued disk devices are aligned.

#cfgadm -o force_update -c configure c39

#cfgadm -o force_update -c configure c40

#cfgadm -o force_update -c configure c45

#cfgadm -o force_update -c configure c46

Then try to re-scan disk devices at OS level.

#devfsadm -Cv

#format

--> Now, the missing disk device at OS level is probably visible.

#vxdisk scandisks

--> And the command line above will help vxconfigd detect that disk device at DMP level.

After this, it ended up with solving the problem.

Applies To

[ VERSION OF OS/PACKAGE ]

SunOS Symc-Sun 5.10 Generic_144488-04 sun4u sparc SUNW,SPARC-Enterprise'

SF5.0MP1RP2

Issue/Introduction

[ ISSUE ]

Newly added two LUNs invisible with the error " VxVM vxconfigd NOTICE V-5-1-13788 Data Corruption Protection Activated - User Corrective Action Needed"

Welcome to "KB Articles"