Having issues updating vMWare vCenter

[naquino1]

Hello I work for an IT Company and one of our clients has a vCenter server that I am trying to update to 7.0 u3f. and its having issues.

The update failed at 87% and I got an error saying Precheck test of one or more RPMs failed, then I saw that the drive went to 100% space. I went ahead and restored to the snapshot taken pre-update and expanded the drive. I wanted to retry the update so I turned off the vCenter server to take a snapshot and when I turned it on the storage drive that I just expanded is back to 100%. Can I get some assistance?

[a_p_]

Please explain which drive exactly you did expand, and how you did it (steps taken).

André

[ganeshteja55]

if its log partition try below - https://kb.vmware.com/s/article/83070
log partition will not allow the services to start, partially you can attemt to expand the disk from ESXi where the vCenter is hosted.
if its archive partition - you can ignore

[swint]

Doesn't sound like you're having the exact problem this KB describes, but the Resolution steps given within describe rebuilding the vCenter's RPM database, which might be worth trying in your situation. Perhaps the precheck is failing against a corrupted RPM package.

"Error in method invocation rpmdb open failed", error while upgrading vCenter Server Appliance 6.x/7...

Regarding the disk space issue, you can read through the following KB article which contains some great information as well as links to some description documentation that details what the different vCSA disks are used for. 

vCenter Server Appliance disk space is full (vmware.com)

List of VMDKs/Partitions for a vCenter Server 7.0 - Size Mount point and Purpose (78515) (vmware.com...

[naquino1]

I expanded the hard disk 4 the core drive partition. It went 100% to 40gb so I expanded it to 80gb and I follow the commands on this page. https://kb.vmware.com/s/article/2145603 and right now its at at 78.6gn and it all got used up after I turned off the VM again to create the snapshot and try the update.

[naquino1]

It is the core partition.

[ganeshteja55]

https://kb.vmware.com/s/article/68020
https://kb.vmware.com/s/article/76563
Validate these two as well. if still unbable to find the issue create a SR.