Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

TrueNas SCALE iSCSI target not accessible via Windows iSCSI Initiator or from Linux via open-iscsi

Description

TrueNAS scale installed baremetal on Dell SC8000. Everything is up and running, but unable to see the iSCSI target 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.

iSCSI Target Config:

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"

I can ping the SAN IP's of the TrueNAS Scale system from the Windows server. Both machines are on same network and plugged into the same switch on SAN network. 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. I can ping TrueNAS Scale from Windows server over the SAN.

I put an Ubuntu VM on the SAN network and attempted to reach the TrueNAS Scale iSCSI target as well. Followed steps from https://www.truenas.com/docs/scale/shares/ . Ubuntu machine could not see the target either. Response from CLI was "iscsiadm: No portals found"

Problem/Justification

None

Impact

None

Activity

Show:

Andrew Walker 
March 18, 2022 at 12:56 AM

Then it sounds like this is a whitespace handling issue in the xen orchestra version you're using. There were a few nightlies prior to the 22.02 release when this was broken in exports generation, but I don't see any issue with spaces in path names in 22.02 release.

Chad High 
March 18, 2022 at 12:36 AM

Yes, mounting NFS normally through Linux seems to work.

Andrew Walker 
March 14, 2022 at 5:10 PM

Can you mount the NFS export with a space in the name outside of xen orchestra? I don't see this issue with Linux or MacOS SMB clients.

Chad High 
March 12, 2022 at 3:25 PM
(edited)

I did a quick test inside of xcp-ng and it looks like its only presenting the name up until the whitespace. Not sure if this is xen orchestra or truenas. The test path I created was 

Also to note, I was not able to see any entry at all previous to the release version of truenas.

Vladimir Vinogradenko 
March 12, 2022 at 2:12 PM

are you still having issues with NFS share path whitespaces in 22.02.0 release?

Cannot Reproduce

Details

Assignee

Reporter

Labels

Impact

Time remaining

0m

Components

Fix versions

Affects versions

Priority

Katalon Platform

Created October 11, 2021 at 3:57 PM
Updated July 6, 2022 at 9:02 PM
Resolved March 18, 2022 at 12:56 AM