vSAN PSOD issue
search cancel

vSAN PSOD issue

book

Article ID: 405809

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptom:

  • PSOD screen issue seen with -




  • In LogEFI.log, we see below entries -

    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)VMware ESXi 8.0.3 [Releasebuild-24280767 x86_64]
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI[2100133]: #PF Exception 14 in world 2099553:VSAN_0x43246 IP 0x420015b6e88c addr 0x19
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)cr0=0x80010031 cr2=0x19 cr3=0x4bd56000 cr4=0x142768
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)FMS=06/6a/6 uCode=0xd0003e7
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)frame=0x4539f631bc20 ip=0x420015b6e88c err=0x0 rflags=0x10203
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)rax=0xbad0007 rbx=0x45baaa0eeb00 rcx=0x4
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)rdx=0x432d81e3c5c0 rbp=0x42001864e70f rsi=0x4314e84b5380
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)rdi=0x17 r8=0x1 r9=0xaed7135fa
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)r10=0x1 r11=0x2540be400 r12=0x432d81e3d390
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)r13=0x432d81e3d430 r14=0xbad0007 r15=0x45da754cc700
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI[2100133]: *PCPU56:2099553/VSAN_0x4324602deb80_Client
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)Code start: 0x420015a00000 VMK uptime: 37:22:57:37.119
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)0x4539f631bce8:[0x420015b6e88c]MCSLockWork@vmkernel#nover+0x8 stack: 0x42001864e70f
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)0x4539f631bcf0:[0x420015a39eaa]vmk_SpinlockLockIgnoreDeathPending@vmkernel#nover+0xf stack: 0x45baaa0eeee0
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)0x4539f631bd00:[0x42001864e70e][email protected]#0.0.0.1+0x6f stack: 0x45baaa0ef36a
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)0x4539f631bd50:[0x420018386b86][email protected]#0.0.0.1+0x1b stack: 0x0
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)0x4539f631bd70:[0x42001838fb3b][email protected]#0.0.0.1+0x2a8 stack: 0x0
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)0x4539f631be40:[0x4200183ee200][email protected]#0.0.0.1+0x35 stack: 0x2
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)0x4539f631be60:[0x4200183eb880][email protected]#0.0.0.1+0x5d stack: 0x72c
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)0x4539f631beb0:[0x4200184a2659][email protected]#0.0.0.1+0x12 stack: 0x1e38b60209d704
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)0x4539f631bed0:[0x420017c7ca46][email protected]#0.0.0.1+0x23f stack: 0x4324602dec40
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)0x4539f631bfa0:[0x420015b9f7f8]vmkWorldFunc@vmkernel#nover+0x31 stack: 0x420015b9f7f4
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)0x4539f631bfe0:[0x4200160d67b2]CpuSched_StartWorld@vmkernel#nover+0xbf stack: 0x0
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)0x4539f631c000:[0x420015b44cef]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0
    LogEFI.log:YYYY-MM-DDThh:mm:ss.###Z In(14) LogEFI: cpu56:2099553)base fs=0x0 gs=0x42004e000000 Kgs=0x0

Environment

VMware vSphere vSAN

Cause

  • The system attempted to access a memory region that was no longer valid, ultimately causing the crash.

Resolution

  • Issue will be fixed in ESX 9.0.1.0.
Powered by Wolken Software