SXiao
Contributor
Contributor

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

Jump to solution

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?

Thanks,

Capture-device.JPGCapture-device-1500g.JPGCapture-device-4t.JPGCapture-datastore.JPG

0 Kudos
1 Solution

Accepted Solutions
SXiao
Contributor
Contributor

Got it working, add datastore step has to be performed under vCenter server not via ESXi host. Mark it closed.

View solution in original post

0 Kudos
3 Replies
vijayrana968
Virtuoso
Virtuoso

Can you make sure there are more than one path to this target, or what was earlier path configuration. Usually 'Degraded' status means there is only path to the target.

0 Kudos
SXiao
Contributor
Contributor

i only has single path for my lab. The other iSCSI LUN (1.42T) has the same setting and degraded LUN, but datastore show up fine.

Found this link using vmkfstools -L targetreset <TARGET_NAME> to unlock LUNs. Not sure if that will work in my case. Need some solid clue and there are vms which resides on this missing datastore.

VMware : iSCSI LUN datastore no longer visible after outage | ITechLounge.net

0 Kudos
SXiao
Contributor
Contributor

Got it working, add datastore step has to be performed under vCenter server not via ESXi host. Mark it closed.

View solution in original post

0 Kudos