iSCSI Conneciton timed out during write

Status
Not open for further replies.

Ken Harvey

Cadet
Joined
Feb 23, 2016
Messages
5
I am attempting to setup an iSCSI connection to VMware ESXi, but I receive an error each time that I try an dadd the storage:
Code:
Call "HostDatastoreSystem.CreateVmfsDatastore" for object "ha-datastoresystem" on ESXi "10.10.4.100" failed.


Specs:
Code:
FreeNAS version:  FreeNAS-9.3-STABLE-201602031011
VMware ESXi 6.0.0 3029758
Hardware: 
    FreeNAS Server:  SSG-5048R-E1CR36L
        CPU:  E5-2620V3
        RAM:  DDR4-2133 (64 GB)
        HD: Seagate 3.5" 6TB SAS 12Gb/s 7.2K RPM (x8 broken into 2 RAIDZ with 4 drives each)
    VMware Server:  SYS-2028R-C1RT (Intel I350-T4V2 iSCSI NIC)
        CPU:  E5-2650V3
        RAM:  DDR4-2133 (128 GB)
    Switch:  HP J9775A with 2 dedicated VLAN's for iSCSI traffic.
    Attached is my debug info


I should precursor this with that I had an iSCSI connection to a Xen Server without issue. But due to limitations in Xen, I was forced to switch over to VMware.
Inside VMware my iSCSI HBA sees the FreeNAS without issue, and when I go to storage it sees the LUN on the FreeNAS without issue, the problem is that I am unable to add the storage.
Originally I had the portals setup on FreeNAS so that I could do MPIO, but I have since changed this to be a single connection, using a single portal, single network port on both VMware and FreeNAS to make sure that it isn't MPIO losing packets somewhere.

The error that VMware is giving me suggests that the LUN isn't formatted properly, so I went to the CLI on VMware and I ran the following commands:
Code:
[root@localhost:~] esxcli storage core path list
sas.500304801c893b00-sas.604f387507f307d3-naa.600304801c893b001e4f387507f307d3
  UID: sas.500304801c893b00-sas.604f387507f307d3-naa.600304801c893b001e4f387507f307d3
  Runtime Name: vmhba2:C2:T0:L0
  Device: naa.600304801c893b001e4f387507f307d3
  Device Display Name: LSI Serial Attached SCSI Disk (naa.600304801c893b001e4f387507f307d3)
  Adapter: vmhba2
  Channel: 2
  Target: 0
  LUN: 0
  Plugin: NMP
  State: active
  Transport: sas
  Adapter Identifier: sas.500304801c893b00
  Target Identifier: sas.604f387507f307d3
  Adapter Transport Details: 500304801c893b00
  Target Transport Details: 604f387507f307d3
  Maximum IO Size: 131072

iqn.1998-01.com.vmware:56cb7d05-a650-3317-ffd0-a0369fa18c98-44a2c03c-00023d000001,iqn.2005-10.org.freenas.ctl:s01t01,t,257-naa.6589cfc0000000f78519af4df2d8dae1
  UID: iqn.1998-01.com.vmware:56cb7d05-a650-3317-ffd0-a0369fa18c98-44a2c03c-00023d000001,iqn.2005-10.org.freenas.ctl:s01t01,t,257-naa.6589cfc0000000f78519af4df2d8dae1
  Runtime Name: vmhba40:C0:T0:L0
  Device: naa.6589cfc0000000f78519af4df2d8dae1
  Device Display Name: FreeBSD iSCSI Disk (naa.6589cfc0000000f78519af4df2d8dae1)
  Adapter: vmhba40
  Channel: 0
  Target: 0
  LUN: 0
  Plugin: NMP
  State: active
  Transport: iscsi
  Adapter Identifier: iqn.1998-01.com.vmware:56cb7d05-a650-3317-ffd0-a0369fa18c98-44a2c03c
  Target Identifier: 00023d000001,iqn.2005-10.org.freenas.ctl:s01t01,t,257
  Adapter Transport Details: iqn.1998-01.com.vmware:56cb7d05-a650-3317-ffd0-a0369fa18c98-44a2c03c
  Target Transport Details: IQN=iqn.2005-10.org.freenas.ctl:s01t01 Alias= Session=00023d000001 PortalTag=257
  Maximum IO Size: 131072


From there I cheked the status of naa.6589cfc0000000f78519af4df2d8dae1 with:
Code:
[root@localhost:~] partedUtil getptbl /vmfs/devices/disks/naa.6589cfc0000000f785
19af4df2d8dae1
unknown
2005120 255 63 32212254720


I was able to change the unknown to msdos without issue, but I still receive the same errors:
Code:
[root@localhost:~] partedUtil setptbl /vmfs/devices/disks/naa.6589cfc0000000f785
19af4df2d8dae1 msdos
msdos
0 0 0 0


But if I attempt to switch it to GPT I receive this error:
Code:
[root@localhost:~] partedUtil setptbl /vmfs/devices/disks/naa.6589cfc0000000f785
19af4df2d8dae1 gpt
gpt
0 0 0 0
Error: Connection timed out during write on /dev/disks/naa.6589cfc0000000f78519af4df2d8dae1
WriteNewPtable: Unable to commit to disk


I am still working on troubleshooting this myself, but I have already killed several hours on this, so I figured I would ask for some help. If I find the solution, I will post it here, but any help would be greatly appreciated.

If I forgot or missed to post something, then just let me know.

Also I should mention that I am able to connect to NFS shares on my FreeNAS. But I just did this as a quick test and NFS is currently disabled.

Edit (since it hasn't been approved by an administrator yet)
I'm digging through the debug logs from the FreeNAS, and it is stating that it cannot ping my ESXi server (10.1.250.100). The 10.1.250.100 is one of my ESXi iSCSI IP addresses. When I go to the console on FreeNAS I am able to ping 10.1.250.100 and 10.1.251.100 without error. So I am unsure why I am receiving this other error.
Code:
Feb 23 09:48:04 SurviosSAN01 WARNING: 10.1.250.100 (iqn.1998-01.com.vmware:56cb7d05-a650-3317-ffd0-a0369fa18c98-44a2c03c): no ping reply (NOP-Out) after 5 seconds; dropping connection
 

Attachments

  • debug-SurviosSAN01-20160223095006..tgz
    194.2 KB · Views: 249
Last edited:

Ken Harvey

Cadet
Joined
Feb 23, 2016
Messages
5
Nope, I was not able to solve the problem using 9.3. But I downgraded to 9.2 and everything is working now without issue.

I read about a couple of bugs in 9.3, which prompted the downgrade, and sure enough it started to work.
 
Status
Not open for further replies.
Top