No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


The host can’t find lun after the host reload OS

Publication Date:  2012-09-18 Views:  88 Downloads:  0

Issue Description

Customer’s environment is Windows 2003 server ×64, connect the iSCSI host’s interface storage S2600. Customer reinstall the system for some reason. After this, we can’t find lun after scanning for it.

Alarm Information


Handling Process

We can guide the customer to add initiator at storage S2600, then scan for the lun at host.

Root Cause

When we install the Microsoft iSCSI Initiator in host it will generate a random iqn number.
So the system will generate a new iqn number after we reinstall the Microsoft iSCSI Initiator.


ISCSI host interface’s IP-SAN is based on the delivery between initiator (host system) and target (storage). We can find lun only when there is a correct link between them.