I have a Centos 6.4 server(Yum repo server -has internet connectivity). When we rebooted the server it's not booting and it went into grub. It shows two kernels in grub
2.6.32-358.el6.x86_64(default)
2.6.32-358.18.1.el6.x86_64

I followed the steps to boot with default kernel
find /vmlinuz-2.6.32-220.el6.x86_64
root (hd0,0)
kernel /vmlinuz-2.6.32-358.el6.x86_64 ro root=LABEL=/
initrd /initramfs-2.6.32-358.el6.x86_64.img
boot

But it's not booting neither in my old/new kernel. Any inputs will be much appreciated.
PFA screenshot for the same. Thanks in advance

Attached Thumbnails

   

check out this link it might help:
http://blog.techprognosis.com/2013/0...r-upgrade.html

Boot from rescue disk, give it to find and mount your installation, chroot into it.
Then you have to recreate initramfs by dracut according to your installation.

Usual reason for not finding / , is missing driver for something in initrd/initramfs.
You need to detect required drivers for disk subsystem and add them to /etc/dracut.conf, like:
add_drivers+="driver1 driver2 driver3"

Then rebuild initramfs to your boot kernel (not to rescue kernel, often mistake).

I entered into rescue mode then mounted the system in /mnt/sysimage using chroot. I then backed up the initramfs file and gave the command

dracut -f initramfs-2.6.32-358.el6.x86_64.img 2.6.32-358.el6.x86_64

the system rebooted and entered grub again. I found my grub.conf file was empty. I have LVM partitions in the system. Is it possible to create grub.conf file again, if so what about the information pertaining to LVMs

Sure, you can. Rescue disk again and check why it is missing.
It shouldn't go away by itself.

You even can bring network up + sshd, when in chrooted environment
to have much easy work with rescued system.

Hi

Can you please elaborate it, I have assigned IP address and even taking the system remotely. How could I find what went wrong in grub and where to look. Even menu.lst which is pointing to grub is empty. Do we have any tool to create grub automatically or we have to create manually.

I *guess* that you do not see grub stuff in chrooted system.
This usually happen when /boot not mounted, or vice versa,
grub was installed (by script mistace) before /boot mounted.
This could happen with strange hardware, or installation

I cannot help you remotely, because this weekend i'll be without internet.
But i still have couple of hours online just now. My skype user voleg4u

Thanks for the help. I need to get permission from network team. But as you said this kind of issue happens on a strange hardware, this is a virtual machine(base proxmox) on IBM HS 23 blade. Do we have any option of bringing the server back.