ESXi 5.0 iscsi issue

[nakuru]

When I migrate ESXi 4.1 to ESXi 5.0

booting is pending on "iscsi_vmk " for a long time

and loging to ESXi5  the iscsi Target is gone ,

on Storage adapters => iscsi initiator properties

the iscsi Target can found on Static Disccovery

but can't connect , use add storage wizard it can't found any iscsi disk

use clear install ESXi5 this problem still exit

[Dave_Mishchenko]

Welcome to the VMware Communities forums.

What sort of hardware are you using?  When you run a storage rescan, have you check the  host's log file.  If you have support mode enabled you can look at /var/log/vmkernel.log.  In the client,  go to the Home view, select System Logs and then select the vmkernel log file.

[nakuru]

I am use FreeNAS 0.7.2 Sabanda (revision 6694)

for iSCSI Target

it work on ESXi 4.0 , 4.1  ,( I am reinstall ESXi 4  to retest , it work)

following is the vmkernel.log when I rescan all

/var/log # tail -f vmkernel.log

2011-08-25T23:34:26.629Z cpu2:2913)Vol3: 647: Couldn't read volume header from control: Invalid handle

2011-08-25T23:34:26.629Z cpu2:2913)FSS: 4333: No FS driver claimed device 'control': Not supported

2011-08-25T23:34:26.786Z cpu4:2913)FSS: 4333: No FS driver claimed device 'mpx.vmhba32:C0:T0:L0': Not supported

2011-08-25T23:34:26.803Z cpu7:2913)VC: 1449: Device rescan time 110 msec (total number of devices 😎

2011-08-25T23:34:26.803Z cpu7:2913)VC: 1452: Filesystem probe time 167 msec (devices probed 6 of 😎

2011-08-25T23:34:27.276Z cpu1:2916)FSS: 4333: No FS driver claimed device 'mpx.vmhba32:C0:T0:L0': Not supported

2011-08-25T23:34:27.306Z cpu7:2916)Vol3: 647: Couldn't read volume header from control: Invalid handle

2011-08-25T23:34:27.306Z cpu7:2916)FSS: 4333: No FS driver claimed device 'control': Not supported

2011-08-25T23:34:27.319Z cpu7:2916)VC: 1449: Device rescan time 88 msec (total number of devices 😎

2011-08-25T23:34:27.319Z cpu7:2916)VC: 1452: Filesystem probe time 226 msec (devices probed 6 of 😎

2011-08-25T23:34:45.094Z cpu7:2913)FSS: 4333: No FS driver claimed device 'mpx.vmhba32:C0:T0:L0': Not supported

2011-08-25T23:34:45.114Z cpu6:2913)Vol3: 647: Couldn't read volume header from control: Invalid handle

2011-08-25T23:34:45.114Z cpu6:2913)FSS: 4333: No FS driver claimed device 'control': Not supported

2011-08-25T23:34:45.190Z cpu6:2913)VC: 1449: Device rescan time 129 msec (total number of devices 😎

2011-08-25T23:34:45.190Z cpu6:2913)VC: 1452: Filesystem probe time 219 msec (devices probed 6 of 😎

2011-08-25T23:34:45.210Z cpu4:2913)ScsiScan: 1098: Path 'vmhba2:C0:T4:L0': Vendor: 'ATA     '  Model: 'ST3500320AS     '  Rev: 'SD1A'

2011-08-25T23:34:45.210Z cpu4:2913)ScsiScan: 1101: Path 'vmhba2:C0:T4:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)

2011-08-25T23:34:45.214Z cpu4:2913)megasas_slave_configure: do not export physical disk devices to upper layer.

2011-08-25T23:34:45.214Z cpu4:2913)WARNING: ScsiScan: 1485: Failed to add path vmhba2:C0:T4:L0 : Not found

2011-08-25T23:34:45.216Z cpu4:2913)ScsiScan: 1098: Path 'vmhba2:C0:T5:L0': Vendor: 'ATA     '  Model: 'ST3500320AS     '  Rev: 'SD1A'

2011-08-25T23:34:45.216Z cpu4:2913)ScsiScan: 1101: Path 'vmhba2:C0:T5:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)

2011-08-25T23:34:45.220Z cpu4:2913)megasas_slave_configure: do not export physical disk devices to upper layer.

2011-08-25T23:34:45.220Z cpu4:2913)WARNING: ScsiScan: 1485: Failed to add path vmhba2:C0:T5:L0 : Not found

2011-08-25T23:34:45.221Z cpu4:2913)ScsiScan: 1098: Path 'vmhba2:C0:T6:L0': Vendor: 'ATA     '  Model: 'Hitachi HDP72505'  Rev: 'A52A'

2011-08-25T23:34:45.221Z cpu4:2913)ScsiScan: 1101: Path 'vmhba2:C0:T6:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)

2011-08-25T23:34:45.222Z cpu4:2913)megasas_slave_configure: do not export physical disk devices to upper layer.

2011-08-25T23:34:45.222Z cpu4:2913)WARNING: ScsiScan: 1485: Failed to add path vmhba2:C0:T6:L0 : Not found

2011-08-25T23:34:45.223Z cpu4:2913)ScsiScan: 1098: Path 'vmhba2:C0:T7:L0': Vendor: 'ATA     '  Model: 'ST3500418AS     '  Rev: 'CC38'

2011-08-25T23:34:45.223Z cpu4:2913)ScsiScan: 1101: Path 'vmhba2:C0:T7:L0': Type: 0x0, ANSI rev: 5, TPGS: 0 (none)

2011-08-25T23:34:45.226Z cpu4:2913)megasas_slave_configure: do not export physical disk devices to upper layer.

2011-08-25T23:34:45.226Z cpu4:2913)WARNING: ScsiScan: 1485: Failed to add path vmhba2:C0:T7:L0 : Not found

2011-08-25T23:34:45.484Z cpu5:2913)FSS: 4333: No FS driver claimed device 'mpx.vmhba32:C0:T0:L0': Not supported

2011-08-25T23:34:45.493Z cpu5:2913)Vol3: 647: Couldn't read volume header from control: Invalid handle

2011-08-25T23:34:45.493Z cpu5:2913)FSS: 4333: No FS driver claimed device 'control': Not supported

2011-08-25T23:34:45.501Z cpu5:2913)VC: 1449: Device rescan time 70 msec (total number of devices 😎

2011-08-25T23:34:45.501Z cpu5:2913)VC: 1452: Filesystem probe time 167 msec (devices probed 6 of 😎

2011-08-25T23:34:45.511Z cpu7:2667)usb-storage: detected SCSI revision number 0 on vmhba32

2011-08-25T23:34:45.511Z cpu7:2667)usb-storage: patching inquiry data to change SCSI revision number from 0 to 2 on vmhba32

2011-08-25T23:34:45.512Z cpu7:2172)ScsiUid: 273: Path 'vmhba32:C0:T0:L0' does not support VPD Device Id page.

2011-08-25T23:34:45.512Z cpu7:2172)VMWARE SCSI Id: Could not get disk id for vmhba32:C0:T0:L0

2011-08-25T23:34:45.585Z cpu2:2913)Vol3: 647: Couldn't read volume header from control: Invalid handle

2011-08-25T23:34:45.585Z cpu2:2913)FSS: 4333: No FS driver claimed device 'control': Not supported

2011-08-25T23:34:45.739Z cpu3:2913)FSS: 4333: No FS driver claimed device 'mpx.vmhba32:C0:T0:L0': Not supported

2011-08-25T23:34:45.750Z cpu3:2913)VC: 1449: Device rescan time 65 msec (total number of devices 😎

2011-08-25T23:34:45.750Z cpu3:2913)VC: 1452: Filesystem probe time 168 msec (devices probed 6 of 😎

2011-08-25T23:34:45.852Z cpu3:2913)Vol3: 647: Couldn't read volume header from control: Invalid handle

2011-08-25T23:34:45.852Z cpu3:2913)FSS: 4333: No FS driver claimed device 'control': Not supported

2011-08-25T23:34:46.004Z cpu1:2913)FSS: 4333: No FS driver claimed device 'mpx.vmhba32:C0:T0:L0': Not supported

2011-08-25T23:34:46.006Z cpu1:2913)VC: 1449: Device rescan time 65 msec (total number of devices 😎

2011-08-25T23:34:46.006Z cpu1:2913)VC: 1452: Filesystem probe time 167 msec (devices probed 6 of 😎

2011-08-25T23:34:46.064Z cpu5:2683)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410015d02520 network resource pool netsched.pools.persist.iscsi associated

2011-08-25T23:34:46.064Z cpu5:2683)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410015d02520 network tracker id 1 tracker.iSCSI.192.168.55.250 associated

2011-08-25T23:34:46.335Z cpu3:2683)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410015d40490 network resource pool netsched.pools.persist.iscsi associated

2011-08-25T23:34:46.335Z cpu3:2683)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410015d40490 network tracker id 1 tracker.iSCSI.192.168.55.250 associated

2011-08-25T23:34:46.336Z cpu3:2683)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410015e17590 network resource pool netsched.pools.persist.iscsi associated

2011-08-25T23:34:46.336Z cpu3:2683)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410015e17590 network tracker id 1 tracker.iSCSI.192.168.55.250 associated

2011-08-25T23:34:46.336Z cpu5:2683)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410015d3fa70 network resource pool netsched.pools.persist.iscsi associated

2011-08-25T23:34:46.336Z cpu5:2683)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410015d3fa70 network tracker id 1 tracker.iSCSI.192.168.55.250 associated

2011-08-25T23:34:46.337Z cpu5:2683)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410015e180f0 network resource pool netsched.pools.persist.iscsi associated

2011-08-25T23:34:46.337Z cpu5:2683)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410015e180f0 network tracker id 1 tracker.iSCSI.192.168.55.250 associated

2011-08-25T23:34:46.338Z cpu5:2683)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410015e188d0 network resource pool netsched.pools.persist.iscsi associated

2011-08-25T23:34:46.338Z cpu5:2683)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410015e188d0 network tracker id 1 tracker.iSCSI.192.168.55.250 associated

2011-08-25T23:34:47.103Z cpu5:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba35:CH:0 T:0 CN:0: iSCSI connection is being marked "OFFLINE" (Event:2)

2011-08-25T23:34:47.103Z cpu5:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID:  TARGET: (null) TPGT: 0 TSIH: 0]

2011-08-25T23:34:47.103Z cpu5:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.55.222:57442 R: 192.168.55.250:3260]

2011-08-25T23:34:48.137Z cpu5:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba35:CH:1 T:0 CN:0: iSCSI connection is being marked "OFFLINE" (Event:2)

2011-08-25T23:34:48.137Z cpu5:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID:  TARGET: (null) TPGT: 0 TSIH: 0]

2011-08-25T23:34:48.138Z cpu5:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.55.176:55187 R: 192.168.55.250:3260]

2011-08-25T23:34:49.175Z cpu0:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba35:CH:0 T:1 CN:0: iSCSI connection is being marked "OFFLINE" (Event:2)

2011-08-25T23:34:49.176Z cpu0:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID:  TARGET: (null) TPGT: 0 TSIH: 0]

2011-08-25T23:34:49.176Z cpu0:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.55.222:60372 R: 192.168.55.250:3260]

2011-08-25T23:34:50.217Z cpu2:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba35:CH:1 T:1 CN:0: iSCSI connection is being marked "OFFLINE" (Event:2)

2011-08-25T23:34:50.217Z cpu2:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID:  TARGET: (null) TPGT: 0 TSIH: 0]

2011-08-25T23:34:50.217Z cpu2:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.55.176:49511 R: 192.168.55.250:3260]

2011-08-25T23:34:51.258Z cpu6:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba35:CH:1 T:2 CN:0: iSCSI connection is being marked "OFFLINE" (Event:2)

2011-08-25T23:34:51.258Z cpu6:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID:  TARGET: (null) TPGT: 0 TSIH: 0]

2011-08-25T23:34:51.258Z cpu6:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.55.176:51652 R: 192.168.55.250:3260]

2011-08-25T23:34:51.762Z cpu5:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba35:CH:0 T:2 CN:0: iSCSI connection is being marked "OFFLINE" (Event:5)

2011-08-25T23:34:51.762Z cpu5:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID:  TARGET: (null) TPGT: 0 TSIH: 0]

2011-08-25T23:34:51.762Z cpu5:2683)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 192.168.55.222:60554 R: 192.168.55.250:3260]

2011-08-25T23:34:52.380Z cpu7:2913)FSS: 4333: No FS driver claimed device 'mpx.vmhba32:C0:T0:L0': Not supported

2011-08-25T23:34:52.387Z cpu6:2913)Vol3: 647: Couldn't read volume header from control: Invalid handle

2011-08-25T23:34:52.387Z cpu6:2913)FSS: 4333: No FS driver claimed device 'control': Not supported

2011-08-25T23:34:52.405Z cpu7:2913)VC: 1449: Device rescan time 91 msec (total number of devices 😎

2011-08-25T23:34:52.405Z cpu7:2913)VC: 1452: Filesystem probe time 169 msec (devices probed 6 of 😎

2011-08-25T23:34:52.856Z cpu4:3390)FSS: 4333: No FS driver claimed device 'mpx.vmhba32:C0:T0:L0': Not supported

2011-08-25T23:34:52.884Z cpu5:3390)Vol3: 647: Couldn't read volume header from control: Invalid handle

2011-08-25T23:34:52.884Z cpu5:3390)FSS: 4333: No FS driver claimed device 'control': Not supported

2011-08-25T23:34:52.929Z cpu2:3390)VC: 1449: Device rescan time 89 msec (total number of devices 😎

2011-08-25T23:34:52.929Z cpu2:3390)VC: 1452: Filesystem probe time 225 msec (devices probed 6 of 😎

[nakuru]

update

Use Windows Sotorage Server R2  create iscsi disk

it can work

It show can't use FreeNAS iscsi Target ( 0.7.2 or 0.8)

I will test openfiler

[pgoggins]

Bug with the FreeNAS implementation? I use to have issues with 0.7.2 & iSCSI but with 0.8.0 it worked ok for me under ESXi4.1 update 1.

[nakuru]

ESXi 4.0 , 4.1 use FreeNAS 0.7.2 and 0.8 is succssful

but use 5.0 it can't be use

[Dave_Mishchenko]

Have you tried a new LUN with ESXi 5.0 or just existing ESXi 4.0 datastores?

[nakuru]

both I have retry

1. exting ESXi4 datastore is not found ( on detail )

2. create new iscsi disk ( 0.7.2 , 0.8 ) still the same

3.Clear install ESXi5 and run step 1, 2  the same issue

4.use Windows storage 2008 R2 iSCSI target  is normal

5. old LUN on Local Disk it can auto import

this test let me think is ESXi5  already not support use FreeNAS as iSCSI server

or that is FreeNAS bug ?

[nakuru]

new update

if use openfiler 2.99 to create iscsi target , it can work

this iscsi issue may only cause in FreeNAS

[rnwnl]

Same issue here, works on ESX4 but doesn't work on ESX5 even though the targets are shown. Same error messages in vmkernel.log

[mars_cydonia]

Same thing happened to me on my home lab.

I had 2 iSCSI Targets: 1 on FreeNAS 8 and the other one on Microsoft iSCSI Target.

The target on Microsoft iSCSI was auto-imported without any kind of problems while I can't import the Target from FreeNAS because it's like is non-existant.

Because I'm using vSphere for my Home lab and not a production environement, I'll try a nightly build of FreeNAS to see if is a bug on FreeNAS 8.

[nakuru]

I have already try nightly version 8r7350 the issue also happen

[nakuru]

NexentaStor this NAS use  iscsi Target is successful

already test several NAS software  openfiler , windows storage server 2008 R2 , NexentaStor all can work normal

only FreeNAS on 0.7.2 ~ 0.8 ~ 0.8.1 (nightly) failed , it seem FreeNAS Bug

[pgoggins]

Brought up a FreeNAS-8-Release 64-bit VM this morning in the lab and after some testing.

Under 4.1 Update 1 - Dynamic Discovery detects the targets correctly and presents all extents. The extents mounted work as expected.

Under 5.0 - Dynamic Discovery discovers correctly discovers the target but fails to detect any extents(paths/devices) associated with the target.

[echtweg]

we've got exactly the same problem with our freenas 8 boxes and our QNAP-NAS, too.

[mattrobinson]

I've been watching the FreeNAS and VMware sides to this issue and finally there's an update in the FreeNAS TRAC system:

http://support.freenas.org/ticket/690

The issue now has an owner assigned along with the following comment:

This requires a new version of istgt to resolve, we will incorporate it into FreeNAS as soon as it is available.

Hopefully a solution is coming!

[manuel_vm]

I had the same problem. The problem was my iscsi configuration in ESXi server.

In the vSphere 5 storage guide, there is a note about iscsi network in ESX:

    If you use separate vSphere switches, you must connect them to different IP subnets. Otherwise,
     VMkernel adapters might experience connectivity problems and the host will fail to discover iSCSI LUNs.

     An alternative is to add all NICs and VMkernel adapters to a single vSphere standard switch. In this case, you
must override the default network setup and make sure that each VMkernel adapter maps to only one
corresponding active physical adapter.

So we need to ensure that we have a 1:1 mapping.

How have you configured iscsi network ?

[pgoggins]

Just a heads up 8.0.1-RC1 has been released today; there were some changes to the iSCSI. I'm not sure if the new release has helped/hurt the situation at all.

[rnwnl]

I did configure a seperate iSCSI network on a different subnet (172.16.x.x while VM's and management are on 10.x.x.x). This didn't work either.

[mattrobinson]

In my case this is a config in my home lab, so nothing fancy going on. Server is a HP ML-115 with a single NIC and vSphere 5 is configured with a single vSwitch on a completely flat network. I can see how mapping the correct NIC to the iSCSI configuraiton could cause problems but I don't think that's my issue.

From the TRAC ticket in the FreeNAS project, it sounds like a new version of istgt (the iSCSI component used in FreeNAS) is required for compatibility. No details are given however. I tried looking for details on istgt to see if a new build was coming but couldn't see any detail. On the bright side, it does look like istgt is actively and regularly maintained.

I'll give FreeNAS 8.0.1 RC1 a go, nothing to lose. Doubt if it'll help here if istgt really is the root cause though.