script to create the folder on the data store please

Hi all!

I'm having difficulties writing a powercli script to create a file on a data store... we have a mixture of guests ESX 3.5, 4.0 and 4.1, using data storage mounted via NFS.

For work I do, I need to:

(1) create a folder on a data store (check that the folder does not already exist).

2) navigate to the folder

(3) and check if a particular file exists in this folder.

The problem is that the context of my current position makes the code does not. the get-location method returns "C:\temp\ESX", being the record that I run the test script to. I try to use set-card with various settings to try to change the location of a particular data store, but it does not yet work-get-location returns "C:\temp\ESX".

I think that the code for step 3) above is ok, but I can't get any code to work for) 1 and 2).

can someone please?

Thank you

Ross.

You must use the vimdatastore provider to access your data warehouses.

It is documented in vSphere PowerCLI Administration Guide, which is installed on the PC where you installled PowerCLI.

You can use the 'normal' cmdlets to navigate, test and create folders.

For example:

CD vmstore:

LS # will show the upper level

CD MyDatastore\MyFolder # navigate with the alias "cd".

test-path MonAutreDossier # check the existence of a folder or file

mkdir test # create a folder

I hope this helps

Tags: VMware

Similar Questions

  • Cannot create the data store

    Hello!

    I installed ESX 3.5 update 4 with success, but I met following problem: I can not create the data store!

    Customer VI can't see my hard drive!

    Once the connection directly to the ESX Server using ssh, we see:

    # esxcfg-vmhbadevs

    #            # empty!!!

    # df h

    Size of filesystem used Avail use % mounted on

    / dev/hde2 3.5 G 1.4 G 2.0 G 41%.

    / dev/hde6 24% 19 M 61 M 84 M/Boot

    No 124M 124M 0 0% / dev/shm

    / dev/hde7 525M 20 M 479M 4% / var/log

    # vdf h

    Size of filesystem used Avail use % mounted on

    / dev/hde2 3.5 G 1.4 G 2.0 G 41%.

    / dev/hde6 24% 19 M 61 M 84 M/Boot

    No 124M 124M 0 0% / dev/shm

    / dev/hde7 525M 20 M 479M 4% / var/log

    devices/vmfs / 33M 33M 0 0% / vmfs/devices

    # fdisk-l

    Disk/dev/hdk: 200.0 GB, 200049647616 bytes

    255 heads, 63 sectors/track, 24321 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes

    + Device boot start end blocks Id system.

    FB/dev/hdk1 1 16709 134215011 unknown

    FB unknown/dev/hdk2 16710 24321 61143328 +.

    Disk/dev/hdi: 1500,3 GB, 1500301910016 bytes

    255 heads, 63 sectors/track, 182401 bottles

    Units = cylinders of 16065 * 512 = 8225280 bytes

    + Device boot start end blocks Id system.

    /dev/hdi1 * 1 182401 1465135968 unknown fb +.

    Disk/dev/hdg: 1500,3 GB, 1500301910016 bytes

    255 heads, 63 sectors/track, 182401 bottles

    Units = cylinders of 16065 * 512 = 8225280 bytes

    + Device boot start end blocks Id system.

    /dev/hdg1 * 1 182401 1465135968 unknown fb +.

    Disk/dev/hde: 500,1 GB, 500107862016 bytes

    255 heads, 63 sectors/track, 60801 cylinders

    Units = cylinders of 16065 * 512 = 8225280 bytes

    + Device boot start end blocks Id system.

    / dev/hde1 1 96 763904 5 extended

    Partition 1 does not stop the cylinder limit.

    / dev/hde2 97 548 3630690 83 Linux

    FB/dev/hde3 618 60802 483425304 unknown

    / dev/HDE4 549 617 554242 82 Linux swap +.

    / dev/13 27 fc 112624 unknown hde5

    / dev/hde6 * 2 12 88326 83 Linux

    / dev/546178 95 28 hde7 83 Linux +.

    Partition table entries are not in the order of disc

    Disk/dev/hdc: 1500,3 GB, 1500301910016 bytes

    255 heads, 63 sectors/track, 182401 bottles

    Units = cylinders of 16065 * 512 = 8225280 bytes

    + Device boot start end blocks Id system.

    / dev/hdc1 43932 182401 1112260275 7 HPFS/NTFS

    /dev/hdc2 * 1-11252-90381658 7 HPFS / NTFS +.

    unknown/dev/hdc3 11253 43931 262494061 FB +.

    Partition table entries are not in the order of disc

    #

    The partitions are present, but vmware won't do an analysis.

    Is there a way to understand what happened?

    My setup

    motherboard: Tyan Thunder n3600m S2932GRN

    disks: SATA seagate and WD.

    NIck

    I see the barebone specification and seem that your controller is a 'soft' RAID

    Take a look at the configuration of the SATA controller.

    When your drive will be recognized as/dev/sdXX, then you can create your data store.

    André

    * If you found this device or any other answer useful please consider awarding points for correct or helpful answers

  • Script to get the ID of the new LUN to create the data store

    Forgive the question from a novice - I'm not a developer at all.

    I am trying to write a script that will create a data store on a new iSCSI LUN - the problem is that I have already several other LUNS with the warehouses of data on it, so after I refresh the HBA, basically need to understand is that the new LUN and create a store of data on it.

    I made all sorts of googling and found scripts to create a new store database, but only in the first store of data on a new iSCSI target.

    Any help would be appreciated.

    Thank you!

    You can try the first script of Arnim in list HBA WWPN and LUN using Powershell

  • Create the data store Partiotion

    Hi all

    She can tell how to set the 'HostDiskPartitionSpec' - & gt; partition property.

    Please help me.

    For more information, please see below, that's what I have to do I have size of vdisk SAN I don't know how to set the following property mainly 'attributes', 'sector statr', 'endsector '.

    Data object - HostDiskPartitionAttributes

    Property of

    [file:///C:/vmware/doc/ReferenceGuide/vim.host.DiskPartitionInfo.Specification.html#field_detail]

    Extends

    [file:///C:/vmware/doc/ReferenceGuide/vmodl.DynamicData.html]

    Data object

    Description

    A single disk partition information.  A partition is a contiguous

    set of blocks on a disk that is marked to be used.  Identifies the typeId

    the data in the partition object.

    Properties

    Name

    Type

    Description

    attributes

    xsd:byte

    The attributes on the partition.

    endSector

    xsd: long

    The end sector.

    logic

    xsd: Boolean

    Flag to indicate if the partition is

    logic.  If true, the partition

    number must be greater than 4.

    partition

    xsd: int

    The number of partition.  Must be a positive integer.

    startSector

    xsd: long

    The boot sector.

    type

    xsd: String

    Data type of the partition.  If it's a well known partition type,

    It will be one of the defined types.  If this isn't the case, then it will be

    reported as a hexadecimal number.  For example, 'none', 'vmfs', 'linux ',.

    and '0 x 20' all values are valid.

    See file:///C:/vmware/doc/ReferenceGuide/vim.host.DiskPartitionInfo.Type.html

    Properties inherited from file:///C:/vmware/doc/ReferenceGuide/vmodl.DynamicData.html

    file:///C:/VMware/doc/ReferenceGuide/vmodl.dynamicdata.html#dynamicProperty, file:///C:/vmware/doc/ReferenceGuide/vmodl.DynamicData.html#dynamicType

    Please answer me as soon as POSSIBLE.

    property 'partition' is a positive integer that identifies the disk partition. So, if you create a logical partition (i.e., setting the property to "logical" true) then you need to assign any positive integer that is greater than 4 to this property.

    I hope this helps.

  • How to create the data store with multiple LUNS

    Someone could please tell me that how can I have multiple LUNS in a single data store, is it possible?

    See the "Storage management" section in the document provided in the previous comment. You are probably looking for information on page 104.

  • Script to create multiple [pooled VM specified data store and resources

    I tried to make the following... writng a powershell script to perform the following operations

    (1) create a resource pool named reservedly set to unlimited

    (2) create 4 Virtuall machines in the yellow resource pool named DB-yellow, yellow-APP1, App2-yellow and yellow-bk

    Yellow-DB

    Yellow-App2, App1-yellow and yellow-bk

    (3) Vrtual all machines must be created in the Datastore YELLOW-OS

    (5) Yellow_DB shoule have a second virtual 8 GB of drive size in the YELLOW-PF data store

    Yellow-App1, App2-yellow and yellow-bk should all have a second virtual 5GB drive size in the YELLOW-PF data store

    Any ideas?

    Kind regards

    (1) create a virtual computer

    Hi Gboskin,

    Take a look at the following doc:

    http://communities.VMware.com/docs/doc-6972

    The script can deploy vm in resourcepools, clusters and on esx hosts. You can specify warehouses of data, ip etc.

    On the site of the doc, I have an older version of the script, I will update as soon as possible.

  • Cannot create the data store: the current licence or ESXi version prohibited the execution of the requested operation.

    using vicfg-nas I am unable to create/remove a datastore nfs on my lab running esxi 6 at home. Is this not supported? Listing them works well. I can create/delete data warehouses nfs using the client to vcenter very well, but it's a little embarrassing.

    I guess that the host is allowed with the free edition of hypervisor! One of the few restrictions of the free version of hypervisor is access to the API. In order to have "write access" (i.e. change things rather than the list of them) you must run the host in evaluation mode, or license (Essentials or better).

    André

  • Command or a script required for the data store, the identifier of NAA and multipath

    The following script/command gets me politics multichannel on a csv file, however, I need to also identify the "Datastore" name with the number of naa.

    Get-cluster 'windows 01' | Get-vmhost | Get-scsilun - luntype disc | Export-csv c:\lun_multipath.csv

    any help would be appreciated.

    Try something like this

    $datastore = get-datastore
    
    $disks = get-cluster 'windows 01' | get-vmhost | get-scsilun -luntype disk$entry = @()$output = @()ForEach ($disk in $disks){  $entry = "" | Select DataStorename, HostName, Canonicalname, Multipathing  $entry.datastorename= $datastore | Where-Object {($_.extensiondata.info.vmfs.extent | %{$_.diskname}) -contains $disk.canonicalname}|select -expand name  $entry.HostName = $disk.VMHost.Name  $entry.canonicalname=$disk.canonicalname  $entry.multipathing=$disk.multipathpolicy  $output += $entry}$output | Export-csv c:\lun_multipath.csv
    
  • Create the new store of data using partition or free space

    Hello

    I am creating the data store in ESXi 5. I want to choose a free partition on the HARD drive or an unpartitioned space. However this option is not available somehow and that the system wants to use all the partitions (delete).

    How can I select only a single partition? Please take a look at the screenshot.

    Thank you!

    If possible, I guess you will need create the VMFS partition manually using fdisk or partedUtil followed by 'vmkfstools vmfs5 - C b 1 m disk_ID:P' see Using vmkfstools

    Maybe http://kb.vmware.com/kb/1009829 and http://kb.vmware.com/kb/1036609 will be useful also

    André

    Post edited by: a.p. - link replaced vmkfstools

  • Cannot create the data in vSphere 4.1 store

    Hi all

    I can't create a data store in my client vSphere 4.1.

    When I start to create the data store, I get this error, notice how it also says that disk is empty - it is also misrepresentation of the size of the 250 GB drive - should be 3.4 TB

    review_disk.PNG

    I can go beyond this by pressing return, and then click Next, but after that I entered a data store name, this error pops up:

    formatting.PNG

    I don't know why this is, I've also tried it on several other client machines, all show the same errors - I join two error logs in the hope that someone will be able to shed some light on this.

    Thank you

    K

    As said, LUNs presented to the host need to be ESXi <= 2tb="" minus="" 512="" bytes="" in="" order="" to="" work="" as="" expected.="" for="" the="" reason="" of="" this="" limitation="" see=""> http://kb.vmware.com/kb/3371739

    Alternatively, you may consider upgrade to ESXi 5.0, supporting the LUN with up to 64 TB.

    André

  • Cloning into a subfolder of the data store

    I have a powershell script that creates daily snapshots and clones on Sunday.  I would like to have clones stored in a subfolder on a NFS share.  I can't figure out how to set the data store in a subfolder like "NFS_NAS_SHARED\CLONES".  The following code fails indicating "'NFS_NAS_SHARED\CLONES' is not found, using the specified filters."  Is it possible to have the destination clone as a subfolder of a data store?

    Start-Transcript-Path "C:\VMWare_Scripts\LOGS\SnapshotsTranscript.log".

    #Get the VMware PowerCLI
    Add-pssnapin VMware.VimAutomation.Core - ErrorAction SilentlyContinue

    # Import the backup information
    #File layout: MasterVM (vmname), BackupDS (DS to store clone), BackupFolder

    #$backupinfo = import-Csv C:\VMWare_Scripts\Snapshot_backups.csv
    $backupinfo = import-Csv C:\VMWare_Scripts\Snapshot_backups_TESTING.csv

    Date format #Set to name
    $datetime = get-Date-Format "YYYYMMDD-hh: mm".
    $date = get-Date-Format "YYYYMMDD".

    #Connect to vCenter
    SE connect-VIServer "localhost".

    #Get the day of the week
    switch ((get-date).dayofweek.toString ())
    {
    Sunday {$dow = "SUN"; break}
    Monday {$dow = 'MY'; break}
    Tuesday {$dow = "KILL"; break}
    Wednesday {$dow = "WED"; break}
    Thursday {$dow = "THU"; break}
    Friday {$dow = "FRI"; break}
    }

    {foreach ($customer to $backupinfo)

    $vm is get - VM $customer. MasterVM
    $days = $customer. DaysToKeep

    Write-Host $vm. Name
    #Write - Host $days

    #Delete snaps more $days
    Get - VM $vm | Get-Snapshot | Where {$_.} Created - lt ((Get-Date).) AddDays(-$days))} | Remove-Snapshot - confirm: $false

    If ($dow - eq 'MY') {}
    #Create a clone

    #Create a new snapshot for cloning
    $cloneSnap = $vm | New-Snapshot - name "clone_snap" - suspend: $true

    # Get the managed object display
    $vmView = $vm | Get-View

    # Get the managed folder object reference
    $cloneFolder = $vmView.parent

    # Construction specification clone
    $cloneSpec = new-object Vmware.Vim.VirtualMachineCloneSpec
    $cloneSpec.Snapshot = $vmView.Snapshot.CurrentSnapshot
    $cloneSpec.Location = new-object Vmware.Vim.VirtualMachineRelocateSpec

    #set the destination clone
    $backupDestination = $customer. BackupDS + $customer. BackupFolder
    $cloneSpec.Location.Datastore = (get-Datastore-name $backupDestination |) Get - View). MoRef
    $cloneSpec.Location.Transform = [Vmware.Vim.VirtualMachineRelocateTransformation]: sparse

    $cloneName = "$vm - $datetime".

    # Create clone
    $vmView.CloneVM ($cloneFolder, $cloneName, $cloneSpec)

    # Write newly created VM to stdout as confirmation
    Get - VM $cloneName

    # Remove snapshot created for clone
    Get-Snapshot - VM (Get - VM $customer. MasterVM) - name $cloneSnap | Remove-Snapshot - confirm: $False


    }
    else {}
    #Take a snapshot
    New-Snapshot - name $datetime - description "scripted Snap: Snapshots.ps1" - vm $vm - suspend: $true
    }

    }

    VCenter #Disconnect
    Disconnect-VIServer-confirm: $false

    Stop-Transcript

    I'm afraid that the CloneVM_Task method you cannot specify subfolders on a data store.

    He wants a data store and use the displayname property of the virtual machine to create a folder on this data store.

    If you clone a computer virtual called XYZ to the store of data DS1, the clone will be located in the "[DS1] XYZ" folder.

    If you want to move the clone to a different folder, you can use the cmdlet Copy-DatastoreItem thereafter.

  • Not be able to reverse engineer the data store by using technology such as postgres

    Hello

    When I am creating a data store for postgres using reverse engineering process he gives error jdbc.

    Then we created the data store manually by using the same schema logic and used in the interface and it was working fine.
    It is not possible to manually create all the data store for postgres we need in my project.

    Error details:
    ODI-20131: unable to retrieve a list of tables
    oracle.odi.core.exception.OdiRuntimeException: java.lang.IllegalArgumentException: could not load driver JDBC [org.postgresql.Driver] class
    at oracle.odi.core.datasource.provider.AbstractDataSourceProvider.configure(AbstractDataSourceProvider.java:107)
    to oracle.odi.core.DataSourceManager$ LoginTimeoutDataSourceProviderProxy.configure (DataSourceManager.java:303)
    at oracle.odi.core.DataSourceManager.createAndConfigureDataSourceProvider(DataSourceManager.java:226)
    to oracle.odi.core.DataSourceManager.access$ 0 (DataSourceManager.java:206)
    to oracle.odi.core.DataSourceManager$ 1.create(DataSourceManager.java:76)
    at org.springframework.util.CachingMapDecorator.get(CachingMapDecorator.java:152)

    Your postgresqldriver is missing (in the folder userlib/agent)-able to load JDBC driver class.

    Similar problem for SQL Server - unable to connect to SQL Server 2005 using ODI 11 g

  • Dell virtual disk are larger. You want to increase the size of the data store.

    Hello

    I started the implementation of a server ESXi 5.5 Update 1 this week. I didn't know Dell shipped the server with two virtual disks instead of one. I realized this _apres_ that I had already created the data store and setup a few virtual machines to the breast. I called Dell who sent specific instructions to increase the removal of the second (empty) virtual disk and add it to the main. In the end, I increased the single VD from 2 TB to 3 TB and I want to give the remaining space in my store of data.

    I tried to follow the article here that explains how to do this via the CLI.

    Well, he did not altogether. Fortunately, I was able to recover my datastore my setting start and end sectors to their original numbers. But I'm still left with this almost 1 TB of space that I can not attribute to the data store. After that I reread storage adapters in the client, the new Dell disk size resulted under measurement devices. Click on "increase...". ", generates the following error which led me on the way to the CLI method:

    Call "HostDatastoreSystem.QueryAvailableDisksForVmfs" to object "ha-datastoresystem" on ESXi '[myservername]' failed.

    I will paste my notes that I took everything by jobs. Things have exploded the rails when I put 4 partition size to the largest size. Any help, please?

    ---

    I use that as a guide:

    http://KB.VMware.com/selfservice/search.do?cmd=displayKC & docType = kc & docTypeID = DT_KB_1_1 & externalId = 2002461


    1 use start hardware device management tools to increase the capacity of additional disk to the device. For more information, commit your hardware provider.

    This has been done. The new size of the virtual disk is 2791,88 GB (TB 2,79188)


    2. open a console to the ESXi host.

    Pretty simple.


    3. get the DeviceID for the data store to change.

    ~ # vmkfstools Pei "/ vmfs/volumes/datastore1 / '.

    System file VMFS-5, 60 extending on 1 partition.

    File system label (if applicable): datastore1

    Mode: public

    Capacity 1971926859776 (blocks of files 1880576 * 1048576), 1042688245760 (994385 blocks) prevail, max size of the 69201586814976 file

    UUID: 534e5121 - 4450-19dc-f8bc1238e18a 260d

    Partitions split (on 'lvm'):

    NAA.6c81f660ef0d23001ad809071096d28a:4


    A couple of things to note:

    a. the device for Datastore1 ID is: naa.6c81f660ef0d23001ad809071096d28a

    b. the number of Partition on the disk is: 4 ' [...]: 4 "»

    c. the prefix, "naa," means "Network address authority" the number immediately after is a single logical unit number.

    4. Enter the amount of disk space available on the data store.

    ~ # df h

    Size of filesystem used available use % mounted on

    VMFS-5 1. 8T 865.4 G 971,1 G 47% / vmfs/volumes/datastore1


    5 team of the device identifier, to identify the existing partitions on the device by using the partedUtil command.

    ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

    364456 255 63 5854986240

    1 63 80324 222 0

    2 80325 8466884 6 0

    3 8466885 13709764 252 0

    4 13711360 3865468766 251 0

    ~ #


    According to the table in article KB

    4 13711360 3865468766 251 0 - primary #4, type 251 = 0xFB = VMFS, 13711360-3865468766 areas

    | |        |          |   |

    | |        |          |   \---attribut

    | |        |          \---type

    | |        \---se finishing sector

    | \---a starting from sector

    partition \---Numero


    Also note how the number of section start the old end sector number is + 1.


    6 identify the partitions that need to be resized and the size of the space to use.

    We want to resize partition 4. I don't really understand the last part of this sentence, however. Read more.


    7 the number of sector end you want for the target data store VMFS partitions. To use all out at the end of the disc space, remove 1 of the size of the disk in the areas as described in step 5 in order to get the last usable area.

    ESXi 5.x has a command to do this:

    ~ # partedUtil getUsableSectors "/ vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a".

    1 5854986239

    This means that we want 4 Partition of "naa.6c81f660ef0d23001ad809071096d28a" to be:

    13711360 - 5854986239 (i.e. the end of the disc)


    8 resize the partition containing the target VMFS Datastore using the command partedUtil, specifying the original existing partition and the desired end sector:

    Using the above information, our command is:

    resize # partedUtil ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 5854986239


    9 step 8, the partedUtil command can report the warning:

    He did not. Displacement.


    10. the tables of partitions have been adjusted, but the VMFS data within the partition store is always the same size. Now there is an empty space in the partition where the VMFS data store can be grown.


    11 launch this v vmkfstools command to perform a refresh for VMFS volumes.

    Fact.


    12 reach the VMFS Datastore in the new space using the command - growfs vmkfstools, specifying the partition containing the VMFS Datastore target twice.

    vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 '.


    It did not work. I got an error:

    / vmfs/volumes # vmkfstools - growfs ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a:4 ' /vmfs/devices/disks/naa.6c81f660ef0d «»

    23001ad809071096d28a:4 ".

    Cannot get device head way /dev/disks/naa.6c81f660ef0d23001ad809071096d28a:4 information


    Also the partition was very different to what I asked:

    ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

    364456 255 63 5854986240

    1 63 80324 222 0

    2 80325 8466884 6 0

    3 8466885 13709764 252 0

    4 13711360 1560018942 251 0


    I fixed it by running these commands:

    ~ # partedUtil resize ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a ' 4 13711360 3865468766

    ~ # vmkfstools v

    ~ # partedUtil get ' / vmfs/devices/disks/naa.6c81f660ef0d23001ad809071096d28a '.

    364456 255 63 5854986240

    1 63 80324 222 0

    2 80325 8466884 6 0

    3 8466885 13709764 252 0

    4 13711360 3865468766 251 0

    Update:

    Since it was such a new machine, not in active production, we have safeguarded the VMs management off the ESXi host. Then flattened the virtual disk, recreated, and then created a store of data with the right size. (TPG this time, naturally.) We put the management of virtual machines on the data store. For Windows virtual machines, we have restored the using AppAssure. Everything is ok now.

    Need to add a new item to the list of punch: check what Dell has done the configuration of the virtual disks. :-)

  • Swapping hard drives for change/increase the size of the data store

    Hello:

    I have an ESXi host 4.1 with 2x146GB RAID1 array (datastore1), 4x300GB RAID5 array (datastore2).  I need more space so I intend to replace 2x146GB by 2x2TB.  I'll first move virtual machines from datastore1 to datastore2, then stop the machine, Exchange records and build the new table.

    • What I need to remove ESXi cfg datastore1. before you physically remove the drives, or will start ESXi gracefully and allow me to remove the data store?
    • I'll be able to add the new data store (2x2TB) to ESXi, ago, i.e. ESXi should see table once initialized on the machine?
    • Existing data warehouses have 1 MB block size max vmdk is 256GB.  I want the new data store to have the block size of 8MB so I can have more VMDK.  I think I can fix the block size of data store when it was created, are, i.e. the ESXi installation can have warehouses of data with different block sizes, are?


    Thanks a lot for the ideas you have!


    Bob

    1.) why not just delete the GUI data store before you remove the discs?

    2.) If your controller has the disks properly there should be no problem with their detection.

    3.) Yes, each data store may have a different block size. The block size can be selected when creating the data store on disk/LUN.

    André

  • Problems with the data store when installting ESXi USB

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

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

    VMware VCP4

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

Maybe you are looking for