iscsi lun recognized but /dev entries not created

A

atatury

New Member
Oct 29, 2023
3
0
1
Hello all,

I've been having a strange problem for a couple of days. In my simple test setup, 3 Huawei 2288H V5 servers and 1 Oceanstore 2200v3 iscsi storage exist. Proxmox PVE 8.1.4 was installed and a 2 TB iscsi lun was presented to all 3 hosts. During iscsi setup of first host, everything went smooth and lun dev entries (/dev/sdb and /dev/sdc) were created. I then proceeded to install multipath, but during one of the reboots /dev entries were gone and no longer come back. The same issue happened for the 2nd server but in the first iscsi lun presentation phase not in multipath setup. Iscsi lun has been seen by PVE but device entries couldn't be created. I checked all regular things but seems fine. How can I proceed ?

Thank you..
 
atatury said:
I checked all regular things but seems fine. How can I proceed ?
Click to expand...
Can you please expand on what the regular things are? Do include actual commands you ran, output you received, and any corresponding log messages and related configuration files.
Please use CODE tags and/or spoiler tags to make the message readable.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Hi,

Storage iscsi portal addresses are 192.168.100.105 and 192.168.100.106. Server initiator is 192.168.100.101. Attached is /etc/pve/storage.cfg file.

root@proxmox01:~# pvesm scan iscsi 192.168.100.105
iqn.2006-08.com.huawei:oceanstor:2100fcbcd177708f::21f01:192.168.100.105 192.168.100.105:3260

root@proxmox01:~# pvesm add iscsi Iscsi-test --portal 192.168.100.105 --target iqn.2006-08.com.huawei:oceanstor:2100fcbcd177708f::21f01:192.168.100.105

root@proxmox01:~# pvesm status
Name Type Status Total Used Available %
Iscsi-test iscsi active 0 0 0 0.00%
local dir active 98497780 18585524 74862708 18.87%
local-lvm lvmthin active 3353231360 40574099 3312657260 1.21%

On the storage side, iscsi initator has been seen and seems ok.

Thank you..
 

Attachments

You seem to have some sort of network or array issue. Perhaps you can reach out to your storage vendor for help?

ay 29 15:50:12 proxmox01 iscsid[1211]: iSCSI daemon with pid=1213 started!
May 29 15:50:16 proxmox01 iscsid[1211]: connect to 192.168.100.105:3260 failed (No route to host)
May 29 15:50:16 proxmox01 iscsid[1211]: connect to 192.168.100.106:3260 failed (No route to host)
May 29 15:50:20 proxmox01 kernel: scsi host15: iSCSI Initiator over TCP/IP
May 29 15:50:20 proxmox01 kernel: scsi host16: iSCSI Initiator over TCP/IP
May 29 15:50:20 proxmox01 kernel: scsi 16:0:0:0: Direct-Access HUAWEI XSG1 4305 PQ: 1 ANSI: 6
May 29 15:50:20 proxmox01 kernel: scsi 15:0:0:0: Direct-Access HUAWEI XSG1 4305 PQ: 1 ANSI: 6
May 29 15:50:20 proxmox01 kernel: scsi 16:0:0:0: Attached scsi generic sg2 type 0
May 29 15:50:20 proxmox01 iscsiadm[1218]: Logging in to [iface: default, target: iqn.2006-08.com.huawei:oceanstor:2100fcbcd177708f::21f01:192.168.100.105, portal: 192.168.100.105,3260]
May 29 15:50:20 proxmox01 iscsiadm[1218]: Logging in to [iface: default, target: iqn.2006-08.com.huawei:oceanstor:2100fcbcd177708f::1021f01:192.168.100.106, portal: 192.168.100.106,3260]
May 29 15:50:20 proxmox01 iscsiadm[1218]: Login to [iface: default, target: iqn.2006-08.com.huawei:oceanstor:2100fcbcd177708f::21f01:192.168.100.105, portal: 192.168.100.105,3260] successful.
May 29 15:50:20 proxmox01 iscsiadm[1218]: Login to [iface: default, target: iqn.2006-08.com.huawei:oceanstor:2100fcbcd177708f::1021f01:192.168.100.106, portal: 192.168.100.106,3260] successful.
May 29 15:50:20 proxmox01 kernel: scsi 15:0:0:0: Attached scsi generic sg3 type 0
May 29 15:50:20 proxmox01 systemd[1]: Finished open-iscsi.service - Login to default iSCSI targets.

May 29 15:50:21 proxmox01 iscsid[1211]: Connection2:0 to [target: iqn.2006-08.com.huawei:oceanstor:2100fcbcd177708f::1021f01:192.168.100.106, portal: 192.168.100.106,3260] through [iface: default] is operational now
May 29 15:50:21 proxmox01 iscsid[1211]: Connection1:0 to [target: iqn.2006-08.com.huawei:oceanstor:2100fcbcd177708f::21f01:192.168.100.105, portal: 192.168.100.105,3260] through [iface: default] is operational now
May 29 15:50:21 proxmox01 chronyd[1246]: Selected source 10.151.101.9

May 29 17:16:15 proxmox01 kernel: connection2:0: detected conn error (1020)
May 29 17:16:15 proxmox01 kernel: connection1:0: detected conn error (1020)
May 29 17:16:16 proxmox01 iscsid[1211]: Kernel reported iSCSI connection 2:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3)
May 29 17:16:16 proxmox01 iscsid[1211]: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3)
May 29 17:16:18 proxmox01 iscsid[1211]: connect to 192.168.100.106:3260 failed (Connection refused)
May 29 17:16:18 proxmox01 iscsid[1211]: connect to 192.168.100.105:3260 failed (Connection refused)
May 29 17:16:21 proxmox01 iscsid[1211]: connect to 192.168.100.106:3260 failed (Connection refused)
May 29 17:16:21 proxmox01 iscsid[1211]: connect to 192.168.100.105:3260 failed (Connection refused)
May 29 17:16:23 proxmox01 pvestatd[1418]: storage 'Iscsi-test2' is not online
May 29 17:16:23 proxmox01 pvestatd[1418]: storage 'Iscsi-test' is not online

The sessions never recovered since then. This is likely a an array issue, or some type of firewall/switch problem.

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
You must log in or register to reply here.
Top Bottom