ESX Error 15


Esx 4.0/4.1 might be not able to boot after reboot. It happens after update installation. Esx console says:

Filesystem type is ext2fs, partition type 0x83
uppermem 819200
kernel /vmlinuz ro root=UUID=ceadc074-b397-adcb-7b7604a8ab4a mem=800M quiet
[Linux-bzImage, setup-0x1e00, size=0x179cdc]
initrd /initrd.img

Error 15: File not found

Press any key to continue...

Console snapshot:

Quick look at usage space:

[root@esx8 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda5             4.9G  1.8G  2.9G  38% /
/dev/sda2             2.0G   97M  1.8G   6% /var/log
/dev/cciss/c0d0p1      99M   91M  2.9M  97% /boot
/dev/cciss/c0d0p2     4.9G  1.6G  3.1G  34% /esx3-installation
/dev/cciss/c0d0p1      99M   91M  2.9M  97% /esx3-installation/boot
/dev/cciss/c0d0p6     2.0G  114M  1.8G   7% /esx3-installation/var/log

There are still esx3 files remaining. This box has been upgraded from esx 3.x to esx 4.0. We can easily remove the old stuff with cleanup-esx3.

[root@esx8 ~]# cleanup-esx3
Are you sure you want to remove ESX v3 references and files? (y/N) y
Cleanup of ESX v3 successful.  Please reboot your system.
[root@esx8 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda5             4.9G  1.8G  2.9G  38% /
/dev/sda2             2.0G   97M  1.8G   6% /var/log
/dev/cciss/c0d0p1      99M   64M   30M  69% /boot
/dev/cciss/c0d0p2     4.9G  1.6G  3.1G  34% /esx3-installation
/dev/cciss/c0d0p1      99M   64M   30M  69% /esx3-installation/boot
/dev/cciss/c0d0p6     2.0G  114M  1.8G   7% /esx3-installation/var/log
[root@esx8 ~]#

Patrition table looks like that after the reboot.

[root@esx8 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sds5             4.9G  1.8G  2.9G  38% /
/dev/sds2             2.0G   89M  1.8G   5% /var/log
/dev/cciss/c0d0p1      99M   83M   12M  89% /boot

Comments:

Colin - Jul 6, 2011

Thankyou a life saver upgrading 6 production hosts memory got the this error once again thankyou

Roby - Oct 4, 2011

Really you save my life today. I was upgrading from V4.0 to ESXi V5 and at reboot of one of my hosts I get this error. MAny thanks for yu suggestion and resolution of the problem !!!!!! Thanks and regards. Roby

vmware