Symptoms
- 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 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
Cause
The issue occurs when the iSCSI configuration is corrupted.
Resolution
The first thing to check on ESXi is if the Ramdisk space is full. For more/related information, see ESXi 4.1.x ramdisk MAINSYS use is at 100% (2001457).
ITo resolve this issue, you must reinitialize the iSCSI configuration.
To reinitialize the iSCSI configuration:
- Log in to the ESX/ESXi host as the root user.
- Run this command to disable the Software iSCSI initiator:
# esxcfg-swiscsi -d - In the ESX/ESXi host, rename all files in the /etc/vmware/vmkiscsid folder . This folder has 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. - Reboot the ESX/ESXi host.
- 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. - Run this command to scan for disks that are available through the Software iSCSI interface:
# esxcfg-swiscsi -s
Based on VMware KB 1038065
