Troubleshooting "LUN Detached by User" (esx.problem.scsi.device.state.off) in ESXi 8.0

Products

• VMware vSphere ESX 8.x
• VMware vSphere ESXi

Issue/Introduction

• A storage device (LUN) disappears from the ESXi host storage view or Datastore list.
• Virtual machines on the affected device may become inaccessible.
• You observe the event esx.problem.scsi.device.state.off in the logs.
• The logs indicate the device was "turned off administratively."  
  
  
  

Environment

VMware ESXi 8.0

Cause

The message "turned off administratively" indicates that the storage device was explicitly detached via a user action or a script/plugin. This is not a storage array failure, pathing issue, or Permanent Device Loss (PDL).

The ESXi host received a command to stop using the device.

• Identified User: The hostd.log shows the user vpxuser:DOMAIN\Administrator initiated the action. This usually implies an administrator logged into vCenter Server.
• Identified Device: naa.xxxxxxxxxxxxxxxxxxxxxxxxx.

The following log entries appear in /var/log/hostd.log and /var/log/vobd.log.

1. /var/log/hostd.log

This log confirms the event type and identifies the specific user who initiated the action.

Plaintext

2026-01-09T04:50:42.181Z In(166) Hostd[263856]: [Originator@6876 sub=Libs ... user=vpxuser:DOMAIN\Administrator] info [Config Store:4fedc81700] Checking for empty objects and arrays in comp esx grp storage key block_devices id naa.xxxxxxxxxxxxxxxxxxxxxxxxx object

2026-01-09T04:50:42.181Z In(166) Hostd[264347]: [Originator@6876 sub=Hostsvc.VmkVprobSource] VmkVprobSource::Post event: (vim.event.EventEx) {

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->     key = 79,

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->     chainId = 564763408,

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->     createdTime = "1970-01-01T00:00:00Z",

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->     userName = "",

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->     host = (vim.event.HostEventArgument) {

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->       name = "node1.example.com",

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->       host = 'vim.HostSystem:ha-host'

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->     },

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->     eventTypeId = "esx.problem.scsi.device.state.off",

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->     arguments = (vmodl.KeyAnyValue) [

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->       (vmodl.KeyAnyValue) {

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->          key = "1",

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->          value = "naa.xxxxxxxxxxxxxxxxxxxxxxxxx"

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->       }

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->     ],

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->     objectId = "ha-host",

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: -->     objectType = "vim.HostSystem",

2026-01-09T04:50:42.182Z In(166) Hostd[263806]: --> }

2026-01-09T04:50:42.183Z In(166) Hostd[263856]: [Originator@6876 ... user=vpxuser:DOMAIN\Administrator] info [Config Store:4fedc81700] [cs:1:1636948984]CommitTransaction invoked.

2. /var/log/vobd.log

This log confirms the VMkernel observed the state change requested by the user.

Plaintext

2026-01-09T04:50:42.180Z In(14) vobd[262395]:  [scsiCorrelator] 6900490752660us: [vob.scsi.device.state.off] Device naa.xxxxxxxxxxxxxxxxxxxxxxxxx  has been turned off administratively.

2026-01-09T04:50:42.180Z In(14) vobd[262395]:  [scsiCorrelator] 6900552974270us: [esx.problem.scsi.device.state.off] Device: naa.xxxxxxxxxxxxxxxxxxxxxxxxx  has been turned off administratively

Resolution

Scenario 1: Intentional Action

If the administrator intended to detach the LUN (e.g., for decommissioning or maintenance), no action is required. The system is behaving as expected.

Scenario 2: Accidental Action

If the LUN was detached by mistake, you must manually re-attach it to restore access to the datastore and VMs.

Method 1: Using the vSphere Client

1. Navigate to node1.example.com > Configure > Storage > Storage Devices.
2. Locate the device naa.xxxxxxxxxxxxxxxxxxxxxxxxx. It will likely be grayed out or listed with a status of "Detached".
3. Select the device and click Attach.
4. Rescan the storage adapter to ensure the datastore mounts.

Method 2: Using ESXCLI

1. Log in to the host via SSH.
2. Confirm the device is in the "off" state:

Bash

esxcli storage core device list -d naa.xxxxxxxxxxxxxxxxxxxxxxxxx

1. Set the device state to "on":

Bash

esxcli storage core device set --device naa.xxxxxxxxxxxxxxxxxxxxxxxxx --state on