WilliamEnright
Contributor
Contributor

Remediation of ESX Host Failed: Reboot - Error 15: File Not Found

Jump to solution

Received error "Update Manager Encountered an Error" during remediation. Rebooted ESX host and received error 15. Can someone tell me how to fix this?

Last build was ESX Server, 3.5.0, 113339 - Successfully remediated it's partner to build 123630 - both identical Dell 2950's.

Much thanks in advance - let me know any additional information I can give.

William.......

Here's the boot screen:

Booting 'VMWare ESX Server'

root (hd0,0)

Filesystem type is ext2fs, partion type 0x83

uppermem 277504

kernel - no-mem-option / vmlinuz - 2.4.21-57 -ELvmnix ro root=UUID=b46f9a6d-e45d-4204-9609-c2e376d2b80f mem=272M

initrd / initrd - 2.4.21-57.ELvmnix.Img

Error 15: File Not Found

0 Kudos
1 Solution

Accepted Solutions
Texiwill
Leadership
Leadership

Hello,

The Update failed on creating the initrd image for the vmkernel you wanted to use. THe solution is to boot into 'Linux' or Tech Support Mode and rebuild the initrd image using esxcfg-boot -r


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

SearchVMware Blog: http://itknowledgeexchange.techtarget.com/virtualization-pro/

Blue Gears Blogs - http://www.itworld.com/ and http://www.networkworld.com/community/haletky

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2022,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill

View solution in original post

0 Kudos
7 Replies
Texiwill
Leadership
Leadership

Hello,

The Update failed on creating the initrd image for the vmkernel you wanted to use. THe solution is to boot into 'Linux' or Tech Support Mode and rebuild the initrd image using esxcfg-boot -r


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

SearchVMware Blog: http://itknowledgeexchange.techtarget.com/virtualization-pro/

Blue Gears Blogs - http://www.itworld.com/ and http://www.networkworld.com/community/haletky

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2022,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
pieter_b
Contributor
Contributor

sorry to hijack this thread but I am having exactly the same issue and I am unable to boot into vmware esx mode nor debug mode nor troubleshooting mode, it allways gives me the Error 15 file not found

Do you have any other suggestions ?

thanks

Pieter

0 Kudos
marony360
Contributor
Contributor

I have exactly the same Problem. I can't start the ESX Host no matter what start option (Debug Mode oder Serviceconsole) i choose. What can i do?

0 Kudos
WilliamEnright
Contributor
Contributor

I ended up burning update 3 to a CD, and doing a manual upgrade to the ESX server.

William

0 Kudos
marony360
Contributor
Contributor

Thank you William for your fast reply. I just called the dell support, because I can't believe that there is not something like a recovery console from cd? Where you can start the esx-boot -r command.

@Willaim: Did you find something like a recovery console?

0 Kudos
WilliamEnright
Contributor
Contributor

Nope,

No recovery console that I was made aware of.

William

0 Kudos
FDUBUC
Contributor
Contributor

got the error on my esx server after update manager failed:

file system type is ext2fs, partition type 0X3 uppermem 277504

kernel = --no-mem-option /vmlinuz-2.4.21-47.0.1.Elvmnix ro root UUID=f228cd6d3-75a1-4c8d-bbb7-bdc5cc09777f mem=272m

[Linux-bzImage, setup = 0X1400, szie = 0X14e372}

initrd /initrd-2.4.21-47.0.1.ELvmnix.img

Error 15 file not found "

Fixed with:

reboot in troubleshooting mode

- esxcfg-boot -p

- esxcfg-boot -b

- esxcfg-boot -r

reboot in normal mode

Done!!

0 Kudos