P2000 Volume sizes as seen by ESXi 5

Similar Questions

• I'm running out of room on a Pentium 3 computer, volume size 14,30 GB using Windows XP Home Edition

  original title: Windows XP Home Edition

  I'm running out of room on a Pentium 3 computer, volume size 14,30 GB using Windows XP Home Edition. This computer is no longer connected to the internet. I did a 'new' installation of the XP disk in an effort to remove unwanted files, but they remain on the computer, too much space? I have 22% free space (3,19 GB). I have the drivers for 2 printers on the computer, 1 regular printer (.38 MB) and 1 photo (63,63 MB). These are only currently installed programs, I put on the computer after the installation of "new". When I try to use the cleaning disc, the screen says I have 539ko internet temporary files and 32 KB of web client / Publisher temporary files. When I try to view these files, this screen is 'empty' or hidden? If I "check mark" these files and tell the computer I don't know I want to remove them, a screen indicates that they are being deleted (this screen only lasts a fraction of a second)?  but they are stll on the computer. Sometimes it deletes temporary internet files only to "come back" and the size can be different?  I tried to run the Disk Defragmenter (it took a lot of time). When I look at the report, I have a long list of files that it could not defragment? An example would be \ documents and settings------quest-my documents-my... I can't find these files? In addition, the computer is reminding me that I have so many days to activate windows after running the XP disk again. Thank you!

  Do a "new installation" Windows to remove unwanted files, it's a bit like swatting flies with a hammer.  And in your case, the hammer was apparently missed.  And, as you have discovered, you have now re - activate.  I hope that you still have your ID handy product.

  What are the files that are too much space and you want to delete?
  Consider to download and execute JDiskReport, a small utility in Java that will graphically show you what files take up more space on your drive.  In order to do this, however, you need to install Java, available here: http://www.java.com/en/

  Here's how to do a "clean" Windows XP installation, which includes the step of the formatting of the hard drive (otherwise said, the Windows CD not implementing in the form as part of the installation process; you don't need any other disk, diskette or other):

  http://www.theeldergeek.com/xp_pro_install_-_graphic.htm
  http://michaelstevenstech.com/cleanxpinstall.html

  There are important things to think before you do another reinstall.

  Although your computer will probably work after a clean install of Windows XP, some of the features of your material are not available until you install the specific drivers for this hardware (rather than the drivers built into Windows XP).  The most likely problems are the video and audio, but since your computer is very old, it is likely that Windows XP has an enough information on your hardware it will, in fact, work OK.

  Unless the Windows XP CD you already includes Service Pack 3, if you're ever going to connect the computer to the Internet, you must install Service Pack 3 (and subsequent critical updates).  The best way to do is to connect the computer to the Internet and go - only - to http://www.update.microsoft.com , even if you're never going to connect to the Internet, Service Pack 3 may have included updates of Windows features you want to use.

• Error adding mirror for Volume - size boot sector?

  Hello

  I'm trying to set up a software RAID 1 on my boot volume.  When I click on "Add Mirror" and choose the other HDD there is a long pause, then I get the message: "all the disks holding the extensions for a given volume must have the same size of sector and the sector size must be valid."

  Hard drives are the same and I didn't format or other of them.  How can I fix?

  Thank you!

  Chris,

  Thanks for the reply.  I'm still confused: If the disk does not contain the operating system, why delete the partition of reserve would interfere with the ability of the computer to boot to the operating system drive?  Also, if the 2nd disc had a different file system than the first and I can create a mirror between the discs as they are, why can't create a mirror of the patition OS?  Is it possible to have different systems files on different partitions, and if so, why doesn't windows simply create a file system in the space unallocated during mirroring?  If this isn't the case, file systems must match or no mirror between readers would be possible, right?

  Thank you

  Steve

  If you are wanting to use win7 software raid, IMO not a good idea, the discs should be dynamic, and if you see a partition reserves so clearly that the disc has been formatted previously

• Increase in size of data store ESXi after increasing the size of the LUN

  Hi all

  Scenario is as follows.

  Remote site with Dell r710 ESXi 4.1 servers 2, 1 Dell MD3200i SAN with 12 600 GB drives.

  Initially when I implemented the San, I created 2 LUNS with 1 TB in each LUN.

  Now, we ran into a situation where we have 1 server which is now need more than 1 TB of sapce on it.

  I've reconfigured the table and now have a unit number logic that I spent in 2 TB to 1 TB and I now need to increase the store of data on the ESX Server.

  If I increase the size he reformatted the LUN whole or just the free space that I create?

  I don't want to remove any exisitng s VM on the SAN.

  maximum size of a vmfs is 2 TB-512 b only. extend wouldn't format the LUNS. Look at this blog: http://www.yellow-bricks.com/2009/03/26/resizing-your-vmfs-the-right-way-exploring-the-next-version-of-esxvcenter/

• Size Max VMDK in ESXi 4.1

  VMDK in ESXi 4.1 maximum size cannot be larger than 2 to 512 Byets? Choose the block size of 128 MB?  Thank you.

  Max is 2 TB minus 512bytes

  http://www.VMware.com/PDF/vSphere4/R41/vsp_41_config_max.PDF

• A procedure to follow to change the block of VMFS Volume size?

  We use a VMFS volume with size of 1 MB blocks.  As the virtual HD size must be greater than 256 GB, to change the size of the block to 2 MB.

  We would like to confirm that the following is correct:

  (1) to migrate all VM this VMFS volume

  (2) delete this VMFS of ESX Cluster

  Add 3) as storage again

  4) format with the 2 MB block size

  Is it Miss?

  Thank you

  There is not another possible procedure

  But as already shown reflect the selection of block size.

  ---

  MCSA, MCTS, VCP, VMware vExpert 2009

  http://blog.vadmin.ru

• investigating the slot sizes and ESX and ESXi 4 4 classic

  I was looking for to set the AP following advanced settings option:

  das.slotCpuInMHz

  das.slotMemInMB

  The reason why because that I don't use of tickets in a few groups of ESX host, but I don't want the slot by default size to use.  So I have a cluster of the armies of ESXi4 and went in the advanced options of the AH and set these parameters, and when I go under Advanced tab LENGTH info summary of cluster slots have clearly changed.  When I try to do the same process on a classic cluster ESX 4, by adding in the settings for the advanced options of the AH, nothing changes in the advanced performance info.  It's as if the settings do not work with ESX classic 4.  These functions only work on ESXi 4 and not ESX 4 classic?

  You can change the size of the slot, but be careful with these settings. Think twice before you edit and do not set a level of memory.

  This is the very good detailed explanation how it works: http://www.yellow-bricks.com/vmware-high-availability-deepdiv/

  ---

  MCSA, MCTS, VCP, VMware vExpert 2009

  http://blog.vadmin.ru

• size of the lowest data store then show storage

  Hello, I do not know why, when I add a new logical unit number data store to what I created in the storage appear at the VMware and then further down in storage.

  for example, I created a new LUN in the storage of 60 GB in size. but when I add a data store that LUN appears only 55.88 GB to 60 GB. where are the others? where are other 4.2 GB of my logic unit number. in storage, it appears with 60 GB.

  Why VMware view only 55, 88 GB 60 GB?

  Follow attached shows a screen created datastore

  Thank you

  Just support Document from HP HP StorageWorks MSA P2000 - Volume size difference between the OS and the MSA.

  André

• What size of volume is a reference to?

  In the paper "Configure maximum' vSphere"Maximum storage"article, there is a line item for the size of the Volume (below).

  What exactly is that reference?

  Volume size 64 to minus16K

  Volume is not the same as the logical unit number. In order to exceed the size of the LUN, you must use extensions.

  Hello.

  What exactly is that reference?

  The maximum volume size for a VMFS volume that is created from the use of the extensions with multiple LUNS.  A single LUN cannot 2 TB - 512 bytes, but the volume can be much bigger by using extensions.

  Good luck!

• ESXi 6.0 U1 U2 upgrade, iSCSI questions

  Hello

  First post, so I'll try and summarize my thoughts and what I did with troubleshooting.  Please let me know if I left anything out or more information is required.

  I use the free ESXi 6.0 on a Board with a CPU Intel Xeon E3-1231v3 and 32 GB of DDR3 ECC UDIMM mATX to Supermicro X10SLL-F.  I use a 4G USB FlashDrive for start-up, 75 GB 2.5 "SATA to local storage (i.e. /scratch) and part of a 120 GB SSD for the cache of the host, as well as local storage.  The main data store for virtual machines are located on a target (current running FreeNAS 9.3.x). iSCSI  This Setup worked great since installing ESXi 6.0 (June 2015), then 6.0 U1 (September 2015) and I recently made the leap to 6.0 U2.  I thought everything should be business as usual for the upgrade...

  However, after upgrading to 6.0 U2 none of the iSCSI volumes are "seen" by ESXi- vmhba38:C0:T0 & vmhba38:C0:T1, although I can confirm that I can ping the iSCSI target and the NIC (vmnic1) vSwitch and VMware iSCSI Software adapter are loaded - I did not bring any changes to ESXi and iSCSI host before the upgrade to 6.0 U2.  It was all work beforehand.

  I went then to dig in the newspapers; VMkernel.log and vobd.log all report that there is not able to contact the storage through a network issue.  I also made a few standard network troubleshooting (see VMware KB 1008083); everything going on, with the exception of jumbo frame test.

  [root@vmware6:~] tail - f /var/log/vmkernel.log | grep iscsi

  [ ... ]

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T: 0 CN:0: iSCSI connection is being marked "OFFLINE" (event: 5)

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

  (2016 03-31 T 05: 05:48.217Z cpu0:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:41620 r L: 0: 10.xxx.yyy.109:3260]

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba38:CH:0 T:1 CN:0: connection iSCSI is being marked "OFFLINE" (event: 5)

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: TARGET: TPGT (null): TSIH 0: 0]

  (2016 03-31 T 05: 05:48.218Z cpu4:33248) WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 10.xxx.yyy.195:32715 r L: 0: 10.xxx.yyy.109:3260]

  [root@vmware6:~] tail - f /var/log/vobd.log

  [ ... ]

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023006us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T0

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622023183us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to iqn.2005 - 10.org.freenas.ctl:vmware - iscsi because of a network connection failure.

  2016 03-31 T 05: 05:48.217Z: [iscsiCorrelator] 1622002451us: [esx.problem.storage.iscsi.target.connect.error] connection iSCSI target iqn.2005 - 10.org.freenas.ctl:vmware - iscsi on vmhba38 @ vmk1 failed. The iSCSI Initiator failed to establish a network connection to the target.

  2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023640us: [vob.iscsi.connection.stopped] iScsi connection 0 arrested for vmhba38:C0:T1

  2016 03-31 T 05: 05:48.218Z: [iscsiCorrelator] 1622023703us: [vob.iscsi.target.connect.error] vmhba38 @ vmk1 could not connect to

  [root@vmware6:~] ping 10.xxx.yyy.109

  PING 10.xxx.yyy.109 (10.xxx.yyy.109): 56 bytes

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,174 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,238 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0,309 ms

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.174/0.240/0.309 ms

  vmkping [root@vmware6:~] 10. xxx.yyy.109

  PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 56 bytes

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 0 ttl = 64 time = 0,179 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 1 ttl = 64 time = 0,337 ms

  64 bytes from 10. xxx.yyy. 109: icmp_seq = 2 ttl = 64 time = 0.382 ms

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 3 packets received, 0% packet loss

  round-trip min/avg/max = 0.179/0.299/0.382 ms

  [root@vmware6:~] NF - z 10. xxx.yyy3260.109

  Connection to 10. xxx.yyy3260.109 port [tcp / *] succeeded!

  [root@vmware6:~] vmkping 8972 10 s. xxx.yyy.109 - d

  PING 10.xxx.yyy.109 (10. xxx.yyy. 109): 8972 data bytes

  -10. ping.109 xxx.yyystats-

  3 packets transmitted, 0 packets received, 100% packet loss

  I began to watch the drivers NIC thinking maybe something got screwed up during the upgrade; not the first time I saw problems with the out-of-box drivers supplied by VMware.  I checked VMware HCL for IO devices; the physical NIC used on that host are Intel I217-LM (nic e1000e), Intel I210 (nic - igb) and Intel® 82574 L (nic-e1000e).  Lists HCL from VMware that the driver for the I217-LM & 82574L should be version 2.5.4 - I210 and 6vmw should be 5.0.5.1.1 - 5vmw.  When I went to check, I noticed that he was using a different version of the e1000e driver (I210 driver version was correct).

  [root@vmware6:~] esxcli list vib software | e1000e grep

  Name Version Date seller installation acceptance level

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

  NET-e1000e 3.2.2.1 - 1vmw.600.1.26.3380124 VMware VMwareCertified 2016-03-31

  esxupgrade.log seems to indicate that e1000e 2.5.4 - VMware 6vmw should have been loaded...

  [root@esxi6-lab: ~] grep e1000e /var/log/esxupdate.log

  [ ... ]

  # ESXi 6.0 U1 upgrade

  2015-09 - 29 T 22: 20:29Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to "/ tmp/stagebootbank".

  [ … ]

  # ESXi 6.0 U2 upgrade

  2016-03 - 31 T 03: 47:24Z esxupdate: BootBankInstaller.pyc: DEBUG: about to write to payload "net-e100" of VIB VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585 to ' / tmp/stagebootbank '

  3.2.2.1 - 1vmw e1000e is recommended for 5.5 U3 and not 6.0 U2 ESXi ESXi driver!  As these drivers are listed as "Inbox", I don't know if there is an easy way to download the drivers supplied by seller (vib) for him, or even if they exist.  I found an article online to manually update drivers on an ESXi host using esxcli; I tried check and install the new e1000e drivers.

  [root@vmware6:~] esxcli software update net-e1000e-n-d vib https://hostupdate.VMware.com/software/VUM/production/main/VMW-Depot-index.XML

  Result of the installation

  Message: The update completed successfully, but the system must be restarted for the changes to be effective.

  Restart required: true

  VIBs installed: VMware_bootbank_net - e1000e_3.2.2.1 - 2vmw.550.3.78.3248547

  VIBs removed: VMware_bootbank_net - e1000e_3.2.2.1 - 1vmw.600.1.26.3380124

  VIBs ignored:

  As you can see there is a newer version and installed it.  However after restarting it still did not fix the issue.  I even went so far as to force the CHAP password used to authenticate to reset and update on both sides (iSCSI initiator and target).  At this point, I wonder if I should somehow downgrade and use the driver of 2.5.4 - 6vmw (how?) or if there is another issue at play here.  I'm going down a rabbit hole with my idea that it is a NETWORK card driver problem?

  Thanks in advance.

  --G

  

  I found [a | the?] solution: downgrade for 2.5.4 drivers - Intel e1000e 6.0 U1 6vmw.  For the file name, see VMware KB 2124715 .

  Steps to follow:

  1. Sign in to https://my.vmware.com/group/vmware/patch#search
  2. Select ' ESXi (Embedded and Installable) ' and '6.0.0 '.  Click on the Search button.
  3. Look for the update of the release name - of - esxi6.0 - 6.0_update01 (released 10/09/2015). Place a check next to it and then download the button to the right.
     
  4. Save the file somewhere locally. Open archive ZIP once downloaded.
  5. Navigate to the directory "vib20". Extract from the record of the net-e1000e.  In East drivers Intel e1000e ESXi 6.0 U1: VMware_bootbank_net - e1000e_2.5.4 - 6vmw.600.0.0.2494585.vib
     
  6. This transfer to your ESXi Server (be it via SCP or even the file within the vSphere Client browser). Save it somewhere you will remember (c.-a-d./tmp).
  7. Connect via SSH on the ESXi 6.0 host.
  8. Issue the command to install it: software esxcli vib install v - /tmp/VMware_bootbank_net-e1000e_2.5.4-6vmw.600.0.0.2494585.vib
     
  9. Restart the ESXi host.  Once it comes back online your datastore (s) iSCSI / volumes should return.  You can check by issuing h df or the list of devices storage core esxcli at the CLI prompt.  vSphere Client also works
  
  

  It took some time to find the correct file (s), the steps and commands to use.  I hope someone else can benefit from this.  I love that VMware can provide for virtualization, but lately, it seems that their QA department was out to lunch.

  Do not always have a definitive explanation as to why Intel e1000e ESXi 5.5 U3 drivers were used when ESXi 6.0 U1 U2.  Maybe someone with more insight or VMware Support person can.

  & out

  --G

• PowerCLI reports wrong of the LUN size when perennial reservations are met * and * size of the LUN is changed.

  My question is: is this expected behavior?

  In short, the situation is this: we have a cluster running ESXi 5.5.0 build 1746018. Two guests Windows Server R2 2012 are running a SQL Server Cluster (MSCS), making use of RDM with a physical SCSI emulation. Which requires LUNS of perennial reservations activated. All is well until the customer decides to expand two of the LUNS. PowerCLI continues to account for the original size of those LUNs, which breaks our reports.

  Logically, it makes sense, but it still seems a bit of an ejection. Has anyone seen elsewhere this behavior and you have found ways around it?

  See you soon!

  You didn't say how to retrieve the size of the LUN.

  If not through esxcli, not the following returns the correct size (change the hostname ESXi and LUN canonicalname)?

  $esxcli = get-EsxCli - VMHost MyEsx

  $esxcli.storage.core.device.list ('naa.60050768123455af1800009876000023')

• free "original vmware' update esxi5 for HP custom esxi 5.1

  Hi @all

  I have a question about the upgrade of an original vmware esxi 5.0 (free version!) on a G7 HP Proliant DL 380 with HP P2000 G3 MSA SAS attached to esxi 5.1

  I can use the customized image of hp for this upgrade or do I use the "VMware ESXi - 5.1.0 - 799733 - depot.zip ' VMware? '"

  https://my.VMware.com/group/VMware/details?downloadGroup=HP-ESXi-5.1.0-GA-10SEP2012 & ProductID = 285

  I have several drivers HP and for example the HP ESXi installed Bundle offline...

  How can I preserve the 3rd third-party drivers installed and beams when I update? the 3rd party drivers and the beams are compatible with esxi 5.0? (I thought it would be great if I can go to the image of HP custom because everything I need is built into this image :-))

  someone has done this before? I have to do it on a production system and I don't really have any other HP hardware to test the vom vmware esxi 5.0 for hp upgrade custom esxi 5.1

  Thanks for your help!

  Kind regards

  Klaus

  Hello vmklaus,

  It works smoothly, and you have two options:

  (a) download the file from VMware "VMware-ESXi-5.1.0-799733-HP-5.34.23.zip" (found on https://my.vmware.com/group/vmware/details?productId=285&downloadGroup=HP-ESXI-5.1.0-GA-10SEP2012) and put them in the data store.

  Then SSH to your ESXi and fire following command:

  Update profile of software esxcli d vmfs/volumes / [your datastore] / [your folder]/VMware-ESXi-5.1.0-799733-HP-5.34.23.zip Pei HP-ESXi 5.1.0 - semi-trailer]

  (b) download the VMware 'VMware-ESXi-5.1.0-799733-HP-5.34.23.iso' file, burn the bootable ESXi HP-Branded 5.1 Installation on a CD for the deployment more far.

  Don't forget to load the updates, available on http://www.vmware.com/patchmgr/findPatch.portal

  Please keep in mind that the HP SmartArray real driver has a bug. It displays an alert on the Firmware even if you load the current Firmware.

  Kind regards

  Josip.

• Necessary for ESXi 5.0 RAID?

  Hi all

  I am quite new to this VMware and it's our first test of society on the implementation of the VM solution to our test environment.

  So please be generous if my question is redundant or I'm a bad advice.

  Our server is HP Proliant DL380 G5 server, and we bought the license VMware Essential Kit.  (installing ESXi 5.0 planning)

  As most of you already know, HP servers have this thing SmartStart which helps the user RAID disks before installing so that cases of dysfunction of a disk, the mirror will do its job until the fix.

  But when I was reading the other articles, it is said that esxi will not recognize software RAID?

  Also, no ESXi have some type of built in resources distribution system that allows virtual machines to function even if one or two hosts readers a malfunction?

  Corrections, suggestions and questions are welcome.

  Moreover, since it is the test environment, HP box is the only host (about 3.8 TB) and we intend to run about 4 ~ 5 VMs.

  Thank you

  Welcome to the community,

  most of the DL380 G5 models come with a built in P400 SmartArray RAID controller, which is a hardware RAID controller supported. The RAID functionality is completely transparent for ESXi in this case (for example, rebuilding after a fialure). So nothing to worry about this controller

  Regarding the size of disk/RAID you mentioned, you may need to divide the RAID in several logical volumes using the ACU (Array Configuration Utility) as a result of a problem with the currently used driver (see http://kb.vmware.com/kb/2006942). I would recommend that you create a logical volume of 10 GB for ESXi and divide the disc space remaining in two logical volumes for use VMFS data warehouses.

  BTW. the controller has BBWC (battery backed write cache)? This is very important and makes a HUGE difference in the performance of the disk.

  André

• ESXi 4.1.0 and local storage

  I have a new installation of ESXi on a new dell Server 4.1.0.  The server is a 4 TB RAID controller.

  Two related questions:

  1. once I have create my first data store (say 100 GB) on this controller and try to create a 2nd... the controller is no longer visible in the addition of storage & gt; disk/lun & gt; Select the disk/lun dialog.  ESX is limited to a data store local by controller or by physical volume or something like that?  (when I delete the first store of data, the controller is displayed again once again.)

  2. I am familiar with the "block size limit problem file size" during the creation of data warehouses.  My goal is to put a virtual record of 3.5 to on a local data store.  The largest block size available is 8 MB that will allow me to make a 2 TB vmdk.  The best way to achieve this just do two vmdk and they extend inside the guest virtual computer (Server 2 K 8 R2), or is there a more elegant way to do at ESX level and provide the guest with a full volume?

  I have a new installation of ESXi on a new dell Server 4.1.0.  The server is a 4 TB RAID controller.

  ESX supports the LUN/Volume sizes up to 2 TB - 512 bytes. You must divide the RAID.

  1. once I have create my first data store (say 100 GB) on this controller and try to create a 2nd... the controller is no longer visible in the addition of storage > disk/lun > select disk/lun dialog.  ESX is limited to a data store local by controller or by physical volume or something like that?  (when I delete the first store of data, the controller is displayed again once again.)

  Due to the partition of the ESXi installation partition, you can create 1 VMFS partition/data store. Furthermore, VMware does support only 1 VMFS datastore by volume.

  2. I am familiar with the "block size limit problem file size" during the creation of data warehouses.  My goal is to put a virtual record of 3.5 to on a local data store.  The largest block size available is 8 MB that will allow me to make a 2 TB vmdk.  The best way to achieve this just do two vmdk and they extend inside the guest virtual computer (Server 2 K 8 R2), or is there a more elegant way to do at ESX level and provide the guest with a full volume?

  I guess ranging in Windows is your only option.

  and then, when I create a data store with a block size of 8MB / 2048... maximum file size it creates the partition as only 558GB even if I chose "maximize capacity" and the volume is empty!

  ESXi only supports 2 TB - 512Bytes by volume. If you have a larger one you won't be able to use the volume size less (to n * 2). For example 4.5 TB - TB 2 * 2 = 0.5 to.

  With a 4 TB RAID, I recommend that divide you the RAID in several logical volumes. I would create a volume to only operating system (ESXi) and a small store of data for example ISO with a volume of 50 GB files. Then create several volumes with max 2 TB - 512 bytes.

  André

• Cannot create a volume larger then Go 212

  Hello

  I created a volume of 12 to on equallogic storage and I'm trying to connect it with a bit of esxi servers.

  Once the storage adapter detects the volume it see all 12 s to.

  But when I try to create a store of data from this volume in vSphere I'm limited to 212GB and I can't create a larger volume.

  Any suggestions are welcome.

  Thank you

  Haris

  Hello and welcome to the forums.

  The maximum volume size is 2 TB - 512 bytes. It is documented in KB 3371739 - you will need to carve up this storage in an appropriate manner.

  Good luck!