VMware Cloud Community
kormen
Contributor
Contributor

ESXi 4.0 -> ESXi 4.1 datastore move

Hil

I have a problem. I install a new esxi server (4.1) and i try to mount my iscsi volume to it. That iscsi contains a vmfs file system with some virtual machine. The method to add:

1,    Shutting down original 4.0 esxi.
2,     booting new 4.1 esxi.
3,    configure iscsi (the iscsi adding success)
4,    rescan devices, volumes.
5,     the vmfs not in my datastores.

Any idea?

This is a fresh created iscsi storage with 4.0 move a few vm on it. all work. then i shut down 4.0 (not dismount not drop nothing, only shut down) and start 4.1 configure, rescan, nothing.

Information:
~ # fdisk -l
Disk /dev/disks/t10.9454450000000000461647163747F6275623023200000000: 1099.5 GB, 1099511627776 bytes
255 heads, 63 sectors/track, 133674 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
                                                           Device Boot      Start         End      Blocks  Id System
/dev/disks/t10.9454450000000000461647163747F6275623023200000000p1             1    133674 1073736341   fb  VMFS

~ # esxcfg-mpath -l
iqn.1998-01.com.vmware:localhost-0c8da9a0-00023d000001,iqn.2011-07.hu.abtwork:storage.usb.vmfs,t,1-t10.9454450000000000461647163747F6275623023200000000
   Runtime Name: vmhba33:C0:T0:L0
   Device: t10.9454450000000000461647163747F6275623023200000000
   Device Display Name: iscsi
   Adapter: vmhba33 Channel: 0 Target: 0 LUN: 0
   Adapter Identifier: iqn.1998-01.com.vmware:localhost-0c8da9a0
   Target Identifier: 00023d000001,iqn.2011-07.hu.abtwork:storage.usb.vmfs,t,1
   Plugin: NMP
   State: active
   Transport: iscsi
   Adapter Transport Details: iqn.1998-01.com.vmware:localhost-0c8da9a0
   Target Transport Details: IQN=iqn.2011-07.hu.abtwork:storage.usb.vmfs Alias= Session=00023d000001 PortalTag=1

~ # vmkiscsi-tool -T -l vmhba33

------ Target [iqn.2011-07.hu.abtwork:storage.usb.vmfs] info ------
NAME                              : iqn.2011-07.hu.abtwork:storage.usb.vmfs
ALIAS                             :
DISCOVERY METHOD FLAGS            : 8
SEND TARGETS DISCOVERY SETTABLE   : 0
SEND TARGETS DISCOVERY ENABLED    : 0
Portal 0                          : 192.168.242.21:3260

-------------------------------------------
Log about rescan:

Aug  4 06:12:50 Hostd: [2011-08-04 06:12:50.916 64352B90 info 'TaskManager' opID=315A332E-00000349] Task Created : haTask-ha-host-vim.host.StorageSystem.rescanAllHba-202
Aug  4 06:12:54 vmkernel: 0:03:34:49.740 cpu3:5416)ScsiScan: 1059: Path 'vmhba1:C0:T0:L0': Vendor: 'IBM-ESXS'  Model: 'ST936701LC    FN'  Rev: 'B415'
Aug  4 06:12:54 vmkernel: 0:03:34:49.740 cpu3:5416)ScsiScan: 1062: Path 'vmhba1:C0:T0:L0': Type: 0x0, ANSI rev: 4, TPGS: 0 (none)
Aug  4 06:12:54 vmkernel: 0:03:34:49.752 cpu3:5416)ScsiUid: 273: Path 'vmhba1:C0:T0:L0' does not support VPD Device Id page.
Aug  4 06:12:54 vmkernel: 0:03:34:49.757 cpu3:5416)VMWARE SCSI Id: Id for vmhba1:C0:T0:L0
Aug  4 06:12:54 vmkernel: 0x33 0x4c 0x43 0x30 0x31 0x53 0x41 0x38 0x30 0x30 0x30 0x30 0x37 0x35 0x31 0x38 0x4a 0x48 0x4e 0x5a 0x53 0x54 0x39 0x33 0x36 0x37
Aug  4 06:12:54 iscsid: discovery_sendtargets::Running discovery on IFACE default(iscsi_vmk) (drec.transport=iscsi_vmk)
Aug  4 06:12:54 iscsid: Login Target Skipped: iqn.2011-07.hu.abtwork:storage.usb.vmfs if=default addr=192.168.242.21:3260 (TPGT:1 ISID:0x1) (Already Running)
Aug  4 06:12:54 iscsid: DISCOVERY: Pending=0 Failed=0
Aug  4 06:12:54 vmkernel: 0:03:34:49.871 cpu1:5416)ScsiScan: 1059: Path 'vmhba33:C0:T0:L0': Vendor: 'IET     '  Model: 'VIRTUAL-DISK    '  Rev: '0   '
Aug  4 06:12:54 vmkernel: 0:03:34:49.871 cpu1:5416)ScsiScan: 1062: Path 'vmhba33:C0:T0:L0': Type: 0x0, ANSI rev: 4, TPGS: 0 (none)
Aug  4 06:12:54 Hostd: [2011-08-04 06:12:54.567 FFEC2B90 verbose 'StorageSystem' opID=315A332E-00000349] SendStorageInfoEvent() called
Aug  4 06:12:54 Hostd: [2011-08-04 06:12:54.568 FFEC2B90 verbose 'Hostsvc::DatastoreSystem' opID=315A332E-00000349] ReconcileVMFSDatastores called: refresh = true, rescan = false
Aug  4 06:12:54 Hostd: [2011-08-04 06:12:54.568 FFEC2B90 verbose 'FSVolumeProvider' opID=315A332E-00000349] RefreshVMFSVolumes called
Aug  4 06:12:54 Hostd: [2011-08-04 06:12:54.845 FFEC2B90 verbose 'FSVolumeProvider' opID=315A332E-00000349] RefreshVMFSVolumes: refreshed volume, id 4e3a0642-6b38c474-f89c-0011254a008f, name datastore1
Aug  4 06:12:54 Hostd: [2011-08-04 06:12:54.845 FFEC2B90 verbose 'Hostsvc::Datastore' opID=315A332E-00000349] SetVolume: Datastore 4e3a0642-6b38c474-f89c-0011254a008f has changed provider volume pointer
Aug  4 06:12:54 Hostd: [2011-08-04 06:12:54.845 FFEC2B90 verbose 'Hostsvc::DatastoreSystem' opID=315A332E-00000349] ReconcileVMFSDatastores: Done discovering new filesystem volumes.
Aug  4 06:12:54 Hostd: [2011-08-04 06:12:54.845 FFEC2B90 info 'TaskManager' opID=315A332E-00000349] Task Completed : haTask-ha-host-vim.host.StorageSystem.rescanAllHba-202 Status success
Aug  4 06:12:54 Hostd: [2011-08-04 06:12:54.851 645F6B90 info 'TaskManager' opID=315A332E-0000034B] Task Created : haTask-ha-host-vim.host.StorageSystem.rescanVmfs-203
Aug  4 06:12:54 Hostd: [2011-08-04 06:12:54.851 645F6B90 verbose 'Hostsvc::DatastoreSystem' opID=315A332E-0000034B] ReconcileVMFSDatastores called: refresh = true, rescan = true
Aug  4 06:12:54 Hostd: [2011-08-04 06:12:54.851 645F6B90 verbose 'FSVolumeProvider' opID=315A332E-0000034B] RefreshVMFSVolumes called
Aug  4 06:12:54 Hostd: [2011-08-04 06:12:54.851 645F6B90 verbose 'FSVolumeProvider' opID=315A332E-0000034B] RescanVmfs called
Aug  4 06:12:54 Hostd: [2011-08-04 06:12:54.879 FFC8CB90 info 'App'] CreateISCSIHBA
Aug  4 06:12:55 vmkernel: 0:03:34:50.432 cpu2:5896)Vol3: 1604: Could not open device 'mpx.vmhba1:C0:T0:L0:8' for probing: Permission denied
Aug  4 06:12:55 vmkernel: 0:03:34:50.487 cpu2:5896)Vol3: 644: Could not open device 'mpx.vmhba1:C0:T0:L0:8' for volume open: Permission denied
Aug  4 06:12:55 vmkernel: 0:03:34:50.594 cpu3:5896)Vol3: 1604: Could not open device 'mpx.vmhba1:C0:T0:L0:6' for probing: Permission denied
Aug  4 06:12:55 vmkernel: 0:03:34:50.660 cpu3:5896)Vol3: 644: Could not open device 'mpx.vmhba1:C0:T0:L0:6' for volume open: Permission denied
Aug  4 06:12:55 vmkernel: 0:03:34:50.711 cpu2:5896)FSS: 3924: No FS driver claimed device 't10.9454450000000000461647163747F6275623023200000000:1': Not supported
Aug  4 06:12:55 vmkernel: 0:03:34:50.738 cpu3:5896)Vol3: 1604: Could not open device 'mpx.vmhba1:C0:T0:L0:5' for probing: Permission denied
Aug  4 06:12:55 vmkernel: 0:03:34:50.768 cpu3:5896)Vol3: 644: Could not open device 'mpx.vmhba1:C0:T0:L0:5' for volume open: Permission denied
Aug  4 06:12:55 Hostd: [2011-08-04 06:12:55.596 64540B90 verbose 'Hostsvc::DatastoreSystem'] VmfsUpdate: got VMFS message [N11HostdCommon18VmkernelUpdateVmfsE:0x6425bef0] timestamp=12890897586 specific=0 name= label=
Aug  4 06:12:55 Hostd: [2011-08-04 06:12:55.943 645F6B90 verbose 'FSVolumeProvider' opID=315A332E-0000034B] RefreshVMFSVolumes: refreshed volume, id 4e3a0642-6b38c474-f89c-0011254a008f, name datastore1
Aug  4 06:12:55 Hostd: [2011-08-04 06:12:55.943 645F6B90 verbose 'Hostsvc::Datastore' opID=315A332E-0000034B] SetVolume: Datastore 4e3a0642-6b38c474-f89c-0011254a008f has changed provider volume pointer
Aug  4 06:12:55 Hostd: [2011-08-04 06:12:55.943 645F6B90 verbose 'Hostsvc::DatastoreSystem' opID=315A332E-0000034B] ReconcileVMFSDatastores: Done discovering new filesystem volumes.
Aug  4 06:12:55 Hostd: [2011-08-04 06:12:55.943 645F6B90 info 'TaskManager' opID=315A332E-0000034B] Task Completed : haTask-ha-host-vim.host.StorageSystem.rescanVmfs-203 Status success

0 Kudos
2 Replies
MarekZdrojewski

Hi kormen,

First of all, why are you shutting down the original ESXi 4.0 host? The power of VMFS is that multiple servers can read/write the same filesystem simultaneously. Second, does the new ESXi 4.1 host have the right permission on the iSCSI LUN? Check the settings on your storage. Also, did you configure the iSCSI initiator correctly on the new ESXi host? Check the dynamic/static discovery tab of the iSCSI initiator.

- hth

Regards.

| Blog: https://defaultreasoning.com | Twitter: @MarekDotZ |
0 Kudos
kormen
Contributor
Contributor

Hi Marek.Z!

The ansver is easy. I mourn my previous datastore. Rest in Peace (but i plan to resurrect somehow) more than 5 vm on it ant few gb data.

Itry to attach that scsi storage a second esxi. since that time the iscsi vmfs "destrolyed" he old and the new esxi can't mount that.

0 Kudos