Corruption in the VMFS data store

Similar Questions

• VM shows this in the NFS data store after passed to the vmfs data store

  Hello

  (1) create a virtual machine using NFS datastore

  (2) had created a few snapshots

  (3) to migrate this virtual machine from the data to the local VMfs store

  (4) all the files are moved to the defined vmfs datastore

  (5) storage > > nfs_datastore > > objects > > VM > > vm is present

  (6) but when did change the setting of this VM, vm is present on the data store local vmfs

  The .vmsn file contains binary data text, so you better not change it manually. The purpose of these files is to be able to return to his instant partner. Depending on the configuration of virtual machines in time you created the snapshot, the virtual machine may require access to the old data store to access the files and folders in there when you return to this snapshot.

  André

• Size = size of the VMFS data store VMDK?

  Is it possible to create a single vmdk equal to the size of a vmfs data store he created in or is it a load element used by vCenter/ESXi.

  I am using vSphere 4 and VMFS data warehouses are in format VMFS 3.33.

  You can't if it is the main drive of a virtual machine and the virtual machine configuration files etc receive on the same data store as the virtual machine directly to the output that the bat will need extra space for a brief amount. For a data reader, this should be possible since there should not be any files will use the space.

• promotion of iSCSI LUN with the VMFS data store

  Hello

  I moved an iSCSI on the website of DR SAN and fact volume so that it was accessible to the ESX host on the site of DR based on the IP address and made the new analysis of the adapter for iSCSI Software in the VI Client on the two hosts on the DR site and he discovered the LUN.

  I don't want to go to the Configuration, storage and add storage as this reformatted the volume and it has a VMware Server already on it running happily on the main site.

  How can I add the volume as a VMFS data store available on the two hosts as he is picked up automatically?

  Thank you

  Paul

  I guess it was a VMFS volume that was used by the ESX environment on main site you, Yes? If you have moved the LUN, i.e. the ESX hosts in the main site no longer have access so that the ESX host at the DR site do not have access, you will need to define EnableResignature = 1 under Advanced settings, LVM

  You restart the analysis for storage and you should access your VMFS volume. You will need to register your virtual machines with the new host.

  When complete set EnableResignature = 0

• VMware 5.5 Upgrade breaks access the VMFS data store (kind of)

  Now, before I get off, I will say that I am sure that the host I'm doing this on IS NOT on the HCL.

  (why I'm running old hardware?-c' is a community organization that I volunteer for which relies on hardware dontated)

  However, please read on.

  Updated an IBM x 3500 and a x 3650 (same generation - they are basically Tower and rack mount versions of the same kit) to esxi 5.1 to 5.5.

  (Exactly the same problem on both)

  Local storage - IBM Serveraid (aacraid)

  I was a bit confused as the controllers of disk and LUN show always also visible (just no VMFS didn't recognize any time how I rescan).

  (normally the LUNS do not appear due to a driver does not)

  I found that I was able to get future LUNS by practice

  'Add a storage '.

  "Disk/LUN.

  (30-60 seconds then shows the LUNS)

  

  It shows the drive bays, I click Next and select "mount disc and keep the signature '...

  

  The lun then comes fine and everything works.

  However rebooting it gets lost again and I have to repeat the process to get the VMFS volumes to come back.

  Possible entries for the vmkernel.log

  (2014 04-22 T 19: 56:42.265Z cpu2:33418) vmklnx_aacraid bunch of module: creation succeeded. ID = 0x410a640c1000

  (2014 04-22 T 19: 56:42.265Z cpu2:33418) < 6 > Adaptec aacraid driver 1.2.1.30300

  (2014 04-22 T 19: 56:42.265Z cpu2:33418) PCI: driver aacraid seeks devices

  (2014 04-22 T 19: 56:42.265Z cpu2:33418) DMA: 612: DMA engine ' vmklnxpci - 0:3:0.0' created using the Mapper "DMANull."

  (2014 04-22 T 19: 56:42.265Z cpu2:33418) DMA: 612: DMA engine ' vmklnxpci - 0:3:0.0' created using the Mapper "DMANull."

  (2014 04-22 T 19: 56:42.308Z cpu2:33418) IRQ: 540: 0x2b < aacraid > shareable, flags 0x10

  (2014 04-22 T 19: 56:42.308Z cpu2:33418) VMK_VECTOR: 218: Manager registered for 0xff2b, 0x10 shared interrupt flags

  (2014 04-22 T 19: 56:43.984Z cpu2:33418) aacraid0 < 6 >: kernel 5.2 - 0 [17003] July 25, 2011

  (2014 04-22 T 19: 56:43.984Z cpu2:33418) aacraid0 < 6 >: monitor 5.2 - 0 [17003]

  (2014 04-22 T 19: 56:43.984Z cpu2:33418) aacraid0 < 6 >: bios 5.2 - 0 [17003]

  aacraid0 < 6 >: serial

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) VMK_PCI: 395: 0000:03:00.0 device name: vmhba1

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) DMA: 612: DMA "vmhba1" engine, created using the Mapper "DMANull."

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C0:T0:L0': seller: 'SERVERA' model: Rev "DIS1": "V1.0".

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiScan: 979: path "vmhba1:C0:T0:L0": Type: 0 x 0, rev ANSI: 2 TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiUid: 273: "vmhba1:C0:T0:L0" path does not support VPD device Id page.

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiScan: 1105: path 'vmhba1:C0:T0:L0': no standard UID: failure. ANSI version ' SCSI-2' (0x2).»

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) VMWARE SCSI Id: Id for vmhba1:C0:T0:L0

  0 x 39 0 x 62 0 x 34 0 x 63 0x61 0 x 30 0x61 0 x 63 x 0 53 0 x 41 0 x 53 0 x 31 0x20 0x20

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiScan: 1503: Add the path: vmhba1:C0:T0:L0

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C0:T1:L0': seller: 'SERVERA' model: Rev "SATA1": "V1.0".

  (2014 04-22 T 19: 56:44.000Z cpu2:33418) ScsiScan: 979: path "vmhba1:C0:T1:L0": Type: 0 x 0, rev ANSI: 2 TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.001Z cpu2:33418) ScsiUid: 273: "vmhba1:C0:T1:L0" path does not support VPD device Id page.

  (2014 04-22 T 19: 56:44.001Z cpu2:33418) ScsiScan: 1105: path 'vmhba1:C0:T1:L0': no standard UID: failure. ANSI version ' SCSI-2' (0x2).»

  (2014 04-22 T 19: 56:44.001Z cpu2:33418) VMWARE SCSI Id: Id for vmhba1:C0:T1:L0

  0 x 39 0 x 37 x 0 39 0 x 38 0x61 0 x 30 0x61 0 x 63 0 x 53 0 x 41 0 x 54 0x41 0 x 31 0x20

  (2014 04-22 T 19: 56:44.001Z cpu2:33418) ScsiScan: 1503: Add the path: vmhba1:C0:T1:L0

  (2014 04-22 T 19: 56:44.018Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T0:L0': seller: "IBM-ESXS" model: Rev 'ST3300655SS': 'BA2D '.

  (2014 04-22 T 19: 56:44.018Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T0:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.020Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T0:L0: not found

  (2014 04-22 T 19: 56:44.021Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T1:L0': seller: "IBM-ESXS" model: Rev 'ST3300655SS': 'BA2D '.

  (2014 04-22 T 19: 56:44.021Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T1:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.023Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T1:L0: not found

  (2014 04-22 T 19: 56:44.025Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T2:L0': seller: "IBM-ESXS" model: Rev 'ST3300655SS': 'BA2D '.

  (2014 04-22 T 19: 56:44.025Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T2:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.027Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T2:L0: not found

  (2014 04-22 T 19: 56:44.029Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T3:L0': seller: model "IBM-ESXS": "N VPBA300C3ETS11' Rev:"A496.

  (2014 04-22 T 19: 56:44.029Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T3:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.032Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T3:L0: not found

  (2014 04-22 T 19: 56:44.034Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T4:L0': seller: 'HUA72202' model: Rev '0ALA330': 'A34H '.

  (2014 04-22 T 19: 56:44.034Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T4:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.039Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T4:L0: not found

  (2014 04-22 T 19: 56:44.041Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T5:L0': seller: 'HUA72202' model: Rev '0ALA330': 'A34H '.

  (2014 04-22 T 19: 56:44.041Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T5:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.047Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T5:L0: not found

  (2014 04-22 T 19: 56:44.049Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T6:L0': seller: 'HUA72202' model: Rev '0ALA330': 'A34H '.

  (2014 04-22 T 19: 56:44.049Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T6:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.054Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T6:L0: not found

  (2014 04-22 T 19: 56:44.056Z cpu2:33418) ScsiScan: 976: path 'vmhba1:C1:T7:L0': seller: 'HUA72202' model: Rev '0ALA330': 'A3GA '.

  (2014 04-22 T 19: 56:44.056Z cpu2:33418) ScsiScan: 979: path "vmhba1:C1:T7:L0": Type: 0 x 0, rev ANSI: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.061Z cpu2:33418) WARNING: ScsiScan: 1408: cannot add the path vmhba1:C1:T7:L0: not found

  (2014 04-22 T 19: 56:44.844Z cpu3:33418) ScsiScan: 976: path 'vmhba1:C3:T0:L0': seller: "IBM" model: "SAS SES-2 DEVICE" Rev: "1.11'."

  (2014 04-22 T 19: 56:44.844Z cpu3:33418) ScsiScan: 979: path "vmhba1:C3:T0:L0": Type: 0xd, ANSI rev: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.845Z cpu3:33418) ScsiScan: 1503: Add the path: vmhba1:C3:T0:L0

  (2014 04-22 T 19: 56:44.874Z cpu3:33418) ScsiScan: 976: path 'vmhba1:C3:T1:L0': seller: "IBM" model: "SAS SES-2 DEVICE" Rev: "1.11'."

  (2014 04-22 T 19: 56:44.874Z cpu3:33418) ScsiScan: 979: path "vmhba1:C3:T1:L0": Type: 0xd, ANSI rev: 5, TPGS: 0 (none)

  (2014 04-22 T 19: 56:44.874Z cpu3:33418) ScsiScan: 1503: Add the path: vmhba1:C3:T1:L0

  (2014 04-22 T 19: 56:44.903Z cpu3:33418) PCI: driver claimed aacraid device 0000:03:00.0

  (2014 04-22 T 19: 56:44.903Z cpu3:33418) PCI: driver claimed aacraid 1 device

  (2014 04-22 T 19: 56:44.903Z cpu3:33418) ScsiNpiv: 1510: GetInfo for adapter vmhba1, [0x4108991c4400], max_vports = 0, vports_inuse = 0, linktype = 0, status = 0, failreason = 0, m = bad0020

  (2014 04-22 T 19: 56:44.903Z cpu3:33418) Mod: 4780: aacraid initialization succeeded with module ID 4174.

  (2014 04-22 T 19: 56:44.903Z cpu3:33418) aacraid loaded successfully.

  (2014 04-22 T 19: 57:07.090Z cpu6:33204) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba32:C0:T0:L0 '.

  (2014 04-22 T 19: 57:07.090Z cpu6:33204) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba0:C0:T0:L0 '.

  (2014 04-22 T 19: 57:07.091Z cpu6:33204) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba1:C3:T1:L0 '.

  (2014 04-22 T 19: 57:07.091Z cpu6:33204) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba1:C3:T0:L0 '.

  (2014 04-22 T 19: 57:07.091Z cpu6:33204) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba1:C0:T1:L0 '.

  (2014 04-22 T 19: 57:07.091Z cpu6:33204) ScsiPath: 4695: Plugin 'NMP' claimed path 'vmhba1:C0:T0:L0 '.

  (2014 04-22 T 19: 57:07.091Z cpu6:33204) ScsiUid: 273: "vmhba1:C0:T0:L0" path does not support VPD device Id page.

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) VMWARE SCSI Id: Id for vmhba1:C0:T0:L0

  0 x 39 0 x 62 0 x 34 0 x 63 0x61 0 x 30 0x61 0 x 63 x 0 53 0 x 41 0 x 53 0 x 31 0x20 0x20

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba1:C0:T0:L0 for the device "unregistered".

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) StorageApdHandler: 698: APD handle created with lock [StorageApd0x410899]

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) ScsiEvents: 501: events subsystem: device, created events!

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) VMWARE SCSI Id: Id for vmhba1:C0:T0:L0

  0 x 39 0 x 62 0 x 34 0 x 63 0x61 0 x 30 0x61 0 x 63 x 0 53 0 x 41 0 x 53 0 x 31 0x20 0x20

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) ScsiDeviceIO: 7419: get VPD 83 inquiry for device "mpx.vmhba1:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.092Z cpu6:33204) ScsiDeviceIO: 7455: get VPD 86 inquiry for device "mpx.vmhba1:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.092Z cpu7:33204) ScsiDeviceIO: 6169: QErr setting for mpx.vmhba1:C0:T0:L0 unit could not detect. Failure of the error.

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) SFS: 5092: pilot no. FS claimed device 'mpx.vmhba1:C0:T0:L0:1': not supported

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) ScsiDevice: 3443: device successfully registered "mpx.vmhba1:C0:T0:L0" from plugin "NMP" of type 0

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) ScsiUid: 273: "vmhba1:C0:T1:L0" path does not support VPD device Id page.

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) VMWARE SCSI Id: Id for vmhba1:C0:T1:L0

  0 x 39 0 x 37 x 0 39 0 x 38 0x61 0 x 30 0x61 0 x 63 0 x 53 0 x 41 0 x 54 0x41 0 x 31 0x20

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba1:C0:T1:L0 for the device "unregistered".

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) StorageApdHandler: 698: APD handle created with lock [StorageApd0x410899]

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) ScsiEvents: 501: events subsystem: device, created events!

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) VMWARE SCSI Id: Id for vmhba1:C0:T1:L0

  0 x 39 0 x 37 x 0 39 0 x 38 0x61 0 x 30 0x61 0 x 63 0 x 53 0 x 41 0 x 54 0x41 0 x 31 0x20

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) ScsiDeviceIO: 7419: get VPD 83 inquiry for device "mpx.vmhba1:C0:T1:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.114Z cpu2:33204) ScsiDeviceIO: 7455: get VPD 86 inquiry for device "mpx.vmhba1:C0:T1:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.115Z cpu2:33204) ScsiDeviceIO: 6169: QErr setting for mpx.vmhba1:C0:T1:L0 of the unit could not detect. Failure of the error.

  (2014 04-22 T 19: 57:07.154Z cpu2:33204) SFS: 5092: pilot no. FS claimed device 'mpx.vmhba1:C0:T1:L0:1': not supported

  (2014 04-22 T 19: 57:07.154Z cpu2:33204) ScsiDevice: 3443: device successfully registered "mpx.vmhba1:C0:T1:L0" from plugin "NMP" of type 0

  (2014 04-22 T 19: 57:07.156Z cpu2:33204) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba1:C3:T0:L0 for the device "unregistered".

  (2014 04-22 T 19: 57:07.156Z cpu2:33204) StorageApdHandler: 698: APD handle created with lock [StorageApd0x410899]

  (2014 04-22 T 19: 57:07.156Z cpu2:33204) ScsiEvents: 501: events subsystem: device, created events!

  (2014 04-22 T 19: 57:07.156Z cpu2:33204) VMWARE SCSI Id: Id for vmhba1:C3:T0:L0

  0 x 50 0x05 0 x 07 0x6c 0 x 07 0xbf 0xe2 0 x 79 0 x 53 x 0 41 0 x 53 0x20 0 x 53 0 x 45

  (2014 04-22 T 19: 57:07.156Z cpu2:33204) ScsiDeviceIO: 7409: get VPD 80 inquiry for device "naa.5005076c07bfe279" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.156Z cpu2:33204) ScsiDeviceIO: 7455: get VPD 86 inquiry for device "naa.5005076c07bfe279" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.166Z cpu3:32792) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808916c0, 0) dev 'naa.5005076c07bfe279' the path 'vmhba1:C3:T0:L0' Failed: H:0 x 7 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 04-22 T 19: 57:07.166Z cpu3:32792) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.5005076c07bfe279' of device NMP doubt; asked the State of the fast path update...

  (2014 04-22 T 19: 57:07.166Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0 x 24 world 0-dev 'naa.5005076c07bfe279' has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.187Z cpu3:32792) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808916c0, 0) dev 'naa.5005076c07bfe279' the path 'vmhba1:C3:T0:L0' Failed: H:0 x 7 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 04-22 T 19: 57:07.207Z cpu2:33204) ScsiDeviceIO: 6169: QErr setting for naa.5005076c07bfe279 of the unit could not detect. Initiator error of storage.

  (2014 04-22 T 19: 57:07.217Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0 x 25 world 0-dev 'naa.5005076c07bfe279' has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.253Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0 x 26 0-dev 'naa.5005076c07bfe279' world has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.289Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0x27 0-dev 'naa.5005076c07bfe279' world has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.317Z cpu3:32792) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808916c0, 0) dev 'naa.5005076c07bfe279' the path 'vmhba1:C3:T0:L0' Failed: H:0 x 7 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 04-22 T 19: 57:07.317Z cpu2:33204) ScsiDevice: 3443: device successfully registered "naa.5005076c07bfe279" from plugin "NMP" of type 13

  (2014 04-22 T 19: 57:07.318Z cpu2:33204) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba1:C3:T1:L0 for the device "unregistered".

  (2014 04-22 T 19: 57:07.318Z cpu2:33204) StorageApdHandler: 698: APD handle created with lock [StorageApd0x410899]

  (2014 04-22 T 19: 57:07.318Z cpu2:33204) ScsiEvents: 501: events subsystem: device, created events!

  (2014 04-22 T 19: 57:07.318Z cpu2:33204) VMWARE SCSI Id: Id for vmhba1:C3:T1:L0

  0 x 50 0x05 0 x 07 0x6c 0 x 07 0xbf 0xe2 0x7b 0 x 53 x 0 41 0 x 53 0x20 0 x 53 0 x 45

  (2014 04-22 T 19: 57:07.318Z cpu2:33204) ScsiDeviceIO: 7409: get VPD 80 inquiry for device "naa.5005076c07bfe27b" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.318Z cpu2:33204) ScsiDeviceIO: 7455: get VPD 86 inquiry for device "naa.5005076c07bfe27b" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.328Z cpu3:32792) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808916c0, 0) dev 'naa.5005076c07bfe27b' the path 'vmhba1:C3:T1:L0' Failed: H:0 x 7 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 04-22 T 19: 57:07.328Z cpu3:32792) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.5005076c07bfe27b' of device NMP doubt; asked the State of the fast path update...

  (2014 04-22 T 19: 57:07.328Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0 x 28 World 0-dev 'naa.5005076c07bfe27b' has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.350Z cpu3:32792) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808916c0, 0) dev 'naa.5005076c07bfe27b' the path 'vmhba1:C3:T1:L0' Failed: H:0 x 7 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 04-22 T 19: 57:07.371Z cpu2:33204) ScsiDeviceIO: 6169: QErr setting for naa.5005076c07bfe27b of the unit could not detect. Initiator error of storage.

  (2014 04-22 T 19: 57:07.381Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0 x 29 World 0-dev 'naa.5005076c07bfe27b' has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.417Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0x2a 0-dev 'naa.5005076c07bfe27b' world has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.453Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e808916c0) 0x1a, CmdSN 0x2b world 0-dev 'naa.5005076c07bfe27b' has no sense H:0 x 7 D:0 x 0 x 0 possible P:0-data: 0 x 0 0 x 0 0 x 0.

  (2014 04-22 T 19: 57:07.479Z cpu3:32792) NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808916c0, 0) dev 'naa.5005076c07bfe27b' the path 'vmhba1:C3:T1:L0' Failed: H:0 x 7 D:0 x 0 P:0 x 0 Possible sense data: 0 x 0 0 x 0 0 x 0. Law: EVAL

  (2014 04-22 T 19: 57:07.479Z cpu2:33204) ScsiDevice: 3443: device successfully registered "naa.5005076c07bfe27b" from plugin "NMP" of type 13

  (2014 04-22 T 19: 57:07.501Z cpu2:33204) ScsiUid: 273: "vmhba0:C0:T0:L0" path does not support VPD device Id page.

  (2014 04-22 T 19: 57:07.510Z cpu2:33204) VMWARE SCSI Id: could not get the disc for vmhba0:C0:T0:L0 id

  (2014 04-22 T 19: 57:07.510Z cpu2:33204) vmw_psp_fixed: psp_fixedSelectPathToActivateInt:479: changing current path from NONE to vmhba0:C0:T0:L0 for the device "unregistered".

  (2014 04-22 T 19: 57:07.511Z cpu2:33204) StorageApdHandler: 698: APD handle created with lock [StorageApd0x410899]

  (2014 04-22 T 19: 57:07.511Z cpu2:33204) ScsiEvents: 501: events subsystem: device, created events!

  (2014 04-22 T 19: 57:07.520Z cpu2:33204) VMWARE SCSI Id: could not get the disc for vmhba0:C0:T0:L0 id

  (2014 04-22 T 19: 57:07.520Z cpu2:33204) ScsiDeviceIO: 7409: get VPD 80 inquiry for device "mpx.vmhba0:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.520Z cpu2:33204) ScsiDeviceIO: 7419: get VPD 83 inquiry for device "mpx.vmhba0:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.520Z cpu2:33204) ScsiDeviceIO: 7455: get VPD 86 inquiry for device "mpx.vmhba0:C0:T0:L0" from Plugin "NMP" failed. Not supported

  (2014 04-22 T 19: 57:07.520Z cpu2:33204) ScsiDeviceIO: 6169: QErr setting for mpx.vmhba0:C0:T0:L0 unit could not detect. Way to not found error.

  (2014 04-22 T 19: 57:07.520Z cpu3:33204) ScsiDevice: 3443: device successfully registered "mpx.vmhba0:C0:T0:L0" from plugin "NMP" of type 5

  (2014 04-22 T 19: 57:07.521Z cpu4:33366) usb-storage: detected SCSI revision number 6 on vmhba32

  (2014 04-22 T 19: 57:07.521Z cpu4:33366) usb-storage: correction of the survey data to change the revision number of the SCSI 6 to 2 on vmhba32

  (2014 04-22 T 19: 57:07.521Z cpu4:33366) usb-storage: correction of the survey data to change removable media, bit of 'stop' on 'on' on vmhba32

  (2014 04-22 T 19: 57:13.043Z cpu3:32792) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.5005076c07bfe279' of device NMP doubt; asked the State of the fast path update...

  (2014 04-22 T 19: 57:13.043Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e80898f40) 0x1a, CmdSN 0xd0 world 0-dev 'naa.5005076c07bfe279' has no data of sense H:0 x 7 D:0 x 0 x 0 possible P:0: 0x5 0x20 0x0.

  (2014 04-22 T 19: 57:13.081Z cpu3:32792) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: State of 'naa.5005076c07bfe27b' of device NMP doubt; asked the State of the fast path update...

  (2014 04-22 T 19: 57:13.081Z cpu3:32792) ScsiDeviceIO: 2337: Cmd (0x412e80898f40) 0x1a, CmdSN 0xd1 world 0-dev 'naa.5005076c07bfe27b' has no data of sense H:0 x 7 D:0 x 0 x 0 possible P:0: 0x5 0x20 0x0.

  (2014 04-22 T 19: 57:13.123Z cpu2:33204) LVM: 8355: mpx.vmhba1:C0:T1:L0:1 detected device can be a snapshot:

  (2014 04-22 T 19: 57:13.123Z cpu2:33204) LVM: 8362: questioned disc ID: type 1, len 14, lun 0, devType 0, scsi 0, h (id) 16746273972281211240 >

  (2014 04-22 T 19: 57:13.123Z cpu2:33204) LVM: 8369: ID of the disk drive: type 0, len 10, lun 0, devType 0, scsi 0, h (id) 1308713170419776745 >

  (2014 04-22 T 19: 57:13.124Z cpu2:33204) LVM: 8355: mpx.vmhba1:C0:T0:L0:1 detected device can be a snapshot:

  (2014 04-22 T 19: 57:13.124Z cpu2:33204) LVM: 8362: questioned disc ID: type 1, len 14, lun 0, devType 0, scsi 0, h (id) 15010766293529110797 >

  (2014 04-22 T 19: 57:13.124Z cpu2:33204) LVM: 8369: ID of the disk drive: type 0, len 10, lun 0, devType 0, scsi 0, h (id) 13427631733060988540 >

  (2014 04-22 T 19: 57:13.131Z cpu2:33204) SFS: 5092: pilot no. FS claimed device 'mpx.vmhba0:C0:T0:L0': unsupported

  (2014 04-22 T 19: 57:13.155Z cpu2:33204) Vol3: 714: could not read the header of control volume: unsupported

  (2014 04-22 T 19: 57:13.155Z cpu2:33204) Vol3: 714: could not read the header of control volume: unsupported

  (2014 04-22 T 19: 57:13.155Z cpu2:33204) SFS: 5092: pilot no. FS claimed "on the remote control": unsupported

  (2014 04-22 T 19: 57:13.202Z cpu2:33204) VC: 2059: device rescan time 101 msec (total number of 5 devices)

  (2014 04-22 T 19: 57:13.202Z cpu2:33204) VC: 2062: Filesystem probe time 70 msec (devices surveyed 5 on 5)

  (2014 04-22 T 19: 57:13.202Z cpu2:33204) VC: 2064: refresh the open volume time 0 msec

  (2014 04-22 T 19: 57:14.826Z cpu3:32851) LVM: 13089: one or more LVM devices have been discovered.

  Commissioning services2014-04 - 22 T 19: 57:16.014Z cpu0:32895) Tcpip_Vmk: 123: nd6_rs_timer: no router on 'vmk0 '. Waive

  (2014 04-22 T 19: 57:16.531Z cpu1:33651) VisorFSRam: 634: vsantraces with (0,300,0,0,755)

  (2014 04-22 T 19: 57:16.531Z cpu1:33651) SFS: 6895: mounting fs visorfs (4108aa584010) with o 0,300,0,0,1,0755, vsantraces on 4108af971220 file descriptor

  Possible the syslog.log entries

  2014 04-15 T 04: 50:20Z jumpstart: storage Info: unable to volume VMFS Mount with the UUID 522a475e-80e96251-5f62-00215e4e123e. SysInfo error on return operation State: County of parameter not valid. See the VMkernel detailed error information log

  2014 04-15 T 04: 50:20Z jumpstart: storage Info: unable to volume VMFS Mount with the UUID 522 a 4783-5bbdaecf-9237-00215e4e123e. SysInfo error on return operation State: County of parameter not valid. See the VMkernel detailed error information log

  Someone at - it useful ideas?

  Thank you!

  Either you have to will the volumes - or clean all paths dead in your esx.conf

• Copying files from a web server to the VMFS data store

  Hi everyone I have a little trouble working it.

  I say a file on a Web server http://webserver/important.txt and I want to copy this file in a local data store.  I am able to copy the file from the Web server to the server I'm running PowerCLI, and then to the data store, but I can't work on how to copy directly.

  Any ideas?

  As far as I know, the Copy-DatastoreItem cannot handle this. The cmdlet requires a path to the Item parameter.

  You will need to first create a local file and then copy in the data store.

• Increase to "enlarge" the VMFS data store

  Hello

  I'm under Esxi 4.1 with vCenter servers. At the storageside, we have an array disk Equallogic iSCSI.

  In this box we have 4 MON, on one of the LUNS we run out of free space, I can increase the LUN to increase it on the side of VMware and Equallogic?

  I know by until it was not recommended, but do not know how it is now with vSphere 4. Any suggestions?

  THX

  extend is possible but then it would be better to create a new LUN, and then balance your IO request and not a large unit number logic.

• How to create LUNS target the same data store?

  In vnx5100, we created two partitions (MON) to be shared separately with 2 VM machines for clustering

  The question here is, that I have assigned the size of the LUN to a new data storage. And when I created ROW for a virtual machine, I had to choose the target LUN, but I wasn't able to see the unit number logic I'm looking for (the one that I have allocated for the storage of data, I created).

  The question here is:

  Why the logic unit number assigned to the storage is not displayed in the list?

  Do we need to create a LUN for the data store and a separate LUN target in Vsphere with the same size of the LUN in VNX?

  What is the target LUN in VMware (vsphere client)?

  Kind regards

  To a RDM and VMFS data store, you must create/submit two LUNS for ESXi hosts. What is stored on the VMFS data store is only the RDM mapping file (this will be created at the time wherever you add the raw LUN to a virtual machine), who shows up with the size of the RDM LUN, but requires no available disk space on the data (as a few bytes) store.

  André

• Extremely high latency during the migration of the local data store to data store shared.

  Hi guys I hope you help me. Sorry for my English btw, I'm not native.

  Let's start!

  I have:

  1 vCenter
  1 host
  1 Distributed Switch (with a pg for managing network/IPstorage the esxi)
  1 standard switch (empty)
  1 FreeNAS to provide iSCSI LUNS
  1 Microsoft to provide iSCSI LUNS

  When I try to migrate virtual machines between the warehouses of shared data or data shared at local store, all right. The problem has become when I try to migrate virtual machines from the local to the shared data store. All data stores down (all paths down) and back up and I get this error:

  "Error caused by the /vmfs/volumes/volumenID/VMDirectory/Disk.vmdk file.

  
  When I try to migrate virtual machines from the local to the FreeNAS iSCSI data store it fails immediately.
  When I do the same local Microsoft iSCSI datastore that it takes a time loooooong to migrate the virtual computer, give it to me even all the paths downwards and uplinks down error but not lacking in migration.

  I'll give you some screenshots to see the errors.

  Thank you very much!

  EDIT: I have extremely high latency notice when I try to migrate from the premises of warehouses of shared data. average 2000ms with peaks of 50,000 (see my response below for more information)

  Finally, I found the solution! The problem is that I have been using E1000E vmnic instead of vmxnet3. I have configured an adapter vmxnet3 and boom! 20 ms in all migration!

  Thank you to all for help, especially Nick_Andreev !

• After the migration of ESXi 4.1 to 5.0 Update 1, ESXi containing the missing data store

  I intend to upgrade to an ESXi 4.1 production host, but I want to run through an upgrade of test on a separate machine. I created this using a virtual machine and the upgrade went well. However, now when I insert my vSphere client, I don't see the data store that contains data to my VM.

  Before migrating to 5, I had 2 drives, a disk of 4 GB for ESXi, and a 40 GB drive for the data of the VM installation. I could see and access times stores via the 4.1 vSphere client, but once the upgrade only the VM data store is available. Is there a reason that this is the case?

  I've updated but has not changed the partitions of data store. I have selected to migrate and keep the VMFS store, which was VMFS-3. I also tried to add the store drive 4 GB with the customer data, but an error message: "the selected disk already has a vmfs data store or the host cannot perform a conversion of partition table.
  Select another disk.

  I found this article on error message: http://KB.VMware.com/kb/2000454 , but I never actually removed from the data store. With the help of the 5.0 ESXi update I can see the VMFS store on 4 GB drive, which should have about 3.2 GB of available disk space (the rest being used by the hypervisor).

  Recommended someone else try esxconfig-volume - the list, and then use the output to a mount (http://communities.vmware.com/message/1666168#1666168), but the list command had no output at all.

  I searched through the forums and Google but you saw nothing.

  ESXi 5 has a different architecture, and I think that the problem is the size of the disk (too small) and the partition of scratch required.

  Have a look here:

  • http://pubs.VMware.com/vSphere-50/topic/com.VMware.ICbase/PDF/vSphere-ESXi-vCenter-Server-50-installation-Setup-Guide.PDF (page 153)
  • http://communities.VMware.com/message/1848769
  • http://KB.VMware.com/kb/1033696
  • http://blogs.VMware.com/ESXi/2011/03/OPS-changes-part-5-scratch-partition.html

  HTH

  Sam

• Help adding extensions to a VMFS data store

  Hello people,

  I am working on some automation for creation of data store and must be able to add extensions to a data store.  The initial creation of data store works well enough at this point, but I'm a little puzzled about how to add additional extensions.  In my example, I am using the navi cli to make the LUN UID off the coast of the Bay of EMC, then format it correctly for the canonical name the host for the creation of data store.

  I read a little about the extendvmfsdatastore here , but I am not able to separate the part "add the measure" of "questioning the existing data store and remove references to pass."  If someone has an extract whose orders must be performed and the text to pass to the .extendvmfsdatastore method, I'd be very happy.  I know measure in several data stores fall into disgrace with VMware, but I can't migrate 10TB data storage immediately.

  Thanks in advance!

  Brent

  omitted variable section

  **********************

  to connect-viserver $VC - https protocol-$VC_USER the username-password $VC_PASSWORD

  Import-CSV C:\PowerShell\VNX_buildout\TEST-DSCreate\Test_DSCreate.csv | {Foreach}
  $LUN = $_.alu
  Naviseccli-address = $UID $VNX_ADDRESS-User $password-VNX_USER_NAME $VNX_PASSWORD-scope 0 lun-list-l $LUN - uid. out-string
  $UID = $UID. Replace (":", "")
  $POS = $UID. IndexOf("6006")
  $UID = $UID. Remove (0, $pos)
  $CN = $UID. Substring (0.32)
  $CN = "naa. $CN ".
  write-host "CN = $CN - Array MONDAY = $LUN"
  New data store - VMHost $ESX_HOST-name $_ .datastr-path $CN - Vmfs-confirm: $false
  DataSet datastore store-$_.datastr - storageiocontrolenabled $true

  # Add the extensions of vmhbax:C:T:L or naa.xxx or?
  }

  I have reviewed the procedure I used, seems that there is an easier way to do it.

  You can try this version of the script?

  $esxName = "MyEsx"
  $tgtDSName = "MyDS"
  $freeLUN = "naa.6005076801801a34d000000000000078"
  
  $esx = Get-VMHost -Name $esxName
  $dsToBeExtended = Get-Datastore -Name $tgtDSName -VMhost $esx $dsSystem = Get-View $esx.ExtensionData.ConfigManager.DatastoreSystem
  $available = $dsSystem.QueryAvailableDisksForVmfs($dsToBeExtended.ExtensionData.MoRef)
  $lun = $available | where {$_.CanonicalName -eq $freeLUN}
  if($lun){
      $options = $dsSystem.QueryVmfsDatastoreExtendOptions($dsToBeExtended.ExtensionData.MoRef,$lun.DevicePath,$true)
      $dsSystem.extendVmfsDatastore($dsToBeExtended.ExtensionData.MoRef, $options[0].Spec)
  }
  

  If the LUN that you pass the $freeLUN variable is not free, the script will not call the extendVmfsDatastore method

• Cannot add the new data store

  VM dear supporters,

  My vSphere environment: 1 vCenter Server Foundation, 3 vSphere 4.0 Enterprise 5.0 and vSphere Client 5.0

  1. read the error message in the attachment:

  "hostdatastoresystem.queryvmfsdatastorecreateoptions...". »

  2. already the ESX02 reboot but still unable to add the new data store.

  New size of the data store = 3.1 TB

  Need to vmsupport on this subject.

  Thank you

  Hello

  Size Max LUN VMFS is 2 TB-512 MB in vSphere 4 (your hosts are in version 4), if you want to add 3.1 TB LUN first upgrade ESX hosts to version 5

  See you soon
  Artur
  

  Please, do not forget the points of call of the "useful" or "correct" answers

• Can I delete the local data store on esx 3.5?

  I have a client with vmware ESX 3.5 no esxi

  They have a local data store but it is formatted with a block size of 1 MB, so I can put only a 256 GB VM out there and I need to put a test VM with a larger size.

  I know that in ESXi 4 you can simply delete the local data store and create a new, but I'm not familiar with ESX 3.5, are there hidden files on the data store that the server uses?  If I search for the store there's nothing in there.

  Thank you

  Mike

  Hi Mike,.

  You can simply reformat your data store. Take a look at the following article:

  • http://userssuck.com/2007/07/12/how-to-change-the-blocksize-of-a-VMFS-filesystem/

  Of course, you must back up and delete any data you have on this data store before the format operation.

  Good luck!

  Concerning

  Franck

• Good way to use the concurrent data store

  Hello

  I'm developing a multithreaded C++ application that uses the C++ of Berkeley DB Library.

  In my case, I have several databases that I composed in a wooded area. It is important for me to use an environment because I need control over the cachesize parameter.

  I don't need no guarantee of transaction and have for most of the readings, so I decided to use the "simultaneous database.

  I first pre-fill all databases with a number of entries (configuration single-threaded phase) and then work on it at the same time (for most readings, but also insertions and deletions).

  I tried all kinds of different configurations, but I can't work without specifying DB_THREAD as a flag of the environment.

  I don't want to because then access all handles is synchronized sequentially according to the documentation:

  "... Note that the activation of this indicator will serialize calls to DB using the handle between the threads. If

  simultaneous scaling is important for your application, we recommend handles separate for each thread opening

  (and do not specify this indicator), rather than share handles between threads. "

  (Berkeley DB QAnywhere C++)

  So I tried to open the environment with the following indicators:

  DB_CREATE | DB_PRIVATE | DB_INIT_MPOOL | DB_INIT_CDB

  All data in this environment handles are open only with the DB_CREATE flag.

  So, since my understanding this same basic access handles need to be synchronized, I opened separate handles foreach database for each thread (opening the handles is still single-threaded).

  In my first approach, I have only made use of the object of global environment. Which does not work and gives the following during operations error message:

  DB_LOCK-> lock_put: Lock is no longer valid

  So I thought, since the same handle global env is passed to all handles separate DB, it is perhaps a race condition critical on the handful of approx.

  So in my next test, I opened also handles separate EPS in each thread (and db handles owned each).

  That does not produce an error in db, but now it seems that each thread sees its own version of the databases (I call it stat early in the life of each thread and he sees all of the empty dbs).

  What is the right way to use the concurrent data store? Each thread should really open his own set of db handles? What about the number of open handles env?

  PS: Without specifying that the DB_PRIVATE flag seems to do the job, but for performance reasons, I want all operations to perform in the cache and do not specify product DB_PRIVATE average of several writes to the disk for my scenario.

  Thanks a lot for your help.

  CD (simultaneous database) allows a single editor with multiple drives, access to the db at a given point in time.    The handle for the writer doesn't have to be shared with readers.   If you share the DB handle then calls are synchronized, but if each thread has its own handle DB then this is not the case.     Since you have an environment, DB_THREAD must be at the level of the environment.   This will allow the sharing of the environment handle.     This type of error "DB_LOCK-> lock_put: Lock is no longer valid" you can provide us your code so we can take a look.   Also what BDB version are you using?

• Need to create a structure for the target data store?

  Hi Experts,

  If I create a structure for the target data store, and then load the data from source to target works fine. If I make mistakes.

  Is necessary to create a structure for target?

  Please help me...

  Thanks in advance.

  A.Kavya.

  I found the answer. No need to create the structure for target temporary data store. and we need to create the structure for the permanent target data store.