Firstly, welcome to the forums, and above all, thank you for being an EMC customer.
Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility. Questions written to the users' own "Discussions" space don't get the same amount of attention and can go unanswered for a long time.
You can do so by selecting "Move" under ACTIONS along the upper-right. Then search for and select: "VNXe Support Forum".
I also tried to search our knowledgebase database and came up short for that specific code: 0x640100d (or even the decimal equivalent: 104861709). Unfortunately the closest I could find was an error code when renaming a datastore.
Error code 0x6000d50 while renaming the datastore on VNXe after renaming on the ESX server
I just encountered this same error while increasing a datastore as well.
After talking with tech support they indicated that this is an error in automatically updating the size to vSphere. We were able to manually add the space to the datastore in vSphere and everything seems to be working fine. The size increased correctly on the VNXe.
While increasing the size of VMWare datastore, VNXe triggers an automatic API call to ESX to increase the size. If that call fails, then VNXe generates the error message that "extension is completed in VNXe but need to increase the size manually on ESX."
For this issue, Please check if all ESX hosts are configured properly and showing in 'OK' state in host-->VMWare host page.
If yes, Please make sure that name of datastore on VNXe and on ESX are identical.
Resolution:
- If size has already been increased on VNXe but same is not visible on vCenter, Right click on datastore on ESX-->Properties and click on Increase option.
- If you see the LUN listed, finish the wizard. (Please make sure that naa ID and LUN ID of existing datastore is matching with extended LUN information).
If there are any inconsistency or require any assistance with this, Please open a case with VNXe team.
christopher_ime
6 Operator
•
1962 Posts
1105
0
Posted January 14th, 2014 22:00
Firstly, welcome to the forums, and above all, thank you for being an EMC customer.
Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility. Questions written to the users' own "Discussions" space don't get the same amount of attention and can go unanswered for a long time.
You can do so by selecting "Move" under ACTIONS along the upper-right. Then search for and select: "VNXe Support Forum".
VNXe Support Forum
I also tried to search our knowledgebase database and came up short for that specific code: 0x640100d (or even the decimal equivalent: 104861709). Unfortunately the closest I could find was an error code when renaming a datastore.
Error code 0x6000d50 while renaming the datastore on VNXe after renaming on the ESX server
https://support.emc.com/kb/164843
Once relocated, let's see what others may suggest; however, in the meantime if you haven't already I'd recommend opening up a ticket with EMC support.