VMware vSphere ESXi 6.7 - can't expand iSCSI-Storage from NAS and can't reconnect VMDK-File to VM

[TheBigM]

Hello.
With an ESXi 6.7 Update 3, I have the problem that I can see and use the originally connected storage with a connected iSCSI storage from a Synology NAS (new model), but I have created this in Synology as a thin LUN in order to use it to be able to expand.
If I now expand the storage compartment for the Synology, I do not see the expanded storage on the ESxi despite updating, unmounting and mounting, and nothing is available even with increasing capacity. Does it have any idea why that is.

I also have the problem that a separate VMDK file can no longer be added to a server.
As soon as I select this via Edit --> Add existing hard disk, 0 bytes are displayed everywhere and the drop-down menus for hard disks are empty and shortened and I can't save either.
I read something about the .vmx that can be solved with a workaround (is that ok and how does it work exactly? Can it be done with the VM running?). Anyone know another solution?

Thanks in advance and best regards.

Mario

 

 

 

 

 

 

 

[Maarten Van Driessen]

Before you see the additional capacity on your iSCSI LUNs, you need to run a rescan on the storage adapter.

If you're running vCenter as well, you can right click on the cluster - storage - rescan all. After the rescan, you should be able to expand the iSCSI volume. If you don't have vCenter, then you can do it on ESXi as well by right clicking the iscsi adapter itself.

[TheBigM]

I have a stand-alone ESXi 6.7 U3 on HP ML350 Gen10.

I have now found the way via Storage -> Devices --> Check again and I was now able to find a way to expand the memory, but it comes when I want to accept the changes (want to test expand 500GB, which is definitely available on the LUN and have been added) the following error message: "Error expanding VMFS datastore SSV-NAS-Storage-iSCSI - The host configuration cannot be changed."

What could be the reason here?

 

Thanks in advance.

greeting

 

 

[a_p_]

>>>If I now expand the storage compartment for the Synology
What exactly did you expand? For ESXi you need to expand the presented LUN.

Regarding the VMDK issue, please run ls -lisa from the command line to get a complete listing of the VM's files, and provide the command's output.

André

[TheBigM]

Hi.

Regarding the VMDK: I know where the VMDK is and it's there too, but when I select and add the VMDK to the VM via edit, it looks like this (see image in attachment 8 sample image on another page, but that's exactly how it looks for me too out of)).

 

What could be the Problem?

 

Thanks in advance.
greeting

[TheBigM]

Does anyone have a solution or a solution for the error message
"Error expanding VMFS datastore SSV-NAS-Storage-iSCSI - The host configuration cannot be changed."
The extended memory is displayed on the ESXi and I can also select it, but the error message mentioned
above comes up when applying the changes. 

Thanks in advance and best regards.

Mario

[Dawid Dudek]

Hi,

Did you try do it using Command Line?

--> Run the following command to check the partition on the disk via SSH. 
partedUtil getptbl "/vmfs/devices/disks/DeviceName"

--> Enter partedUtil fixGpt "/vmfs/devices/disks/DeviceName" to confirm if there are any problems with the partition (it will be processing and fix them timely). Press Y.

--> Find the end sector, use command: 
partedUtil getUsableSectors "/vmfs/devices/disks/DeviceName"

--> Expand the partition: 
partedUtil resize "/vmfs/devices/disks/DeviceName" PartitionNumber NewStartSector NewEndSector

--> Then grow the VMFS file system: 
vmkfstools --growfs "/vmfs/devices/disks/DeviceName:PartitionNumber" "/vmfs/devices/disks/DeviceName:PartitionNumber"

You can check official kb: https://kb.vmware.com/s/article/2002461 

Regards,
Dawid

[TheBigM]

Thank you, that solved my problem. However, the last command was not necessary for me. I created my own wiki article for this. No idea why this doesn't work in the GUI, but it worked without any problems. Although the fix command recognized a problem and apparently fixed it, the extension was still only possible via SSH command. Thanks again.

 

Greetings Mario