ESX not coming online during reboot (after patching)

[gothicreader]

Hi,

I rebooted the ESX this morning after patching, and now I'm getting the following error:

"root (0;0)

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 "

ESX350-200808201-UG - PATCH

Sorry for my ignorance in this, but I'm very limited in knowledge when it comes to Linux commands to reload the kernel or load the right kernel.

Judy

[gothicreader]

After further research........................

I was finally able to get into the "troubleshooting mode". In looking at the log file, it's looking for:

esxcfg-boot: 2008-10-07 08:12:01 (847) ERROR: Could not copy '/boot/initrd-2.4.21-47.0.1.ELvmnix.img' to '/tmp/vmware.0.tmp': No such file or directory

When I look at the grub.conf file:

vmware:configversion 1

1. grub.conf generated by anaconda

#

1. Note that you do not have to rerun grub after making changes to this file

1. NOTICE: You have a /boot partition. This means that

1. all kernel and initrd paths are relative to /boot/, eg.

1. root (hd0,0)

1. kernel /vmlinuz-version ro root=/dev/cciss/c0d0p2

1. initrd /initrd-version.img

#boot=/dev/cciss/c0d0

timeout=10

default=0

title VMware ESX Server

#vmware:autogenerated esx

root (hd0,0)

uppermem 277504

kernel --no-mem-option /vmlinuz-2.4.21-57.ELvmnix ro root=UUID=f28cd6d3-75a1-4c8d-bbb7-bdc5cc09777f mem=272M

initrd /initrd-2.4.21-57.ELvmnix.img

title VMware ESX Server (debug mode)

#vmware:autogenerated esx

root (hd0,0)

uppermem 277504

kernel --no-mem-option /vmlinuz-2.4.21-57.ELvmnix ro root=UUID=f28cd6d3-75a1-4c8d-bbb7-bdc5cc09777f mem=272M console=ttyS0,115200 console=tty0 debug

initrd /initrd-2.4.21-57.ELvmnix.img-dbg

title Service Console only (troubleshooting mode)

#vmware:autogenerated esx

root (hd0,0)

uppermem 277504

kernel --no-mem-option /vmlinuz-2.4.21-57.ELvmnix ro root=UUID=f28cd6d3-75a1-4c8d-bbb7-bdc5cc09777f mem=272M tblsht

initrd /initrd-2.4.21-57.ELvmnix.img-sc

Which is pointing to a different file.

So, more than likely I need to find the "initrd-2.4.21-47.0.1.ELvmnix.img" file.

When I look in the boot directory, this file is missing, except for the "initrd-2.4.21-57.ELvmnix.img"

So, I'm betting I have to find this find and move it back to the boot directory?

[gothicreader]

I went ahead and rebuilt the ESX host server since I figured my virtual machines are on a datastore (san).

Everything went smoothly and I can see the datastores. However, the million dollar question is, why don't I see these virtual machines in the VI client? Even though the datastores are present?

In fact the ESX host server has these datastores mapped, therefore, when I got to directory /vmfs/"I see and browse the VM's".

If I start up the VM converter, and log into the ESX host server, none of the virtual machines show up.

How do I point these VM back to this ESX host servers?

Thanks

Judy

[gothicreader]

I found the solution!

""Try to upload the .vmx and .vmdk to your datastore. Then use the datastore browser and point to the .vmx file and choose add to inventory."