iSCSI volumes showing normal,degraded in VMware after update to 9.10.2-U2

[Evan Richardson]

I updated a few weeks ago to 9.10.2-U2, and without chnaging any settings, my two iscsi volumes in ESX went into a Normal, Degraded state:

I've tried to disable and re-enable iscsi, delete everything and start over, but whatever I do, I can't get the disks to show back up as datastores. One, the 80G, is a File Extent, the other is a ZVOL. Both were working previously. Anyone know why?

 

[SweetAndLow]

Hardware specs, FreeNAS logs? Any errors?

Sent from my Nexus 5X using Tapatalk

 

[Evan Richardson]

Hardware specs, FreeNAS logs? Any errors?

Sent from my Nexus 5X using Tapatalk

Freenas:
Supermicro 2U server with E5-1230v5 processor
X11SSL-F board
32GB ram
Intel X520-DA2 NIC
freenas 9.10.2-U2



ESXi:
Supermicro A1SAi-2750f board (octa-core atom)
32GB RAM
Intel X520-DA1 10G nic
ESXi 6.5.0

there are no logs, short of messages

Code:

May  4 20:42:15 vega notifier: Stopping ctld.
May  4 20:42:15 vega notifier: Waiting for PIDS: 42474.
May  4 20:42:20 vega notifier: Starting ctld.
May  4 20:42:42 vega notifier: ctld already running?  (pid=62346).
May  4 20:42:45 vega ctld[62346]: exiting on signal
May  4 20:42:45 vega notifier: Stopping ctld.
May  4 20:42:45 vega notifier: Waiting for PIDS: 62346.
May  4 20:42:49 vega notifier: Starting ctld.

when i start/stop iscsi service. When I enter the host/port in dynamic targets section of ESXi, it automatically finds the two shares.., finds the static target name, and finds my disks., size and everything. ESX logs only show the following (vobd):

Code:

2017-05-05T03:49:46.635Z: [scsiCorrelator] 348669737471us: [vob.scsi.scsipath.add] Add path: vmhba64:C0:T0:L0
2017-05-05T03:49:46.635Z: [scsiCorrelator] 348669738343us: [vob.scsi.scsipath.add] Add path: vmhba64:C0:T0:L1
2017-05-05T03:49:46.689Z: [scsiCorrelator] 348669800307us: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba64:C0:T0:L1 changed state from dead
2017-05-05T03:49:46.700Z: [scsiCorrelator] 348669811564us: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba64:C0:T0:L0 changed state from dead

when I readd the dynamic target. As a test, I added a brand new extent, maped it, and rescanned in ESX...no change:

Code:

2017-05-05T03:52:32.906Z: [scsiCorrelator] 348836015839us: [vob.scsi.scsipath.add] Add path: vmhba64:C0:T0:L2
2017-05-05T03:52:32.908Z: [scsiCorrelator] 348836020093us: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba64:C0:T0:L2 changed state from dead

 

[mav@]

According to: https://communities.vmware.com/thread/431627:
--> If there is only one path to the target then the status is "degraded".

 

[Evan Richardson]

According to: https://communities.vmware.com/thread/431627:
--> If there is only one path to the target then the status is "degraded".

Thanks. This link ended up fixing it:
https://kb.vmware.com/selfservice/m...nguage=en_US&cmd=displayKC&externalId=2129058


specifically,

Code:

esxcfg-advcfg -s 0 /LVM/DisallowSnapshotLun

This returns output similar to:

Value of DisallowSnapshotLun is 0

After this is done, issue a storage controller rescan followed by a filesystem refresh:

esxcli storage core adapter rescan --all
vmkfstools -V

 

[CZ Eddie]

Thank you, Evan. My iSCSI devices were detected but I couldn't add them as a datastore, they just wouldn't show up. I typed exactly your commands listed above and without even needing a reboot, my datastores showed up again.