Errors during ESX 4.1 upgrade from 4.0

Posted on 2010-09-22
Last Modified: 2012-05-10
I am currently upgrading to 4.1 from 4.0 using esxupdate following these video instructions.

I encounter checksum errors and see that is normal and not considered harmful.

However, my upgrade just continues scrolling these errors along with more detail about options.
See attached picture. It just keeps cycling through the two pictures attached and never completes.

Any suggestions?
Question by:romatlo
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
LVL 26

Expert Comment

ID: 33738445
This is a known error from VMware. Does not affect to the server. However, I have always preferred the reinstall ESX instead of upgrade. Your server should be OK. Check this blog:


Author Comment

ID: 33738564
Thanks Inkevin.

I saw that, but you can see I have an extra screen of different errors and its still going in a loop.  My upgrade never completed and now I am scared that I may lose my VMs ...I know I should have backed up :(

I guess I could shut it down and power on to see what happens...
LVL 23

Expert Comment

by:Luciano Patrão
ID: 33738652

If you don't erase the vmfs partition(or any Storage disk) on your VMware host, the VMs are still in place, even after a new install.

I had so many issues regarding upgrades, that I decided that when is new big version, i do a fresh install.

Regarding your VMs are in a local storage? SAN?

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

LVL 26

Accepted Solution

lnkevin earned 400 total points
ID: 33738691
Upgrade OS won't affect your vm's either local storage or SAN storage. You can just stop the upgrade and reinstall ESX. When it asks you to keep the vm's make sure you check it. That's it! after you check the option to keep all your vm's it won't delete them.

LVL 23

Assisted Solution

by:Luciano Patrão
Luciano Patrão earned 100 total points
ID: 33738941

lnkevin that option is only necessary if the VMs are in the local storage. Today I install a new 4.1 in a 4.0 ESX that use boot from the SAN(this disk have 20Gb) and has also 4 more Storage(2 of 1Tb and 2 of 800Gb), i just choose the Storage to boot(boot from SAN 20Gb) and don't check it because I want to erase all that partitions and install a fresh one.

I install into that storage only and all is ok. After the install all the Storage are in place and all the VMs in the Storage SAN.

I do this on a VMware host that have boot from the SAN, if is local storage to install a new, for safety I disconnect the fibre cables before installing the new VMware version(I have seen many disasters when people want to install into a storage and install by mistake into the Storage that have the VMs). So my experience is that I always disconnect any SAN from the host before a new install(after the install, just reconnect).

Hope this can help others to be more careful with this type of install.


Author Comment

ID: 33748123
Excellent information!  I am using Direct attached storage.
I ended up hard powering off the server and after reboot everything is ok.
Not sure why the upgrade did not complete successfully.

I have one more to install so may use Inkevin method.

Thanks again!

Author Closing Comment

ID: 33748170

Featured Post

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
ISCSI and VM ESXI 6.0 28 137
esxi root user permission 7 78
Samsung Dex 3 98
PXE boot for ESXi on CENTOS 7 25 108
Will try to explain how to use the VMware feature TAGs in the VMs and create Veeam Backup Jobs using TAGs. Since this article is too long, I will create second article for the Veeam tasks.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
This Micro Tutorial steps you through the configuration steps to configure your ESXi host Management Network settings and test the management network, ensure the host is recognized by the DNS Server, configure a new password, and the troubleshooting…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question