mount the windows share in the data store

Similar Questions

• Target iscsi ESXI 5.0, active path connected, mounted, are not not in the data store data store

  HI -.

  I am looking for help to point me in the right direction.  This problem occurred after a reboot of the system.

  I'm in vmware esxi essentials 5.0.0 821926

  I use the starwind software as my iSCSI target

  I use ISCSI to connect to my server from storage to the esxi hosts.

  I have 2 warehouses of data showing inactive under clusters of data storage and the data store.  I have a third-party data store on the same server that is loading properly.

  I currently have the same behavior on three esxi hosts:

  under configuration - storage adapters is the ISCSI path is active. Data warehouses appear under devices and mounted.  In data warehouses, they are inactive. On the same storage server

  on the starwind Server - I have

  built a new target

  removed and added the databases to the new target

  Changed the IP address of the target.

  On Esxi hosts, I removed the ISCSI server, discover places BOF dynamic and static and added under the same or IPs news discovery

  I can restart esxi hosts & storage servers and get to that same point.

  Whenever I find myself in the same place - course assets, devices mounted, inactive in data warehouses

  I don't know what else to share, let me know what you need to know to help out me.

  Thank you

  Dylan

  OK, incase someone crosses my ramblings, it may help.  My original question was warehouses of data that would not rise.  They were visible as devices in the area of storage under devices and as devices in the scsi adapter.

  When I would try to force mount them, add storage, keep the signature, mount they wouldn't mount.  I did some research and my question was after a failed mount attempt strength as got data attached as snapshots warehouses.  I then mounted force them and he tells will data warehouses and I got them back.

  I followed this KB to identify and resolve the problem

  manipulation of vSphere detected as snapshot LUN LUN (1011387)

  When it was over, I tried to add vms back and found a new show.  Power of vms would expire.  the vmkernel.log showed;

  2014 05-27 T 07: 20:40.010Z [verbose 'Vmsvc' 564D7B90] Vmsvc: filtering Vms: ignored not ready to request power state vm vim. VirtualMachine:75

  AND

  (2014 05-27 T 03: 45:47.821Z cpu4:2052) NMP: nmp_PathDetermineFailure:2084: SCSI cmd RESERVE failed on the vmhba35:C0:T1:L0 path, booking on eui.cff548d1952b1e4c of device status is unknown.

  I had latency huge read write showing upwards, 3K and more

  After several searches, I had in the ESXShell and found that there is no conflict of booking.

  On a whim, I took inventory all virtual machines that are now inaccessible.  I then added a DOS virtual machine. Alto! the latency down to version 1.2 a.7 ms for all data warehouses.

  ultimately the instructions said you may need to add virtual machines in the inventory, but does not remove all virtual machines first.  I was grabbing vms that were not in stock, so I didn't remove the old virtual machines in the inventory.

  A recruit Mennonites, Yes.

• IP address on the virtual machine windows endangered endangered after the importation of the data store.

  I'm gaving a problem with the IP on windows vm disappear after having mounted the snapshot to restore. Here's what I do.

  Mount making LUNS to the esx host area

  I have eyebrows outside the data store to find the vm I want to right click and click Import the vmx file.

  Imports of the virtual machine and when I start it up I wonder if I've moved or copied the VM. I have tried both moved and copy but when I connect to the virtual machine is missing all its IP info.

  Any way to avoid the losting vm sound IP info when I import to the host from a LUN outlet?

  Hello

  Installs on the forum of the Virtual Machine and the guest operating system.

  The MAC of a virtual computer is based on the UUID/name of the virtual machine so if you are not using a static MAC (one that recognizes VMware) and it will change the IP address might also change if you are using DHCP. So I suggest to use a static MAC in the VM configuration.

  Another way is to set up the guest operating system in the virtual machine with a static IP address instead of a DHCP function.

  But if you are unable to remove the virtual machine or the copy in the virtual machine, there may be something locking these files would be an another running virtual machine. If you need to find this VM and kill him. In this case, "vmware-cmd - L" and 'vmware-cmd - l' host in question can be useful to find where the 'hidden' VM is running.  Ultimately you can use ' vm-support - x "to find a list of the virtual machines running by how the hypervisor lists. Then use 'vm-support - Z' to suspend the offending virtual machine that should unlock everything.

  Yes, the use of these commands is command line.

  However, before using these commands determine if you can find the place where life VM incriminated.

  Best regards

  Edward L. Haletky

  Host communities, VMware vExpert,

  Author: VMware vSphere and Virtual Infrastructure Security,VMware ESX and ESXi in the 2nd business edition

  Podcast: the Podcast for security virtualization of resources: the virtual virtualization library

• Local data store has disappeared from the data store window (necessary emergency aid)

  Dear team,

  I m facing a very strange problem, all of a sudden one of the local ESX datastore disappeared thereafter are full details we have encountered/noticed.

  A local data store disappeared from the data store window.able to see this data store to add storage Wizard, which allows us to format the same.

  * If we take a session putty from here we can see and browse this store of data without problem.

  * Virtual computers that are running on this data store work as well (all files are accessible / VM is accessible on the network)

  * Unable to take backup image do error "the object has already been deleted or was not completely created.

  * Not able to take a «cannot complete the copy file... network» clone »

  Getting from newspapers in vmkernel:

  (14 dec 17:11:39 localhost vmkernel: 0:01:55:28.677 cpu1:4097) ScsiDeviceIO: 747: command 0 x 28-the device 'mpx.vmhba1:C0:T1:L0' failed, the data of sense H:0 x D:0 x 2 P:0 x 0 0 valid: 0 x 4 0 44 x 0 x 0.

  (14 dec 17:11:39 localhost vmkernel: 0:01:55:28.677 cpu1:4097) ScsiDeviceToken: 293: Sync IO 0 x 28-the device 'mpx.vmhba1:C0:T1:L0' failed: error/o H:0 x D:0 x P:0 x 0 2 0 valid sense data: 0x4 0 44 x 0 x 0.

  (14 dec 17:11:39 localhost vmkernel: 0:01:55:28.677 cpu6:4110) capability3: 5354: Sync READ error ('. fbb.sf') (ioFlags: 8): i/o error

  Need your help urgently to solve the same.

  concerning

  Mr. VMware

  

  Dear all,

  We have enclosed a case at VMware, please find their findings on the same.

  ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  After the webex session, we just had, I discovered the root cause of the problem reported to an underlying problem on the block device (the logical drive, or a problem on the Board) presented to accommodate the data in question store successfully.

  In short, whenever we try to do raw reading from the disk (from sector 0), the same always fail when we reach the 30932992 bytes (31 MB) brand with an IO error (which is consistent, he is always on this region of the disc that read operations fail, no more, no less). This result can be seen, even if no partition is in the disk (using if = / dev/sdb instead of/dev/sdb1 with dd) and even after zeroing on all sectors (if dd \u003d/dev/zero of = / dev/sdb). Strangely, read operations work fine (as he writes zeros of random data) throughout the entire disk. Keep in mind that the tests I did with no VMware tools (I used almost only dd for these operations), which prohibits certainly a VMware problem (in fact, if you were to try to start the server with a Linux live CD and run the same tests that I did, you would see the same behavior).

  I know that there is no report of material of any bad behavior on the table, but data collected with our tests today completely invalid who. The next step is for you to take this to the server provider to check for problems on the table or discs, because they are there and they are the reason for the problem you reported initially.

  Please let me know if you have other questions about it.

  Thank you

  -

  David Meireles

  Technical Support Engineer

  ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  Now we have blocked a case from the hardware vendor, to see what the next move will be.

  concerning

  Mr. VMware

• Visible data VMFS store on 3 of the 6 armies. 3 the remaining hosts see LUNS, status is mounted, but the data store is not visible.

  As the title suggests, all hosts see LUNS... can't understand the question. Here is a shot of the vmkernel.log captured from the server, as it was a new analysis (which translates into a loop of activity in the log file and hard + 10 minutes without change for storage).

  The SAN is preesnting LUN and successfully... so it must be on the host side. In an act of desperation, yesterday I reinstalled ESXi on a troubled host. He was able to see the data stores. Today, they were more visible.

  Thanks in advance for any help.

  VMkernel.log:

  (2013 06-26 T 13: 07:56.778Z cpu1:15038) score: 558: entered reading of TPG (hdrlba = 1) doesn't have the 'naa.600144f0f9e18d0000005160917e0001': i/o error

  (2013 06-26 T 13: 07:56.778Z cpu1:15038) Partition: 661: primary gpt table read failed on 'naa.600144f0f9e18d0000005160917e0001 '.

  (2013 06-26 T 13: 07:56.778Z cpu1:15038) ScsiDeviceIO: 2303: Cmd (0x4124003a4680) 0 x 88, CmdSN 0xabd of the world 0-dev 'naa.600144f0f9e18d0000005160917e0001' has no sense H:0 x 2 D:0 x 0 x 0 possible P:0-data: 0 x 6 0 29 x 0 x 0.

  (2013 06-26 T 13: 07:56.863Z cpu1:8193) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 07:57.005Z cpu1:8193) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 07:57.063Z cpu8:8776) iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410022110b10 network netsched.pools.persist.iscsi associated pool resource

  (2013 06-26 T 13: 07:57.063Z cpu8:8776) iscsi_vmk: iscsivmk_ConnNetRegister: 0x410022110b10 network Tracker id 1 tracker.iSCSI.192.168.70.10 associated with socket

  (2013 06-26 T 13: 07:57.091Z cpu1:8193) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 07:57.234Z cpu1:8193) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 07:57.378Z cpu1:8193) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 07:57.520Z cpu1:8193) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 07:57.563Z cpu1:8193) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP State of 'naa.600144f0f9e18d0000005160917e0001' of the device in case of doubt; asked the State of the fast path update...

  (2013 06-26 T 13: 07:57.568Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is marked as "ONLINE."

  (2013 06-26 T 13: 07:57.568Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023 000002 d TARGET: iqn.2012 - 11.com.rhineaux:nex70 TPGT: TSIH 2: 0]

  (2013 06-26 T 13: 07:57.568Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 192.168.70.50:49286 r L: 0: 192.168.70.10:3260]

  (2013 06-26 T 13: 07:57.578Z cpu8:8603) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' on the way 'vmhba38:C0:T0:L0' failed: H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 6 0 29 x 0 x 0. Bill: NO

  (2013 06-26 T 13: 07:57.578Z cpu8:8603) ScsiDeviceIO: 2303: Cmd (0x4124003a4680) 0 x 88, CmdSN 0xabd of the world 0-dev 'naa.600144f0f9e18d0000005160917e0001' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 6 0 29 x 0 x 0.

  (2013 06-26 T 13: 07:57.578Z cpu8:8603) ScsiCore: 1483: power - on delivery took place the naa.600144f0f9e18d0000005160917e0001

  (2013 06-26 T 13: 08:07.901Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is being marked "OFFLINE" (event: 4)

  (2013 06-26 T 13: 08:07.901Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023 000002 d TARGET: iqn.2012 - 11.com.rhineaux:nex70 TPGT: TSIH 2: 0]

  (2013 06-26 T 13: 08:07.901Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 192.168.70.50:49286 r L: 0: 192.168.70.10:3260]

  (2013 06-26 T 13: 08:07.901Z cpu10:8778) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP State of 'naa.600144f0f9e18d0000005160917e0001' of the device in case of doubt; asked the State of the fast path update...

  (2013 06-26 T 13: 08:07.901Z cpu10:8778) ScsiDeviceIO: 2303: Cmd (0x4124003a4680) 0 x 88, CmdSN 0xabe of the world 0-dev 'naa.600144f0f9e18d0000005160917e0001' has no sense H:0 x 2 D:0 x 0 x 0 possible P:0-data: 0 x 6 0 29 x 0 x 0.

  (2013 06-26 T 13: 08:07.988Z cpu10:13652) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:08.130Z cpu10:13652) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:08.273Z cpu10:13652) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:08.415Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:08.558Z cpu10:8805) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:08.558Z cpu10:8805) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP State of 'naa.600144f0f9e18d0000005160917e0001' of the device in case of doubt; asked the State of the fast path update...

  (2013 06-26 T 13: 08:08.696Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:08.837Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:08.980Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:09.123Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:09.265Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:09.409Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:09.551Z cpu10:8671) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:09.565Z cpu10:8202) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP State of 'naa.600144f0f9e18d0000005160917e0001' of the device in case of doubt; asked the State of the fast path update...

  (2013 06-26 T 13: 08:09.694Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:09.838Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:09.980Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:10.123Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:10.265Z cpu10:8778) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:10.409Z cpu10:8778) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:10.551Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:10.551Z cpu10:8202) WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP State of 'naa.600144f0f9e18d0000005160917e0001' of the device in case of doubt; asked the State of the fast path update...

  (2013 06-26 T 13: 08:10.673Z cpu8:8776) iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410022110b10 network netsched.pools.persist.iscsi associated pool resource

  (2013 06-26 T 13: 08:10.673Z cpu8:8776) iscsi_vmk: iscsivmk_ConnNetRegister: 0x410022110b10 network Tracker id 1 tracker.iSCSI.192.168.70.10 associated with socket

  (2013 06-26 T 13: 08:10.694Z cpu10:8778) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:10.838Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:10.979Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:11.123Z cpu10:8202) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' the path 'vmhba38:C0:T0:L0' Failed: H:0 x 2 D:0 x 0 P:0 x 0 Possible sense data: 0 x 6 0 29 x 0 x 0. Law: EVAL

  (2013 06-26 T 13: 08:11.178Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StartConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is marked as "ONLINE."

  (2013 06-26 T 13: 08:11.178Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StartConnection: Sess [ISID: 00023 000002 d TARGET: iqn.2012 - 11.com.rhineaux:nex70 TPGT: TSIH 2: 0]

  (2013 06-26 T 13: 08:11.178Z cpu8:8776) WARNING: iscsi_vmk: iscsivmk_StartConnection: Conn [CID: 192.168.70.50:59905 r L: 0: 192.168.70.10:3260]

  (2013 06-26 T 13: 08:11.191Z cpu12:8204) NMP: nmp_ThrottleLogForDevice:2319: Cmd 0 x 88 (0x4124003a4680, 0) dev 'naa.600144f0f9e18d0000005160917e0001' on the way 'vmhba38:C0:T0:L0' failed: H:0 x 0 D:0 x 2 P:0 x 0 valid sense data: 0 x 6 0 29 x 0 x 0. Bill: NO

  (2013 06-26 T 13: 08:11.191Z cpu12:8204) ScsiDeviceIO: 2303: Cmd (0x4124003a4680) 0 x 88, CmdSN 0xabe of the world 0-dev 'naa.600144f0f9e18d0000005160917e0001' has no sense H:0 x D:0 x 2 P:0 valid 0 x 0-data: 0 x 6 0 29 x 0 x 0.

  (2013 06-26 T 13: 08:11.191Z cpu12:8204) ScsiCore: 1483: power - on delivery took place the naa.600144f0f9e18d0000005160917e0001

  volumes/vmfs / #.

  Finally I thought of her. The switches have been on a MTU of 9000. I ran each port to the max 9216 and everything works perfectly. A little shocked by him but I'm just glad it is resolved.

• Dell virtual disk are larger. You want to increase the size of the data store.

  Hello

  I started the implementation of a server ESXi 5.5 Update 1 this week. I didn't know Dell shipped the server with two virtual disks instead of one. I realized this _apres_ that I had already created the data store and setup a few virtual machines to the breast. I called Dell who sent specific instructions to increase the removal of the second (empty) virtual disk and add it to the main. In the end, I increased the single VD from 2 TB to 3 TB and I want to give the remaining space in my store of data.

  I tried to follow the article here that explains how to do this via the CLI.

  Well, he did not altogether. Fortunately, I was able to recover my datastore my setting start and end sectors to their original numbers. But I'm still left with this almost 1 TB of space that I can not attribute to the data store. After that I reread storage adapters in the client, the new Dell disk size resulted under measurement devices. Click on "increase...". ", generates the following error which led me on the way to the CLI method:

  Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" to object "ha-datastoresystem" on ESXi '[myservername]' failed.

  I will paste my notes that I took everything by jobs. Things have exploded the rails when I put 4 partition size to the largest size. Any help, please?

  ---

  I use that as a guide:

  http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2002461

  
  

  1 use start hardware device management tools to increase the capacity of additional disk to the device. For more information, commit your hardware provider.

  This has been done. The new size of the virtual disk is 2791,88 GB (TB 2,79188)

  
  

  2. open a console to the ESXi host.

  Pretty simple.

  
  

  3. get the DeviceID for the data store to change.

  ~ # vmkfstools Pei "/ vmfs/volumes/datastore1 / '.

  System file VMFS-5, 60 extending on 1 partition.

  File system label (if applicable): datastore1

  Mode: public

  Capacity 1971926859776 (blocks of files 1880576 * 1048576), 1042688245760 (994385 blocks) prevail, max size of the 69201586814976 file

  UUID: 534e5121 - 4450-19dc-f8bc1238e18a 260d

  Partitions split (on 'lvm'):

  NAA.6c81f660ef0d23001ad809071096d28a:4

  
  

  A couple of things to note:

  a. the device for Datastore1 ID is: naa.6c81f660ef0d23001ad809071096d28a

  b. the number of Partition on the disk is: 4 ' [...]: 4 "»

  c. the prefix, "naa," means "Network address authority" the number immediately after is a single logical unit number.

  4. Enter the amount of disk space available on the data store.

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 1. 8T 865.4 G 971,1 G 47% / vmfs/volumes/datastore1

  
  

  5 team of the device identifier, to identify the existing partitions on the device by using the partedUtil command.

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  ~ #

  
  

  According to the table in article KB

  4 13711360 3865468766 251 0 - primary #4, type 251 = 0xFB = VMFS, 13711360-3865468766 areas

  | |        |          |   |

  | |        |          |   \---attribut

  | |        |          \---type

  | |        \---se finishing sector

  | \---a starting from sector

  partition \---Numero

  
  

  Also note how the number of section start the old end sector number is + 1.

  
  

  6 identify the partitions that need to be resized and the size of the space to use.

  We want to resize partition 4. I don't really understand the last part of this sentence, however. Read more.

  
  

  7 the number of sector end you want for the target data store VMFS partitions. To use all out at the end of the disc space, remove 1 of the size of the disk in the areas as described in step 5 in order to get the last usable area.

  ESXi 5.x has a command to do this:

  ~ # partedUtil getUsableSectors "/ vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a".

  1 5854986239

  This means that we want 4 Partition of "naa.6c81f660ef0d23001ad809071096d28a" to be:

  13711360 - 5854986239 (i.e. the end of the disc)

  
  

  8 resize the partition containing the target VMFS Datastore using the command partedUtil, specifying the original existing partition and the desired end sector:

  Using the above information, our command is:

  resize # partedUtil ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 5854986239

  
  

  9 step 8, the partedUtil command can report the warning:

  He did not. Displacement.

  
  

  10. the tables of partitions have been adjusted, but the VMFS data within the partition store is always the same size. Now there is an empty space in the partition where the VMFS data store can be grown.

  
  

  11 launch this v vmkfstools command to perform a refresh for VMFS volumes.

  Fact.

  
  

  12 reach the VMFS Datastore in the new space using the command - growfs vmkfstools, specifying the partition containing the VMFS Datastore target twice.

  vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 '.

  
  

  It did not work. I got an error:

  / vmfs/volumes # vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' /vmfs/devices/disks/naa.6c81f660ef0d «»

  23001ad809071096d28a:4 ".

  Cannot get device head way /dev/disks/naa.6c81f660ef0d23001ad809071096d28a:4 information

  
  

  Also the partition was very different to what I asked:

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 1560018942 251 0

  
  

  I fixed it by running these commands:

  ~ # partedUtil resize ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 3865468766

  ~ # vmkfstools v

  ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

  364456 255 63 5854986240

  1 63 80324 222 0

  2 80325 8466884 6 0

  3 8466885 13709764 252 0

  4 13711360 3865468766 251 0

  Update:

  Since it was such a new machine, not in active production, we have safeguarded the VMs management off the ESXi host. Then flattened the virtual disk, recreated, and then created a store of data with the right size. (TPG this time, naturally.) We put the management of virtual machines on the data store. For Windows virtual machines, we have restored the using AppAssure. Everything is ok now.

  Need to add a new item to the list of punch: check what Dell has done the configuration of the virtual disks. :-)

• Machine virtual IOPS / s report, how to display the name of the data store?

  Hi guys

  I am new to the Foglight community, this is a great tool, and I learn a lot.

  Currently I am trying to create a simple table that will show me metric of my VMware environment: Virtual Machine name, Datastore IOPS and data store.

  However I can't find how to include data store name in the table, because it is not a measure of the Virtual Machine. I think I need to expand the scope of my table to include VMware Datastore, but I don't know how to do this.

  -Mark

  

  Check the options available it seems that it can be done with WCF (the frame behind the Foglight dashboards).  We recommend generally customers who plan to build views WCF take adequate training or our PSO people engaged in it.

  In any case I can help show a quick example of how it's done.

  Please try this on a local/test server.

  Go to Configuration > definition >

  

  Make sure that you are in my definition, and click the icon to add a view. then choose from the tables and trees - oriented line table

  

  Give a name to the view, go public and make a portlet/reportlet and apply

  

  Switch to the configuration tab and click the change for the lines and choose a query

  Under query, expand the VMware and scroll down

  

  Until you can select the query for virtual machines

  

  And press the set button.

  Your view should look like this

  

  Now you must select the columns.

  Each column has a value you can edit and there is a button + to add additional columns.

  Lets start with the name of the virtual machine - click on the button to change to your default column and choose the context.

  

  Click on the drop down menu to enter key and choose the current line (virtual vmware machine)

  

  Click on the drop down menu to access path and scroll down until you can select the name and then click on set.

  

  You have created a table that lists the names of all virtual machines.

  You can click on save. and then click test, choose a time and click the result. A new window will open a show the list you of virtual machines.
  From here you can continue to add additional columns, each time choosing the key entry in the current line and the path to the metric/string to display.

  For example, the name of the data store.
  I change the module

  

  Click the configuration tab and click the icon to add a column

  

  For the column value, that I chose defined context once again, the key input is the current row and for the path, I expand the node for the data store

  

  And scroll until I see the Proprietename

  

  If you save and test you will see the result

  

  Keep adding columns and the data you want, notice that you have arrows that allow you to control the order of the columns.

  Note that you can click Show advanced configuration properties

  

  This will give you the opportunity to see the properties of the extra table, such as header - giving you the opportunity to give a more meaningful name (name of the data store, the name of the virtual machine, etc.) to the column header.

  

  You can now go you drag and drop the table edge/report and under my eyes, you will see your new view

  

  Drop it in the main view

  

  I hope this has given you the starting point to build this table.

  As I said, I strongly recommend going through our WCF training if you plan build more custom views or hire software Dell PSO Organisation to help build you views that correspond to your need.

  Best regards

  Golan

• VDP: Cannot access the data store

  Hello!

  I have a problem.

  Every day I see error for one of my servers in "reports":

  2016-07 - 05T 06: 00:47.971 + error 06:00-[7F2F3FA5E700] [Originator@6876 = transport sub]

  Cannot use hotadd mode to access the FileSrv1/FileSrv1_1.vmdk [Cisco2-datastore]: can't get using this method.

  (Mounting VM using vm-3198 transport hotadd failed: cannot access the data store for one of the drives of the Machine virtual FileSrv1..)

  At the same time, I havn't this error for the other servers.

  "FileSrv1" has not has installed "VMWare tools". After the instalation "VMWare tools" on this server, the problem is resolved.

• Please help: measure is missing from the data store

  Hello

  I have an a 20 TB drive data store and a magnitude of about 40 TB (local disks, areca raid controller).

  Long story short, I had to delete and re-create the volume 40 to on the RAID controller (without initialization, of course).

  Now all the data is there but eui has changed for the 40 to volume and vmware is unable to mount.

  log/hostd.log:2016-05-10T07:17:16.107Z of information pass [3D380B70] [Originator@6876 sub = Vimsvc.ha - eventmgr] event 118: a connected device eui.001b4d2051676528:1 may be offline. [Backvol1, 55e980d4-386dfa7f-7cb2-0cc47a09ba36] file system now is in a degraded state. While the data store is always available, parts of data residing on the extent which went offline may be inaccessible.

  [root@esxi2:/vmfs/volumes/55e980d4-386dfa7f-7cb2-0cc47a09ba36]

  esxcli instant vmfs storage list

  Volume name:

  VMFS UUID:

  Can mount: false

  UN-mountability reason: a few missing extensions

  Can will: false

  Reason for non-resignaturability: some missing extensions

  County of measure pending: 1

  Can someone help me please?

  Thank you!

  Hello
  You asked for instructions on how to readd a missing measure.
  Basically, it's pretty easy:
  in the VMFS to VMFS-based volume header section, you can assign extends it.
  Lets say that the basic volume is mpx.vmhba1:C0:T3:L0:1
  first of all extend is mpx.vmhba1:C0:T4:L0:1
  second extension is mpx.vmhba1:C0:T5:L0:1
  Then you will see this string in the VMFS header:
  vmhba1:3:0
  and a little later

  MPX.vmhba1:C0:T3:l0:1

  MPX.vmhba1:C0:T4:l0:1

  MPX.vmhba1:C0:T5:l0:1
  Just change the list of stretches.
  But: normally you can't change this section at all, and to add to the confusion, these values are stored in RAM is not trivial to change this value correctly.
  I highly recommend that instead of try it yourself and repeat all the mistakes I made while learning it - call me.
  I rather help you personally to give dangerous advice that will probably make things worse.

• ESXi 5.5 only 4 TB usable for the data store

  Hi all

  Although in vSphere Client 5,46 TB of capacity is visible, I can only use 3.64 TB to a data store.

  Configuration:

  -HP Proliant Microserver N40L

  -HP Smart Array P410/512 MB BBWC, FW 3.66 Controller

  -4 x 2 TB as a Raid5

  HP-ESXi - 5.5.0 - iso - 5.72 A

  I read a lot of articles on > limits of 2 TB of older versions of ESXi or controllers, limitation of 4 TB of c# vSphere Client, old firmware and esxi driver problems, etc.

  But I could not understand the problem.

  The P410 controller shows 5.5 TB:

  ~ # esxcli hpssacli cmd - q "controller connector = 1 see the config.

  Smart Array P410 in slot 1 (sn: PACCRID110510NR)

  Array A (SATA, used space: 0 MB)

  logicaldrive 1 (5.5 TB, RAID 5, OK)

  then 2I:0:5 (port 2I:box 0:bay 5, SATA, 2 TB, OK)

  then 2I:0:6 (port 2I:box 0:bay 6, SATA, 2 TB, OK)

  then 2I:0:7 (port 2I:box 0:bay 7, SATA, 2 TB, OK)

  then 2I:0:8 (port 2I:box 0:bay 8, SATA, 2 TB, OK)

  MS (Vendor ID PMCSIERA, model SRC 8x6G) 250 (WWID: 5001438013D9F37F)

  ESXi obviously knows the same size:

  ~ # Esxcli storage core devices list

  NAA.600508b1001ca5e68adc0bc4bc508d6e

  Full name: Serial Attached SCSI disk HP (naa.600508b1001ca5e68adc0bc4bc508d6e)

  Definable display name: true

     Size: 5723091

  Device type: Direct access

  Multichannel plugin: NMP

  Devfs Path: /vmfs/devices/disks/naa.600508b1001ca5e68adc0bc4bc508d6e

  Vendor: HP

  Model: VOLUME LOGIC

  Review: 3.66

  SCSI level: 5

  (etc.)

  But does that 4 TB:

  ~ # df h

  Size of filesystem used available use % mounted on

  VMFS-5 T 3.6 2.1 T 1. 5 t 58% / vmfs/volumes/mainstorage

  vfat 249.7 M 177.2 M 72.6 M 71% / vmfs/volumes/aeda2aeb-c934ad60-46ce-cb77abdfabaa

  vfat 249.7 M 175.9 M 73.9 M 70% / vmfs/volumes/c8ace7e9-a96a5914-16 d 4-a697ad4634d9

  vfat 285.8 M 191.4 M 94.4 M 67% / vmfs/volumes/55d7af6e-a25f7c97-c3ec-6805ca0de93c

  I tried to increase the size of the data store, last used area was 11720890367 and last sector was 11720890510 which doesn't really seem to translate into an increase of 1.8 to.

  Thanks for your help.

  DC

  Your output, it shows that there are two partitions vmfs

  3 10229760 3907029134 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

  4 3907031040 11720890367 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

  A partition with 1.8 to and another with 3.8 to.   That's the reason why you see only 3.8 to

  I don't know why the 1.8 to vmfs volume is not list anywhere (which does not appear in the list of file system of storage of esxcli also). Do you have any before partition created manually. If you think that if there is no data in this 1.8 to vmfs partition you can remove it by using the partedutil command and then use this free space to extend the existing 3.8 to. But do not forget before you delete the partitiaon

• VM attached to the data store, but not in the config

  I have a few virtual machines that show that they are attached to a store data, but when you look at the parameters of the client both in the vmx file there is nothing that refers to this data store.  And, to top it off, the data store is just a deposit of file I only download iso files to mount for CD-ROMs.  I have made sure that the iso is not mounted on the machine (of course) and have paid through any other part of the config, but still it shows attached to that store of data, by the customer and by a powercli script.

  When you browse the data store, there is no folders or files on there that refer to this virtual machine.  I have about 10 machines all in this difficult situation.  Any ideas?

  Thank you!

  Hello..

  VM snapshots come with a .iso mounted for them? If so, that would explain it...

  / Rubeck

• 0 blocks free PTR - cannot create new files on the data store

  We have been experiencing problems trying to power on virtual machines. When attempting to power on virtual machines, we see the error "cannot extend the pagefile from 0 KB to 2097152 KB".

  We checked the .vswp file are created in the folder of the Virtual Machine on the data store. Connection to the ESXi host, we have seen the following in vmkernel.log error message:

  (2016 01-16 T 21: 19:40.556Z cpu1:4971732) WARNING: Res3: 6984: "freenas-6-ds": [rt 3] No. Space - has not found enough resources after the second pass! (requis_:_1,_trouvé_:_0) 2016-01 - 16 T 21: 19:40.556Z cpu1:4971732) Res3: 6985: "freenas-6-ds": [rt 3] resources t 0, e 0, PN 16, BM 0, b 0, RCs u 0, i 0, 4031 nf, pe 0, 0 2016-01-16 T 21 oe: 19:40.556Z cpu1:4971732) WARNING: SwapExtend: 683: impossible to extend the pagefile from 0 KB to 2097152 KB.

  This was surprising given that we have about 14 TB of space available on the data store:

  [root@clueless:~] df h

  Size of filesystem used available use % mounted on

  VMFS-5 20.0 T 5.4 T 14.6 T/vmfs/volumes/freenas-six-ds 27%

  However, when we use "dd" to write a 20 GB file, we would get "no space left on device:

  [root@clueless:/vmfs/volumes/55a00d31-3dc0f02c-9803-025056000040/deleteme] dd if = / dev/urandom of = deleteme bs = 1024 count = 2024000

  DD: writing "deleteme": no space is available on the device

  263734 + 0 records in

  out 263733 + 0 reviews

  [root@clueless:/vmfs/volumes/55a00d31-3dc0f02c-9803-025056000040/deleteme] ls - lh deleteme

  -rw - r - r - 1 root root 19 Jan 255,1 M 01:02 deleteme

  We checked that we have free inodes:

  The ramdisk name system include in reserved Coredumps used Maximum reserved free use pic free maximum allocated Inodes used Inodes Inodes Mount Point

  ------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  root of true true 32768 KiB 32768 KiB KiB KiB 99% 99% 9472 4096 3575 176 176.

  true true etc 28672 KiB 28672 KiB 284 KiB 320 KiB 99% 99% 4096 1024 516/etc

  Choose true true 0 KiB KiB 0 KiB KiB 0 100% 0% 8 1024 8192 32768 / opt

  var true true 5120 KiB 49152 484 516 99% 90% 8192 384 379 KiB KiB KiB / var

  tmp false false 2048 KiB 262144 KiB 20 KiB 360 KiB 99% 99% 8 256 8192/tmp

  false false hostdstats KiB 310272 KiB 3076 KiB 3076 KiB 99 0% 0% 8192 32 5/var/lib/vmware/hostd/stats

  
  

  We believe that our cause is due to have 0 free blocks of PTR:

  [root@clueless:/vmfs/volumes/55a00d31-3dc0f02c-9803-025056000040] vmkfstools Pei - v 10/vmfs/volumes/freenas-six-ds.

  System file VMFS-5, 61 extending on 1 partition.

  File system label (if applicable): freenas-six-ds

  Mode: public TTY only

  Capacity 21989964120064 (blocks of files 20971264 * 1048576), 16008529051648 (15266923 blocks) prevail, max supported size of the 69201586814976 file

  Volume creation time: Fri Jul 10 18:21:37 2015

  Files (max / free): 130000/119680

  Blocks of PTR (max / free): 64512/0

  Void / blocks (max / free): 32000/28323

  The secondary blocks of Ptr (max / free): 256/256

  Drop blocks (approve/used/approve %): 0/5704341/0

  Blocks of PTR (approve/used/approve %): 64512/0/0

  Void / blocks (approve/used/approve %): 3677/0/0

  Size of volume metadata: 911048704

  UUID: 55a00d31-3dc0f02c-9803-025056000040

  Logical unit: 55a00d30-985bb532-BOI.30-025056000040

  Partitions split (on 'lvm'):

  NAA.6589cfc0000006f3a584e7c8e67a8ddd:1

  Instant native is Capable: YES

  OBJLIB-LIB: ObjLib cleaned.

  WORKER: asyncOps = 0 maxActiveOps = 0 maxPending = 0 maxCompleted = 0

  When we turn off a virtual machine, it will release 1 block of PTR and we would be able to on another VM / create the 20 GB file using "dd". Once we reached 0 free blocks of PTR, we are unable to create new files.

  Can anyone give any suggestions on how we may be able to clear the blocks PTR? We have already tried to restart all services of management on all ESXi hosts connected.

  FreeNAS is not running on a virtual machine.

  We solved the problem by finding a lot PTR blocks have been used by many of our models of virtual machine. Remove the disk models solved the problem.

• Install centos6.4 of the data store

  Hello

  Does anyone know how can I install centos 6.4 on vm. I have the file iso centos on centos6.4_2.iso and vmware server /vmfs/volumes/isos/centos6.4_1.iso

  I selected vm - material - cd/dvd-> iso datastore stressed the centos6.4 - 1.ISO, then connect to option is under

  When I start the VM in a single step, he asks where is the binary located [cd/dvd, nfs, hard drive mounting and url] how can I tell the virtual machine it needs to install from the data store [which is on vmware server 5.x]

  -Sagar

  Hello

  during the installation process will be o.s. installed from cd/DVD, as in the physical environment and it is not necessary specify a data store location. I think you may have an invalid ISO. Check its integrity...

• How do you get the path of the data store or the URL of a virtual disk in vRealize Orchestrator?

  I need to eager zero a virtual disk while building a virtual machine. I found the eagerZeroVirtualDisk_Task() under VcVirtualDiskManager function, which takes in 2 parameters:

  name - (String) the name of the disk, is a path to the data store or a URL pointing to the virtual disk that needs to be inflated.

  Data Center - (VcDatacenter) if the name is a path of data store, the data center for the path of the data store. Not necessary when called directly on ESX. If not specified on a call to VirtualCenter, the name must be a URL.

  How can I get the correct path of data store given the virtual disk? I intend to iterate through the features of the virtual machine to get the disks.

  Thank you!

  Actually figured out how to get the path of the data store, and how a drive zeros. In case it is useful to share the code here:

  var vimHost = vm.vimHost; VM instanceof VCVirtualMachine

  var vDiskMgr = vimHost.virtualDiskManager;

  for each disk

  var features = vm.config.hardware.device;

  for each {(dev var in devices)

  dev.backing contains a lot of useful things...

  If (dev instanceof VcVirtualDisk) {}

  a disc!

  var dsPath = dev.backing.fileName;

  System.log ("path of disk:" + dsPath);

  Data var Center =

  System.getModule('com.vmware.library.vc.datastore').getDatacenterForDatastore (dev.backing.datastore);

  var vcTask = vDiskMgr.eagerZeroVirtualDisk_Task (dsPath, datacenter);

  wait

  var waitResult =

  System.getModule('com.vmware.library.vc.basic').vim3WaitTaskEnd (vcTask, true, 5);

  }

  }

• How to create the new virtual machine vm existing in the data store on ESXI

  I have ESXi and couple of virtual machines.

  I have the vsphere client on Windows 7.

  I then deploy the ovf from the vsphere client vm and it began to import my VM 30 GB.

  In the morning, I realized my vm with a vmdk file file has been transferred in the data store

  But I couldn't see any virtual computer.

  Now I don't know how to turn on this vmdk file that is in my data store

  @King_Robert

  It's a very bad habit of yours to just copy and paste content created by someone else, without even mentioning the source (http://www.mustbegeek.com/create-copy-of-existing-virtual-machine-in-esxi-server/)

  André