PSOD due to same Replication Identifiers for different VMs

Products

• VMware vSphere ESXi

Issue/Introduction

• ESXi host crashes with the below backtrace:
  
  YYYY-HH-MMThh:mm:ss.130Z In(14) LogEFI: cpu43:43466381)ESC[45mESC[33;1mVMware ESXi 8.0.2 [Releasebuild-24585300 x86_64]ESC[0m
YYYY-HH-MMThh:mm:ss.922Z In(14) LogEFI[2100165]: #PF Exception 14 in world 43466381:vmx IP 0x420024d245e9 addr 0x0
YYYY-HH-MMThh:mm:ss.922Z In(14) LogEFI[2100165]: PTEs:0xa0c3ea3027;0xb241e17027;0x0;
YYYY-HH-MMThh:mm:ss.922Z In(14) LogEFI[2100165]:
YYYY-HH-MMThh:mm:ss.922Z In(14) LogEFI[2100165]: Module(s) involved in panic: [hbr_filter Implements v20.21; built: <date>]
YYYY-HH-MMThh:mm:ss.131Z In(14) LogEFI: cpu43:43466381)cr0=0x80010031 cr2=0x0 cr3=0xc8f326f000 cr4=0x142768
YYYY-HH-MMThh:mm:ss.131Z In(14) LogEFI: cpu43:43466381)FMS=06/55/7 uCode=0x5003707
YYYY-HH-MMThh:mm:ss.131Z In(14) LogEFI: cpu43:43466381)frame=0x453a8fc9aa90 ip=0x420024d245e9 err=0x2 rflags=0x10202
YYYY-HH-MMThh:mm:ss.131Z In(14) LogEFI: cpu43:43466381)rax=0x0 rbx=0x43379ac06fe0 rcx=0x0
YYYY-HH-MMThh:mm:ss.131Z In(14) LogEFI: cpu43:43466381)rdx=0x2c rbp=0x43379ac3a550 rsi=0x453a8fc9ab6b
YYYY-HH-MMThh:mm:ss.132Z In(14) LogEFI: cpu43:43466381)rdi=0x0 r8=0x453a0e81f000 r9=0x42004ac00000
YYYY-HH-MMThh:mm:ss.132Z In(14) LogEFI: cpu43:43466381)r10=0x0 r11=0x810000 r12=0x43379ac3a588
YYYY-HH-MMThh:mm:ss.132Z In(14) LogEFI: cpu43:43466381)r13=0x433345419eef r14=0x43379ac0703c r15=0x43379ac06fe0
YYYY-HH-MMThh:mm:ss.922Z In(14) LogEFI[2100165]: *PCPU43:43466381/vmx
YYYY-HH-MMThh:mm:ss.922Z In(14) LogEFI[2100165]: PCPU  0: SSUUSSSVVSSSSSSVSSSSSSSSVSVVVSSSVSVVSSVVVUSUVSSVSVVVVSVSVVVVVVVV
YYYY-HH-MMThh:mm:ss.922Z In(14) LogEFI[2100165]: PCPU 64: VVUVSVVVVVVSVVVV
YYYY-HH-MMThh:mm:ss.132Z In(14) LogEFI: cpu43:43466381)Code start: 0x420024c00000 VMK uptime: 87:08:06:48.121
YYYY-HH-MMThh:mm:ss.133Z In(14) LogEFI: cpu43:43466381)0x453a8fc9ab58:[0x420024d245e9]SPLockWork@vmkernel#nover+0x15 stack: 0x43379ac074a0
YYYY-HH-MMThh:mm:ss.133Z In(14) LogEFI: cpu43:43466381)0x453a8fc9ab60:[0x42002647ab0b]Task_Terminate@(hbr_filter)#<None>+0x2c stack: 0xbad0005
YYYY-HH-MMThh:mm:ss.133Z In(14) LogEFI: cpu43:43466381)0x453a8fc9ab80:[0x42002647833a]Sync_TerminateTask@(hbr_filter)#<None>+0x43 stack: 0x1
YYYY-HH-MMThh:mm:ss.133Z In(14) LogEFI: cpu43:43466381)0x453a8fc9aba0:[0x420026473ed4]HbrShutdownTaskQueueLocked@(hbr_filter)#<None>+0x3d stack: 0x2000
YYYY-HH-MMThh:mm:ss.134Z In(14) LogEFI: cpu43:43466381)0x453a8fc9abb0:[0x4200264754a1]Hbr_Attach@(hbr_filter)#<None>+0x10a stack: 0x453a8fc9b550
YYYY-HH-MMThh:mm:ss.134Z In(14) LogEFI: cpu43:43466381)0x453a8fc9b520:[0x42002645f382]HbrFilterAttachFilter@(hbr_filter)#<None>+0xbf stack: 0x433345419e20
YYYY-HH-MMThh:mm:ss.134Z In(14) LogEFI: cpu43:43466381)0x453a8fc9b5b0:[0x420025224455]VSCSIFilter_AttachFilter@vmkernel#nover+0x15e stack: 0x2973e9c
YYYY-HH-MMThh:mm:ss.134Z In(14) LogEFI: cpu43:43466381)0x453a8fc9b610:[0x42002520b5c0]VSCSI_AttachFilter@vmkernel#nover+0x99 stack: 0x0
YYYY-HH-MMThh:mm:ss.135Z In(14) LogEFI: cpu43:43466381)0x453a8fc9b650:[0x4200251e4581]UWVMKSyscall_VSCSIAttachFilter@vmkernel#nover+0x5e stack: 0x1124555867acd338
YYYY-HH-MMThh:mm:ss.135Z In(14) LogEFI: cpu43:43466381)0x453a8fc9b6a0:[0x4200251f1871]UW64VMKSyscallUnpackVSCSIAttachFilter@vmkernel#nover+0x66 stack: 0x87
YYYY-HH-MMThh:mm:ss.135Z In(14) LogEFI: cpu43:43466381)0x453a8fc9bed0:[0x4200251841c8]User_UWVMK64SyscallHandler@vmkernel#nover+0x129 stack: 0xd6573d81f0
YYYY-HH-MMThh:mm:ss.136Z In(14) LogEFI: cpu43:43466381)0x453a8fc9bf40:[0x420024d64c54]SyscallUWVMK64@vmkernel#nover+0x90 stack: 0x0
YYYY-HH-MMThh:mm:ss.147Z In(14) LogEFI: cpu43:43466381)base fs=0x0 gs=0x42004ac00000 Kgs=0x0

Environment

• VMware vSphere ESXi 8.x

Cause

• PSOD happens due to two different VMs having the same replicated disk IDs.

Resolution

• Need to find those VMs and how the replication disks got the same disk ID. Please open a Support Request with Broadcom Support for fruther assistance.