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>


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


Cannot find block device name for mapped LUN – iSCSI issue on Linux

Publication Date:  2014-09-20 Views:  66 Downloads:  0
Issue Description
Customer reported that he cannot find the device name from his Linux server. He can login into the iSCSI target with no issue, but he can only see an empty item of the LUN but without a valid block device name. The screenshot shows that he can successfully  logout nd login with storage's iSCSI target, but the output from command lsscsi still shows that there is no block device name:

Alarm Information
Handling Process
1. From ISM, add appropriate initiator to host:

2. From Linux server side, restart iscsi service. Then you'll find that the block device is back:

Root Cause
After checking through all the configurations between storage and server, it shows that someone removed host’s initiator from storage side. After adding initiator to host on storage side, the issue is resolved. From below screenshot we can see, there is no initiator attached on the host:
This problem is caused by the information inconsistence between storage and Linux server. An rescan operation can also make thing correct. However, use iscsiadm to rescan the iSCSI session will not help, please see below screenshot. You’ll have to restart iSCSI service or reboot the Linux server to make it correct.