Truenas Scale Hosting iSCSI Targets - Unable to connect to Targets from Windows server 2019 VM hosted on ESXI

[berichards]

Hello All,

I hope you are doing well. We had an old Dell Compellant Storage array at work. I have taken one of the SC8000 controller heads from the Compellant, two SC200 Compellant drive bays with the intent to re-purpose them for Video Surveillance dump storage. For those unfamiliar, the SC8000 is basically a Dell r720 chassis with a different badge on it (don't let anyone tell you otherwise). The SC200 drive bays are 2U 12x drive bays with dual SAS controllers on the back.

I have managed to get TrueNAS scale installed on the SC8000 controller and I have all of the drives from the SC200 drive bays together in a pool. Everything is up and running, but I am unable to see the iSCSI shares from the Truenas scale setup on my Windows Server VM's. I am wondering if the ISCSI service on TrueNAS scale is verified and functioning.

I have seen some posts from the middle of last year on the forums about iSCSI service not starting, but I do not feel those are applicable because my service is starting. I have iSCSI running on 5x other TrueNAS core boxes, so I know all of the settings that I need to have in place are funtional (at least in TrueNas Core) I have also configured:

• A Single zVol for iSCSI testing
  • labelled zVol1
• Truenas Scale iSCSI portal
  • Currently set up to listen on ALL of the interfaces (just for testing)
  • I have previously tried advertising just my 2 SAN networks on the portal listener but that did not work either
• Initiators Group is set to allow all initiators (again, for testing)
• Authorized access
  • No authorized access set up (again for the sake of testing)
• iSCSI target
  • set the target name to test
  • set the portal group ID to the only portal group
  • Initiator group ID is set to the all group
• iSCSI Extents
  • Pointed at the single zVol
  • Labelled the Extent "test"
  • Left all other setting default
• Associated Target
  • Target = Selected "test"
  • Lun ID = 0
  • Extent = "test"

Our surveillance system servers are on a completely separate VMware/ESXI and SAN infrastructure. The only purpose the TrueNAS scale system will serve is dump storage for the Windows 2019 VM's that host our Video Surveillance. I have 2 VMWare NIC's on the Server guest OS's that are connected to our SAN. I can ping the SAN IP's of the TrueNAS Scale system from the Windows Surveillance server. I also have a TrueNAS Core system functioning on the same 2 SAN networks and connected to the guest, so I assume that the network portion is good.

As stated earlier I beleive there may be a problem with the iSCSI connector on the TrueNAS Scale box, but I have no idea where to start looking for evidence of that. I was hoping someone may be able to point me in a direction that I have yet to look.

 

[berichards]

I have rebuilt my iSCSI config on TrueNAS Scale at least 10 times at this point.

To verify my SAN network connectivity between the Windows Server VM (the iSCSI initiatior) I enabled SMB on Scale and created a test user. I can browse to the SMB share just fine over the SAN network. At this point I am still leaning toward iSCSI service issues on TNAS Core.

Also, I just realized I did not give specs on my Dell SC8000 (Still just an R720 without the drive bays).

2x Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz
64 GB ECC Memory
Dell LSI 9206-16e hba sas card with latest Broadcom IT firmware
2x Compellant SC200 2u drive enclosures, each with 12x 6TB Dell Branded Seagate 7200 rpm drives

 

[berichards]

I have rebuilt my iSCSI config on TrueNAS Scale at least 10 times at this point.

To verify my SAN network connectivity between the Windows Server VM (the iSCSI initiatior) I enabled SMB on Scale and created a test user. I can browse to the SMB share just fine over the SAN network. At this point I am still leaning toward iSCSI service issues on TNAS Core.

Also, I just realized I did not give specs on my Dell SC8000 (Still just an R720 without the drive bays).

2x Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz
64 GB ECC Memory
Dell LSI 9206-16e hba sas card with latest Broadcom IT firmware
2x Compellant SC200 2u drive enclosures, each with 12x 6TB Dell Branded Seagate 7200 rpm drives

Sorry, still new here... I am running TrueNAS-SCALE-21.08-BETA.1

 

[Samuel Tai]

From what I can gather in the release notes for SCALE, iSCSI should work. In the 2019 initiator, are you first browsing the portal SCALE has running to discover the available targets?

 

[flyingducktape]

I am running TrueNAS-SCALE-21.08-BETA.2, experiencing the same.
Can't discover any targets from win 10 iSCSI initiator or linux machine.

root@proliant:~# iscsiadm -m discovery -t sendtargets -p 10.1.1.130
iscsiadm: No portals found

No errors reported on either side, server logs:

Oct 9 06:37:02 truenas systemd[1]: Starting LSB: SCST - A Generic SCSI Target Subsystem...
Oct 9 06:37:02 truenas kernel: DLM installed
Oct 9 06:37:02 truenas kernel: [532265]: scst: User interface thread started
Oct 9 06:37:02 truenas kernel: [532250]: scst: Attached to scsi1, channel 0, id 0, lun 0, type 0
Oct 9 06:37:02 truenas kernel: [532250]: scst: Attached to scsi0, channel 0, id 0, lun 0, type 0
Oct 9 06:37:02 truenas kernel: [532250]: scst: Attached to scsi0, channel 0, id 1, lun 0, type 0
Oct 9 06:37:02 truenas kernel: [532250]: scst: Attached to scsi0, channel 0, id 2, lun 0, type 0
Oct 9 06:37:02 truenas kernel: [532250]: scst: Attached to scsi3, channel 0, id 0, lun 0, type 5
Oct 9 06:37:02 truenas kernel: [532250]: scst: Attached to scsi0, channel 0, id 3, lun 0, type 0
Oct 9 06:37:02 truenas kernel: [532250]: scst: Attached to scsi0, channel 0, id 4, lun 0, type 0
Oct 9 06:37:02 truenas kernel: [532250]: scst: Attached to scsi0, channel 0, id 5, lun 0, type 0
Oct 9 06:37:02 truenas kernel: [532250]: scst: Attached to scsi0, channel 0, id 6, lun 0, type 13
Oct 9 06:37:02 truenas kernel: [532276]: scst: Init thread started
Oct 9 06:37:02 truenas kernel: [532277]: scst: Task management thread started
Oct 9 06:37:02 truenas kernel: [532250]: scst: Target template copy_manager registered successfully
Oct 9 06:37:02 truenas kernel: [532278]: scst: Management thread started
Oct 9 06:37:02 truenas kernel: [532250]: scst: Target copy_manager_tgt for template copy_manager registered successfully
Oct 9 06:37:02 truenas kernel: [532250]: scst: Using security group "copy_manager_tgt" for initiator "copy_manager_sess" (target copy_manager_tgt)
Oct 9 06:37:02 truenas kernel: [532250]: scst: SCST version 3.6.0-pre loaded successfully (global max mem for commands ignored, per device 998MB)
Oct 9 06:37:02 truenas kernel: [532250]: scst: Enabled features: TRACING
Oct 9 06:37:02 truenas kernel: [532250]: iscsi-scst: iSCSI SCST Target - version 3.6.0-pre
Oct 9 06:37:02 truenas kernel: [532250]: iscsi-scst: Registered iSCSI transport: iSCSI-TCP
Oct 9 06:37:02 truenas kernel: [532250]: scst: Target template iscsi registered successfully
Oct 9 06:37:02 truenas kernel: [532279]: iscsi-scst: Read thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532284]: iscsi-scst: Read thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532280]: iscsi-scst: Read thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532290]: iscsi-scst: Write thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532281]: iscsi-scst: Read thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532282]: iscsi-scst: Read thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532283]: iscsi-scst: Read thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532285]: iscsi-scst: Read thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532286]: iscsi-scst: Read thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532287]: iscsi-scst: Read thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532288]: iscsi-scst: Read thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532289]: iscsi-scst: Write thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532291]: iscsi-scst: Write thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532292]: iscsi-scst: Write thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532293]: iscsi-scst: Write thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532294]: iscsi-scst: Write thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532295]: iscsi-scst: Write thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532296]: iscsi-scst: Write thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532297]: iscsi-scst: Write thread for pool 00000000c48dd33f started
Oct 9 06:37:02 truenas kernel: [532298]: iscsi-scst: Write thread for pool 00000000c48dd33f started
Oct 9 06:37:03 truenas kernel: [532250]: iscsi-scst: Registered iSCSI transport: iSER
Oct 9 06:37:03 truenas kernel: [532313]: iscsi-scst: Created iser portal cm_id:00000000c07a0484
Oct 9 06:37:03 truenas kernel: [532313]: iscsi-scst: iser portal cm_id:00000000c07a0484 listens on: 0.0.0.0:3260
Oct 9 06:37:03 truenas kernel: [532313]: iscsi-scst: Created iser portal cm_id:000000008ab82cb9
Oct 9 06:37:03 truenas kernel: [532313]: iscsi-scst: iser portal cm_id:000000008ab82cb9 listens on: 0000:0000:0000:0000:0000:0000:0000:0000 3260
Oct 9 06:37:03 truenas kernel: [532265]: scst: Removed all devices from group copy_manager_tgt
Oct 9 06:37:03 truenas kernel: [532313]: scst: Target iqn.2005-10.org.freenas.ctl:test for template iscsi registered successfully
Oct 9 06:37:03 truenas kernel: [532265]: scst: Waiting for 1 active commands to complete...
Oct 9 06:37:03 truenas kernel: [532265]: scst: All active commands completed
Oct 9 06:37:03 truenas kernel: [532265]: scst: Waiting for 1 active commands to complete...
Oct 9 06:37:03 truenas kernel: [532265]: scst: All active commands completed
Oct 9 06:37:03 truenas kernel: [532265]: scst: Added name *#* to group security_group (target iqn.2005-10.org.freenas.ctl:test)
Oct 9 06:37:03 truenas scst[532235]: Loading and configuring SCST.
Oct 9 06:37:03 truenas systemd[1]: Started LSB: SCST - A Generic SCSI Target Subsystem.
Oct 9 06:37:10 truenas iscsi-scstd[532313]: Connect from 10.1.1.128:26202 to 10.1.1.130:3260
Oct 9 06:37:13 truenas iscsi-scstd[532313]: Connect from 10.1.1.150:33030 to 10.1.1.130:3260

 

[berichards]

From what I can gather in the release notes for SCALE, iSCSI should work. In the 2019 initiator, are you first browsing the portal SCALE has running to discover the available targets?

Samuel, Thank you for the response. I am browsing for the targets in the Windows VM and I am coming up with no results. I think it is important to note, the quick connect window in the VM does not say connection failed when I try to connect to the SCALE iSCSI IP. It says "No Targets available for Login using Quick Connect":

 

[berichards]

Samuel, Thank you for the response. I am browsing for the targets in the Windows VM and I am coming up with no results. I think it is important to note, the quick connect window in the VM does not say connection failed when I try to connect to the SCALE iSCSI IP. It says "No Targets available for Login using Quick Connect":

View attachment 49864

I will also post iSCSI configuration for clarity's sake.

Target Global Configuaration Tab:

• Global Configuration
  • Base Name: iqn.2005-10.org.freenas.ctl
  • ISNS Servers: Blank
  • Pool Available Space Threshold (%): Blank

Portals Tab:

 

[Samuel Tai]

Is your Windows VM co-resident in the same host as the SCALE VMs? Does the portal work from an initiator off-box?

 

[berichards]

Is your Windows VM co-resident in the same host as the SCALE VMs? Does the portal work from an initiator off-box?

SCALE is installed baremetal on the SC8000 chassis. It is a separate server from the Windows VM.

The Windows VM is on a separate SAN with Dell Blade servers as the Compute. The Dell Blade/Windows VM and the SC8000/SCALE are both direct connected to a top of the rack Cisco Switch with 10Gb NICs.

I have tried to reach the portal from the iSCSI initiator on my desktop PC. It does not appear to be able to reach the portal either.

 

[Samuel Tai]

OK, everything looks correct configuration-wise. Go ahead and submit a bug report.

 

[berichards]

OK, everything looks correct configuration-wise. Go ahead and submit a bug report.

Thank you. Bug report submitted. Link to ticket here: https://jira.ixsystems.com/browse/NAS-112782

 

[flyingducktape]

For me seems to be resolved in 22.02-RC.1

 

[flyingducktape]

Following the wizard was the easiest way to reach a basic valid configuration.
You must setup one initiator group (thought default was "Allow All Initiators" implicitly), one extent and associate it with the target in order for the discovery to work now.

But is all that expected behavior?
I can understand that the initiator group is mandatory, but having a extent configured simply for the discovery to work does not seem right to me. Is that part of the protocol?

 

[hescominsoon]

https://jira.ixsystems.com/browse/NAS-109891

 

[Marv21]

https://jira.ixsystems.com/browse/NAS-109891

After 5 times resetup i finaly found the solution.
Like in the comment section mentioned if you have a Pool with an space in the Path, Iscsi isnt working.
You will get not error or anything - you just wont find your iscsi device on your client side...

 

[rwebb802]

Stumbled across this today - confirmed solution with same problem in SCALE 22.02.0.

Removing all spaces from path made my target show up instantly.

Created an account to say thank you. :)