Hello everyone,
after the pricing debacle with VM-Ware we are switching from ESXi to ProxMox VE in out Lab enviroment.
So far everything went smoothly until we tried to attach our external storage over iSCSI to our lab host.
I have an established connection but when we try to create an LVM ProxMox isn't showing us any LUNs or Harddrives.
A bit more investigation and testing and we saw that the connection is established but it seams like the host is trying to log into the storage but fails.
To make sure that it's not some hidden CHAP problem on the storages side we configured CHAP on both ends to without success.
I also looked up the status of iSCSI witch confused me even more:
Our Host is an PRIMERGY RX2540 M1, our storage a Fujitsu DX60 S3.
They are directly attached to each other.
Hope you can help me fix this, so far i had no luck with any of the forum posts I found.
I'm also fairly new to ProxMox and Linux in general, so please be patient
after the pricing debacle with VM-Ware we are switching from ESXi to ProxMox VE in out Lab enviroment.
So far everything went smoothly until we tried to attach our external storage over iSCSI to our lab host.
I have an established connection but when we try to create an LVM ProxMox isn't showing us any LUNs or Harddrives.
A bit more investigation and testing and we saw that the connection is established but it seams like the host is trying to log into the storage but fails.
Code:
root@Lab-Host:/# iscsiadm -m discovery -t sendtargets -p 10.20.30.1
iscsiadm: cannot make connection to 10.20.30.1: Connection refused
iscsiadm: cannot make connection to 10.20.30.1: Connection refused
iscsiadm: cannot make connection to 10.20.30.1: Connection refused
iscsiadm: cannot make connection to 10.20.30.1: Connection refused
iscsiadm: cannot make connection to 10.20.30.1: Connection refused
iscsiadm: cannot make connection to 10.20.30.1: Connection refused
iscsiadm: connection login retries (reopen_max) 5 exceeded
Code:
root@Lab-Host:/# journalctl -u iscsid -f
Dec 11 15:52:35 Lab-Host iscsid[465478]: connection1:0 is operational after recovery (2 attempts)
Dec 11 15:52:35 Lab-Host iscsid[465478]: connection2:0 is operational after recovery (2 attempts)
Dec 12 11:03:03 Lab-Host iscsid[465478]: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3)
Dec 12 11:03:03 Lab-Host iscsid[465478]: Kernel reported iSCSI connection 2:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3)
Dec 12 11:03:23 Lab-Host iscsid[465478]: connection1:0 is operational after recovery (2 attempts)
Dec 12 11:03:23 Lab-Host iscsid[465478]: connection2:0 is operational after recovery (2 attempts)
Dec 12 11:03:39 Lab-Host iscsid[465478]: Kernel reported iSCSI connection 3:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3)
Dec 12 11:03:39 Lab-Host iscsid[465478]: Kernel reported iSCSI connection 4:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3)
Dec 12 11:03:59 Lab-Host iscsid[465478]: connection3:0 is operational after recovery (2 attempts)
Dec 12 11:03:59 Lab-Host iscsid[465478]: connection4:0 is operational after recovery (2 attempts)To make sure that it's not some hidden CHAP problem on the storages side we configured CHAP on both ends to without success.
I also looked up the status of iSCSI witch confused me even more:
Code:
× open-iscsi.service - Login to default iSCSI targets
Loaded: loaded (/lib/systemd/system/open-iscsi.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Thu 2024-12-19 13:31:07 CET; 4min 17s ago
Docs: man:iscsiadm(8)
man:iscsid(8)
Process: 25095 ExecStart=/sbin/iscsiadm -m node --loginall=automatic (code=exited, status=19)
Main PID: 25095 (code=exited, status=19)
CPU: 3ms
Dec 19 13:31:07 Lab-Host systemd[1]: Starting open-iscsi.service - Login to default iSCSI targets...
Dec 19 13:31:07 Lab-Host systemd[1]: open-iscsi.service: Main process exited, code=exited, status=19/n/a
Dec 19 13:31:07 Lab-Host iscsiadm[25095]: iscsiadm: Could not login all leading-login portals
Dec 19 13:31:07 Lab-Host systemd[1]: open-iscsi.service: Failed with result 'exit-code'.
Dec 19 13:31:07 Lab-Host systemd[1]: Failed to start open-iscsi.service - Login to default iSCSI targets.
root@Lab-Host:~# systemctl start open-iscsi
Job for open-iscsi.service failed because the control process exited with error code.
See "systemctl status open-iscsi.service" and "journalctl -xeu open-iscsi.service" for details.
root@Lab-Host:~# journalctl -xeu ope^Ciscsi.service
Dec 19 11:06:34 Lab-Host systemd[1]: Starting open-iscsi.service - Login to default iSCSI targets...
░░ Subject: A start job for unit open-iscsi.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit open-iscsi.service has begun execution.
░░
░░ The job identifier is 31.
Dec 19 11:06:34 Lab-Host iscsiadm[1212]: iscsiadm: Could not login all leading-login portals
Dec 19 11:06:34 Lab-Host systemd[1]: open-iscsi.service: Main process exited, code=exited, status=19/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit open-iscsi.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 19.
Dec 19 11:06:34 Lab-Host systemd[1]: open-iscsi.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit open-iscsi.service has entered the 'failed' state with result 'exit-code'.
Dec 19 11:06:34 Lab-Host systemd[1]: Failed to start open-iscsi.service - Login to default iSCSI targets.
░░ Subject: A start job for unit open-iscsi.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit open-iscsi.service has finished with a failure.
░░
░░ The job identifier is 31 and the job result is failed.
Dec 19 13:31:07 Lab-Host systemd[1]: Starting open-iscsi.service - Login to default iSCSI targets...
░░ Subject: A start job for unit open-iscsi.service has begun execution
░░ Defined-By: systemd
░░ Support: [URL='https://www.debian.org/support https://www.debian.org/support[/URL]Our Host is an PRIMERGY RX2540 M1, our storage a Fujitsu DX60 S3.
They are directly attached to each other.
Hope you can help me fix this, so far i had no luck with any of the forum posts I found.
I'm also fairly new to ProxMox and Linux in general, so please be patient
Last edited: