Re: 5.5 U1 Install not seeing existing esxi installation

Cause

This issue occurs when the /bootbank/state.XXXXXXXX directory is not empty.

Resolution

To resolve this issue, ensure the /bootbank/state.XXXXXXXXdirectory is empty.

To ensure the /bootbank/state.XXXXXXXX directory is empty:

1. Log in to the ESXi Management console.
2. Run the command:
   
   cd /var/log
3. Using the grep command, find state.XXXXXXX and its corresponding directory within the vua.log file (replace XXXXXXX with the number indicated in the error)
   
   For example:
   grep state.31110473 vua.log
4. Run these commands:
   
   cd /bootbank/
   run ls -l
   Note: The preceding commands may also be required on /altbootbank because this directory can also hold state.XXXXXXX.
5. Run this command to change directory to state.XXXXXXX directory indicated in the /var/log/vua.logfile:
   
   cd state.XXXXXXX
   For example:
   
   cd state.31110473
6. Run this command:
   
   run ls -lYou see an output similar to:
   
   -rwx------ 1 root root 18297 Jan 10 2011 local.tgz
7. Note the name of the file within the state.XXXXXXXdirectory. For example, local.tgz.
8. Run this command to move the file up one directory level:
   
   mv file_name ../
   Where file_name is the name of the file noted in Step 7.
   
   For example:
   
   mv local.tgz ../
9. In vCenter Server, remediate the host.
   
   
   1. Select the ESXi host.
   2. Click the Update Manager tab.
   3. Click Remediate.