Soha_Fouad
VMware Employee
VMware Employee

Hi,

The issue that you explained is mentioned in the below KB:

https://kb.vmware.com/s/article/1011754

So after expanding the lun from the storage side first you need to do a rescan on the cluster level

(Right click on the cluster >> Storage >>rescan)

If it is not showing from the vcenter interface try to access the host client directly as per the KB

If it is not showing from the host client interface >>you need to expand it from the command line

By following the below KB:

https://kb.vmware.com/s/article/2002461

To make it easy for you I shared an example :

1)you need to know the identifier by running the below command:

esxcli storage vmfs extent list | grep datastorename

Then follow the below steps mentioned in the KB

1)partedUtil getptbl "/vmfs/devices/disks/naa.xxxxxx"

Output:

336746 255 63 21474836480

1  2048 21474836446 0 0

 

Where 1 :is the no of the partition

2- partedUtil getUsableSectors "/vmfs/devices/disks/naa.xxxxx"

34 21474836446

From the output of the above 2 commands >>you will use them in the third command as below

4-#partedUtil resize "/vmfs/devices/disks/naa.xxxx" 1 2048 21474836446

5-Refresh the storage # vmkfstools -V

6-#vmkfstools --growfs "/vmfs/devices/disks/naa.xxxxx:1" "/vmfs/devices/disks/naa.xxxxx:1"

Note :1 mentioned in the above command is the no of the partition that we got from the first command

  • Refresh the storage  # vmkfstools -V

 

Then rescan the cluster from the vcenter interface

 

Note :Sometimes when you run the first command it will give you the error in the below KB:

 

https://kb.vmware.com/s/article/2121741

so fix the error first by following the KB then follow the command line steps mentioned above

 

Hope this helps

 

Best Regards

Soha Fouad

Reply
0 Kudos