can't see vm after upgrade to esxi 3.5. VM folder exists on the DATA store.

Similar Questions

• 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é

• Unable to see VM in the data store after a restore of vcenter

  Hello

  One of my colleagues tried to install Service Pack 3 to SQL 2005 on our vcenter SQL instance.  Unfortunately, this was not and no services would begin once he did the upgrade.

  He gave the entire server to a backup that was taken a week ago.  Now, we have some problems where we do not see the virtual machines if browse us the data store, it is just to show as thought that there is no data there (see screenshot) and a virtual machine appears as orphans.

  Normally I would just delete the virtual machine of vcenter and go back and import it again but I can't do what I'm not.

  Any ideas?

  Try removing the host and adding back to vCenter. It will update the agent, vpxa.

• How can I see "a link to a file" given in adobe acrobat pro on the mouseover?

  How can I see "a link to a file" given in adobe acrobat pro on the mouseover?

  It's because it's actually a link that points to a local file (using the file:/// syntax). If you change the action associated with this link, you will see that it is a command "open a web link", not a command "open a file". The latter does not display this information, that I know.

• After upgrading to Snow Leopard 10.6.5 most of the files does not open in CS3 Rosetta, grayed out menu items

  After upgrading to Snow Leopard 10.6.5 most of the files will not open in CS3 and more menu items are gray,

  like "Photoshop" and "quit Photoshop. I have to force it to quit. Don't know what version of CS3 since 'about this Mac' is not available.

  But CS3 runs in mode of "Rosetta". I had done this years ago, my scanner would work.

  I don't remember how I managed to do run in Rosetta and don't know how to do so he could operate normally, if necessary.

  Change the name of the file or the plugin to have ~ as first character will prevent it to be loaded.

• Cannot remove the data store in esxi 3.5 - can help you

  OK - I have a problem. I messed up and now I'm stuck.

  I was "apparently" in the middle of a converter working, and I deleted the comments of esxi3.5, while the converter still worked.

  I selected the rafale and made a removal of the disc that worked, however the structure of associated file (windows 2000 Server) for this guest has not been deleted, so I chose my data store (datastore1) and - do you have a store of navigation data and when I try to delete the folder associated with the guest, I deleted I get the following error :

  "General failure caused by file" (with a "/" on the next line) and all I can do at this point is to click OK box to acknowledge the error and I can't delete the folder. I can't rename it either.

  I don't know how to get rid of it. I tried to create a new client with the same name as the folder and delete the comments again, but that does not work either.

  I'm really stuck - I'm afraid to go into maintenance mode because I have no idea what I'm going to be confronted here since I never used the maintenance mode.

  any help or ideas would be really appreciated.

  You can try to do a refresh of the data store. The folder structure is not re read very often. In the data store Navigator, click the folder root on the left side and click on the Refresh button.

• Add the new hard drive into the data store in ESXi 4.1

  Hi all

  I got ESX 4.1 installed on the Dell server, and I have 3 virtual machines on a data store.

  I added a new 500 GB scsi hard drive to the server,

  and I need to add it to the datasore or create a new...

  How can I see this new hard drive? and add it to the data store?

  Waiting for your help.

  concerning

  Abrams

  Oracle system engineer

  Abrams,

  That's all I can help you.  These instructions are based on the Perc 5 / i controller, which I think you have on our system.  You have not specified the server so I just assumed that this is so.

  1. unscrew the hot spare that you just made.  Follow this link from Dell.
  http://support.Dell.com/support/eDOCS/storage/RAID/PERC5/en/UG/HTML/chapterh.htm#wp1061343

  2 follow the link for the installation of virtual disks - http://support.dell.com/support/edocs/storage/RAID/PERC5/en/UG/HTML/chapterh.htm#wp1069357

  This link has three steps to void, skip the step on "spare parts of designate hot."
  a. create the virtual disks and select virtual disk options.   -Online steps to create another disk group and add the new disk to the disk group.
  (b) designate the drives hot spares (optional). =>, YOU CAN SKIP THIS STEP
  c. initialize virtual disks. -online must do.  just do not initialize the incorrect disk.

  After the step #2 c, you should be able to access the drive in ESXi or command-line (list of nmp esxcli devices).

  And no, you cannot add this manaully until do you step #2 above which is to define the disk group, creating virtual disks and initialize the virtual disk.

  Good luck.

• 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

• 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.

• How can I get an alarm for VM in bad condition when you run lack of space on the data store

  Hello

  After ignoring the alarm messages on disk space used almost, a VM doesn't work with this error message:

  "Message from VMHost1.test.net: there is no more space for virtual disk.

  vmfs/volumes/4fb7ee7c-9c2aceee-a0df-00215acb6f4a/VMHost1/VMHost1_1_1.VMDK. You may be able to

  continue this session by freeing up disk space on the relevant volume, and then click Retry. Click Cancel to end this

  session. "

  At this point, I would like to have another alarm to ignore ;-)

  I'm trying to find a VMware alarm that can warn me in this case. (As the alarm 'use of data to drive store"set up to warn me when 90% is used)

  Basically, when the data store is full, and a virtual machine on it ask the e/s, due to the fact that it is thin provisioned, it is currently interrupted by ESXi. All virtual machines that do not require what I/O may still work. When this happens, you get an error like this:

  

  What the virtual machine that will come to you, is basically a VM Message. Using vCenter, you can create an alarm that goes off when the virtual machine (an individual) information message. The message that I used was something like this:

  

  When I then make a virtual machine on a data store set up thin, my alarm clock personalized using thin disks implemented short of space, was triggered.

  

  NB. I saw icon of the virtual machine in a State of alarm after that I clicked retry on the popup. If you don't do this, the virtual machine icon will be the State in question, but will always be triggered the custom alarm.

  Hope this helps,

  Tom

• 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.

• ESX host cannot see the data store

  Hello team, I have vcenter management 5 2 host esxi5. now added an esxi4 in the cluster and added iniitators for file systems. I can see the paths under this host of esx4 showing the LUN of the registrants. but I'm not able to see the data to store. When I tried to edit a newly created virtual machine to find the iso from the data store, it shows only the local hard disk of the host, which is a UCS blade. exsi5 hosts the two ok to see all data stores. can someone tell which part is wrong? Thank you!

  Looks like there is no problem with the presentation of the logic unit number since you can see the path to the LUN from the host.

  Is - these created data VMFS storages are 50 ESXi? If so, the VMFS version 5 (VMFS 5) which is not supported in ESXi 4.1.

  In this case, its expected that the host ESXi 4.1 will not show VMFS5 data warehouses.

• Can photos be deleted from the data store directly?

  Hello

  I just doubt. Can shapshots be deleted directly from the data store.

  I checked the Snapshot Manager, but was not able to locate snapshots in it, but at the same time there were three snapshots in particular virtual machine data store. What it means?

  And what is my isNativeSnapshot = 'no'?

  I just doubt. Can shapshots be deleted directly from the data store.

  No, snapshots work as a string. Deletion of one of the links in the chain breaks the chain. Please take a look at http://kb.vmware.com/kb/1015180 to see how snapshots work.

  I checked the Snapshot Manager, but was not able to locate snapshots in it, but at the same time there were three snapshots in particular virtual machine data store. What it means?

  Information about snapshots are kept in .vmsd the virtual machine folder. If this file is corrupt - for some reason-you won't see the correct string snapshot in the Snapshot Manager.

  Please create a list of all files in the folder of the virtual machine (dir *. * /oen > filelist.txt (for Windows) or ls-lisa > filelist.txt (for Linux)) and after (tie) the filelist.txt, file .vmx VM as well as the file .vmsd for your next post.

  André

• 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

• New install ESXi 4, do not recognize the data store

  Hello everyone,

  First here is the configuration hardware server, with that I currently have problems

  HP DL360 G5

  6 x 146 GB SAS (Raid 5) Local storage

  HP Smart Array p400i

  With this server, we started to have only a 4-drive raid 5 (which was working fine), but this week, we have installed more than 2. To do this, I deleted the existing logical drive and creates a new one that included two new hard drives to bring the total to 6.

  Well regardless of how many times I try when ESXi 4 completed installation there is no established data store (what she has always done automatically in the past). Please see attached screenshot named data store for more details. When I look at the devices that it displays the partitions that have been created and one of them is VMFS with a 678 GB in size (see devices.jpg for more details). If I try to create a data store, it goes through the motions but shows an error message "error during the configuration of the host: unable to update the disk partition information.

  I erased all the disks, deleted and recreated the drive bays and the logical drives all nothing made. We have another box that is identical to that where the same procedure was performed and it has worked flawlessly. I'm so full of ideas. If someone could provide information I would be very appreciate it. Thank you!

  This may sound stupid (maybe it is) but you can clear the RAID, exchange of HARD drives (bay1 <->bay6 bay2 <->Area5, bay3 <->bay4), then recreate the RAID and try again? In case there are a few old patterns on disks that are recognized during installation.

  André