Data store is no longer visible in ESXi 5.0

Similar Questions

• Need help an existing data store is no longer to go in

  I have a data store that no longer exists on my SAN.  It still appears in the inventory as being inactive.  I can't remove it.  When I try to get the following:

  Call 'HostDatastoreSystem.RemoveDatastore' of object "datastoreSystem-121"on vCenter Server 'VCENTERSERVER2.onebane.com' failed."
  Operation failed, the diagnostic report: unable to query live VMFS volume State. : no such file or directory

  In addition, an of my hosts shows that it is always connected to what is interesting because the LUN has disappeared.  No VM appear on the virtual computers tab.

  Is there a way to force this LUN of stocks?

  Thank you very much!

  I've not seen instructions either - I just connect via ssh as root
  Then I use winscp and navigate to/etc/vmware
  There you can right click on esx.conf and change it.

  Helped me once to solve a similar problem.

  You will find a section starting with
  LUN/storage.

  Each logic unit number has two lines... I just removed the two lines for you LUN in question.

  First, create a backup of the file

• Question about data store more than 2 TB on ESXi 5.5

  I have a data store that is currently 2 TB. I need to grow a little bigger for the snapshot space. We run ESXi 5.5. Is there something special I need to do or worry about when adding space to the LUN to make it more 2 TB? It's the first data store that I got is that great so I want to see if there are special considerations.

  I intend to go in my SAN management software, increase the size of the LUN and then go to vSphere, rescan storage and add extra space for the data store.

  Thank you!

  Who should do - the only isssue is if it is a VMFS (improved VMFS3) legacy data store that is my understanding evan if he has been upgraded to VMFS5 you will not be able to go beyond 2 TB.

• Data store for config files shared with esxi and free license

  Hello

  currently I am setting up a test environment with two esxi nodes that share a database on an EMC Clariion. Virtual disks itself will be shared by RDM, there is no problem.

  But if I change the configuration of a virtual machine to a physical computer (node A) the other (node B) still use the old configuration, node B does not notice the change applied to node A. What I am doing wrong? Is there a set up where node B will automatically refresh the virtual machine configuration after modification on node A?

  If I download the file vmx of navigation on the B node data store, I see the applied changes written to the file. So I guess it isn't a caching issue. The vmx file we re - read when turn on/off the virtual machine? Why isn't she re-read on the opening of the vm configuration dialog box?

  What is the recommended set for two guests free esxi who should be able to run virtual machines in the other machine? I don't think that of VMotion or HA! I just want if node A has a power outage on some VMs on the node B.

  Thank you!

  Good bye

  Daniel

  You must not register VMs on of two ESXi. Installing vCenter or register VMs on host-host these specific VMs will run on. If you need to move the VM to an another ESXi then delete the inventory on the single host and add to the inventory on the other.

  ---

  VMware vExpert 2009

  http://blog.vadmin.ru

• Deletion of the data store

  Hello

  I deleted a data on a cluster through a host store. The data store is not longer available on all hosts, but it still appears on home / inventory / data warehouses.

  The hosts are in 4.1.0 (build 260 247), the vCenter is 4.1.0 Build 258 902.

  The data store has been 200 GB and used on 10 hosts, all with the same version.

  The "Delete" option is not available on the data (by clicking right on) store, the data store is no longer visible on the hosts.

  How can I clean the records of data store on the inventory of the data store?

  Thank you very much in advance for your answers.

  KB http://kb.vmware.com/kb/1026661 explains the process of how to remove the vCenter Server DB data store in a case like this.

  André

• Failed to create data store on LUN ISCSI

  Get the following error when attempting to create a new data store after a new installation of ESXi 5.5U2.

  Location:

  • UCS B200 servers using the VIC-1280 map and
  • Interfaces ISCSI connected directly from the fabric of interconnection to the NetApp FAS2552 with TwinAx cables
  • MTU is set for extended frames (9000) on the interface of NetApp, vNIC for ISCSI vKernel vSwitch and group interface ports
  • During the initial setup of the vSwitches, I forgot the MTU setting Port and interfaces group wouldn't even ping, so all the MTU setting are good
  • ISCSI connection is green and LUN created and present storage warehouses are considered as available on the ESX Server to create a data store (sizes 1 TB and 2 TB tested times)
  • The NetApp storage have been created as a thin provisioned and thick provisioned - neither works and gets the same error

  

  Any ideas would be very useful. Technical support has not yet responded.

  Thanks in advance.

  DM

  OK, after working with NetApp and VMware on a conference call (after both made each other) bottom line "fix" was to remove the iSCSI port bindings, remove broken paths, remove the vSwitches and rebuild again.

  1. create vKernel vSwitch with appropriate port group

  2. set the MTU to 9000 on the port group and vSwitch

  3. create the bindings for each interface iSCSI Port

  4 re-scan

  5 successfully create the data store

  Oddly enough, I had to repeat this process 3 times for one of the blades, but it worked the first time for 3 other involved blades.

  VMware technical support did provide the following as a look at the LUN of the CLI:

  1. / vmfs/devices/disks cd

  ls-l

  We see and out of all the available discs

  Identify the Lun Naa.xxxxxxxx

  2. run the Naa.xxxxx reported in step 2

  partedUtil getptbl /vmfs/devices/disks/naa.xxxxxxx

  If there is a partition, you might see something similar to

  1 63 2249099 131 128 > 1 is the partition number

  or

  You can see and error, if error please contact technical support

  3. If there is partition, you can delete

  partedUtil remove /vmfs/devices/disks/naa.xxxxxxx 1

  NOTE: This process did not work, but is still useful nonetheless. It could work if the LUN has been used by another operating system and need cleaning. But my situation was all greenfield.

• Accessibility of the data store

  I need determine if a given data store is accessed from ESX

  hosts.  I noticed that the MO data store has a property named

  accessible.  However, in my tests, even when I take the data store down

  (it was a test NFS data store and I just close the NFS host), the

  accessible property always return true.

  Does anyone know how to determine when / if a given data store is no longer accessible by an ESX host?

  Thank you very much in advance for your help.

  -Moby

  Did you call UpdsateViewData after you turned off the NFS server?

  $ds = Get-Datastore  | Get-View
  ....
  # NFS server powered off
  $ds.UpdateViewData()
  ....
  

  Note that in PowerCLI 4.1, you have access to the MO via the ExtensionData property.

  ____________

  Blog: LucD notes

  Twitter: lucd22

• 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

• Disk groups are not visible cluster. vSAN datastore exists. 2 guests (on 8) cluster do not see the vSAN data store. Their storage is not recognized.

  http://i.imgur.com/pqAXtFl.PNG

  http://i.imgur.com/BnztaDD.PNG

  Do not know how even tear it down and rebuild it if the disk groups are not visible. The discs are in good health on each host storage adapters.

  Currently the latest version of vCenter 5.5. Hosts running 5.5 build 2068190

  Just built. Happy to demolish and rebuild. Just do not know why it is not visible on the two hosts and the disk groups are only recognized 3 guests when more are contributing. Also strange that I can't get the disk groups to fill in vCenter. I tried two different browsers (chrome and IE).

  I have now works.

  All the identical 5.5 relies on ESXi hosts. All hosts are homogeneous CPU/sum of the prospects for disk controller / installed RAM/storage.

  I have work. I had to manually destroy all traces of the vSAN on each single to help host node:

  (1) put the hosts in maintenance mode and remove the cluster. I was unable to disable vSAN in the cluster, I made on each node host (manually via the CLI below) then disconnected web client vCenter and return to finally refresh the ability to disable on the cluster.

  esxcli vsan cluster get - to check the status of each host.

  esxcli vsan cluster drop - the vSAN cluster host.

  storage of vsan esxcli list - view records in the individual host group

  esxcli vsan storage remove-d naa.id_of_magnetic_disks_here - to remove each of the disks in the disk group (you can ignore this using the following command to remove the SSD only falling each disc in this host group).

  esxcli vsan storage remove s naa.id_of_solid_state_disks_here - this is the SSD and all the magnetic disks in a given disk group.

  After that, I was able to manually add hosts to the cluster, leave maintenance mode and configure the disk groups. Aggregated data of the vSAN data store is correct now, and everything is functional.

  Another question for those of you who still read... How to configure such as the VM storage strategy that migrates towards (or inspired) the vSAN data store will immediately resume the default storage policy, I built for VSANs?

  Thanks for anyone who has followed.

• How do I cancel the mapping of a data store of esxi host without data loss

  Dear team,

  I want to cancel a data store that is mapped on two cluster mapping (cluster1 10 esxi host and cluster2 esxi 4 guests)

  
  

  
  

  Query1

  What step will be OK

  Disassemble = > detach = > start the activity of storage (storage poweroff) movement = > move the storage = > poweron = > join = > mounting

  or

  Disassemble = > detach = > team san will cancel the mapping = > start the activity of storage (storage poweroff) movement = > move the storage = > poweron = > san team will map the data store = > join = > mount

  Query2:

  Once I sail, I am able to see vpshere ha and dvs folder data, I just want to confirm if I want to take it apart and to separate the data store it will allow me to do it or it will throw an error, please confirm.

  Query3:

  If we remove and detach a data store, before that I have to cancel the registration of all the virtual machines?

  
  

  
  

  concerning

  Mr. Vmware

  Please find the right measures

  Query1

  
  

  before the take-off of export activity VM that are stored on the data store

  
  

  Home-online store of data and the data cluster store => select the data-VMs online store => add all columns => take export VM

  
  

  take the last export RVTool.

  
  

  
  stop all VMs-online you unsubscribe from all models and virtual computers-online RK on Cluster (change the setting-online data store-online here hearbeating we have to choose another data store and click OK)

  
  

  to confirm the new data store is visible as heartbeat data store select Cluster-online Sumamry-online state Custer-online Heartbeat Datastore)

  If we are able to see the new data store, then now remove old data from the heart rate data store store

  
  

  RK on Cluster (change the setting-online data store-online here hearbeating he have to uncheck the data store and click OK)
  

  
  

  disassemble => detach (you will need to perform this step on all esxi hosts)-online san team will be unmap-online beginning of movement storage (storage poweroff) => move the storage-online poweron-online san team will map the data-attach online store ((need to perform this step on all esxi hosts) => set up the data store)

  
  

  Register for all virtual machines

  
  

  PowerOn all VMs if get message (moved or copied) select moved.

  
  

  Query2:

  He doesn't throw any errors, will work flawless.

  
  

  Query3:

  Yes we must cancel the registration of all models and virtual computers before disassembling a data store.

  
  

  concerning

  Mr. VMware
  

  
  

  
  

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

• VMware ESXi 5.1.0 VMFS5 maximum data store size

  Hi all

  I read white papers on VMFS and I get conflicting answers on the maximum size of a VMFS5 data store.

  We are using a Dell EqualLogic PS6100 and linking the LUNS via iSCSI for host servers.

  I need to create a data store TB 4 for my file server reside on.

  (A) is it possible?

  (B) are there performance problems with the largest data warehouses such as I want to do.

  Block sizes C) must be modified to mount a data store of this size and how you do it.

  Any idea or article links would be greatly appreciated.

  Keith

  (A) Oui it is possible but you will need to use a RDM - ESXi 5 allows access to 64 TB but the size of the virtual disk is always capped at 2 TB - 512b

  (B) you must not

  (C) with ESXi 5 block size is no longer a variable that you define for a VMFS data store

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

• ESXi host sees no data store after the reboot

  Hi all

  I'm new to the community and ESXi itself.  Everything has been working great until today when I rebooted my host.

  I installed it on a Dell T110 server, we had in the back for testing.  It has a 250 GB HARD drive installed in the case.  ESXi installed fine and I had 220 GB or more storage at my disposal.  Multiple VM installed, and once again, everything seems to work properly.

  Today, I wanted to activate usb passthrough for a Server 2008 VM I installed it, I went through the process and had to reboot the host at the end.

  After the restart, he seems to have forgotten the HARD disk that is installed and is no longer, I see my store data or virtual machine access I had running.

  There are a couple screenshots attachedthat screen what I see.

  Thanks for any help or advice!

  Is this the same controller that is attached to the 250 GB HARD drive? Passing the controller to the virtual computer may have unpresented it host, then you won't be able to access and to store configuration settings. Since this is a test system you can consider / try to run "Reset System Configuration" from the DCUI. If this does not work, you may need to reinstall ESXi of CD (the VMFS retaining of course data store).

  André

• ESXi 4 and USB data store

  Is it possible to use a USB external hard drive as the data store used by ESXi 4?  If so, how do you implement it?  Thank you very much!

  Hello

  No, I'm sorry to say that this is not supported and will not longer work.

  --

  Wil

  _____________________________________________________

  VI-box tools & scripts wiki at http://www.vi-toolkit.com