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

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

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

• Cannot add host to vCenter server as data store is shared with an existing host to vCenter

  Recently, I removed a physical host to a virtual appliance of vCenter Server and am not able to add it to vCenter Server because I get an error message on the existing data store.  I run a simple server vCenter environment with two physical hosts and shared storage.  I've only been administering vCenter for a few months, so I'm relatively new on the technology and processes.  I searched the Internet for a few days now, but have not found documentation everyone has the same problem I have (which I find strange considering the simplicity my problem and configuration), so I tried to get help from the community of VMware.

  I received an error message a day this vCenter Server cannot connect to either of the two hosts so I removed the host (rather than disconnect and plug as I should have done).  Now, I am not able to connect to the host to vCenter server because the shared storage data store comes into conflict with the same data store used by the host in vCenter Server.  I get the error message is ' "Datastore"datastore_name"is in conflict with a store of data that exists in the data center which has the same URL (ds: / / / vmfs/volumes/UUID /), but is supported by different physical storage." "  I try to remove the host data store, but get the following error message: "resource" data store name: datastore_name VMFS uuid: UUID' is in use. ".  The error stack said: "'HostStorageSystem.UnmountVmfsVolume' call failed for object 'storage system' on ESXi"IP address"."  Cannot unmount volume ' data store name: datastore_name VMFS uuid: 'UUID' because the file system is busy. Correct the problem and retry the operation. "I tried to delete all virtual machines of the inventory, put the hosts in maintenance mode, restart physical hosts, but none of my troubleshooting contributes.

  I don't know what steps to take to get this data store driving with the host so that I can add it in vCenter Server.  You can provide me with any help is appreciated.

  Good thing you already moved the VMs on.  For what is 'disconnect', 'remove' or 'delete' might work anyway.  You should maybe put the host in maintenance mode or even reboot the host before you can remove data warehouses.  In an extreme case, I even had to remove the host and the hypervisor installed completely rebuild on the spot.  It is not that difficult or does not take long to reinstall, so be not afraid on this subject.  A clean reinstall could still save time compared to the deletion of data warehouses.

• Local data store renaming problem with the cmdlet set-datastore

  Hiya,

  I just started using powercli to configure my ESX Servers 4.1i.

  Most of my script version works fine - but I can't rename the local data store.

  I do a get-data store based on the name that works very well, I then pipe series-store data with a new name-, but it just seems to ignore the order and leave it with the old name.

  No error message is produced.

  I pasted in the results of the "get-data store" (just to show that it exists) and the results of the 'get-datastore piped to set-data store", below.

  I'm sure I'm missing something really obvious - but I do not know what?

  [vSphere PowerCLI] D:\powershell > get-datastore-name 'test1' | fl

  
  DatacenterId: Datacenter-ha-datacenter
  Datacenter: ha-datacenter
  ParentFolderId: Folder-ha-folder-datastore
  ParentFolder: datastore
  DatastoreBrowserPath: vmstores:\ohst213vmh.blah.co.uk@443\ha-datacenter\test1
  FreeSpaceMB: 64207
  CapacityMB: 64768
  Accessible: true
  Type: VMFS
  ExtensionData: VMware.Vim.Datastore
  ID:-Datastore-4d4c2877-c48e1465-b0be - 00237d 358458
  Name: test1
  UID: /[email protected]:443 / Datastore = Datastore-4d4c2877-c48e1465-b0be-002
  37d 358458.

  [vSphere PowerCLI] D:\powershell > get-datastore-name "test1" |-store game data-name 'test2' | fl

  
  DatacenterId: Datacenter-ha-datacenter
  Datacenter: ha-datacenter
  ParentFolderId: Folder-ha-folder-datastore
  ParentFolder: datastore
  DatastoreBrowserPath: vmstores:\ohst213vmh.blah.co.uk@443\ha-datacenter\test1
  FreeSpaceMB: 64207
  CapacityMB: 64768
  Accessible: true
  Type: VMFS
  ExtensionData: VMware.Vim.Datastore
  ID:-Datastore-4d4c2877-c48e1465-b0be - 00237d 358458
  Name: test1
  UID: /[email protected]:443 / Datastore = Datastore-4d4c2877-c48e1465-b0be-002
  37d 358458.

  See you soon

  Jordan

  When you add a server ESX to vCenter, agent VirtualCenter (vpxa) service is installed on the ESX Server.

  All actions you take in the vSphere ESX server customer or a PowerCLI script when you are connected to the vCenter, passed through this vpxa service. This service manages the resources on the ESX Server.

  To avoid problems when you change some resources directly from the COS of ESX, vpxa services locks these resources.

  That's why you can not change the datastorename when you are connected directly to an ESX Server that has been added to a vCenter.

  BTW, if you connect a vSphere client directly to the ESX Server, you will see the same phenomena as what you see in your script PowerCLI.

  If you need to change the datastorename locally on the ESX for some reason, you can try to remove the ESX Server with Remove-VMHost to vCenter, connect to the server with Connect-VIServer ESX, make your changes and add it to the vCenter with Add-VMHost.

• How to specify what data store for use with OVFtool

  It drives me crazy! Way that you specify what data store to use when there are several?

  I ran exactly the same command on a box that had a data store and it worked fine (as expected). He created the folder of the virtual machine to the root of the SD and then pulled on the virtual machine of the FVO. However, with multiple it just says not: no datstore target specified. I tried 1 million combinations of?-ds = with hooks, without. It is said to be sometimes found in the inventory. I guess that's looking for a folder. But this cannot be so difficult?

  C:\Program VMware OVF tool & gt; ovftool P:\Downloads\PanoManagerVM-2.8.0

  -ovf\panomanager.ovf ' vi: / / [email protected].

  Source OVF opening: P:\Downloads\PanoManagerVM-2.8.0-ovf\panomanager.ovf

  ATTENTION: No manifest file

  Please enter the login information for the target vi://192.168.1.5/

  User name: root

  Password: *.

  Target of opening VI: vi: / / [email protected]/

  Error: No data store target specified

  Data warehouses is on target:

  SAN storage

  storage1

  something like

  OVFTool - ds = "SAN Storage" source target

  should work

  If you write ovftool - help you can see the full syntax.

  Eske

• Data store growing VMFS with the running virtual machine

  Hey, gentlemen.

  Have a quick question. We have configured incorrectly datastore VMFS on VM production, basically, is size of the SAN LUNS to 1.99 and virtual disk was created as thin provisioned and 2 TB.

  vSphere shows no free space. I intend to grow data store, we found 100 GB also on SAN and I have an add on vsphere.

  I'm not sure we need to stop the VM to make this change?

  I guess not, because Guest OS should see no change - drive keep 2 TB, changes will happen only at the level of vSphere.

  If I have good documentation of VMware on VMFS, one of the main benefits of VMFS is:

  http://www.VMware.com/files/PDF/VMFS-best-practices-WP.PDF

  Facilitates the dynamic growth

  Through the use of a volume management layer VMFS allows an interface to storage resources so that several

  types of storage (Fibre Channel, iSCSI and FCoE) can be presented as warehouses of data on which virtual machines can

  resident. What allows a dynamic growth of these storages of data through the aggregation of storage resources provides the

  ability to increase a shared without incurring downtime storage resource pool.

  This means that I didn't stop Guest OS to make such changes?

  Thank you in advance!

  This means that I didn't stop Guest OS to make such changes?

  Yes, you need not shutodown comments and/or host.

  Just check out this recommendation from VMware:

  Note: If the LUN knows a high i/o rate by cultivating the VMFS, the ESX host isn't able to complete the operation. In this case, repeat the operation after hours and when backup operations are not executed. If the problem persists, turn off some of the virtual machines that reside on the LUN, and then try again.

  Source: VMware KB: growing or expand a VMFS volume or data store

• Smart Array P440ar: ProLiant DL380 g9 & controller Smart Array boot order

  Work on a server of gen9 ProLiant DL380 (SFF) with an of P440ar (version 3.00) at location 0 (embedded RAID) and a controller (version 2.52) P840 to location 1. I have the P440ar connected to the risers on the front of the system, and I'm starting off the P840 6.5 RHEL. If no hard drive is attached to the P440ar, it works, but if all the disks are connected to the P440ar, the boot device is not found. I tried to change the order of boot in RSBU controller, but the P440ar was the ONLY listed controller. I didn't even have an option to change the P840.

  Am I allowed to configure the system in this way?

  After fighting with it for several days, I deleted the system P840 and started with just the P440ar. Then I added the P840 in the system and restarting, the system automatically added the P840 to startup controller command list. Works fine now.

• PowerEdge T-420 with Perc 310 - how do controller ports relate to the physical disks

  I understand that Perc 310 has two connectors for SAS, each controller has four ports.  However, I can't end on how they relate to real disk slots in the bottom of basket.

  We will have four disks raid 1 + 0, and I want to make sure they are properly prepared so that if a channel controller fails it has the right mix of disks on the other channel continues to run.

  Thank you

  Sorry NickC_UK

  It would be 0-7 on the SAS and SAS b 8-15.

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

• Commit photos with different data stores

  I have a question of space with one of my servers.  We have a 300 GB LUN with essentially a 300 GB VMDK (for simplicity).  We moved the file access to a data store VMX different with a lot of storage space so that when you take a snapshot he will have space to keep the delta files.  My question though is when he goes to renew their commitment, there will be more space required on the data store where the VMDK or recommit this space will be used on the data store where the VMX file?  I've always heard that instant reengagement essentially requires free space equal the size of instant collective delta files.  Does it matter if the VMDK is thick or thin?  Obviously thin can extend but I mean for snapshots.

  Thank you!

  John

  Therefore the Consolidation assistance snapshot gets created with all other delta files?

  The 'Consolidation' Helper is like another instant and only created if you remove snapshots, while the virtual machine is up and running.

  .. instant .single can only grow to the size of the VMDK (so thin provisioned space) parent...

  That's right, a single snapshot can only grow to the size of the basic disk (more a minor overload, see http://kb.vmware.com/kb/1012384), because it contains only modified data blocks and a mapping table.

  André

• Expansion / Upgrade ProLiant DL380 G5 and ProLiant DL360 G5

  Hi all, we have two servers, Proliant DL380 G5 with SmartArray 400 and Proliant DL360 G5 with SmartArray 200icontroller controller, expand us on the disks, memory and cards network, the problem is that after we see the documentation which is sometimes wrong and don't know not the limitations of each of the parties, the issues are:

  Proliant DL380 G5 SmartArray 400:
  - STORAGE: up to 8 SAS / SATA, not clear what size that can be used with this controller, we understand that up to 500 GB SATA 7200 RPM and maximum 2 TB SAS 7200 RPM, we currently use with 146 GB drives to 10,000 rpm, whose original documentation is the maximum allowed value.
  -MEMORY: Up to 64 GB modules of maximum memory up to 8 GB.
  - NETWORK: update with PCI Express, support cards that I can find are HP NC110T PCI Express and PCI-Express HP NC373 HP NC360T PCI-Express.

  Proliant DL360 G5 SmartArray 200i:

  - STORAGE: up to 4 SAS / SATA controller supports only 200i SmartArray four drives in RAID 0, 1, 1 + 0 if we wanted to expand to six bays that are available on the disk server, it would change the controller and memory. Yet, the size of disk maximum supported based on the documentation is 72 GB SAS and SATA drive 60 GB, but looking it seems as if you agree at least 300 Gb SAS disks at 10 000 rpm and up to 500 GB 7200 RPM.
  - MEMORY: up to 64 GB maximum memory modules up to 8 GB.
  - NETWORK: update with PCI Express, support cards that I can find are HP NC110T PCI Express and PCI-Express HP NC373 HP NC360T PCI-Express.

  This is what I have gathered and what interests me in the expansion and to say that the documentation I found to give the feeling of this conflict, is perhaps by the dates of their procedures, but before you make a payment would guarantee the purchase. Also getting information guides, manuals and forums, I have also consulted compatibiliy HP Proliant Server Guide, so I have consutlado with HP before purchasing, but have yet to receive an answer.

  A greeting and thank you very much

  Hello jranerosc. I think you'd have better luck trying Business Forums of HP. You should get more specific help.

  Have a great day!

• 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

• Extension of a data store

  Hello

  I'm trying to expand my existing data store size. I have a HP Proliant DL370 G6 with a Smart Array P410i. I've added 4 additional disks and expanded the chart via HP Array Configuration Utility, so all readers are added at home and in vSphere 4.1 search it shows as having the ability 'new' to 1.9.

  The problem is, when I go in vSphere under Configuration, storage, it shows "total capacity" 833 GB (original capacity when it was created). When I look under the box "Measuring device", it shows the ability of 'new' of 1.91 TB.  (see attached photo)

  If I click on the button 'Increase' it starts the Wizard "Measurement device", but I get nothing that appears in my list and I can't hit next to continue the wizard. I assumed it would be where I can specify the new piece of storage, I added to enlarge the data store but nothing shows, so I'm at a loss. Any thoughts?

  

  Here is a picture of the wizard of the measuring device

  Thank you.

  Welcome to the community,

  increase the VMFS partition on the installation disc is not possible using the GUI. For a description, take a look at http://deinoscloud.wordpress.com/2010/05/03/how-to-increase-the-size-of-a-local-datastore-on-an-esxi4/

  Warning: Make sure you only select the VMFS partition during this operation. In the example it is partition 2, but it could be the 3 with your installation partition!

  Although it should work without problem, I highly recommend you backup the existing VM before doing this.

  André

• Can't see the logical volume when creating data store - vSphere 4.1

  Hi guys, got another problem with ESXi 4.1 on a HP Proliant ML350 G6.

  ESXi 4.1 update 1 has been installed successfully on the server on an internal USB. Our next step is to create a store of data through the vSphere client.

  The server has five 500 GB SAS configured in a RAID 5 array drives. The server has a HP Smart Array P410i RAID controller. I see five physical disks and logical volume of about 2.3 TB in RAID Utility. However, when access us the hypervisor via the vSphere client and try to create a data via a storage LUN/local store, the display shows then no logical volumes or the drive bays on which to create a data store.

  We are usnure why this is, as the ESXi 4.1 installation program could see this logical volume when I was installing the hypervisor, but he does not appear in vSphere for use in a data store.

  If anyone can help?

  Thank you very much.

  Each disk must be less than 2 TB - 512b