Kernel Update ---> System offline !

[aboukouris]

Hi,

I saw the warnings about old kernel security issues, and i thought i should update my kernel's (i have 3 servers).

I read this forum about known problems, or issues, and i read that you can update kernel using yum update, without problem, and cpanel will not crash.

.... well i did it, and system doesn't work since i rebooted.

System is going on only in read-only filesystem. I found that mtab is not the right one, so i changed (changed back system to read/write) but when i reboot it does some things again.

What shall i do? Cpanel and WHM is not working at all...

what else a kernel update can do to a machine, becuase the other 2 servers i have are realy critical!

Thank you,

Alexander

 

[compunet2]

A bad kernel update can render a machine completely unbootable.

 

[dalem]

edit your Grub or lillo boot loader (which ever one your using) to boot to your old kernel

if you have no console access to your server you should really only boot to the new kernel once and if there is no problems then change your grub or lillo config

li

 

[aboukouris]

i found a way to bring machine to live, but is only a temporary...

i change filesystem to RW with "mount -o remount /dev/hda2".
I start services manualy with "service start ...".

Now i can access cPanel, since i open the service cpanel.

Is there anything i can do from there?
I think my problem is that system is coming up in Read Only mode... shall i try re-update kernel?
Does cpanel can do anything?

Thanks,

Alexander

 

[thehostinghut]

You may want to contact your datacenter. They may be able to help. They may charge a small fee to do it though.

This would not be a cPanel problem as they are not responsible for this kind of thing.

Thanks

 

[jsnape]

What shall i do? Cpanel and WHM is not working at all...

what else a kernel update can do to a machine, becuase the other 2 servers i have are realy critical!

Thank you,

Alexander

2 words - hire somebody

but its an easy fix if you have physical access, or a console. While its booting, when grub comes up press the down arrow and choose the old kernel. But your best bet might be, transfer the remaining 2 and the one w/problem (after booting into the old kernel) to a new machine, with console access, and line someone up for the things you can't do.

 

[aboukouris]

hire somebody is not an option, since i don't have managed server, and i don't want to have one.

I could solve this problem with some help...

do you believe the problem is on the kernel? shall i re-install kernel?
How can i change back to the old kernel from ssh?

thanks in advance,
Alexander

 

[nyjimbo]

hire somebody is not an option, since i don't have managed server, and i don't want to have one.

I could solve this problem with some help...

do you believe the problem is on the kernel? shall i re-install kernel?
How can i change back to the old kernel from ssh?

thanks in advance,
Alexander

I think you should be asking this in a REAL linux forum, not here. This is something you will need a bunch of kernel hacker types to look into and they will probably want to know some specific information.

Find out a good forum for your linux version and post a thread with ALL the details of the things you did and you are more likely to get better answers there.

 

[nickp666]

It may just be that your hard drive is dying, linux will boot read-only if the drive is having problems, have you asked the dc to look at that first?