VMware vSAN 8.x
NVMe controller encountered an internal error which was followed by controller reset. This usually indicates there is some hardware issue.
2025-11-26T23:05:39.033Z In(182) vmkernel: cpu90:2098639)NVMEIO:3233 Controller 260 received async event: type 0, info 3, log page ID 1.
2025-11-26T23:05:49.033Z Wa(180) vmkwarning: cpu36:2098047)WARNING: NVMEDEV:9036 Failed to read log page 0x1, retry 0, controller 260.2025-11-26T23:05:59.036Z Wa(180) vmkwarning: cpu38:2098047)WARNING: NVMEDEV:9036 Failed to read log page 0x1, retry 1, controller 2602025-11-26T23:06:09.036Z Wa(180) vmkwarning: cpu36:2098047)WARNING: NVMEDEV:9036 Failed to read log page 0x1, retry 2, controller 260
2025-11-26T23:06:09.036Z In(182) vmkernel: cpu36:2098047)NVMEDEV:8245 Resetting controller 260 (nqn.1994-11.com.samsung:nvme:######:2.5-inch:##############)2025-11-26T23:06:09.036Z In(182) vmkernel: cpu36:2098047)NVMEDEV:8260 Controller 260 state changed from 5 to 8(INRESET)
2025-11-26T23:06:09.055Z In(182) vmkernel: cpu38:2098047)NVMEDEV:8493 Reset controller 260 successful.
For further investigation engage the Server Hardware vendor to assess the health of the NVMe disk.