Extend the data store

Similar Questions

• Extend the data store on ESXI 5.0 servers

  I have (2) 5.0 to aid a ESXI servers an ISCSI SAN that I increased the storage capacity on.  I see that I can increase the ability to store data in the Client VMware;  But I was wondering how this is done when there are (2) ESXI servers share the same SAN?

  Can I increase the storage in one or do I have to do the same for both?

  I was wondering,

  Ken

  Hello

  After that lie on the same host, the second should rescan it's HBA and detect the new size. If it does not, trigger a manual rescan.

  Tim

• Extend the data via vSphere Client store - error ' call 'HostDatastoreSystem.QueryVmfsDatastoreExtendOptions' object 'ha-datastore System' on ESXi 'IP' failed '.

  Hi @all,

  I want to thank my datastore on my 5.1 esxi.

  When you extend the data store on the vSphere Client Console, I get the error message:

  German: Call von 'HostDatastoreSystem.QueryVmfsDatastoreExtendOptions' as Objekt "ha-datastoresystem" auf fehlgeschlagen ESXi 'IP' ist.

  English: Call 'HostDatastoreSystem.QueryVmfsDatastoreExtendOptions' to object "ha-store system data" in ESXi 'IP' failed

  Anyone an idea why I can't extend the data store? The new drive is correctly detected.

  Best regards

  Andreas Acker

  Hello

  This seems to be a local data store. ? This is where the ESXi host is installed. ?

  Thank you
  Avinash

• Problem adding disks to the data store

  I currently have a data store RAID 5 consisting of four discs of 250gig. I bought two identical drives more and am trying to extend the data store.

  I have a HP Proliant ML350 G6. I plugged the two new drives, add them in the raid array and now get this error in esxi:

  Volme 1 on HPSA1 logic: RAID 5: 698 GB disk 1,2,3,4,5,6: currently in expansion

  I thought it was a normal phenomenon since I am expanding the raid, but I don't think it would take more than a few minutes. He had this attention for at least four hours now. I did something wrong? I'm trying to expand this data store for the two new drives in the raid to enlarge.

  I've attached a screenshot of the warning.

  The virtual machine has a snapshot. In order to increase the size of the virtual drive, remove the snapshot by using the Snapshot Manager. As long as there is a snapshot virtual disk, that they can not be changed.

  André

• Technical question from the data store

  Hello everyone.

  I have a question that you can maybe answer:

  "Is it possible to have a WARNING message (check) before formatting a LUN (EMC)?"

  Let me explain:

  We currently have a datastore composed of 12 LUN (of 236 GB), and even if this isn't in the best practices of VMware, I made a mistake (und) when creating a new data store.

  Indeed, I used a logic unit number which was attached directly to a virtual machine (in Raw Device) pour set up my new data store.

  Would you have a solution that makes a data control (on the logic unit number) and which could see us the partition proposed pour extend the data store contains data!

  Thanks in advance for your answer!

  J. Gaspoz

  Hi Julien

  Nice to see you on communities

  The vCenter will list all LUNS that are not already in the "Add storage" wizzard data warehouses, and by definition, a RDM en of is not formatted VMFS, since the lun belongs to the VM and it met with filesystem clean so son.

  There is therefore no direct way to pour do what you're asking (UN ESX knows nothing about the data on a non-vmfs LUNs).

  Personally, plug-in a simple way: the LUN ID. All the LUNs that will be used in RDMS are presented to my ESX with UN LUN ID between 50 and 70 (f.ex.). So I know whether or not a lun is RDM.

  Otherwise maybe third-party products (rv maybe tools) can get out a report listing the VM using the RDM.

  I hope that helps!

  Best regards.

  Stéphane Grimbuhler

  Senior consultant virtualization & storage (VCP / VCAP-DCA)

  VMware instructor (VCI)

  My Blog: www.virtualgeek.ch

• How to extend the size of the data store

  Hello
  
  Everyone knows how to perform this task?
  
  
  Thank you
  
  
  
  Lewis

  As long as you have enough memory and disk space to accommodate the largest data store, the procedure is as follows:

  1. stop the data store and make sure that it is unloaded from memory

  2. increase the values for PermSize or TempSize on the DSN (sys.odbc.ini) parameters

  3. load the store data in memory again.

  Fact!

  If you use TimesTen 11 g, step (3) must be performed as long as the user administrator of the o/s instance.

  Chris

• Please help: measure is missing from the data store

  Hello

  I have an a 20 TB drive data store and a magnitude of about 40 TB (local disks, areca raid controller).

  Long story short, I had to delete and re-create the volume 40 to on the RAID controller (without initialization, of course).

  Now all the data is there but eui has changed for the 40 to volume and vmware is unable to mount.

  log/hostd.log:2016-05-10T07:17:16.107Z of information pass [3D380B70] [Originator@6876 sub = Vimsvc.ha - eventmgr] event 118: a connected device eui.001b4d2051676528:1 may be offline. [Backvol1, 55e980d4-386dfa7f-7cb2-0cc47a09ba36] file system now is in a degraded state. While the data store is always available, parts of data residing on the extent which went offline may be inaccessible.

  [root@esxi2:/vmfs/volumes/55e980d4-386dfa7f-7cb2-0cc47a09ba36]

  esxcli instant vmfs storage list

  Volume name:

  VMFS UUID:

  Can mount: false

  UN-mountability reason: a few missing extensions

  Can will: false

  Reason for non-resignaturability: some missing extensions

  County of measure pending: 1

  Can someone help me please?

  Thank you!

  Hello
  You asked for instructions on how to readd a missing measure.
  Basically, it's pretty easy:
  in the VMFS to VMFS-based volume header section, you can assign extends it.
  Lets say that the basic volume is mpx.vmhba1:C0:T3:L0:1
  first of all extend is mpx.vmhba1:C0:T4:L0:1
  second extension is mpx.vmhba1:C0:T5:L0:1
  Then you will see this string in the VMFS header:
  vmhba1:3:0
  and a little later

  MPX.vmhba1:C0:T3:l0:1

  MPX.vmhba1:C0:T4:l0:1

  MPX.vmhba1:C0:T5:l0:1
  Just change the list of stretches.
  But: normally you can't change this section at all, and to add to the confusion, these values are stored in RAM is not trivial to change this value correctly.
  I highly recommend that instead of try it yourself and repeat all the mistakes I made while learning it - call me.
  I rather help you personally to give dangerous advice that will probably make things worse.

• 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

• 0 blocks free PTR - cannot create new files on the data store

  We have been experiencing problems trying to power on virtual machines. When attempting to power on virtual machines, we see the error "cannot extend the pagefile from 0 KB to 2097152 KB".

  We checked the .vswp file are created in the folder of the Virtual Machine on the data store. Connection to the ESXi host, we have seen the following in vmkernel.log error message:

  (2016 01-16 T 21: 19:40.556Z cpu1:4971732) WARNING: Res3: 6984: "freenas-6-ds": [rt 3] No. Space - has not found enough resources after the second pass! (requis_:_1,_trouvé_:_0) 2016-01 - 16 T 21: 19:40.556Z cpu1:4971732) Res3: 6985: "freenas-6-ds": [rt 3] resources t 0, e 0, PN 16, BM 0, b 0, RCs u 0, i 0, 4031 nf, pe 0, 0 2016-01-16 T 21 oe: 19:40.556Z cpu1:4971732) WARNING: SwapExtend: 683: impossible to extend the pagefile from 0 KB to 2097152 KB.

  This was surprising given that we have about 14 TB of space available on the data store:

  [root@clueless:~] df h

  Size of filesystem used available use % mounted on

  VMFS-5 20.0 T 5.4 T 14.6 T/vmfs/volumes/freenas-six-ds 27%

  However, when we use "dd" to write a 20 GB file, we would get "no space left on device:

  [root@clueless:/vmfs/volumes/55a00d31-3dc0f02c-9803-025056000040/deleteme] dd if = / dev/urandom of = deleteme bs = 1024 count = 2024000

  DD: writing "deleteme": no space is available on the device

  263734 + 0 records in

  out 263733 + 0 reviews

  [root@clueless:/vmfs/volumes/55a00d31-3dc0f02c-9803-025056000040/deleteme] ls - lh deleteme

  -rw - r - r - 1 root root 19 Jan 255,1 M 01:02 deleteme

  We checked that we have free inodes:

  The ramdisk name system include in reserved Coredumps used Maximum reserved free use pic free maximum allocated Inodes used Inodes Inodes Mount Point

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

  root of true true 32768 KiB 32768 KiB KiB KiB 99% 99% 9472 4096 3575 176 176.

  true true etc 28672 KiB 28672 KiB 284 KiB 320 KiB 99% 99% 4096 1024 516/etc

  Choose true true 0 KiB KiB 0 KiB KiB 0 100% 0% 8 1024 8192 32768 / opt

  var true true 5120 KiB 49152 484 516 99% 90% 8192 384 379 KiB KiB KiB / var

  tmp false false 2048 KiB 262144 KiB 20 KiB 360 KiB 99% 99% 8 256 8192/tmp

  false false hostdstats KiB 310272 KiB 3076 KiB 3076 KiB 99 0% 0% 8192 32 5/var/lib/vmware/hostd/stats

  
  

  We believe that our cause is due to have 0 free blocks of PTR:

  [root@clueless:/vmfs/volumes/55a00d31-3dc0f02c-9803-025056000040] vmkfstools Pei - v 10/vmfs/volumes/freenas-six-ds.

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

  File system label (if applicable): freenas-six-ds

  Mode: public TTY only

  Capacity 21989964120064 (blocks of files 20971264 * 1048576), 16008529051648 (15266923 blocks) prevail, max supported size of the 69201586814976 file

  Volume creation time: Fri Jul 10 18:21:37 2015

  Files (max / free): 130000/119680

  Blocks of PTR (max / free): 64512/0

  Void / blocks (max / free): 32000/28323

  The secondary blocks of Ptr (max / free): 256/256

  Drop blocks (approve/used/approve %): 0/5704341/0

  Blocks of PTR (approve/used/approve %): 64512/0/0

  Void / blocks (approve/used/approve %): 3677/0/0

  Size of volume metadata: 911048704

  UUID: 55a00d31-3dc0f02c-9803-025056000040

  Logical unit: 55a00d30-985bb532-BOI.30-025056000040

  Partitions split (on 'lvm'):

  NAA.6589cfc0000006f3a584e7c8e67a8ddd:1

  Instant native is Capable: YES

  OBJLIB-LIB: ObjLib cleaned.

  WORKER: asyncOps = 0 maxActiveOps = 0 maxPending = 0 maxCompleted = 0

  When we turn off a virtual machine, it will release 1 block of PTR and we would be able to on another VM / create the 20 GB file using "dd". Once we reached 0 free blocks of PTR, we are unable to create new files.

  Can anyone give any suggestions on how we may be able to clear the blocks PTR? We have already tried to restart all services of management on all ESXi hosts connected.

  FreeNAS is not running on a virtual machine.

  We solved the problem by finding a lot PTR blocks have been used by many of our models of virtual machine. Remove the disk models solved the problem.

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

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

• 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

• Machine virtual IOPS / s report, how to display the name of the data store?

  Hi guys

  I am new to the Foglight community, this is a great tool, and I learn a lot.

  Currently I am trying to create a simple table that will show me metric of my VMware environment: Virtual Machine name, Datastore IOPS and data store.

  However I can't find how to include data store name in the table, because it is not a measure of the Virtual Machine. I think I need to expand the scope of my table to include VMware Datastore, but I don't know how to do this.

  -Mark

  

  Check the options available it seems that it can be done with WCF (the frame behind the Foglight dashboards).  We recommend generally customers who plan to build views WCF take adequate training or our PSO people engaged in it.

  In any case I can help show a quick example of how it's done.

  Please try this on a local/test server.

  Go to Configuration > definition >

  

  Make sure that you are in my definition, and click the icon to add a view. then choose from the tables and trees - oriented line table

  

  Give a name to the view, go public and make a portlet/reportlet and apply

  

  Switch to the configuration tab and click the change for the lines and choose a query

  Under query, expand the VMware and scroll down

  

  Until you can select the query for virtual machines

  

  And press the set button.

  Your view should look like this

  

  Now you must select the columns.

  Each column has a value you can edit and there is a button + to add additional columns.

  Lets start with the name of the virtual machine - click on the button to change to your default column and choose the context.

  

  Click on the drop down menu to enter key and choose the current line (virtual vmware machine)

  

  Click on the drop down menu to access path and scroll down until you can select the name and then click on set.

  

  You have created a table that lists the names of all virtual machines.

  You can click on save. and then click test, choose a time and click the result. A new window will open a show the list you of virtual machines.
  From here you can continue to add additional columns, each time choosing the key entry in the current line and the path to the metric/string to display.

  For example, the name of the data store.
  I change the module

  

  Click the configuration tab and click the icon to add a column

  

  For the column value, that I chose defined context once again, the key input is the current row and for the path, I expand the node for the data store

  

  And scroll until I see the Proprietename

  

  If you save and test you will see the result

  

  Keep adding columns and the data you want, notice that you have arrows that allow you to control the order of the columns.

  Note that you can click Show advanced configuration properties

  

  This will give you the opportunity to see the properties of the extra table, such as header - giving you the opportunity to give a more meaningful name (name of the data store, the name of the virtual machine, etc.) to the column header.

  

  You can now go you drag and drop the table edge/report and under my eyes, you will see your new view

  

  Drop it in the main view

  

  I hope this has given you the starting point to build this table.

  As I said, I strongly recommend going through our WCF training if you plan build more custom views or hire software Dell PSO Organisation to help build you views that correspond to your need.

  Best regards

  Golan

• hp has extended the date of return to the offer of the College?

  hp has extended the date of return to the offer of the College?

  You need to ask HP directly for more information about this.

  This is the support forum for the consumer and not a business unit of HP.

• TDSB import error "does not exist in the data store."

  I have a problem when you import a relative definition, do not know if it is to have a focus in the name.

  When I run the command on the server,

  Java com.fatwire.csdt.client.main.CSDT $WCS_CONTENT username = password CS_USER $= $CS_PASS resources = ImagePD:876f1718-06e7-40bd-bbc3-cea02d07d1f1 cmd = listds

  I have the answer,

  No such resource (s).

  But the file exists in the directory,

  sites\export\envision\cs_workspace\src\_metadata\ASSET\ImagePD\73\10\(876f1718-06e7-40bd-bbc3-cea02d07d1f1) of notícia. main.xml

  When I run the command to import,

  Java com.fatwire.csdt.client.main.CSDT $WCS_CONTENT username = password CS_USER $= $CS_PASS resources = ImagePD:876f1718-06e7-40bd-bbc3-cea02d07d1f1 cmd = import

  I get this error message,

  [2015-05-27 19:16:50, 883 UTC] [ERROR] [.kernel. [Default (self-adjusting)'] [com.fatwire.csdt] error on import: import error: import error: resource DSKEY:ImageP-876f1718-06e7-40bd-bbc3-cea02d07d1f1 does not exist in the data store.

  com.fatwire.cs.core.realtime.DataException: import error: resource DSKEY:ImageP-876f1718-06e7-40bd-bbc3-cea02d07d1f1 does not exist in the data store.

  at com.fatwire.realtime.packager.CSDTUtil._import(CSDTUtil.java:422)

  at com.fatwire.realtime.packager.CSDTUtil._import(CSDTUtil.java:455)

  at com.fatwire.realtime.packager.CSDTUtil.Import(CSDTUtil.java:360)

  at com.fatwire.csdt.service.impl.ImportService.importData(ImportService.java:227)

  at com.fatwire.csdt.service.impl.ImportService.execute(ImportService.java:88)

  at jsp_servlet._jsp._cs_deployed._openmarket._xcelerate._prologactions._publish._csdt.__csdtservice._jspService(__csdtservice.java:223)

  at weblogic.servlet.jsp.JspBase.service(JspBase.java:35)

  to weblogic.servlet.internal.StubSecurityHelper$ ServletServiceAction.run (StubSecurityHelper.java:227)

  at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)

  at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)

  at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:185)

  at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:526)

  at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:447)

  to com FutureTense.Servlet.ServletRequest.include(ServletRequest.java:1411)

  to com FutureTense.Servlet.FRequestObj.include(FRequestObj.java:1429)

  to com FutureTense.Servlet.JSPServices.runJSP(JSPServices.java:111)

  to com FutureTense.Platform.FileSystem.FILESYSTEMJSPManager.runJSP(FILESYSTEMJSPManager.java:463)

  to com FutureTense.Servlet.JSPServices.runJSPObject(JSPServices.java:50)

  to com FutureTense.Platform.FileSystem.FILESYSTEMJSPManager$ JSPDataFile.run (FILESYSTEMJSPManager.java:190)

  at COM.FutureTense.Common.ContentServer.jspExecute (ContentServer.java:3027)

  at COM.FutureTense.Common.ContentServer.evalTemplate (ContentServer.java:2621)

  at COM.FutureTense.Common.ContentServer.generatePage (ContentServer.java:1640)

  at COM.FutureTense.Common.ContentServer.evalPage (ContentServer.java:1276)

  at COM.FutureTense.Common.ContentServer.execute (ContentServer.java:465)

  to com FutureTense.Servlet.FTServlet.execute(FTServlet.java:129)

  to com FutureTense.Servlet.FTServlet.doPost(FTServlet.java:62)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

  at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)

  to weblogic.servlet.internal.StubSecurityHelper$ ServletServiceAction.run (StubSecurityHelper.java:227)

  at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)

  at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)

  at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)

  at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)

  at com.fatwire.auth.RequestAuthenticationFilter.doFilter(RequestAuthenticationFilter.java:193)

  at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)

  at com.fatwire.wem.sso.cas.filter.CASFilter.doFilter(CASFilter.java:701)

  at com.fatwire.wem.sso.SSOFilter.doFilter(SSOFilter.java:51)

  at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)

  at com.fatwire.cs.ui.framework.UIFilter.doFilter(UIFilter.java:109)

  at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)

  to weblogic.servlet.internal.WebAppServletContext$ ServletInvocationAction.wrapRun (WebAppServletContext.java:3730)

  to weblogic.servlet.internal.WebAppServletContext$ ServletInvocationAction.run (WebAppServletContext.java:3696)

  at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)

  at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)

  at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)

  at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)

  at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)

  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

  at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

  I think that it is not recognizing the file because the name has an accent. But I have another server that recognizes, but can not find the differences.

  Can anyone help?

  I took care of my problem.

  At the beginning of WebLogic has been set the different LANG of enconding placed in the CLASSPATH.