Migrated iSCSI device identified in ESXi but can't add datastore

Status
Not open for further replies.
S

SubX

Explorer
Joined
Sep 15, 2017
Messages
56
Background
- Detach a iSCSI LUN (vmfs 5 datastore) from FreeNAS 1
- Unplug the drive and insert into FreeNAS2
- import volume, create new iSCSI sharing (portal, target, extent, associate etc...)
- ESXi setup iSCSI connection to FreeNAS 2, rescan iSCSI, found device (vmfs partion etc...)

Issue
- datastore doesn't show up, in the past need to create datastore, device pops up, use a new signature then it will works. This time nothing shown up, couldn't continue.
- ssh to esxi host, find the device, found device naa.id shown in /vmfs/devices/disks
- however when show vmfs, not there.

Help
- how to remount the vmfs so that datastore will shown up again? via esxcli?

Code:
[root@esx1:~] esxcli storage core device list
naa.6589cfc00000089031a984064cf4b497
   Display Name: FreeNAS iSCSI Disk (naa.6589cfc00000089031a984064cf4b497)
   Has Settable Display Name: true
   Size: 3584000
   Device Type: Direct-Access
   Multipath Plugin: NMP
   Devfs Path: /vmfs/devices/disks/naa.6589cfc00000089031a984064cf4b497
   Vendor: FreeNAS
   Model: iSCSI Disk
   Revision: 0123
   SCSI Level: 6
   Is Pseudo: false
   Status: degraded
   Is RDM Capable: true
   Is Local: false
   Is Removable: false
   Is SSD: false
   Is VVOL PE: false
   Is Offline: false
   Is Perennially Reserved: false
   Queue Full Sample Size: 0
   Queue Full Threshold: 0
   Thin Provisioning Status: unknown
   Attached Filters:
   VAAI Status: supported
   Other UIDs: vml.010006000036633632366439383338653530300000695343534920
   Is Shared Clusterwide: true
   Is Local SAS Device: false
   Is SAS: false
   Is USB: false
   Is Boot USB Device: false
   Is Boot Device: false
   Device Max Queue Depth: 128
   No of outstanding IOs with competing worlds: 32
   Drive Type: unknown
   RAID Level: unknown
   Number of Physical Drives: unknown
   Protection Enabled: false
   PI Activated: false
   PI Type: 0
   PI Protection Mask: NO PROTECTION
   Supported Guard Types: NO GUARD SUPPORT
   DIX Enabled: false
   DIX Guard Type: NO GUARD SUPPORT
   Emulated DIX/DIF Enabled: false

t10.KINGSTONDataTraveler_3.01.01
   Display Name: Local USB Direct-Access (t10.KINGSTONDataTraveler_3.01.01)
   Has Settable Display Name: false
   Size: 7416
   Device Type: Direct-Access
   Multipath Plugin: NMP
   Devfs Path: /vmfs/devices/disks/t10.KINGSTONDataTraveler_3.01.01
   Vendor: Kingston
   Model: DataTraveler 3.0
   Revision: 0100
   SCSI Level: 2
   Is Pseudo: false
   Status: on
   Is RDM Capable: false
   Is Local: true
   Is Removable: true
   Is SSD: false
   Is VVOL PE: false
   Is Offline: false
   Is Perennially Reserved: false
   Queue Full Sample Size: 0
   Queue Full Threshold: 0
   Thin Provisioning Status: unknown
   Attached Filters:
   VAAI Status: unsupported
   Other UIDs: vml.0000000000766d68626133323a303a30
   Is Shared Clusterwide: false
   Is Local SAS Device: false
   Is SAS: false
   Is USB: true
   Is Boot USB Device: true
   Is Boot Device: true
   Device Max Queue Depth: 1
   No of outstanding IOs with competing worlds: 32
   Drive Type: unknown
   RAID Level: unknown
   Number of Physical Drives: unknown
   Protection Enabled: false
   PI Activated: false
   PI Type: 0
   PI Protection Mask: NO PROTECTION
   Supported Guard Types: NO GUARD SUPPORT
   DIX Enabled: false
   DIX Guard Type: NO GUARD SUPPORT
   Emulated DIX/DIF Enabled: false


Code:
[root@esx1:~] esxcli storage core device world list -d naa.6589cfc00000089031a984064cf4b497
[root@esx1:~] esxcfg-scsidevs –m | grep naa.id
[root@esx1:~] esxcfg-scsidevs --uids
Primary UID													 Other UID
naa.5000c500512f8e8c											vml.0100000000202020202020202020202020533146304d483446535433303030
naa.6589cfc00000089031a984064cf4b497							vml.010006000036633632366439383338653530300000695343534920
t10.KINGSTONDataTraveler_3.01.01								vml.0000000000766d68626133323a303a30


Code:
[root@esx1:~] esxcli storage core device world list
Device							World ID  Open Count  World Name
--------------------------------  --------  ----------  ------------
t10.KINGSTONDataTraveler_3.01.01	 66802		   1  hostd-worker
naa.5000c500512f8e8c				 65551		   1  idle0
naa.5000c500512f8e8c				 65694		   1  BCFlush-0
naa.5000c500512f8e8c				 65695		   1  BCFlush-1


Code:
[root@esx1:~] esxcli storage core path list
usb.vmhba32-usb.0:0-t10.KINGSTONDataTraveler_3.01.01
   UID: usb.vmhba32-usb.0:0-t10.KINGSTONDataTraveler_3.01.01
   Runtime Name: vmhba32:C0:T0:L0
   Device: t10.KINGSTONDataTraveler_3.01.01
   Device Display Name: Local USB Direct-Access (t10.KINGSTONDataTraveler_3.01.01)
   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

sata.vmhba0-sata.0:0-naa.5000c500512f8e8c
   UID: sata.vmhba0-sata.0:0-naa.5000c500512f8e8c
   Runtime Name: vmhba0:C0:T0:L0
   Device: naa.5000c500512f8e8c
   Device Display Name: Local ATA Disk (naa.5000c500512f8e8c)
   Adapter: vmhba0
   Channel: 0
   Target: 0
   LUN: 0
   Plugin: NMP
   State: active
   Transport: sata
   Adapter Identifier: sata.vmhba0
   Target Identifier: sata.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:59d17a51-39e4-bdc2-e30e-082e5f25a5d8-08448cde-00023d000001,iqn.2005-10.org.freenas.ctl:target-4t,t,257-naa.6589cfc00000089031a984064cf4b497
   UID: iqn.1998-01.com.vmware:59d17a51-39e4-bdc2-e30e-082e5f25a5d8-08448cde-00023d000001,iqn.2005-10.org.freenas.ctl:target-4t,t,257-naa.6589cfc00000089031a984064cf4b497
   Runtime Name: vmhba66:C0:T0:L6
   Device: naa.6589cfc00000089031a984064cf4b497
   Device Display Name: FreeNAS iSCSI Disk (naa.6589cfc00000089031a984064cf4b497)
   Adapter: vmhba66
   Channel: 0
   Target: 0
   LUN: 6
   Plugin: NMP
   State: active
   Transport: iscsi
   Adapter Identifier: iqn.1998-01.com.vmware:59d17a51-39e4-bdc2-e30e-082e5f25a5d8-08448cde
   Target Identifier: 00023d000001,iqn.2005-10.org.freenas.ctl:target-4t,t,257
   Adapter Transport Details: iqn.1998-01.com.vmware:59d17a51-39e4-bdc2-e30e-082e5f25a5d8-08448cde
   Target Transport Details: IQN=iqn.2005-10.org.freenas.ctl:target-4t Alias= Session=00023d000001 PortalTag=257
   Maximum IO Size: 131072


Code:
[root@esx1:~] esxcfg-scsidevs –-list --vmfs
naa.5000c500512f8e8c:1										   /vmfs/devices/disks/naa.5000c500512f8e8c:1 50300171-caf2dd3b-0d68-001d7dd1e541  0  Local-ESX1-3T
[root@esx1:~] cd /vmfs
[root@esx1:/vmfs] cd devices
[root@esx1:/dev] cd disks
[root@esx1:/dev/disks] ls
naa.5000c500512f8e8c												  vml.0000000000766d68626133323a303a30
naa.5000c500512f8e8c:1												vml.0000000000766d68626133323a303a30:1
naa.6589cfc00000089031a984064cf4b497								  vml.0000000000766d68626133323a303a30:5
naa.6589cfc00000089031a984064cf4b497:1								vml.0000000000766d68626133323a303a30:6
t10.KINGSTONDataTraveler_3.01.01									  vml.0000000000766d68626133323a303a30:7
t10.KINGSTONDataTraveler_3.01.01:1									vml.0000000000766d68626133323a303a30:8
t10.KINGSTONDataTraveler_3.01.01:5									vml.0000000000766d68626133323a303a30:9
t10.KINGSTONDataTraveler_3.01.01:6									vml.0100000000202020202020202020202020533146304d483446535433303030
t10.KINGSTONDataTraveler_3.01.01:7									vml.0100000000202020202020202020202020533146304d483446535433303030:1
t10.KINGSTONDataTraveler_3.01.01:8									vml.010006000036633632366439383338653530300000695343534920
t10.KINGSTONDataTraveler_3.01.01:9									vml.010006000036633632366439383338653530300000695343534920:1

Thanks,
 
bigphil

bigphil

Patron
Joined
Jan 30, 2014
Messages
486
So in the vSphere Web Client, under storage devices, you need to make sure the disk show operational state of "attached." After that you need to go to datastores and verify that the previous VMFS datastore you had is listing there and make sure its mounted.
 
S

SubX

Explorer
Joined
Sep 15, 2017
Messages
56
bigphil said:
So in the vSphere Web Client, under storage devices, you need to make sure the disk show operational state of "attached." After that you need to go to datastores and verify that the previous VMFS datastore you had is listing there and make sure its mounted.
Click to expand...

Capture-device.JPG
Capture-device-1500g.JPG
Capture-device-4t.JPG
Capture-datastore.JPG
Capture-datastore.JPG
thanks!

from below screenshoot, seems there is nothing difference between the newly created iSCSI Lun (1.42T) and the problematic iSCSI Lun (3.4T). Using esxi 6.5, a bit different from what you mentioned above.

3.4T should be seen by ESXi per screenshoot and ESXi SSH output, but it probably is not mounted. In the past I add new datastore , see the LUN and assign new signature, it then works. not this time. still no luck.
 
S

SubX

Explorer
Joined
Sep 15, 2017
Messages
56
Got it working, add datastore step has to be performed under vCenter server not via ESXi host. Mark it closed.
 
Status
Not open for further replies.

Similar threads

J
Cannot connect iSCSI zvol under FN 11.1-U7
Replies
2
Views
1K
James S
J
K
  • Locked
iSCSI Conneciton timed out during write
Replies
2
Views
4K
Ken Harvey
K
Patrick M. Hausen
ESXi and iSCSI I/O policy - how to make persistent?
Replies
2
Views
3K
Patrick M. Hausen
Patrick M. Hausen
T
FreeNAS 11.2u7 newly created iSCSI device not showing up in ESXi 6.7u3 - duplicate extent serial number
Replies
3
Views
2K
shpokas
shpokas
M
vSphere Hypervisor with iSCSI FreeNAS - Connectivity Issues
Replies
6
Views
3K
mune3b
M
Top