Issue of strange things in data store

Similar Questions

• SCSI local data store connectivity issues

  Hi all
  I installed the server ESXi 4.1 before six months. now, I've seen continuous events related to data store connectivity issues. I changed the SATA cable also, but it won't help. How can I fix this without interrupting the VMs.

  As ESXi before 5, it is located on the var

  You can find them easily by starting from the root directory of newspapers:

  var/log/messages of cat | grep vmkernel | less

• Strange problem after moving from the virtual computer to a new data store

  I am migrating our VM existing (8 in total) a 'problem' RAID to a new table on a new controller and am having a strange problem. Here are the steps I took (host OS is Ubuntu 8.0.4 LTS x 64):

  (1) off the power the virtual computer from the Web interface

  (2) the directories created for each virtual on the new RAID array computer (in this case a RAID 10 array on LSI 9750-8i controller)

  (3) rSync used to copy the data from RAID1 to be RAID2

  4) has created a new data store on the new RAID through the Web Server of VMWare user interface.

  (5) removed VM of the inventory through the Web, their return, added user interface then choose files .vmx on new data store on RAID2

  They have all power save fine... but three of them are not accessible on the network. I can open a console in the Web Server of VMWare user interface and they all run normally... but I can't their ping or access the respective virtual machine Web GUI. It seems quite arbitrary that those who work and those who are not. In this case... the VM that don't work is a license Autodesk, a Squid proxy server and a VM of cactus. All three of these virtual machines are 32-bit Ubuntu Server VM (two 8.0.4 and a 10.0.4)... and are the only Ubuntu VM on this host. It must be signifigant but I'm not see how.

  If I delete these three virtual machines of the inventory again and add to their original location (on the RAID1) they light up AND work normally. A consultant that we were working seemed surprised, as he had also done this experiment with some of the older VMWare products. I don't see how it would be the physical location of the files of the virtual machine. Any ideas?

  We rely on the migration to ESXi soon but in the meantime, we get these a few VM out of this RAID array problem. I'm stuck.

  Depending on the application, it may be enough to reconfigure the IP parameters (they are very probably on DHCP now) for the newly detected virtual NIC.

  André

• General issue of file on why my data store has 3 files with a _1 and _2

  OK, I'm a little new to this thing of VMware, but I was the main actor in this migration and have been the building and move all our servers to our ESX 3.5 with a back-end SAN platform.

  I did well until this weird thing, that I think that I understand, but I just don't know how to solve, or how it happened.  And right next to the bat, no I did not the instant code with this server... those that have been cleaned in the time there... Now

  My situation:

  I have virtual machines that are created equal, that they all have a 'C' drive for the operating system on another dedicated "LUNS for OS Storage" and then they have their readers of 'd' of the newspapers "SQL" on a dedicated LUN in mirror, and then the 'E' drive is on dedicated aonther "LUN DATA.

  If all servers have 2 or 3 LUNS associated with them. That's how the SAN engineer and I designed it. OK works great.  Until one day, I noticed that I was shy about 40 GB space on my SQL LUN. Took time but I think I found the culprit, but I don't know how to solve this problem, or if it will break my dose. So here I ask you all.

  One of my servers called "Server01" has 2 drives associated with it and supposedly 2 / 2 data warehouses, or even what he had initially when it was built in August!

  Now, the operating system data store is fine.

  When I'm on Console V and I click with the button straight on my server and go to his 'change settings' is what I see:

  SERVER01of properties on the "change settings of ' Advanced ' your drive hard 1" to the appropriate LUN and all the VMDK and those files are there. ""  (IE OS LUN 10)

  But "hard drive 2" pointing to the right LUNS (IE SQL LUN11), but his record is called "server01_2"?  What?    She was built and given a hard drive on this LUN, but the name of the folder is wrong.   So I'll browse my store data and low and this is, I have 3 files with the same server name (IE... ( Server01, Server01_1, Server01_2 ) OK so what happened? Why? How? and how in the heck can I get my space back 40gig?

  I checked records the name of the original server, as well as the other files on the data store with the numbers in the annex of _1 and 2 and they have all VMDK files in it... of course dates on all the VMDK files are different and I guess that since the server points to the folder called + "SERVER012" + and its VMDK file has the most recent data buffer on this subject since the last Vmotion We did it, he must then use this folder.

  OK great... but now that messes up my folder structure, and if this server does not use other VMDK files and folders he ate up to 40 GB of my precious space!

  I'm pretty sure when I went on vacation last year, because it is the time of the timestamp on the VMDK files in older records and "dates of the task of the procedures as" trying to clone, suspend, model, reconfgure, snapshot "etc. that the other members of the team tried to do something, which lead to my having 3 files on my store of data with 3 VMDK files in them.?  Nobody seems to know or remind us what it is they are trying to do... great... Well...

  I just want to know + If the server points to a folder called "Server01_2" and it has the most recent date stamp on this subject, can I then rename other files? + and then I can delete them?   And if I successful, how can I get my server to have the name of the correct folder again?    Instead of a * _2* on the end of it?

  Any suggestion would be great!    I learned the hard way that if your VM operating system is built and pointing to a file with a specific name, and you try to rename it to match the server, your operating system does not start!. LOL I hope that is not the case with a folder that has a 20gig assigned to HDD with oner VMDK file in it...

  Help!

  Thank you

  DAWNE

  No problem.  Cold migration allows you to move all your files in a data store.  You can use svmotion to move disks to different LUN, but the syntax is somewhat more complex.  The help option shows exactly how to move a machine virtual disk at a time.  Basically, you can move a disk with the config file, so basically, you move the config file and the disk of your choice in the data store that you need.  Move back the config for the original data store file, then repeat the process with the next disc.

  -KjB

  VMware vExpert

  Don't forget to leave some points for messages useful/correct.

• Issue of Cluster data store

  Hello

  Is it possible to have 4 ESXi clusters, each with their own set of SAN data warehouses, all joined to a Cluster of unique data store? I have not found exactly this configuration described anywhere. I understand there are limitations such as 32 data etc. stores and paths to data warehouses will be available from certain hosts.

  Has anyone tried this before? I'm trying to simplify investment VM for Cloud management platform.

  Thank you

  Mike

  This is a supported configuration, and I have a few clients that are running this configuration without problem. Have a look here for details: linking DRS multiple clusters in a single Storage DRS datastore cluster. - frankdenneman.nl

• SWAP file data store remove issue

  Hello

  I'm currently moving VMs to the data store newly created as well the datastore file swap. I have already change on all ESXi hosts, the data store were swap file will reside, however, I have still a few virtual machines on the old data store. I know not if I vMotion virtual machines from one host to another it will change the location for the swap file. My question is, can I just remove the old data store without affecting production not VMs remained the swapfile on the old location? Just try to find a solution faster than vMotion every single one of the virtual machines.

  Thanks for any suggestions or comments!

  Chris

  Hello

  As long as all hosts are no longer using the data store and the cluster is not defined using volume swapfile host (rather than storing with VM) then you should be able to disassemble the old swap partition.

  Bare in mind, vMotion/svMotion a virtual computer, you must be sure to move all the files and the virtual machine is set to store his exchange with the virtual machine files. Check that the old swap partition is no longer in use, and then take it apart. In theory the fastest way is to ensure that all VMs are defined to store swap with virtual machine files to the off and on again, forcing a new .vswp file in the same device. But it would of course affect your VM availability.

  I've seen in the past that even if the volume was no longer used by the guests, that guests required a restart until I managed to remove the old Exchange store data, just in case you meet that!

• Data store / latency issues with HP ProLiant DL380 G7 - controller HP Smart Array P410i after disk 2014.09.0 SPP / hpsa - 5.0.0.74 update

  Hello

  We are currently investigating massive data store and the problems of latency of disk (mainly READING) on some of our HP ProLiant DL380 G7 with P410i (BBWC) controller.

  It all started after our half of regularly updated cycle for ESXi 5.1 U2 to:

  ESXi510-201407001 (no problem)

  -hp - esxi5.0uX - bundle - 2.1.1 - 2 (no problem)

  -HP-HPUtil-esxi5.0-bundle-2.1-15 (no problem)

  -hpsa - 5.0.0.74 (pilot) & SPP2014.09.0 (-assigned problems)

  It is not a permanent increase in the latency of reading, but rather meeting points that trigger alerts of Veeam. Store of data read latency increases about 5 MS to 100 ms as soon as this happens, but after a few seconds, everything is back to normal. These data warehouses special are RAID5 (but we have also seen some alerts on RAID1), having read and write cache enabled and the most affected machines are those with the LOWEST its use.

  We have a few WinServer2012R2 RDP for a small number of sessions (less than 5) - there is no noticeable delay on work on these.

  Maybe someone of you knows a similar behavior after you apply the updates of HP ProLiant servers. We don't have any idea on what to try next, a SPP restoration is not possible, maybe the pilot, but we find the correct predecessor, as the old drivers of 2014 HPSA leads the Group on the host computer.

  Best regards

  HZ

  Hello

  most likely, you have already solved the problem... I did some research and was in contact with HP. It is a problem with the driver hpsa - 5.0.0.74. It occasionally crashes when used with P410i. In the papers, you can find "WARNING: LinScsi: SCSILinuxAbortCommands:1843: failure, pilot hpsa to vmhba0. HP knows talking and working on the new driver. As a workaround, you can use hpsa - 5.5.0.60 (at least it works well for us).

  BR

  Maachah

• Issue of SDRS to vCloud Director after you add the new data store to the Cluster of DTS

  Hi people,

  We use vCloud Director 5.5 in a vSphere full 5.5 environment.

  We have several DTS Cluster in vSphere and connected to vCloud Director.

  Following problem.

  When I add a data store to a Cluster of DTS and connect this to the corresponding storage profile data store, the storage profile is not available to vCloud Director more.

  After removing the new store data in the cluster of DTS, the profile becomes available again.

  Any ideas?

  Concerning

  Jean

  How did you the storage profile associated with the data store?  via c# client or vSphere web client?

  If you did the wrong way (c#) there no storage class label appropriate against it.

  A data cluster store has the storage class who would have all preparations of data contained inside.

  I think that you should check the service class is associated properly in vSphere web client (before adding to the DS Cluster).  Once it displays correctly, and then add the data store to the cluster.

• Issue of data store

  Hello

  Currently I have a disk (SSD) running the operating system and of my virtual machines.  I want to consolidate all of my machines at home on this machine.  I want to reuse the 3ware 9650se card to run a Raid1 and have a few VMs there to act as file servers.  I also want to have a single SATA drive for a VM acting under the name of backup.

  For recovery purposes, lets say if I have to reinstall the ESXi, the other data store on the SATA drive is recoverable?  Maybe even the readers on the 3ware if map I have reinstall the driver for the card?

  TIA,

  TT

  Evening,

  I'm not sure what you're asking... but here's my knife to 100%.  If you have two hard disks:

  Disc 1: Has ESXi and some vm

  Disc 2: VM only

  If you want to reinstall ESXi on disc 1, this could be done without destroying the virtual machine, as long as the current score has room for ESXi installation.

  Thank you

  J

• strange data store inventory list

  ESXi 4.1

  I view "Inventroy-> data warehouses" open in vsphere.  What's weird, is that it shows one of my virtual machines sitting on the local host (HDD) data store and then it also shows the same virtual machine sitting on another store of data on my SAN.  I have 4 models of installation as well as appear in the same way.  I have not any virtual machines stored in the store of data to the local host (local hard drives) so I don't know why it happens that way.  I've traveled even to check that it wasn't some kind of copy.  We never saw it?

  you have an ISO on a local storage that may be connected to a guest?  Check the virtual machine in question to see if something is mounted, also check e HARD drive to see where to point their VMDK.

• Issue of reports of data store

  Looking for a fairly simple report... I've seen reports that do what I want, but I don't have the knowledge to assemble them.

  You are looking for the following information:

  Name of data store - free space (in GB if possible) - number of virtual machines on the data store

  I found this to get the number of virtual machines on the data store:

  Get-Datastore. Sort-Object Name. Get-View | Format-Table @{Label = "Data store name"; {Expression = {$_.Info.Name}}, @{Label = 'Number of virtual machines'; Expression = {$_.} UM length}}

  That works, but I need to add a column free space.

  FreeSpace is stored in the. Property of Info.FreeSpace.

  Just add another column as

  @{Label = "FreeSpaceGB"; Expression={$_.info.FreeSpace/1gb}}

  To put it all together:

  Get-Datastore

   

   

  | Sort-Object Name | Get-View | Format-Table @{Label = "Data store name"; {Expression = {$_.Info.Name}}, @{Label = 'Number of virtual machines'; Expression = {$_.} UM length}}, @{Label = "FreeSpaceGB"; Expression={$_.info.FreeSpace/1gb}}

  See you soon,.

  Arnim

• Lost access to local data store

  Hi people:

  I have ESXi 6.0 running on an Intel S2600CWTS motherboard using the LSI SAS controller onboard and six readers Samsung 850 Pro SSD in a RAID 5 configuration.  This server is about a month and a half, and it worked fine for the first month, but in the last few weeks I started to do in the case where journal messages saying that ESXi has lost access to the data store, then, most of the time, about 15 seconds later access is restored.   Several times it took more time, which one crashed the server.  On these long, the motherboard Intel event log showed that a player had failed and began a regeneration and once the motherboard has shown that two different drives had failed, and it took both offline originally ESXi crashing.  On it that I was able to bring the two records back online via the RAID bios and everything worked fine again.  I suspect that I have hard disk problems because these discs are new and because different readers have been reported as failed, and also because no data has been lost even if 2 drives went offline at the same time.   I guess I could have a bad controller LSI, or a cable has come loose somewhere, but I expect to happen if it is really the case of data loss.

  I also noticed that lost access messages tend to appear in the log at the moment I start a virtual machine.  At first I thought that it would be one thing to flow, thinking a VM departure did a lot of IO, but this happens immediately, before even the bios of the virtual screen machine disappears, so I don't think that the virtual machine is actually reading the disc again.  In addition, as a precaution, I started the migration of some virtual machines on the server to the old server I still had available, and there is no lost access messages in the event log while that was happening, while about 50 megabytes per second of i/o has reached the disk during transfers.  I put the last patch on ESXi in mid-May, about two weeks before this started, and I begin to suspect that the patch may have something to do with it, because it seems to me that if something is happening between ESXi and the disk controller making hang up or lose interruptions during a short period of time , and I wonder if it goes pretty long if material in the motherboard sensors interpret this as some sort of hardware and simply brand failure according to readers I / O was hooked as bad then.

  Unfortunately I'm out of town now so I wanted more I had to the remote server, lest I do not not get back to the top.  I moved a couple of the most critical virtual machines from the old server which I was remotely start and transfer to virtual machines.  I also noticed that this issue tended to occur more frequently when I got to the top of the VCenter Server apparatus that any other (sometimes to others, but has happened every time I tried to start the device VCenter).  So who was the first that I moved to the old server, but strangely enough there is no error logged when I transferred the files, so the issue is not that ESXi had trouble reading the VMs vmdk file when I started it.

  I also wanted to ask you if there are any vibs for the LSI Megaraid controller on motherboard S2600CWTS I could install that would allow me to access the RAID controller without having to pick up the server and do it from the BIOS configuration screens, similar to how you can access the controller RAID from Dell while ESXi is running via a vib add-on.  So far I have not found one.

  My intention when I go to the server is to run an integrity check against the RAID 5 array via the controller and then use the AIMÉ ESXi utility on the data store to see if something is wrong here.  If not, then I guess I'll rewritten can patch.

  Ideas or suggestions welcome.

  Success!  I finally understood what the problem was corrected.  The problem is the fact that although the last vib driver LSI has been installed, for some reason any it would not automatically replace the default ESXi pilot lsi_mr3.  I did not notice that even though the latest driver package vib properly installed LSI controller was still using the original driver.  This could be considered by a 'esxcfg-scsidev - a' command showed that even "vmhba1 lsi_mr3 link-n/a sas.5001e67ca647e000 (0000:0: 00.0) controller LSI MegaRAID SAS Fury."  The second field after the controller (vmhba1) is the current manager used.  The pilot, which was to be used was: "vmhba1 megaraid_sas link-n/a unknown.vmhba (0000:03:00.0) Avago (LSI / Symbios Logic) Invader MegaRAID SAS controller.

  To fix this I had to disable the lsi_mr3 driver so that ESXi is forced to use it.  The procedure to do is the following:

  (1) make sure you have the new EXSi driver you want to use already installed.  I assume that bad things would happen if you have disabled the only driver who could run your disk controller.  Use this command to view the drivers installed: "esxcli software vib list" and you should get something similar to the following:

  [root@intelserver:~] esxcli list of software of vib

  Name Version Date seller installation acceptance level

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

  MegaRAID SCSI-sas 6.608.11.00 - 1OEM.600.0.0.2494585 Avago VMwareCertified 2015-07-19

  LSI - mr3 6.606.10.00 - 1OEM.550.0.0.1391871 LSI VMwareCertified 2015-06-19

  mtip32xx-native 3.8.5 - 1vmw.600.0.0.2494585 VMWARE VMwareCertified 2015-04-28

  ATA-pata-amd 0.3.10 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-atiixp 0.4.6 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-cmd64x 0.2.5 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-hpt3x2n 0.3.4 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-pdc2027x 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-serverworks 0.4.3 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-sil680 0.4.8 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  ATA-pata-via 0.3.3 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  block-cciss 3.6.14 - 10vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  CPU-microcode 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  EHCI-ehci-hcd 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  elxnet 10.2.309.6v - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Emulex-10.2.309.6v - 0.0.2494585 VMwareCertified-2015-04-28 VMware esx-elxnetcli

  ESX-based 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  ESX-dvfilter-credits-fastpath 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  ESX-tboot 6.0.0 - 0.0.2494585 VMware VMwareCertified-2015-04-28

  6.0.0 - 0.0.2494585 of xserver-ESX VMware VMwareCertified 2015 - 04 - 28

  IMA-qla4xxx 2.02.18 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-devintf 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-paremeter 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  IPMI-ipmi-TR-drv 39, 1 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LPFC 10.2.309.8 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSI-msgpt3 06.255.12.00 - 7vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-hp-hpsa-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-lsi-lsi-mr3-plugin 1.0.0 - 2vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  LSU-lsi-lsi-msgpt3-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU lsi megaraid sas plugin 1.0.0 - 2vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  LSU-lsi-mpt2sas-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  LSU-lsi-mptsas-plugin 1.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  Misc-cnic-register 1.78.75.v60.7 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Misc-pilots 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  NET-bnx2 2.2.4f.v60.10 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-bnx2x 1.78.80.v60.12 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-cnic 1.78.76.v60.13 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-e1000 8.0.3.1 - 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-e1000e 2.5.4 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-enic 2.1.2.38 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-forcedeth 0, 61 - 2vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-igb 5.0.5.1.1 - 5vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  NET-IGB 3.7.13.7.14iov - 20vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-mlx4-core 1.9.7.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-mlx4-en 1.9.7.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-nx-nic 5.0.621 - 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-tg3 3.131d.v60.4 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  NET-vmxnet3 1.1.3.0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  nmlx4-core 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nmlx4-en 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nmlx4-rdma 3.0.0.0 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  nVMe 1.0e.0.35 - 1vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  OHCI-usb-ohci 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  qlnativefc 2.0.12.0 - 5vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  REST 2.0.2.0088 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  Ahci SATA 3, 0 - 21vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  ATA-SATA-piix 2: 12 - 10vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  NV-sata-SATA 3, 5 - 4vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  SATA-sata-promise 2: 12 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-sil24 1, 1 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-sil 2, 3 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SATA-sata-svw 2, 3 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-aacraid 1.1.5.1 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-adp94xx 1.0.8.12 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-3, 1 - aic79xx 5vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-bnx2fc 1.78.78.v60.8 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-bnx2i 2.78.76.v60.8 - 1vmw.600.0.11.2809209 VMware VMwareCertified 2015-07-21

  SCSI-DNI 1.5.0.45 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-hpsa 6.0.0.44 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-ips 7.12.05 - 4vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-megaraid-mbox 2.20.5.1 - 6vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-megaraid2 2.00.4 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mpt2sas 19.00.00.00 - 1vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mptsas 4.23.01.00 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-mptspi 4.23.01.00 - 9vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  SCSI-qla4xxx 5.01.03.2 - 7vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  UHCI-usb-uhci 1, 0 - 3vmw.600.0.0.2494585 VMware VMwareCertified-2015-04-28

  VMware-esx-dvfilter-maclearn-1, 00 1.00 VMware VMwareCertified 2015-05-12

  xHCI-xhci 1, 0 - 2vmw.600.0.0.2494585 VMware VMwareCertified 2015-04-28

  Tools-light 6.0.0 - 0.11.2809209 VMware VMwareCertified 2015-07-21

  [root@intelserver:~

  Verify that the scsi-megaraid-sas driver is installed before proceeding.

  (2) to disable the lsi_mr3 driver do the following: "esxcli set of module system - enabled = false - module = lsi_mr3 '

  (3) reboot

  After restarting, do: "esxcfg-scsidev - a" to check megaraid_sas driver is assigned to your disk controller.

  I don't know how ESXi decided to prioritize if two or more drivers are applicable to a single hardware device, or if the installation of the new driver LSI process is supposed to disable or remove default lsi_mr3 driver and simply failed to do so.  Also, I don't know what's going to happen when I put on the next patch of ESXi, specially if the lsi_mr3 driver will be once more the priority.  If anyone knows how the driver installation process is supposed to work in this situation, please let me know.  I am so happy that I finally got this problem because the server has been seriously covered with the data store become unaccessable for 5 to 10 seconds every time a VM started or stopped, and the former driver at least once done something bad enough to deceive the controller into thinking that one of the disks has went wrong and began a RAID Resync.

• Data store space used not maching between VMWare and 3PAR

  Hello world

  I have a strange behavior between our environment VMWare and 3PAR storage system.

  I checked each data store of our cluster and for each of them, the space used in vSphere Client does not match the size of the user 'used' their volume associated with 3PAR.  The value displayed in VMware is higher.

  For example, our data store named DS03 has space around 1 TB in VMWare.  And when I checked in the Console of 3PAR, I see that the volume created for this data store has a size of the user 'used' 722 GB.

  While doing some research, I came across this post: ability to store data about the free space is not the same thing in VMware and 3PAR

  But the problem I encounter is quiet different. It's the opposite. I do not understand why the displayed value is higher in VMWare...  We are also running vSphere Server version 5.1.0

  Any advice? Ideas?

  Thank you very much.

  It's the ASIC 3PAR inline zero detection function stripping zeros of incoming data until they land on the disc. Www.3parug.com try this happens a lot.

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

• migration of data store has failed - now there are two vm - one power off?

  I was migrating a vm fw at different stores of data when a failure has occurred. They may have been cancelled or it may have been the fact that our vcenter server has restarted. I don't know if this would have caused this problem.

  In any case, now, two of the VM series two - power and the other copies are turned off. One that is off is the data store b and the virtual machine is the one data store. The strange thing is, shows of b (power off vm) data store which is where the files are located while the virtual machine is on a. When I browse a datastore I cannot find all files... It just hangs. I googled but am stuck.

  See the screenshots for more details. Thanks in advance!

  Edit: finally to load two data warehouses. They both show identical files: vmdk, vmfx, vmsd etc. for the two virtual machines on two data stores. It's weird!

  Edit 2: or vm, on or off, power to the high/off or migrate or remove from the inventory. Both are 'ping' and one that is good though.

  I figured this out. I have ssh was the host of the virtual machine is on (the two virtual machines were on the same hosts). Down to power, I ran the following command "esxcli vm kill process - type = soft - world id = xxxxx."

  That he got the vm to stop. The virtual machine of the same name already powered off then showed as "orphans". I removed the orphan vm of the inventory, the other vm started automatically acknowledgement of receipt, then I deleted the orphan vm of the 2nd data store.