Give us more information about your problem's situation please
Did you upgrade the VCSA to up3 completely and then issue has been occurred?
Did you check remaining spaces of your VCSA virtual Disks (VMDK)?? (df -h)
and one point: you said bare metal... do you means your old VCSA is a physical/Windows-Based vCenter server?Please mark my comment as the Correct Answer if this solution resolved your problem
here some more Information:
We use VMWare ESXi since 8 years or so. The vCenter Server was long time a physical Server (2008R2). At the last big Upgrade we use the Chance and switch with the Migration Assistant to a VSCA.
The Appliance works fine. The Conditions are good. The Management Interface looks fine.
The Installed Version is 126.96.36.1990. I Update the Server over the Management Port.
First i try the update to .3000 and it fails. After the Restart, the Center Server crash direct at the Start. AFAIK ( in can check it tomorrow) i see in the vpxd.log Exit Code 1.
I have restore the Backup. Restart the Server and go back to the "daily doing".
I try then the next Update in May (.3100?) and the last time the Update mid July. Same Problem. The most Services Starts fine, Center Server crashes at start.
The Disks looks good (i check it tomorrow again). I think, there is a bad Config since long time (we Migrate the Server from 5->5.5->6.0->6.5). The only 3rd Party Plugin is IBM Spectrum Protect (v 8.4.1).
- Is your Host based on a Intel Skylake or newer?
- If you have updated VCSA vHW to higher than 10/13?
Did you check the firstboot.log? There may be some information about all problematic state of your VCSA.
Is your PSC embedded or external? did you check its services?
What's the status of license of vCenter? Did you check its correctness after upgrade?
If you migrate your VCSA's VM to another ESXi, is the problem still exist or not?Please mark my comment as the Correct Answer if this solution resolved your problem
Processor is Xeon E5-3650 (Sandy Bridge)
VSCA HW is 13.
The Hostsystem is a ESX 6.5 on IBM X Series.
I try at the First Tests a nother ESXi Server, and same Problem.
Licences are ok (but this Service also Crash)
I check now the firstboot log.
On another Host it is the same. PSC is embedded. I can try another Update today, and make a List which Services are crashed.
In April this year i updated a customer environment
- 6.5/6.7? -> VCSA 6.7latest
- Replace Dell Server with R740(Skylake)
All went very well and runs 2 days.... until i schedule the vHW upgrade of the VCSA to the latest/highest and pressing the restart button. After that our VCSA reacts as same as hours which mean a lot of servcies starting very well but at the end some are crashing or not starting and already started services disapeers.
We opened a #SR and it took a long fight with GSS and after 3 days they found the solution
- As we knows within the vHW also its hardcoded which CPU features are presented to the VM(GuestOS)
- The VCSA contains libraries which acts differently when seeing a Skylake and the Features are enabled. Certains code contains bugs the the services crashed or never starts
The engineer de-register the VCSA VM, edit the *.vmx and change vHW to 10. Register and starts the VM and our VCSA was back into the game and runs perfectly.
Your CPUs are older so its another issure youre facing. I suggest to open a #SR.
GSS als says they seen a lot of problem when the VCSA is jonied a Windows AD. The suggest to use the "LDAP" option to connect to AD rather than using the kerberos integration.
i can check the HW. I upgrade the HW for a last change yesterday. The redeployment from the Backup with the old vHW ist easier.
I restore the VSCA from the Backup. Select Medium Type for more resources. vHW Type is 10.
Shutdown the VM for Snapshot.
Reboot and Install the Upgrade at the WebUI.
Image Builder (we don´t use it)
Profile Storage Service
I don´t have access to Licence Server to check it. I try at Monday Backup and Restore a VSCA to a new ESXi with the .3200 Version.
I check the first logs, and its look like a fail from vmware-sps. I think a need disable the 3rd Party Plugin and Check the Configs.
How you are trying to update
By command line or GUI.
What error you are getting , provide full name of ISO which you are using for upgrade.
I use the WebUI (Port 5480)
Patch for VMWare VCSA 188.8.131.52000 from Jul 16.
Have you logged a support call?
Yes i have.
I start later with the next try.
So, some testing and clean up and found a Problem.
I can't delete one Datacenter. There are a datastore who has no Host and some old Networks (without any hosts).
Any hint how can I delete these? I can access the DB or shell if we need it.
Use in CLI (Shell/SSH) following commands to show your datastore's attributes:
esxcli storage vmfs extent list
esxcli storage core device list
Then copy naa.xxx of considered for next command:
esxcli storage core device detached remove -d naa.xxxPlease mark my comment as the Correct Answer if this solution resolved your problem