Software iSCSI LUNs disappear after rebooting or upgrading the ESX/ESXi host
search cancel

Software iSCSI LUNs disappear after rebooting or upgrading the ESX/ESXi host


Article ID: 340055


Updated On:


VMware vSphere ESXi


  • After rebooting or upgrading the ESX/ESXi host, the Software iSCSI LUNs disappear
  • After upgrading from ESXi 4.x to ESXi 5.0 the Software iSCSI adapter is missing
  • The iSCSI initiator cannot find the targets presented to it
  • Dynamic IP addresses are listed under the iSCSI Server Location in the Dynamic Discovery tab of the iSCSI Initiator properties
  • Removing existing Dynamic/Static IPs for the software iSCSI target fails
  • Adding new Dynamic/Static IPs for the Software iSCSI target fails
  • Rescanning for new iSCSI targets fails
  • The vSphere Client reports the error:

    iScsiLibException: status(80000000): unknown error; Message= IMA_RemoveDiscoveryAddress


VMware ESXi 6.5.x
VMware ESXi 4.0.x Embedded
VMware vSphere ESXi 5.1
VMware ESXi 6.7.x
VMware vSphere ESXi 5.0
VMware ESXi 4.1.x Embedded
VMware ESXi 4.1.x Installable
VMware vSphere ESXi 7.x
VMware ESXi 4.0.x Installable
VMware vSphere ESXi 5.5
VMware ESXi 6.0.x
VMware ESX 4.0.x
VMware ESX 4.1.x


The issue occurs when the iSCSI configuration is corrupted.


Note: Before proceeding, ensure that there is sufficient free ramdisk space on the ESXi host.

For more/related information, see:
To resolve this issue, you must reinitialize the iSCSI configuration.
To reinitialize the iSCSI configuration:
  1. Log in to the ESX/ESXi host as the root user.
  2. Run this command to disable the Software iSCSI initiator:

    # esxcfg-swiscsi -d

  3. In the ESX/ESXi host, rename all files in the /etc/vmware/vmkiscsid folder . This folder contains these files:

    • initiatorname.iscsi
    • iscsid.conf
    • vmkiscsid.db

    To rename the files, run these commands:

    # mv initiatorname.iscsi initiatorname.iscsi.old
    # mv iscsid.conf iscsid.conf.old
    # mv vmkiscsid.db vmkiscsid.db.old

    Additional files, such as vmkiscsid.db-journal, if present, must also be renamed.

  4. Reboot the ESX/ESXi host.
  5. After rebooting the host, run this command to re-enable the Software iSCSI initiator:

    # esxcfg-swiscsi -e

    Note: A new software iSCSI initiator ID is generated. This IQN needs to be added to the SAN.

  6. Run this command to scan for disks that are available through the Software iSCSI interface:

    # esxcfg-swiscsi -s


  • If iSCSI re-initialization still does not allow the host to detect presented LUNs, try rebooting the physical network switch.
  • Any virtual machines housed on temporarily disconnected LUNs may have to be re-added to inventory.

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box..
Investigating disk space on an ESX or ESXi host
ESXi 4.1.x ramdisk MAINSYS use is at 100%
ESX/ESXi ホストの再起動またはアップグレード後、ソフトウェア iSCSI LUN が表示されなくなる