ESXi host might fail with a purple diagnostic screen while getting SMART statistics from an NVMe drive
search cancel

ESXi host might fail with a purple diagnostic screen while getting SMART statistics from an NVMe drive

book

Article ID: 431301

calendar_today

Updated On:

Products

VMware vSphere ESXi 8.0

Issue/Introduction

ESXi host might fail with a PSoD while getting SMART statistics from an NVMe drive on some situation.

  •  A synchronous command such as VMK_NVME_ADMIN_CMD_GET_LOG_PAGE delays for more than 120 seconds
  •  The command time out was due to a bad drive or any other reason while ESXi fetching SMART statistics from an NVMe drive.

--vmkernel.log--
YYYY-MM-DDTHH:MM:SS cpu14:#######)WARNING: NVMEDEV:3045 Controller cannot be disabled, status: Timeout
YYYY-MM-DDTHH:MM:SS cpu14:#######)WARNING: NVMEDEV:8261 Failed to disable controller 260, status: Timeout
YYYY-MM-DDTHH:MM:SS cpu14:#######)WARNING: NVMEDEV:9647 Controller 260 recovery already active.

--PSoD--
YYYY-MM-DDTHH:MM:SS cpu48:#######)Backtrace for current CPU #48, worldID=#######, fp=0x42004c006840
YYYY-MM-DDTHH:MM:SS cpu48:#######)0x453a4ec1bdd0:[0x42000c58b8c5]TimerInsert@vmkernel#nover+0x61 stack: 0x453a4ec1f300, 0x0, 0x42000cad4e50, 0x19fc50542d3d1, 0xffffffffffffffff
YYYY-MM-DDTHH:MM:SS cpu48:#######)0x453a4ec1bde0:[0x42000c58c958]Timer_AddTCWithLockDomain@vmkernel#nover+0x14d stack: 0x42000cad4e50, 0x19fc50542d3d1, 0xffffffffffffffff, 0x0, 0x41ffcc8507e0
YYYY-MM-DDTHH:MM:SS cpu48:#######)0x453a4ec1be60:[0x42000c58ca37]Timer_AddTC@vmkernel#nover+0x24 stack: 0x41ffcc518a40, 0x2001, 0x453a4ec1bee0, 0x19fc4f5ad64fd, 0x453a4ec1bee0
YYYY-MM-DDTHH:MM:SS cpu48:#######)0x453a4ec1bea0:[0x42000cad9194]CpuSchedSleepUntilTC@vmkernel#nover+0x99 stack: 0x2001, 0x453a4ec1bee0, 0x43030640ab90, 0x1168f9a5255fb, 0x1
YYYY-MM-DDTHH:MM:SS cpu48:#######)0x453a4ec1bf60:[0x42000c55f0e1]IntrCookieRetireLoop@vmkernel#nover+0x1f2 stack: 0x180, 0x453a000000e0, 0x42004c000250, 0x94, 0x30
YYYY-MM-DDTHH:MM:SS cpu48:#######)0x453a4ec1bfe0:[0x42000cad67b2]CpuSched_StartWorld@vmkernel#nover+0xbf stack: 0x0, 0x42000c544cf0, 0x0, 0x0, 0x0
YYYY-MM-DDTHH:MM:SS cpu48:#######)0x453a4ec1c000:[0x42000c544cef]Debug_IsInitialized@vmkernel#nover+0xc stack: 0x0, 0x0, 0x0, 0x0, 0x0

Environment

VMware ESXi 8.0

Resolution

This issue is resolved in the VMware ESXi 8.0 Update 3h (Build 25067014)

Additional Information

VMware ESXi 8.0 Update 3h Release Notes
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/release-notes/esxi-update-and-patch-release-notes/vsphere-esxi-80u3h-release-notes.html