InvalidProperty when you info.vmfs the data store when you query properties

Similar Questions

• 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

• VMDK is not displayed when you add the drive but shows on browse the data store

  This may be a simple solution but my forehead hurts to hit my head against the wall and need your expert help.

  Environment: running ESX 4.0 with 4 nodes in the cluster.  Each node in the cluster has only one HBA card with double fiber connections that connect to both sides of FC SAN.  There is not a fiber between nodes and SAN switch, so direct connect.  Built two systems to support Exchange 2007 using the CCS.  Using a FC SAN to shared disk space and iSCSI for disk space not shared.

  Problem: have added 5 player glow spaces on System #1 using RDM and they appear.  Try to load the same readers in the System #2.  I am able to load 4 readers in the System #2 but the 5th disc (which is in fact the reader 3rd in the series) refuses to show when I added the player.  The change settings - & gt; Add Hard Drive - & gt; Use the existing - & gt; Open the data store and the folder where the virtual machine from the system files and the folder where the LUN mapping lie as they are stored with the system.  But at the opening of this file the LUN mapping in question is absent.  All others appear.  However when I right click to browse the data store outside of the settings and go to the folder where the LUN mapping for the virtual drive and it appears.

  Attempts to resolve:

  (1) have removed the drive and delete system #1 data store and we readded to the system = & gt; nothing.

  (2) removed the disk without delete system data store #1 and it added (thus creating two virtual disks in the file for the system to the same LUN... xxx_3.vmdk and xxx_7.vmdk) = & gt; without success.  (xxx_3.vmdk, nor xxx_7.vmdk appear when trying to add a player)

  (3) tried to use a system not intended within the CSC Exchange cluster, attemtped to add the xxx_3.vmdk or xxx_7.vmdk and both appear as an option.

  I am at a total loss.  Do I need to trash the system no. 2 and rebuild?  Is there a problem of possible system configuration #2 that does not allow him to see the two virtual drives?  The #2 system configuration is corrupt?  Do I have to power System #2 power on and off and then try to add readers?  I can the virtual cycle vCenter system?  Or I am much more of a noob that the answer is with myself and I can't see it?  Any help would be welcome.

  When you want to use RDM on hosts, please make sure lun the same number on hosts.

  for example you have assigned the lun 3 host A storage, make sure that it is also the lun 3 to host b.

  Let me know if it does not

  Binoche, VMware VCP, Cisco CCNA

• Recommended minimum on the data store when free disk space you use connection vRanger 5

  I was wondering if anyone can tell me what the recommendation is on the left of free space on a data store. I use 5 vRanger connection to back up my VM to another physical server. As such, I will not take snapshots 'manual '. I'm not sure if vRanger connection, running on a separate server, creates additional files on the data store.

  I've read a few threads on this site and some are advocating to let free, 20 to 25%, while that of others, offer 10% left free may be sufficient. Is there an official number for this or if anyone can share valuable experince?

  Welcome to the community,

  I generally recommend to have about 20% of free space on each data store. However, this depends on the activity/writes to disk during backup. vRanger connection - as well as any other backup software - create a snapshot, back up the virtual machine and then remove / commit the snapshot again. This is necessary in order to access the virtual disk files. Usually the backups are made during hours, so snapshots should not grow too much. However, you must also take into account the fact that in the case of a mistake - if the snapshot cannot be deleted - it will grow until it is deleted manually.

  André

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

• 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);

  }

  }

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

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

• Problems with the data store when installting ESXi USB

  I had problems getting free ESXi reliable running.  I am able to install a flash drive fine and initially everything works and I am able to create virtual machines.  Upon the first connection to vSphere, told me that there is no data store, so I create one on my controller LSI 400 GB RAID1 8308elp without problem.  However, once I reboot the server ESXi I lose the data store.  When I check my warehouses under Configuration it is listed.  At this point, if I try to create the data store, yet once I get "Error during the configuration of the host".  I read about using fdisk from the console when people have had this problem but there is no access console in the free version.  Is that what I can do to work around this problem?

  Right in the HCL... SAS/SATA-RAID of the lists for older versions, SCSI for the current version... Search within i/o devices for "LSI 8308elp '...

  VMware VCP4

  Review the allocation of points for "useful" or "right" answers.

• The data store could not be found.

  Hello!

  I have Esxi installed 4.0 on HP DL 380 G6. I have 2 x SAS (2x146GB) drives and I have also attached storage iSCSI (from HP MSA P2000 G3). on which I recorded a few servers. When I run the script ghettoVCB I get the result:

  /SKRIPTA #./ghettoVCB.sh f lista g /skripta/ghettoVCB.conf
  . / ghettoVCB.sh: /skripta/ghettoVCB.conf: line 14: not found
  Recording output to ' / tmp/ghettoVCB-2011-08-23_12-00-27.log '...
  2011-08-23 12:00:27 - info: = ghettoVCB NEWSPAPER BEGIN =.

  2011-08-23 12:00:27 - info: CONFIG - CONFIGURATION GLOBAL GHETTOVCB = /skripta/ghettoVCB.conf FILE using
  2011-08-23 12:00:27 - info: CONFIG - VERSION = 2011_06_28_1
  2011-08-23 12:00:27 - info: CONFIG - GHETTOVCB_PID = 33245431
  2011-08-23 12:00:27 - info: CONFIG - VM_BACKUP_VOLUME = VMFS/Synology.
  2011-08-23 12:00:27 - info: CONFIG - VM_BACKUP_ROTATION_COUNT = 2
  2011-08-23 12:00:27 - info: CONFIG - VM_BACKUP_DIR_NAMING_CONVENTION = 2011-08-23_12-00-27
  2011-08-23 12:00:27 - info: CONFIG - DISK_BACKUP_FORMAT = thin
  2011-08-23 12:00:27 - info: CONFIG - ADAPTER_FORMAT = buslogic
  2011-08-23 12:00:27 - info: CONFIG - POWER_VM_DOWN_BEFORE_BACKUP = 0
  2011-08-23 12:00:27 - info: CONFIG - ENABLE_HARD_POWER_OFF = 0
  2011-08-23 12:00:27 - info: CONFIG - ITER_TO_WAIT_SHUTDOWN = 3
  2011-08-23 12:00:27 - info: CONFIG - POWER_DOWN_TIMEOUT = 5
  2011-08-23 12:00:27 - info: CONFIG - SNAPSHOT_TIMEOUT = 15
  2011-08-23 12:00:27 - info: CONFIG - LOG_LEVEL = info
  2011-08-23 12:00:27 - info: CONFIG - BACKUP_LOG_OUTPUT = /tmp/ghettoVCB-2011-08-23_12-00-27.log
  2011-08-23 12:00:27 - info: CONFIG - VM_SNAPSHOT_MEMORY = 1
  2011-08-23 12:00:27 - info: CONFIG - VM_SNAPSHOT_QUIESCE = 1
  2011-08-23 12:00:27 - info: CONFIG - VMDK_FILES_TO_BACKUP = all
  2011-08-23 12:00:27 - info: CONFIG - EMAIL_LOG = 0
  2011-08-23 12:00:27 - info:
  The data store could not be found.

  The data store could not be found.

  The data store could not be found.

  2011-08-23 12:00:36 - info: start backup for Windows 2008 R2 coaching
  2011-08-23 12:00:36 - info: creation of snapshot "ghettoVCB-snapshot-2011-08-23" for Windows 2008 R2 coaching

  2011-08-23 12:03:40 - info: ERROR: error in the backup of "/ vmfs/volumes/4d5ed225-cdb17961-51bb-d8d385ac2800/Windows 2008 R2 coaching / Windows 2008 R2 Podpora_1.vmdk" for Windows 2008 R2 coaching

  2011-08-23 12:03:40 - info: ERROR: error in the backup of "/ vmfs/volumes/iSCSI/Windows 2008 R2 coaching / Windows 2008 R2 Podpora.vmdk" for Windows 2008 R2 coaching
  2011-08-23 12:03:42 - info: Instant withdrawal of Windows 2008 R2 coaching...
  2011-08-23 12:03:47 - Info: backup duration: 3.18 Minutes
  2011-08-23 12:03:47 - info: ERROR: unable to backup Windows 2008 R2 coaching because of the error in VMDK backup!

  2011-08-23 12:03:47 - info: # final status: ERROR: No. VMs saved! ######

  2011-08-23 12:03:47 - info: = ghettoVCB JOURNAL END =.

  I also do backups on iSCSI NAS storage.

  First ghetto script does not detect the data stores that are local disks where I run few servers and secondly I get error of backup server located on iSCSI for HP MSA.

  Thank you.

  Your destination data store is set incorrectly

  VM_BACKUP_VOLUME = VMFS/Synology.

  It should be

  VM_BACKUP_VOLUME = / vmfs/volumes/Synology.

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

• local storage in the data store

  I have 4 ESXi 5.5 cluster nodes (host1, 2... 5) + 3par storage, I noticed that the local drive of host2 is detected as a data store.

  When I create a VM and I choose the data store, I can see all data related to my on3par LUN stores but it seems this drive local host2 too!

  I would like to remove it! Can you offer me please?

  You must hide hide this data store using permissions, you must run the following procedure: Open-> inventory-> warehouses vSphere-> select the select data-> permissions VMFS store-> click the user or group in the list and set them to 'No access' - are not propagated.

  Once achieve you its judgment showing everywhere.

• Name of device for the data store list

  Need help with this simple script

  $datastores = get-Datastore-location "CXXV. Where-Object {$_.ExtensionData.Info.GetType ().} Name - eq "VmfsDatastoreInfo"}

  $myColCurrent = @)

  ForEach ($store in $datastores)

  {

  $myObj = "" | Select-Object Name, devicename

  $myObj.Name = $store.name

  Write-Host $myObj.Name

  $myObj.devicename = $store.ExtensionData.Info.Vmfs.Extent.DiskName

  Write-Host $myObj.devicename

  the name of the data store is writtenl properly but the devicename is empty and get this warning:

  WARNING: The 'Accessible' type of data store property is obsolete. Use the property 'State '.

  Strange thing is that the Script works lab powercli linking the vCenter lab. But gives the error in the production powecli server to vcenter prod.  powercli and vcenter server versions are the same.

  Help is greatly appreciated

  The extended property is an array.

  Try to change this line

  $myObj.devicename = $store.ExtensionData.Info.Vmfs.Extent.DiskName

  in this

  $myObj.devicename = [string]: join (",",($store.ExtensionData.Info.Vmfs.Extent |) %{$_. DiskName}))

  You can safely ignore the warning messages, or may disable them with the Set-PowerCLIConfiguration cmdlet and the DisplayDeprecationWarnings switch.

• Error e/s download large vmdk file to the data store

  Hi, I am looking to download a large file (400 GB) vmdk to our SAN by using the method of the vsphere client browser store data but get IO error when it gets to about 270 GB. Is there a limit to how big a file can be? any other recommended method?

  Thank you

  Rob

  What is the version of VMFS (VMFS3 or VMFS5) of the data store? In the case of VMFS3 there are limitations on file size depending on the block size of the data store (for example, 1 MB block size-> ~ 256 GB).

  André

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