Query: extended raid on P2000 G3 SAS doesnt show on VMWare

[AtypicalITGuy]

Hello,

a client is using a P2000 G3 SAS, which recently got two new drives that expanded a raid 5 volume (by 1.2 TB from 5.4 TB to 6.6 TB). VMWare however doesn't recognize the increased storage size. It still shows the 4.9 TB that it had before the changes.

I'm not familiar with these systems and couldnt find the reason for this behavior. Are any more steps necessary for VMWare to accept the increase in storage size? The only thing not being tried so far is rebooting the host server. Would this be the solution or am I missing something on the configuration side?

[support_s]

System recommended content:

1. HPE P2000 G3 MSA Array Systems -Troubleshooting

2. HPE P2000 G3 MSA Array Systems - Product Information Reference | Software Compatibility

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[AtypicalITGuy]

Unfortunately I couldn't find anything in the given links that solves the issue.

[AtypicalITGuy]

I've tried some additional troubleshooting:

The entire system has been restarted. All 3 physical servers have been restarted simultaneously. 

Afterwards, the storage adapter and datastore was rescanned. 

Still no success... here are screenshots of the current raid configuration, maybe I'm missing something? (Before enhancing the raid was 5.4 TB). The storage has been expanded before, so I know it works. 

[Vinky_99 · Accepted solution]

@AtypicalITGuy 

You may give try to the below instructions:

1. In the VMware vSphere client, navigate to the host server's configuration tab and select "Storage Adapters." From there, right-click on the SAS storage adapter and choose "Rescan." This action prompts VMware to re-scan the storage devices connected to the server and detect any changes.

2. In the VMware vSphere client, go to the host server's configuration tab and select "Storage." Then, click on the datastore and choose "Properties." In the Properties window, select "Manage Paths" and click "Rescan." This action triggers VMware to rescan the VMFS volumes and update the available storage capacity.

3. Ensure that the RAID array expansion process completed successfully on the P2000 G3 SAS. Verify the expanded capacity is reflected in the storage array management interface. If the expansion process is still in progress or encountered any errors, it might not be visible to VMware until it is completed or resolved.

4. Confirm that the newly expanded LUN (logical unit number) is visible to the VMware host server. You can do this by checking the storage adapter and LUN masking settings on the P2000 G3 SAS. Ensure that the host server has the necessary permissions to see and access the expanded storage.

5. If the LUN is visible, but the expanded capacity is still not recognized, it's possible that VMware is not detecting the updated VMFS signature. In this case, you can try resignaturing the VMFS volume. To do this, navigate to the host server's configuration tab, select "Storage," and click on the datastore. Choose "Properties" and then "Manage Paths." From there, click "Unmount" and then "Mount." This action triggers the VMFS resignaturing process, which can detect the changes in the storage volume.

If none of the above steps resolve the issue, you may need to consider rebooting the host server as a last resort.

NOTE: when performing any configuration changes or rebooting a production server. It's always a good idea to have a backup for safer side.

Hope this helps!

[JonPaul]

@AtypicalITGuy 
As pointed out, the problem is likely the ESX instance not detecting the expanded capacity.  It might be a good idea to go to a VMware forum.
I did find this which I think is basically the same info from Vinky_99:  https://kb.vmware.com/s/article/1011754

[Sham82]

Hello,

Please follow - https://kb.vmware.com/s/article/1011754

If the issue remains , please contact Vmware support.

Regards

HPE