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.

Knowledge Base

Unable to Automatically Mount S5100 Disks After the iSCSI Initiator Name on the Host is Changed

Publication Date:  2012-07-20  |   Views:  216  |   Downloads:  0  |   Author:  anliku  |   Document ID:  EKB1000009394


Issue Description

At a commercial deployment, the T8000 blade server cannot automatically mount LUNs on the S5100 after restart. However, disks can be detected by manually logging out of and then logging in to the T8000.After each restart of the T8000, the connected status can be viewed on the iSCSI initiator software, but no disk can be detected until a manual connection attempt is implemented. Server: T8000 blade server Operating system: Windows 2003 Server SP2 Storage device: S5100 b031

Alarm Information


Handling Process

Log out of the T8000, remove targets from Persistent Targets, and log in to the T8000. After the updated initiator name is validated, disks can be automatically recognized by restarting the S5100.

Root Cause

Given the initiator name is updated during the configuration, the updated initiator name is displayed as connected on the iSCSI initiator software after restart. In this condition, a manual connection is required for proper disk detection. To validate the updated initiator, users need to remove targets from Persistent Targets after updating the initiator name and then log in to the T8000. Otherwise, the preupdate initiator name is used after restart. To correct the error, use either of the following methods: Method 1. Log out of the T8000, remove targets from Persistent Targets, update the initiator name, and log in to the T8000. Method 2. Update the initiator name, log out of the T8000. Remove targets from Persistent Targets, and log in to the T8000.


When disks cannot be automatically mounted under IP SAN environments, troubleshoot iSCSI initiators and targets or operating systems for prompt fault location.