iSCSI connection errors connecting to EqualLogic storage

rhp

New Member
Nov 10, 2026
10
1
3
Hi all,

We are in the process of moving from vSphere/ESXi to Proxmox (as many are).
Our setup uses two dedicated 10Gbps nics per host to connect iSCSI to a Dell EqualLogic storage array. This is the same setup as we are using on vSphere.
We use multipath on top of the iSCSI connections and we are using LVM on top of the iSCSI LUNs.

We used this document https://linux.dell.com/files/whitepapers/iSCSI_Multipathing_in_Ubuntu_Server.pdf for the initial setup.

Although it appears to be working, we see many iSCSI level errors, with dropping connections, and even some I/O errors now and then.
The errors we are seeing include:
  • iscsi_tcp: datalen 10957675 > 262144
  • received itt 8568d1c expected session age (8)
  • [sdaz] tag#28 FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK cmd_age=50s
    [sdaz] tag#28 CDB: Write(16) 8a 00 00 00 00 00 9c a3 a9 00 00 00 06 80 00 00
  • ping timeout of 5 secs expired, recv timeout 5, last rx 4793794517, last ping 4793799680, now 4793804800
  • I/O error, dev sdo, sector 4047049216 op 0x1:(WRITE) flags 0x4a00 phys_seg 83 prio class 2
I have attached our iscsid.conf and multipath.conf.

We are having some trouble identifying the root cause of these issues, since (as far as we can tell). We have tried to fiddle with some of the iscsid timeout settings and tried various multipath options, but without making much of a difference.

We hope that there are some experts here that recognize some of these errors, and are willing to help us out.
 

Attachments

Last edited:
Hi @rhp , welcome to the forum.

At first glance - you have a network configuration/path problem. You've provided config files but did not supply any running state from the system. The state may contain the key.

You mentioned that the configuration was lifted from VMware - that is not always possible without changes. Few things worth collecting first, please provide them as text using CODE tags the forum edit box:
ip a
iscsiadm -m session
iscsiadm -m target
iscsiadm -m session -P 2
Is MTU correct?

iscsi_tcp: datalen 10957675 > 262144

What this means: The initiator read a PDU header saying the data segment is about 10.9 MB. This is obviously larger than the negotiated MaxRecvDataSegmentLength is 256 KB. No real target sends a 10.9 MB segment - that number is invalid, which means the initiator was parsing bytes that are not a real PDU header.
This could also be caused by your NIC offload. Frankly, the troubleshooting you need to do is not PVE specific but rather standard Linux/Network debug.


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

Thanks for taking the time to respond to my message.
The output is a bit large for code blocks, so I attached them as files instead.

We checked the MTUs on all nics, in the switches and in EqualLogic. They are all set to 9000.

Code:
~# iscsiadm -m target
iscsiadm: target mode is unkonwn/unsupported

Frankly, the troubleshooting you need to do is not PVE specific but rather standard Linux/Network debug.

We are well aware of this, but we thought this might be a good place to start.
If you can recommend a forum where we'll have better chances, I'm happy to move the conversation there.
 

Attachments

Assuming for the moment that you thoroughly applied all the kernel level values recommended in the Dell guide, and those are _critical_ for operations of a Linux Multihome system (same network on multiple interfaces). Your next best step is to disable NIC offload:
ethtool -K <nic> gro off lro off

But, I would first disconnect one of the paths (physically, virtually, deconfigure) and try access with single path only. Get your configuration to the most minimal workable set and start building from there.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Code:
~# iscsiadm -m node
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-00c6d8c0c-e6a006f7db96ace2-cird11-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-00c6d8c0c-e6a006f7db96ace2-cird11-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-03e6d8c0c-ee2006f7dbb6ace2-cird12-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-03e6d8c0c-ee2006f7dbb6ace2-cird12-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-05c6d8c0c-311006f7dbd6ace2-cird13-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-05c6d8c0c-311006f7dbd6ace2-cird13-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-0736d8c0c-594006f7dbf6ace2-cird14-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-0736d8c0c-594006f7dbf6ace2-cird14-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-09b6d8c0c-36f006f7dc16ace2-cird19-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-09b6d8c0c-36f006f7dc16ace2-cird19-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-0b86d8c0c-7d3006f7dc36ace2-cird20-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-0b86d8c0c-7d3006f7dc36ace2-cird20-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-0d56d8c0c-a0b006f7dc56ace2-cird21-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-0d56d8c0c-a0b006f7dc56ace2-cird21-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-0f76d8c0c-44b006f7dc76ace2-cird25-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-0f76d8c0c-44b006f7dc76ace2-cird25-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-12c6d8c0c-d0f006f7dc96ace2-cird101-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-12c6d8c0c-d0f006f7dc96ace2-cird101-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-1d46d8c0c-716006f7dcb6ace2-cita1-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-1d46d8c0c-716006f7dcb6ace2-cita1-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-2026d8c0c-dca006f7dcd6ace2-cita2-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-2026d8c0c-dca006f7dcd6ace2-cita2-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-21f6d8c0c-23a006f7dcf6ace2-cita3-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-21f6d8c0c-23a006f7dcf6ace2-cita3-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-2396d8c0c-c4d006f7dd16ace2-cita4-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-2396d8c0c-c4d006f7dd16ace2-cita4-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-2556d8c0c-b63006f7dd36ace2-cita5-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-2556d8c0c-b63006f7dd36ace2-cita5-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-26f6d8c0c-3b8006f7dd56ace2-cita6-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-26f6d8c0c-3b8006f7dd56ace2-cita6-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-33d6d8c0c-916006f7dd96ace2-management-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-33d6d8c0c-916006f7dd96ace2-management-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-38a6d8c0c-b87006f7ddb6ace2-templates-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-38a6d8c0c-b87006f7ddb6ace2-templates-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-40a6d8c0c-b56006f7dde6ace2-userlab-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-40a6d8c0c-b56006f7dde6ace2-userlab-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-cc76d8c0c-ade006f7da46ace1-cird01-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-cc76d8c0c-ade006f7da46ace1-cird01-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-d9d6d8c0c-743006f7da66ace1-cird02-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-d9d6d8c0c-743006f7da66ace1-cird02-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-dd66d8c0c-a8d006f7da86ace1-cird03-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-dd66d8c0c-a8d006f7da86ace1-cird03-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-f0c6d8c0c-212006f7daa6ace1-cird04-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-f0c6d8c0c-212006f7daa6ace1-cird04-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-f386d8c0c-c47006f7dac6ace1-cird05-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-f386d8c0c-c47006f7dac6ace1-cird05-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-f586d8c0c-8eb006f7daf6ace1-cird06-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-f586d8c0c-8eb006f7daf6ace1-cird06-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-f796d8c0c-eb7006f7db16ace1-cird07-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-f796d8c0c-eb7006f7db16ace1-cird07-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-f926d8c0c-5c3006f7db36ace1-cird08-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-f926d8c0c-5c3006f7db36ace1-cird08-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-fa96d8c0c-188006f7db56ace1-cird09-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-fa96d8c0c-188006f7db56ace1-cird09-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-fc36d8c0c-cee006f7db76ace1-cird10-phoenix
10.0.0.250:3260,1 iqn.2001-05.com.equallogic:0-8a0906-fc36d8c0c-cee006f7db76ace1-cird10-phoenix
 
I tried running `ethtool -K <nic> gro off lro off` and it gave me this output:


Code:
~# ethtool -K nic3 gro off lro off
Actual changes:
rx-gro: off
rx-gro-hw: off [not requested]

It seems "lro" does not work on my systems.
 
It seems "lro" does not work on my systems.
It is possible, it is also possible it was already disabled. I don't know what NIC you are using. You should be able to check supported modes in your documentation.

Make sure you disable it on both card, you can also try to disable various other offloads:
ethtool -K nic2 tso off gso off
ethtool -K nic3 tso off gso off

You can check the state with:
ethtool -k nic3 | grep -E "generic-receive-offload|large-receive"



Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Before changing more offload settings, I'd try to pin one of the write errors to a path. On the affected host, multipath -ll shows the device name and SCSI address for each path. Match the device in the kernel error to that list, then check iscsiadm -m session -P 3 for the attached disk and current portal. The -P 3 view adds the SCSI device details to the session output you already collected. Use the current portal for that session, since the portal stored in the configuration can differ. Open-iSCSI session details · DM Multipath path output

If the errors recur, note the time and compare the change in RX/TX errors and drops on both storage NICs and their switch ports around that event. On Linux, ip -s -s link show dev NIC gives the detailed interface counters. That helps you see whether the same session or physical port keeps showing up. The large datalen message identifies a receive-length check that failed, and that message alone leaves the failing layer open. I'd leave the live LVM paths in place while collecting these observations. Linux interface statistics · iSCSI TCP receive check in Linux

OpenAI Codex assisted with drafting this reply.
 
@bbgeek17 We applied the offload settings and let it run for a day. It does not seem to have made much of a difference.
We are still observing the datalen errors, as well as the others.
 
@sanoc_mars Thanks so much for helping out.
FYI: We are seeing these problems across a set of 10 hosts. 5x HP DL380 using ethernet cables, 3x HP DL380 using fiber and 2x Dell R750 also using fiber.
It looks like the errors are not specific to a single iSCSI session.
 
Hi @bbgeek17,

Thanks for taking the time to respond to my message.
The output is a bit large for code blocks, so I attached them as files instead.

We checked the MTUs on all nics, in the switches and in EqualLogic. They are all set to 9000.

Code:
~# iscsiadm -m target
iscsiadm: target mode is unkonwn/unsupported



We are well aware of this, but we thought this might be a good place to start.
If you can recommend a forum where we'll have better chances, I'm happy to move the conversation there.
Hi,
do you have controlled the mtu?
Code:
ping -s 8972 -M do ip.of.equal.logic
Udo
 
FYI: We are seeing these problems across a set of 10 hosts. 5x HP DL380 using ethernet cables, 3x HP DL380 using fiber and 2x Dell R750 also using fiber.
It looks like the errors are not specific to a single iSCSI session.
While less likely than a misconfiguration, there could be a software issue/bug on the target (EqualLogic ) side. If you are using this system in production now, it may be a good idea to turn on header checksums until you figured this out


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Last edited:
What does Dell say when you asked them?
Laughs. if you can get anyone who still remembers what Equallogic is, I believe the reply would be "can I interest you in PowerStore?"

@rhp assuming you have a PS6X10, you've been operating it for going on 10 years (and possibly longer.) Its likely still "fine" but firmware hasnt really been maintained to account for switch and initiator upgrades in the interim. At some point you have to ask yourself what your time is worth.