ISCSI issue with vmware

Status
Not open for further replies.
B

bed

Dabbler
Joined
Jun 17, 2011
Messages
38
I'm hoping someone can point out something simple I'm overlooking on this one. I've got new hardware and I'm running 11.2 rc1. I had a couple of old pools I had imported and were not working well due to block size so I decided to reconfigure the pools and make new iscsi targets.

Currently I have 3 targets, one for windows and two for vmware (esxi 6.7 U1). All sharing the same portal and initiator. Windows can see and use any of the targets without problems. VMware can see all the targets but only lists the windows target as a device. The extents are identical. I am not using port bindng. In vcenter the paths are detected but have a status of dead. Screen shot of that attached.

when I do a rescan vmkernal.log shows
Code:
2018-11-12T14:57:59.641Z cpu8:2099951 opID=81979b41)World: 11943: VC opID RescanStorageFormMediator-apply-862-ngc:70000188-ab-23-3c58 maps to vmkernel opID 81979b41
2018-11-12T14:57:59.641Z cpu8:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.641Z cpu8:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T1:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.641Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.641Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C1:T1:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.641Z cpu4:2099951 opID=81979b41)WARNING: NMP: nmpPathClaimEnd:1206: Device, seen through path vmhba64:C1:T1:L1 is not registered (no active paths)
2018-11-12T14:57:59.641Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.641Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T2:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.641Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.641Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C1:T2:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.641Z cpu4:2099951 opID=81979b41)WARNING: NMP: nmpPathClaimEnd:1206: Device, seen through path vmhba64:C1:T2:L1 is not registered (no active paths)
2018-11-12T14:57:59.737Z cpu10:2097625)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.737Z cpu10:2097625)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T1:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.737Z cpu19:2097622)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.737Z cpu19:2097622)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T2:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.737Z cpu10:2097625)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.737Z cpu10:2097625)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C1:T1:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.737Z cpu19:2097622)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.737Z cpu19:2097622)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C1:T2:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.738Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.738Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T1:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.738Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.738Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C1:T1:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.738Z cpu4:2099951 opID=81979b41)WARNING: NMP: nmpPathClaimEnd:1206: Device, seen through path vmhba64:C1:T1:L1 is not registered (no active paths)
2018-11-12T14:57:59.738Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.738Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T2:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.738Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.738Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C1:T2:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.738Z cpu4:2099951 opID=81979b41)WARNING: NMP: nmpPathClaimEnd:1206: Device, seen through path vmhba64:C1:T2:L1 is not registered (no active paths)
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T1:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C1:T1:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: NMP: nmpPathClaimEnd:1206: Device, seen through path vmhba64:C1:T1:L1 is not registered (no active paths)
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T2:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C1:T2:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: NMP: nmpPathClaimEnd:1206: Device, seen through path vmhba64:C1:T2:L1 is not registered (no active paths)
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T1:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C1:T1:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: NMP: nmpPathClaimEnd:1206: Device, seen through path vmhba64:C1:T1:L1 is not registered (no active paths)
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T2:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C1:T2:L1" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T14:57:59.874Z cpu4:2099951 opID=81979b41)WARNING: NMP: nmpPathClaimEnd:1206: Device, seen through path vmhba64:C1:T2:L1 is not registered (no active paths)
2018-11-12T14:58:00.692Z cpu11:2111033)WARNING: NFS: 1227: Invalid volume UUID naa.6589cfc000000ed8f4c4ed6e16600ce9:2
2018-11-12T14:58:00.698Z cpu11:2111033)FSS: 6092: No FS driver claimed device 'naa.6589cfc000000ed8f4c4ed6e16600ce9:2': No filesystem on the device
2018-11-12T14:58:01.697Z cpu0:2097211)ScsiDeviceIO: 3068: Cmd(0x459a4cadfd80) 0x1a, CmdSN 0x199e from world 0 to dev "t10.SanDisk_Cruzer_Fit______4C532000020629114362" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2018-11-12T14:58:02.122Z cpu23:2099952 opID=d24ec10f)World: 11943: VC opID RescanStorageFormMediator-apply-863-ngc:70000188-e-9d-3c62 maps to vmkernel opID d24ec10f
2018-11-12T14:58:02.122Z cpu23:2099952 opID=d24ec10f)VC: 4616: Device rescan time 419 msec (total number of devices 6)
2018-11-12T14:58:02.122Z cpu23:2099952 opID=d24ec10f)VC: 4619: Filesystem probe time 1402 msec (devices probed 5 of 6)
2018-11-12T14:58:02.122Z cpu23:2099952 opID=d24ec10f)VC: 4621: Refresh open volume time 37 msec


I thought it could be network related but the old targets worked well enough in that regard and I am not sure what to do next.

Edit:
I have 2 pools for vmware storage each with 6 Seagate SAS drives in a mirrored stripe and a single zvol on each for use as a target. Standard GUI creation with no options changed.
ESXI host is a Supermicro X9DRi-LN4 with dual 2660v2 and 128Gb RAM using an intel 10G x550 plus whats listed as an Intel 82599EB 10-Gigabit SFP+ that I was pretty sure was a MELLANOX CONNECTX-2.
NAS is in my sig and besides hard drives the only other addition was a Chelsio 10GB 2-Ports SFP+ card.

Currently iscsi network is not yet isolated and everything runs on a Netgear XS728T.
 

Attachments

  • paths.jpg
    paths.jpg
    78.4 KB · Views: 692
  • global.jpg
    global.jpg
    61.5 KB · Views: 668
  • extent.jpg
    extent.jpg
    81.2 KB · Views: 662
  • initiator.jpg
    initiator.jpg
    70.2 KB · Views: 584
  • portal.jpg
    portal.jpg
    80.8 KB · Views: 588
  • target ass.jpg
    target ass.jpg
    41.4 KB · Views: 576
  • target.jpg
    target.jpg
    76.5 KB · Views: 586
  • pool.jpg
    pool.jpg
    81.7 KB · Views: 612
  • vmkernal adapters.jpg
    vmkernal adapters.jpg
    81.1 KB · Views: 612
Last edited:
kdragon75

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
bed said:
2018-11-12T14:58:01.697Z cpu0:2097211)ScsiDeviceIO: 3068: Cmd(0x459a4cadfd80) 0x1a, CmdSN 0x199e from world 0 to dev "t10.SanDisk_Cruzer_Fit______4C532000020629114362" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
Click to expand...
Something is WAY off if ESXi is able to SEE trying to access what I suspect is your FreeNAS boot device...

Per forum rules, please list detailed hardware and pool config. In addition to that, please post screenshots of each page from your iSCSI settings on FreeNAS.
 
B

bed

Dabbler
Joined
Jun 17, 2011
Messages
38
I was hoping it would be you kdragon. Updated original post and added additional screen captures. And yes that little flash drive is the boot drive.
 
kdragon75

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
That looks like a fairly straight forward setup... The pool vmdata1 has a zvol (also named vmdata1) that is mapped as an extent to the data1 target with two portal IPs...
can you provide the output of cat /etc/ctl.conf in [ code ] tags? FreeNAS seems to be doing something screwy...
Also try:
ping -S 172.16.6.1 -r 172.16.6.10
and
ping -S 172.16.4.1 -r 172.16.4.10
This will ping from FreeNAS -S IP to ESXi but skip the -r routing table. This will prevent any pings from being routed and ensures a "direct" L2 path (only because we know 172.16.X.10 is not a router)
https://www.freebsd.org/cgi/man.cgi...FreeBSD+11.2-RELEASE&arch=default&format=html
 
B

bed

Dabbler
Joined
Jun 17, 2011
Messages
38
Those pings worked fine from freenas. vmkping from the host works also.
Code:
root@znas:~ # ping -S 172.16.6.1 -r 172.16.6.10
PING 172.16.6.10 (172.16.6.10) from 172.16.6.1: 56 data bytes
64 bytes from 172.16.6.10: icmp_seq=0 ttl=64 time=2.192 ms
64 bytes from 172.16.6.10: icmp_seq=1 ttl=64 time=0.244 ms
64 bytes from 172.16.6.10: icmp_seq=2 ttl=64 time=0.643 ms
64 bytes from 172.16.6.10: icmp_seq=3 ttl=64 time=0.241 ms
64 bytes from 172.16.6.10: icmp_seq=4 ttl=64 time=0.218 ms
^C
--- 172.16.6.10 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.218/0.708/2.192/0.759 ms
root@znas:~ # ping -S 172.16.4.1 -r 172.16.4.10
PING 172.16.4.10 (172.16.4.10) from 172.16.4.1: 56 data bytes
64 bytes from 172.16.4.10: icmp_seq=0 ttl=64 time=3.232 ms
64 bytes from 172.16.4.10: icmp_seq=1 ttl=64 time=0.214 ms
64 bytes from 172.16.4.10: icmp_seq=2 ttl=64 time=0.348 ms
^C
--- 172.16.4.10 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.214/1.265/3.232/1.392 ms


Code:
root@znas:~ # cat /etc/ctl.conf
portal-group default {
}

portal-group pg1 {
		tag 0x0001
		discovery-filter portal-name
		discovery-auth-group no-authentication
		listen 172.16.6.1:3260
		listen 172.16.4.1:3260
		option ha_shared on
}

lun "NeoD" {
		ctl-lun 5
		path "/mnt/neoD/neoSet/data"
		blocksize 512
		option pblocksize 0
		serial "ac1f6b6c292405"
		device-id "iSCSI Disk	  ac1f6b6c292405				 "
		option vendor "FreeNAS"
		option product "iSCSI Disk"
		option revision "0123"
		option naa 0x6589cfc000000ed8f4c4ed6e16600ce9
		option insecure_tpc on
		option rpm 1
}

lun "vmdata1" {
		ctl-lun 6
		path "/dev/zvol/vmdata1/vmdata1"
		blocksize 4096
		option pblocksize 0
		serial "ac1f6b6c292406"
		device-id "iSCSI Disk	  ac1f6b6c292406				 "
		option vendor "FreeNAS"
		option product "iSCSI Disk"
		option revision "0123"
		option naa 0x6589cfc00000074b2ada1d40d148e508
		option insecure_tpc on
		option rpm 1
}

lun "vmdata2" {
		ctl-lun 7
		path "/dev/zvol/vmdata2/vmdata2"
		blocksize 4096
		option pblocksize 0
		serial "ac1f6b6c292407"
		device-id "iSCSI Disk	  ac1f6b6c292407				 "
		option vendor "FreeNAS"
		option product "iSCSI Disk"
		option revision "0123"
		option naa 0x6589cfc000000a7ed61583ecc0aeb56d
		option insecure_tpc on
		option rpm 1
}

target iqn.2017-10.nerds.bytes:znas201:neo {
		alias "neo"
		portal-group pg1 no-authentication

		lun 1 "NeoD"
}

target iqn.2017-10.nerds.bytes:znas201:vmdata1 {
		alias "data1"
		portal-group pg1 no-authentication

		lun 1 "vmdata1"
}

target iqn.2017-10.nerds.bytes:znas201:vmdata2 {
		alias "data 2"
		portal-group pg1 no-authentication

		lun 1 "vmdata2"
}
 
HoneyBadger

HoneyBadger

actually does care
Administrator
Moderator
iXsystems
Joined
Feb 6, 2014
Messages
5,112
It shouldn't be an issue, but best practice is usually to not present the same LUNs to Windows and VMware due to potential issues. Windows is supposed to be polite and not clobber the partition table/resignature it - but Windows is supposed to do a lot of things that it doesn't.

Re: your ctl.conf - did you manually assign LUN ID 1 to the mappings, or is that the new default in 11.2? Mine are all LUN 0.
 
B

bed

Dabbler
Joined
Jun 17, 2011
Messages
38
HoneyBadger said:
It shouldn't be an issue, but best practice is usually to not present the same LUNs to Windows and VMware due to potential issues. Windows is supposed to be polite and not clobber the partition table/resignature it - but Windows is supposed to do a lot of things that it doesn't.

Re: your ctl.conf - did you manually assign LUN ID 1 to the mappings, or is that the new default in 11.2? Mine are all LUN 0.
Click to expand...

New default.

As long as you don't favorite the targets in windows it shouldn't try to connect to it. When I get a little further along the windows target will get its own portal and initiator. Will have to wait till I get a second switch though (need more SFP+ ports).
 
B

bed

Dabbler
Joined
Jun 17, 2011
Messages
38
HoneyBadger said:
It's likely better now than it was before.

What does the ESX output of esxcli storage core path list look like?
Click to expand...
Code:
[root@localhost:~] esxcli storage core path list
iqn.1998-01.com.vmware:compute1-00023d000001,iqn.2017-10.nerds.bytes:znas201:neo,t,1-naa.6589cfc000000ed8f4c4ed6e16600ce9
   UID: iqn.1998-01.com.vmware:compute1-00023d000001,iqn.2017-10.nerds.bytes:znas201:neo,t,1-naa.6589cfc000000ed8f4c4ed6e16600ce9
   Runtime Name: vmhba64:C0:T0:L1
   Device: naa.6589cfc000000ed8f4c4ed6e16600ce9
   Device Display Name: FreeNAS iSCSI Disk (naa.6589cfc000000ed8f4c4ed6e16600ce9)
   Adapter: vmhba64
   Channel: 0
   Target: 0
   LUN: 1
   Plugin: NMP
   State: active
   Transport: iscsi
   Adapter Identifier: iqn.1998-01.com.vmware:compute1
   Target Identifier: 00023d000001,iqn.2017-10.nerds.bytes:znas201:neo,t,1
   Adapter Transport Details: iqn.1998-01.com.vmware:compute1
   Target Transport Details: IQN=iqn.2017-10.nerds.bytes:znas201:neo Alias= Session=00023d000001 PortalTag=1
   Maximum IO Size: 131072

sas.500605b00582f650-sas.606bab2d9facfd72-naa.600605b00582f650236bab2d9facfd72
   UID: sas.500605b00582f650-sas.606bab2d9facfd72-naa.600605b00582f650236bab2d9facfd72
   Runtime Name: vmhba0:C2:T0:L0
   Device: naa.600605b00582f650236bab2d9facfd72
   Device Display Name: Local LSI Disk (naa.600605b00582f650236bab2d9facfd72)
   Adapter: vmhba0
   Channel: 2
   Target: 0
   LUN: 0
   Plugin: NMP
   State: active
   Transport: sas
   Adapter Identifier: sas.500605b00582f650
   Target Identifier: sas.606bab2d9facfd72
   Adapter Transport Details: 500605b00582f650
   Target Transport Details: 606bab2d9facfd72
   Maximum IO Size: 262144

usb.vmhba32-usb.0:0-t10.SanDisk_Cruzer_Fit______4C532000020629114362
   UID: usb.vmhba32-usb.0:0-t10.SanDisk_Cruzer_Fit______4C532000020629114362
   Runtime Name: vmhba32:C0:T0:L0
   Device: t10.SanDisk_Cruzer_Fit______4C532000020629114362
   Device Display Name: Local USB Direct-Access (t10.SanDisk_Cruzer_Fit______4C532000020629114362)
   Adapter: vmhba32
   Channel: 0
   Target: 0
   LUN: 0
   Plugin: NMP
   State: active
   Transport: usb
   Adapter Identifier: usb.vmhba32
   Target Identifier: usb.0:0
   Adapter Transport Details: Unavailable or path is unclaimed
   Target Transport Details: Unavailable or path is unclaimed
   Maximum IO Size: 32768

iqn.1998-01.com.vmware:compute1-00023d000002,iqn.2017-10.nerds.bytes:znas201:vmdata2,t,1-
   UID: iqn.1998-01.com.vmware:compute1-00023d000002,iqn.2017-10.nerds.bytes:znas201:vmdata2,t,1-
   Runtime Name: vmhba64:C1:T2:L1
   Device: No associated device
   Device Display Name: No associated device
   Adapter: vmhba64
   Channel: 1
   Target: 2
   LUN: 1
   Plugin: NMP
   State: dead
   Transport: iscsi
   Adapter Identifier: iqn.1998-01.com.vmware:compute1
   Target Identifier: 00023d000002,iqn.2017-10.nerds.bytes:znas201:vmdata2,t,1
   Adapter Transport Details: Unavailable or path is unclaimed
   Target Transport Details: Unavailable or path is unclaimed
   Maximum IO Size: 131072

iqn.1998-01.com.vmware:compute1-00023d000001,iqn.2017-10.nerds.bytes:znas201:vmdata2,t,1-
   UID: iqn.1998-01.com.vmware:compute1-00023d000001,iqn.2017-10.nerds.bytes:znas201:vmdata2,t,1-
   Runtime Name: vmhba64:C0:T2:L1
   Device: No associated device
   Device Display Name: No associated device
   Adapter: vmhba64
   Channel: 0
   Target: 2
   LUN: 1
   Plugin: NMP
   State: dead
   Transport: iscsi
   Adapter Identifier: iqn.1998-01.com.vmware:compute1
   Target Identifier: 00023d000001,iqn.2017-10.nerds.bytes:znas201:vmdata2,t,1
   Adapter Transport Details: Unavailable or path is unclaimed
   Target Transport Details: Unavailable or path is unclaimed
   Maximum IO Size: 131072

iqn.1998-01.com.vmware:compute1-00023d000002,iqn.2017-10.nerds.bytes:znas201:vmdata1,t,1-
   UID: iqn.1998-01.com.vmware:compute1-00023d000002,iqn.2017-10.nerds.bytes:znas201:vmdata1,t,1-
   Runtime Name: vmhba64:C1:T1:L1
   Device: No associated device
   Device Display Name: No associated device
   Adapter: vmhba64
   Channel: 1
   Target: 1
   LUN: 1
   Plugin: NMP
   State: dead
   Transport: iscsi
   Adapter Identifier: iqn.1998-01.com.vmware:compute1
   Target Identifier: 00023d000002,iqn.2017-10.nerds.bytes:znas201:vmdata1,t,1
   Adapter Transport Details: Unavailable or path is unclaimed
   Target Transport Details: Unavailable or path is unclaimed
   Maximum IO Size: 131072

iqn.1998-01.com.vmware:compute1-00023d000001,iqn.2017-10.nerds.bytes:znas201:vmdata1,t,1-
   UID: iqn.1998-01.com.vmware:compute1-00023d000001,iqn.2017-10.nerds.bytes:znas201:vmdata1,t,1-
   Runtime Name: vmhba64:C0:T1:L1
   Device: No associated device
   Device Display Name: No associated device
   Adapter: vmhba64
   Channel: 0
   Target: 1
   LUN: 1
   Plugin: NMP
   State: dead
   Transport: iscsi
   Adapter Identifier: iqn.1998-01.com.vmware:compute1
   Target Identifier: 00023d000001,iqn.2017-10.nerds.bytes:znas201:vmdata1,t,1
   Adapter Transport Details: Unavailable or path is unclaimed
   Target Transport Details: Unavailable or path is unclaimed
   Maximum IO Size: 131072

sas.500605b00582f650-sas.606bf9784a60e3d2-naa.600605b00582f650236bf9784a60e3d2
   UID: sas.500605b00582f650-sas.606bf9784a60e3d2-naa.600605b00582f650236bf9784a60e3d2
   Runtime Name: vmhba0:C2:T1:L0
   Device: naa.600605b00582f650236bf9784a60e3d2
   Device Display Name: Local LSI Disk (naa.600605b00582f650236bf9784a60e3d2)
   Adapter: vmhba0
   Channel: 2
   Target: 1
   LUN: 0
   Plugin: NMP
   State: active
   Transport: sas
   Adapter Identifier: sas.500605b00582f650
   Target Identifier: sas.606bf9784a60e3d2
   Adapter Transport Details: 500605b00582f650
   Target Transport Details: 606bf9784a60e3d2
   Maximum IO Size: 262144

iqn.1998-01.com.vmware:compute1-00023d000002,iqn.2017-10.nerds.bytes:znas201:neo,t,1-naa.6589cfc000000ed8f4c4ed6e16600ce9
   UID: iqn.1998-01.com.vmware:compute1-00023d000002,iqn.2017-10.nerds.bytes:znas201:neo,t,1-naa.6589cfc000000ed8f4c4ed6e16600ce9
   Runtime Name: vmhba64:C1:T0:L1
   Device: naa.6589cfc000000ed8f4c4ed6e16600ce9
   Device Display Name: FreeNAS iSCSI Disk (naa.6589cfc000000ed8f4c4ed6e16600ce9)
   Adapter: vmhba64
   Channel: 1
   Target: 0
   LUN: 1
   Plugin: NMP
   State: active
   Transport: iscsi
   Adapter Identifier: iqn.1998-01.com.vmware:compute1
   Target Identifier: 00023d000002,iqn.2017-10.nerds.bytes:znas201:neo,t,1
   Adapter Transport Details: iqn.1998-01.com.vmware:compute1
   Target Transport Details: IQN=iqn.2017-10.nerds.bytes:znas201:neo Alias= Session=00023d000002 PortalTag=1
   Maximum IO Size: 131072
 
kdragon75

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
Ok so the SanDisk is the boot drive for ESXi. That's a relief. On your target association, try setting your second lun to LUN 2. I vaguely remember something about ESXi only allowing one LUN 1, 2, and so fourth per portal. i could be off on this but it's easy enough to test. If this fixes the issue, you should file a bug report as defaulting to LUN 1 per target may not be ideal even if its standard.
 
kdragon75

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
You could also just move both vmware LUNs into one target. That's perfectly acceptable.
 
HoneyBadger

HoneyBadger

actually does care
Administrator
Moderator
iXsystems
Joined
Feb 6, 2014
Messages
5,112
kdragon75 said:
I vaguely remember something about ESXi only allowing one LUN 1, 2, and so fourth per portal
Click to expand...

You can have multiple of the same LUN ID per portal as long as each is behind a different target:

upload_2018-11-12_11-57-8.png


I think something's amiss on the FreeNAS CTL side. Can you try creating a new LUN 0 and see if it is presented?
 
B

bed

Dabbler
Joined
Jun 17, 2011
Messages
38
I tried adjusting LUNs to no avail. I tried multiple combinations including moving the windows target to 3 and and splitting the vm targets on LUN 1 and 2 and vice versa. LUN 0 is not allowed via the GUI.

I removed one of the vm targets for testing and now not able to create any additional targets regardless of name used. A reboot did not help. messages says
Code:
Nov 12 10:20:06 znas ctld[2359]: no LUNs defined for target "iqn.2017-10.nerds.bytes:znas201:vmdata2"
Nov 12 10:20:08 znas ctld[2359]: no LUNs defined for target "iqn.2017-10.nerds.bytes:znas201:vmdata2"

Should I wipe my iscsi config and redo it?

Edit:
Looks like you get that error if you have no LUN 1. Changed one of them back to LUN 1 and I can create targets again.
 
Last edited:
B

bed

Dabbler
Joined
Jun 17, 2011
Messages
38
I added the vm based targets back and the esx host generated this in the vmkernel.log without doing a rescan. Looks different than last log I posted.
Code:
2018-11-12T17:40:28.943Z cpu6:2098149)ScsiDeviceIO: 3082: Cmd(0x459a4e6ba280) 0x15, CmdSN 0x26e8 from world 0 to dev "naa.6589cfc000000ed8f4c4ed6e16600ce9" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x1a 0x0.
2018-11-12T17:40:28.943Z cpu11:2097605)WARNING: ScsiDeviceIO: 8460: SITPUA set to 0 for device naa.6589cfc000000ed8f4c4ed6e16600ce9. This may cause log spam. The system was unable to change this setting to 1. Failure
2018-11-12T17:40:28.946Z cpu11:2097605)WARNING: NFS: 1227: Invalid volume UUID naa.6589cfc000000ed8f4c4ed6e16600ce9:2
2018-11-12T17:40:28.951Z cpu11:2097605)FSS: 6092: No FS driver claimed device 'naa.6589cfc000000ed8f4c4ed6e16600ce9:2': No filesystem on the device
2018-11-12T17:40:28.951Z cpu11:2097605)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 40, Parameter: 0x43049b3966c0, Registered!
2018-11-12T17:40:28.951Z cpu11:2097605)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 200, Parameter: 0x43049b3966c0, Registered!
2018-11-12T17:40:28.951Z cpu11:2097605)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 800, Parameter: 0x43049b3966c0, Registered!
2018-11-12T17:40:28.951Z cpu11:2097605)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 400, Parameter: 0x43049b3966c0, Registered!
2018-11-12T17:40:28.951Z cpu11:2097605)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 8, Parameter: 0x43049b3966c0, Registered!
2018-11-12T17:40:28.951Z cpu11:2097605)ScsiDevice: 5189: Successfully registered device "naa.6589cfc000000ed8f4c4ed6e16600ce9" from plugin "NMP" of type 0
2018-11-12T17:40:28.951Z cpu11:2097605)NMP: nmp_DeviceUpdateProtectionInfo:748: Set protection info for device 'naa.6589cfc000000ed8f4c4ed6e16600ce9', Enabled: 0 ProtType: 0x0 Guard: 0x0 ProtMask: 0x0
2018-11-12T17:40:28.951Z cpu11:2097605)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 180, Parameter: 0x430ab12da450, Registered!
2018-11-12T17:40:40.467Z cpu1:2098164)iscsi_vmk: iscsivmk_ConnNetRegister:2170: socket 0x430c5c5ceda0 network resource pool netsched.pools.persist.iscsi associated
2018-11-12T17:40:40.467Z cpu1:2098164)iscsi_vmk: iscsivmk_ConnNetRegister:2198: socket 0x430c5c5ceda0 network tracker id 403658154 tracker.iSCSI.172.16.6.1 associated
2018-11-12T17:40:40.467Z cpu1:2098164)iscsi_vmk: iscsivmk_ConnNetRegister:2170: socket 0x430c5c5e7a40 network resource pool netsched.pools.persist.iscsi associated
2018-11-12T17:40:40.467Z cpu1:2098164)iscsi_vmk: iscsivmk_ConnNetRegister:2198: socket 0x430c5c5e7a40 network tracker id 403658154 tracker.iSCSI.172.16.4.1 associated
2018-11-12T17:40:40.467Z cpu1:2098164)iscsi_vmk: iscsivmk_ConnNetRegister:2170: socket 0x430c5c5e0750 network resource pool netsched.pools.persist.iscsi associated
2018-11-12T17:40:40.467Z cpu1:2098164)iscsi_vmk: iscsivmk_ConnNetRegister:2198: socket 0x430c5c5e0750 network tracker id 403658154 tracker.iSCSI.172.16.6.1 associated
2018-11-12T17:40:40.467Z cpu1:2098164)iscsi_vmk: iscsivmk_ConnNetRegister:2170: socket 0x430c5c5c8c30 network resource pool netsched.pools.persist.iscsi associated
2018-11-12T17:40:40.467Z cpu1:2098164)iscsi_vmk: iscsivmk_ConnNetRegister:2198: socket 0x430c5c5c8c30 network tracker id 403658154 tracker.iSCSI.172.16.4.1 associated
2018-11-12T17:40:40.721Z cpu1:2098164)WARNING: iscsi_vmk: iscsivmk_StartConnection:880: vmhba64:CH:0 T:1 CN:0: iSCSI connection is being marked "ONLINE"
2018-11-12T17:40:40.721Z cpu1:2098164)WARNING: iscsi_vmk: iscsivmk_StartConnection:881: Sess [ISID: 00023d000001 TARGET: iqn.2017-10.nerds.bytes:znas201:vmdata1 TPGT: 1 TSIH: 0]
2018-11-12T17:40:40.721Z cpu1:2098164)WARNING: iscsi_vmk: iscsivmk_StartConnection:882: Conn [CID: 0 L: 172.16.6.10:51500 R: 172.16.6.1:3260]
2018-11-12T17:40:40.723Z cpu1:2098164)WARNING: iscsi_vmk: iscsivmk_StartConnection:880: vmhba64:CH:1 T:1 CN:0: iSCSI connection is being marked "ONLINE"
2018-11-12T17:40:40.723Z cpu1:2098164)WARNING: iscsi_vmk: iscsivmk_StartConnection:881: Sess [ISID: 00023d000002 TARGET: iqn.2017-10.nerds.bytes:znas201:vmdata1 TPGT: 1 TSIH: 0]
2018-11-12T17:40:40.723Z cpu1:2098164)WARNING: iscsi_vmk: iscsivmk_StartConnection:882: Conn [CID: 0 L: 172.16.4.10:11419 R: 172.16.4.1:3260]
2018-11-12T17:40:40.725Z cpu1:2098164)WARNING: iscsi_vmk: iscsivmk_StartConnection:880: vmhba64:CH:0 T:2 CN:0: iSCSI connection is being marked "ONLINE"
2018-11-12T17:40:40.725Z cpu1:2098164)WARNING: iscsi_vmk: iscsivmk_StartConnection:881: Sess [ISID: 00023d000001 TARGET: iqn.2017-10.nerds.bytes:znas201:vmdata2 TPGT: 1 TSIH: 0]
2018-11-12T17:40:40.725Z cpu1:2098164)WARNING: iscsi_vmk: iscsivmk_StartConnection:882: Conn [CID: 0 L: 172.16.6.10:62295 R: 172.16.6.1:3260]
2018-11-12T17:40:40.726Z cpu1:2098164)WARNING: iscsi_vmk: iscsivmk_StartConnection:880: vmhba64:CH:1 T:2 CN:0: iSCSI connection is being marked "ONLINE"
2018-11-12T17:40:40.726Z cpu1:2098164)WARNING: iscsi_vmk: iscsivmk_StartConnection:881: Sess [ISID: 00023d000002 TARGET: iqn.2017-10.nerds.bytes:znas201:vmdata2 TPGT: 1 TSIH: 0]
2018-11-12T17:40:40.726Z cpu1:2098164)WARNING: iscsi_vmk: iscsivmk_StartConnection:882: Conn [CID: 0 L: 172.16.4.10:19297 R: 172.16.4.1:3260]
2018-11-12T17:40:41.520Z cpu2:2099535 opID=249ebf9d)World: 11943: VC opID RescanStorageFormMediator-apply-10981-ngc:70000362-8b-ee-4b0c maps to vmkernel opID 249ebf9d
2018-11-12T17:40:41.520Z cpu2:2099535 opID=249ebf9d)StorageApdHandler: 977: APD Handle  Created with lock[StorageApd-0x43049b3dafc0]
2018-11-12T17:40:41.520Z cpu2:2099535 opID=249ebf9d)ScsiEvents: 501: Event Subsystem: Device Events, Created!
2018-11-12T17:40:41.520Z cpu2:2099535 opID=249ebf9d)VMWARE SCSI Id: Id for vmhba64:C0:T1:L2
0x61 0x63 0x31 0x66 0x36 0x62 0x36 0x63 0x32 0x39 0x32 0x34 0x30 0x36 0x00 0x00 0x69 0x53 0x43 0x53 0x49 0x20
2018-11-12T17:40:41.520Z cpu2:2099535 opID=249ebf9d)VMWARE SCSI Id: Id for vmhba64:C1:T1:L2
0x61 0x63 0x31 0x66 0x36 0x62 0x36 0x63 0x32 0x39 0x32 0x34 0x30 0x36 0x00 0x00 0x69 0x53 0x43 0x53 0x49 0x20
2018-11-12T17:40:41.521Z cpu2:2099535 opID=249ebf9d)ScsiDeviceIO: 8073: QErr is correctly set to 0x0 for device naa.6589cfc000000b84480742fe5a3fc2c7.
2018-11-12T17:40:41.521Z cpu36:2098147)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x15 (0x459a4e60b140, 0) to dev "naa.6589cfc000000b84480742fe5a3fc2c7" on path "vmhba64:C0:T1:L2" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x1a 0x0. Act:NONE
2018-11-12T17:40:41.521Z cpu36:2098147)ScsiDeviceIO: 3082: Cmd(0x459a4e60b140) 0x15, CmdSN 0x2737 from world 0 to dev "naa.6589cfc000000b84480742fe5a3fc2c7" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x1a 0x0.
2018-11-12T17:40:41.521Z cpu2:2099535 opID=249ebf9d)WARNING: ScsiDeviceIO: 8460: SITPUA set to 0 for device naa.6589cfc000000b84480742fe5a3fc2c7. This may cause log spam. The system was unable to change this setting to 1. Failure
2018-11-12T17:40:41.521Z cpu2:2099535 opID=249ebf9d)ScsiDevice: 3664: Failing registration of device 'naa.6589cfc000000b84480742fe5a3fc2c7':  Unsupported device attributes isLocal:0, isSSD:1, isNmpPlugin:1
2018-11-12T17:40:41.521Z cpu2:2099535 opID=249ebf9d)ScsiDevice: 5477: Failed to Unregister 'REPORTED LUNS DATA CHANGED' unit attention for device:naa.6589cfc000000b84480742fe5a3fc2c7. Reason: Not found
2018-11-12T17:40:41.521Z cpu2:2099535 opID=249ebf9d)ScsiDevice: 5487: Failed to Unregister 'MODE PARAMETERS CHANGED' unit attention for device:naa.6589cfc000000b84480742fe5a3fc2c7. Reason: Not found
2018-11-12T17:40:41.521Z cpu2:2099535 opID=249ebf9d)ScsiDevice: 5497: Failed to Unregister 'CAPACITY DATA HAS CHANGED' unit attention for device:naa.6589cfc000000b84480742fe5a3fc2c7. Reason: Not found
2018-11-12T17:40:41.522Z cpu2:2099535 opID=249ebf9d)ScsiDevice: 5507: Failed to Unregister 'ASYMMETRIC ACCESS STATE CHANGED' unit attention for device:naa.6589cfc000000b84480742fe5a3fc2c7. Reason: Not found
2018-11-12T17:40:41.522Z cpu2:2099535 opID=249ebf9d)ScsiDevice: 5517: Failed to Unregister 'INQUIRY PARAMETERS CHANGED' unit attention for device:naa.6589cfc000000b84480742fe5a3fc2c7. Reason: Not found
2018-11-12T17:40:41.522Z cpu2:2099535 opID=249ebf9d)ScsiDevice: 5583: Unregistered device 'naa.6589cfc000000b84480742fe5a3fc2c7' [0x43049b3dc640]
2018-11-12T17:40:41.522Z cpu2:2099535 opID=249ebf9d)ScsiEvents: 545: Event Subsystem: Device Events, Destroyed!
2018-11-12T17:40:41.522Z cpu2:2099535 opID=249ebf9d)WARNING: NMP: nmp_RegisterDevice:852: Registration of NMP device with primary uid 'naa.6589cfc000000b84480742fe5a3fc2c7' failed. Not supported
2018-11-12T17:40:41.522Z cpu2:2099535 opID=249ebf9d)StorageApdHandler: 1063: Freeing APD handle 0x43049b3dafc0 []
2018-11-12T17:40:41.522Z cpu2:2099535 opID=249ebf9d)StorageApdHandler: 1147: APD Handle freed!
2018-11-12T17:40:41.524Z cpu16:2099535 opID=249ebf9d)StorageApdHandler: 977: APD Handle  Created with lock[StorageApd-0x43049b3dafc0]
2018-11-12T17:40:41.524Z cpu16:2099535 opID=249ebf9d)ScsiEvents: 501: Event Subsystem: Device Events, Created!
2018-11-12T17:40:41.525Z cpu16:2099535 opID=249ebf9d)VMWARE SCSI Id: Id for vmhba64:C0:T2:L2
0x61 0x63 0x31 0x66 0x36 0x62 0x36 0x63 0x32 0x39 0x32 0x34 0x30 0x37 0x00 0x00 0x69 0x53 0x43 0x53 0x49 0x20
2018-11-12T17:40:41.525Z cpu16:2099535 opID=249ebf9d)VMWARE SCSI Id: Id for vmhba64:C1:T2:L2
0x61 0x63 0x31 0x66 0x36 0x62 0x36 0x63 0x32 0x39 0x32 0x34 0x30 0x37 0x00 0x00 0x69 0x53 0x43 0x53 0x49 0x20
2018-11-12T17:40:41.525Z cpu16:2099535 opID=249ebf9d)ScsiDeviceIO: 8073: QErr is correctly set to 0x0 for device naa.6589cfc00000096fb69249ad26fa5e8e.
2018-11-12T17:40:41.526Z cpu36:2098147)NMP: nmp_ThrottleLogForDevice:3781: Cmd 0x15 (0x459a4e60b140, 0) to dev "naa.6589cfc00000096fb69249ad26fa5e8e" on path "vmhba64:C0:T2:L2" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x1a 0x0. Act:NONE
2018-11-12T17:40:41.526Z cpu36:2098147)ScsiDeviceIO: 3082: Cmd(0x459a4e60b140) 0x15, CmdSN 0x273d from world 0 to dev "naa.6589cfc00000096fb69249ad26fa5e8e" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x1a 0x0.
2018-11-12T17:40:41.526Z cpu16:2099535 opID=249ebf9d)WARNING: ScsiDeviceIO: 8460: SITPUA set to 0 for device naa.6589cfc00000096fb69249ad26fa5e8e. This may cause log spam. The system was unable to change this setting to 1. Failure
2018-11-12T17:40:41.526Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 3664: Failing registration of device 'naa.6589cfc00000096fb69249ad26fa5e8e':  Unsupported device attributes isLocal:0, isSSD:1, isNmpPlugin:1
2018-11-12T17:40:41.526Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5477: Failed to Unregister 'REPORTED LUNS DATA CHANGED' unit attention for device:naa.6589cfc00000096fb69249ad26fa5e8e. Reason: Not found
2018-11-12T17:40:41.526Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5487: Failed to Unregister 'MODE PARAMETERS CHANGED' unit attention for device:naa.6589cfc00000096fb69249ad26fa5e8e. Reason: Not found
2018-11-12T17:40:41.526Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5497: Failed to Unregister 'CAPACITY DATA HAS CHANGED' unit attention for device:naa.6589cfc00000096fb69249ad26fa5e8e. Reason: Not found
2018-11-12T17:40:41.526Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5507: Failed to Unregister 'ASYMMETRIC ACCESS STATE CHANGED' unit attention for device:naa.6589cfc00000096fb69249ad26fa5e8e. Reason: Not found
2018-11-12T17:40:41.526Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5517: Failed to Unregister 'INQUIRY PARAMETERS CHANGED' unit attention for device:naa.6589cfc00000096fb69249ad26fa5e8e. Reason: Not found
2018-11-12T17:40:41.526Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5583: Unregistered device 'naa.6589cfc00000096fb69249ad26fa5e8e' [0x43049b3dc640]
2018-11-12T17:40:41.526Z cpu16:2099535 opID=249ebf9d)ScsiEvents: 545: Event Subsystem: Device Events, Destroyed!
2018-11-12T17:40:41.526Z cpu16:2099535 opID=249ebf9d)WARNING: NMP: nmp_RegisterDevice:852: Registration of NMP device with primary uid 'naa.6589cfc00000096fb69249ad26fa5e8e' failed. Not supported
2018-11-12T17:40:41.526Z cpu16:2099535 opID=249ebf9d)StorageApdHandler: 1063: Freeing APD handle 0x43049b3dafc0 []
2018-11-12T17:40:41.526Z cpu16:2099535 opID=249ebf9d)StorageApdHandler: 1147: APD Handle freed!
2018-11-12T17:40:41.660Z cpu16:2099535 opID=249ebf9d)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T17:40:41.660Z cpu16:2099535 opID=249ebf9d)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T1:L2" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T17:40:41.661Z cpu16:2099535 opID=249ebf9d)StorageApdHandler: 977: APD Handle  Created with lock[StorageApd-0x43049b3dafc0]
2018-11-12T17:40:41.661Z cpu16:2099535 opID=249ebf9d)ScsiEvents: 501: Event Subsystem: Device Events, Created!
2018-11-12T17:40:41.661Z cpu16:2099535 opID=249ebf9d)VMWARE SCSI Id: Id for vmhba64:C0:T1:L2
0x61 0x63 0x31 0x66 0x36 0x62 0x36 0x63 0x32 0x39 0x32 0x34 0x30 0x36 0x00 0x00 0x69 0x53 0x43 0x53 0x49 0x20
2018-11-12T17:40:41.662Z cpu16:2099535 opID=249ebf9d)VMWARE SCSI Id: Id for vmhba64:C1:T1:L2
0x61 0x63 0x31 0x66 0x36 0x62 0x36 0x63 0x32 0x39 0x32 0x34 0x30 0x36 0x00 0x00 0x69 0x53 0x43 0x53 0x49 0x20
2018-11-12T17:40:41.662Z cpu16:2099535 opID=249ebf9d)ScsiDeviceIO: 8073: QErr is correctly set to 0x0 for device naa.6589cfc000000b84480742fe5a3fc2c7.
2018-11-12T17:40:41.663Z cpu2:2098149)ScsiDeviceIO: 3082: Cmd(0x459a4e60b140) 0x15, CmdSN 0x2743 from world 0 to dev "naa.6589cfc000000b84480742fe5a3fc2c7" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x1a 0x0.
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)WARNING: ScsiDeviceIO: 8460: SITPUA set to 0 for device naa.6589cfc000000b84480742fe5a3fc2c7. This may cause log spam. The system was unable to change this setting to 1. Failure
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 3664: Failing registration of device 'naa.6589cfc000000b84480742fe5a3fc2c7':  Unsupported device attributes isLocal:0, isSSD:1, isNmpPlugin:1
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5477: Failed to Unregister 'REPORTED LUNS DATA CHANGED' unit attention for device:naa.6589cfc000000b84480742fe5a3fc2c7. Reason: Not found
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5487: Failed to Unregister 'MODE PARAMETERS CHANGED' unit attention for device:naa.6589cfc000000b84480742fe5a3fc2c7. Reason: Not found
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5497: Failed to Unregister 'CAPACITY DATA HAS CHANGED' unit attention for device:naa.6589cfc000000b84480742fe5a3fc2c7. Reason: Not found
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5507: Failed to Unregister 'ASYMMETRIC ACCESS STATE CHANGED' unit attention for device:naa.6589cfc000000b84480742fe5a3fc2c7. Reason: Not found
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5517: Failed to Unregister 'INQUIRY PARAMETERS CHANGED' unit attention for device:naa.6589cfc000000b84480742fe5a3fc2c7. Reason: Not found
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5583: Unregistered device 'naa.6589cfc000000b84480742fe5a3fc2c7' [0x43049b3dc640]
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)ScsiEvents: 545: Event Subsystem: Device Events, Destroyed!
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)WARNING: NMP: nmp_RegisterDevice:852: Registration of NMP device with primary uid 'naa.6589cfc000000b84480742fe5a3fc2c7' failed. Not supported
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)StorageApdHandler: 1063: Freeing APD handle 0x43049b3dafc0 []
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)StorageApdHandler: 1147: APD Handle freed!
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T17:40:41.663Z cpu16:2099535 opID=249ebf9d)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T2:L2" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T17:40:41.664Z cpu16:2099535 opID=249ebf9d)StorageApdHandler: 977: APD Handle  Created with lock[StorageApd-0x43049b3dafc0]
2018-11-12T17:40:41.664Z cpu16:2099535 opID=249ebf9d)ScsiEvents: 501: Event Subsystem: Device Events, Created!
2018-11-12T17:40:41.664Z cpu16:2099535 opID=249ebf9d)VMWARE SCSI Id: Id for vmhba64:C0:T2:L2
0x61 0x63 0x31 0x66 0x36 0x62 0x36 0x63 0x32 0x39 0x32 0x34 0x30 0x37 0x00 0x00 0x69 0x53 0x43 0x53 0x49 0x20
2018-11-12T17:40:41.664Z cpu16:2099535 opID=249ebf9d)VMWARE SCSI Id: Id for vmhba64:C1:T2:L2
0x61 0x63 0x31 0x66 0x36 0x62 0x36 0x63 0x32 0x39 0x32 0x34 0x30 0x37 0x00 0x00 0x69 0x53 0x43 0x53 0x49 0x20
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)ScsiDeviceIO: 8073: QErr is correctly set to 0x0 for device naa.6589cfc00000096fb69249ad26fa5e8e.
2018-11-12T17:40:41.665Z cpu2:2098149)ScsiDeviceIO: 3082: Cmd(0x459a4e60b140) 0x15, CmdSN 0x2749 from world 0 to dev "naa.6589cfc00000096fb69249ad26fa5e8e" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x1a 0x0.
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)WARNING: ScsiDeviceIO: 8460: SITPUA set to 0 for device naa.6589cfc00000096fb69249ad26fa5e8e. This may cause log spam. The system was unable to change this setting to 1. Failure
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 3664: Failing registration of device 'naa.6589cfc00000096fb69249ad26fa5e8e':  Unsupported device attributes isLocal:0, isSSD:1, isNmpPlugin:1
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5477: Failed to Unregister 'REPORTED LUNS DATA CHANGED' unit attention for device:naa.6589cfc00000096fb69249ad26fa5e8e. Reason: Not found
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5487: Failed to Unregister 'MODE PARAMETERS CHANGED' unit attention for device:naa.6589cfc00000096fb69249ad26fa5e8e. Reason: Not found
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5497: Failed to Unregister 'CAPACITY DATA HAS CHANGED' unit attention for device:naa.6589cfc00000096fb69249ad26fa5e8e. Reason: Not found
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5507: Failed to Unregister 'ASYMMETRIC ACCESS STATE CHANGED' unit attention for device:naa.6589cfc00000096fb69249ad26fa5e8e. Reason: Not found
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5517: Failed to Unregister 'INQUIRY PARAMETERS CHANGED' unit attention for device:naa.6589cfc00000096fb69249ad26fa5e8e. Reason: Not found
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)ScsiDevice: 5583: Unregistered device 'naa.6589cfc00000096fb69249ad26fa5e8e' [0x43049b3dc640]
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)ScsiEvents: 545: Event Subsystem: Device Events, Destroyed!
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)WARNING: NMP: nmp_RegisterDevice:852: Registration of NMP device with primary uid 'naa.6589cfc00000096fb69249ad26fa5e8e' failed. Not supported
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)StorageApdHandler: 1063: Freeing APD handle 0x43049b3dafc0 []
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)StorageApdHandler: 1147: APD Handle freed!
2018-11-12T17:40:41.665Z cpu16:2099535 opID=249ebf9d)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T17:40:41.666Z cpu16:2099535 opID=249ebf9d)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T1:L2" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T17:40:41.666Z cpu16:2099535 opID=249ebf9d)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T17:40:41.666Z cpu16:2099535 opID=249ebf9d)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C1:T1:L2" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T17:40:41.666Z cpu16:2099535 opID=249ebf9d)WARNING: NMP: nmpPathClaimEnd:1206: Device, seen through path vmhba64:C1:T1:L2 is not registered (no active paths)
2018-11-12T17:40:41.666Z cpu16:2099535 opID=249ebf9d)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T17:40:41.666Z cpu16:2099535 opID=249ebf9d)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C0:T2:L2" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T17:40:41.666Z cpu16:2099535 opID=249ebf9d)WARNING: VMW_SATP_ALUA: satp_alua_determineStatus:572: VMW_SATP_ALUA:Unknown Check condition 0/2 0x5 0x20 0x0.
2018-11-12T17:40:41.666Z cpu16:2099535 opID=249ebf9d)WARNING: VMW_SATP_ALUA: satp_alua_issueCommandOnPath:786: Probe cmd 0xa3 failed for path "vmhba64:C1:T2:L2" (0x5/0x20/0x0). Check if failover mode is still ALUA.
2018-11-12T17:40:41.666Z cpu16:2099535 opID=249ebf9d)WARNING: NMP: nmpPathClaimEnd:1206: Device, seen through path vmhba64:C1:T2:L2 is not registered (no active paths)
2018-11-12T17:40:42.548Z cpu25:2112339)WARNING: NFS: 1227: Invalid volume UUID naa.6589cfc000000ed8f4c4ed6e16600ce9:2
2018-11-12T17:40:42.554Z cpu25:2112339)FSS: 6092: No FS driver claimed device 'naa.6589cfc000000ed8f4c4ed6e16600ce9:2': No filesystem on the device
2018-11-12T17:40:43.556Z cpu16:2097227)ScsiDeviceIO: 3068: Cmd(0x45a24d0dd100) 0x1a, CmdSN 0x2819 from world 0 to dev "t10.SanDisk_Cruzer_Fit______4C532000020629114362" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.
2018-11-12T17:40:43.952Z cpu25:2099453 opID=61c3a554)World: 11943: VC opID RescanStorageFormMediator-apply-10984-ngc:70000362-fe-6c-4b1d maps to vmkernel opID 61c3a554
2018-11-12T17:40:43.952Z cpu25:2099453 opID=61c3a554)VC: 4616: Device rescan time 458 msec (total number of devices 6)
2018-11-12T17:40:43.952Z cpu25:2099453 opID=61c3a554)VC: 4619: Filesystem probe time 1413 msec (devices probed 5 of 6)
2018-11-12T17:40:43.952Z cpu25:2099453 opID=61c3a554)VC: 4621: Refresh open volume time 0 msec
2018-11-12T17:41:28.934Z cpu7:2098020)NMP: nmp_ResetDeviceLogThrottling:3575: last error status from device Unregistered Device repeated 1 times
2018-11-12T17:41:28.934Z cpu7:2098020)NMP: nmp_ResetDeviceLogThrottling:3575: last error status from device Unregistered Device repeated 1 times
 
kdragon75

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
bed said:
I tried adjusting LUNs to no avail. I tried multiple combinations including moving the windows target to 3 and and splitting the vm targets on LUN 1 and 2 and vice versa. LUN 0 is not allowed via the GUI.

I removed one of the vm targets for testing and now not able to create any additional targets regardless of name used. A reboot did not help. messages says
Code:
Nov 12 10:20:06 znas ctld[2359]: no LUNs defined for target "iqn.2017-10.nerds.bytes:znas201:vmdata2"
Nov 12 10:20:08 znas ctld[2359]: no LUNs defined for target "iqn.2017-10.nerds.bytes:znas201:vmdata2"

Should I wipe my iscsi config and redo it?

Edit:
Looks like you get that error if you have no LUN 1. Changed one of them back to LUN 1 and I can create targets again.
Click to expand...
File a bug report on this one. The UI needs better validation.
 
B

bed

Dabbler
Joined
Jun 17, 2011
Messages
38
An update.
I destroyed the pools and recreated them using different names and the targets work now. I had recreated the pools several times but always used the same names. Maybe it didn't like having a pool and zvol using the same (nested) names?
I'll still probably have to add an SSD for a log or cache device on each pool but so far it seems to be working ok.
 
kdragon75

kdragon75

Wizard
Joined
Aug 7, 2016
Messages
2,457
I'm glad you got it working. I still wish we know what was up with it.
 
HoneyBadger

HoneyBadger

actually does care
Administrator
Moderator
iXsystems
Joined
Feb 6, 2014
Messages
5,112
bed said:
I'll still probably have to add an SSD for a log or cache device on each pool but so far it seems to be working ok.
Click to expand...

Those are different purposes (log vs cache) - also, can I ask why didn't you make one larger pool with 12 drives in mirrors and cut a larger zvol from that?
 
B

bed

Dabbler
Joined
Jun 17, 2011
Messages
38
HoneyBadger said:
Those are different purposes (log vs cache) - also, can I ask why didn't you make one larger pool with 12 drives in mirrors and cut a larger zvol from that?
Click to expand...

Its been my understanding that a pool with that many drives was not advisable. Could be old thinking or my own misconceptions. As far as log/cache drive, Its because I forget which one is more beneficial for vm environments. I want to say I am seeking a log device for my purposes and while I type this am noticing your sig, that will be my next stop. Thanks.
 
Status
Not open for further replies.

Important Announcement for the TrueNAS Community.

The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums.

Related topics on forums.truenas.com for thread: "ISCSI issue with vmware"

Similar threads

M
vSphere Hypervisor with iSCSI FreeNAS - Connectivity Issues
Replies
6
Views
4K
mune3b
M
J
VMware ESXi 7 + iSCSI MP + ALUA Errors
Replies
6
Views
4K
morganL
M
M
ISCSI Presenting issues to VMware 6.7
Replies
6
Views
5K
milne301
M
S
  • Locked
SOLVED Never managed to get "Network Places" to work with my build - help please to troubleshoot?
Replies
3
Views
4K
Stilez
S
Q
  • Locked
Space utilization on thin-provisioned device
Replies
7
Views
14K
joeschmuck
joeschmuck
Top