So I upgraded my Dell T710 from a Perc 6 to an H700 and upgraded to 4tb drives from 2tb drives. The array has been expanded and is running just fine and somehow my VMFS says it is using the full disk but that differs from the actual datastore usage. I am running 6.0.0 (Build 3620759) on the host with a vCenter Appliance Server running version 6.5.0.5600 Build Number 5705665.
Disk Layout:
Actual Usage:
I have followed the Growing a local datastore from the command line in vSphere ESXi (2002461) guide with multiple reboots with no success.
I have local and remote console access to the machine and I am more than happy to provide any and all information needed to help me correct this issue as I am planning the same type of migration on a T310 once this process is complete on the T710.
Here is the error I get when attempting the commands:
When I get to the end of the guide this is what i get for the error:
[root@esxi:~] partedUtil fixGpt "/vmfs/devices/disks/naa.6782bcb029d1cb0020e269f
008379987"
FixGpt tries to fix any problems detected in GPT table.
Please ensure that you don't run this on any RDM (Raw Device Mapping) disk.
Are you sure you want to continue (Y/N): Y
gpt
2917998 255 63 46877638656
1 2048 46877638622 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
[root@esxi:~] vmkfstools --growfs "/vmfs/devices/disks/naa.6782bcb029d1cb0020e26
9f008379987:1" "/vmfs/devices/disks/naa.6782bcb029d1cb0020e269f008379987:1"
Not found
Error: No such file or directory
[root@esxi:~] ls /vmfs/devices/disks/
mpx.vmhba32:C0:T0:L0
mpx.vmhba32:C0:T0:L0:1
mpx.vmhba32:C0:T0:L0:5
mpx.vmhba32:C0:T0:L0:6
mpx.vmhba32:C0:T0:L0:7
mpx.vmhba32:C0:T0:L0:8
mpx.vmhba34:C0:T0:L1
naa.6782bcb029d1cb0020e269f008379987
naa.6782bcb029d1cb0020e269f008379987:1
vml.0000000000766d68626133323a303a30
vml.0000000000766d68626133323a303a30:1
vml.0000000000766d68626133323a303a30:5
vml.0000000000766d68626133323a303a30:6
vml.0000000000766d68626133323a303a30:7
vml.0000000000766d68626133323a303a30:8
vml.0000010000766d68626133343a303a31
vml.02000000006782bcb029d1cb0020e269f008379987504552432048
vml.02000000006782bcb029d1cb0020e269f008379987504552432048:1
[root@esxi:~]
Any help is greatly appreciated.