HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   Kernel Questions (http://www.howtoforge.com/forums/forumdisplay.php?f=6)
-   -   Debian Etch: After the kernel package install, lilo.conf is not changed (http://www.howtoforge.com/forums/showthread.php?t=12974)

milos 28th May 2007 09:38

Debian Etch: After the kernel package install, lilo.conf is not changed
 
Hi :)
Actually, since this is my first message here, let me yell: Hello World! :D

Now, the problem:
I got a Debian 4.0 Etch webserver, with AMD Athlon 64 X2 4200+ Dual Core, 2GB of RAM and 2 300GB SATA disks.
I've been "playing" with it for the last week or two (i'm no guru, just an ad hoc admin) and, although i'm satisfied with how everything works, it seems that have a problem:

First it looked like I'm unable to install any of the "virtual server" software. I tried OpenVZ, Xen and Linux Vserver and with all of them i get the same symptoms:
Installation passes ok, i get the "installation successful" message, but when i reboot -it doesn't work.

I noticed that when i enter the "uname -r" command after reboot, it shows the same kernel which was before the installation.
I checked the /boot dir and saw that all of the image files are there.
Finally, i checked lilo.conf and i saw that it remains unchanged...
This is the lilo.conf (it's same before and after install):
Code:

boot=/dev/sda
root=/dev/sda2
map=/boot/map
delay=20
default=Standardkernel

image=/boot/vmlinuz
        label=Standardkernel
        read-only
        initrd=/boot/initrd.img

Here's the contents of /boot dir after the installation of vserver (i prefer OpenVZ, but this is just a copy/paste after one of the tries):
Code:

boot.0800           
boot.0810           
map
config-2.6.18-4-amd64   
config-2.6.18-4-vserver-amd64   
System.map-2.6.18-4-amd64
System.map-2.6.18-4-vserver-amd64
initrd.img
initrd.img-2.6.18-4-vserver-amd64
initrd.img-2.6.18-4-amd64   
initrd.img-2.6.18-4-amd64.bak   
vmlinuz
vmlinuz-2.6.18-4-amd64
vmlinuz-2.6.18-4-vserver-amd64

As you can see, the image files are there...

I would try to change the lilo.conf manually and add the lines needed to boot the new kernel, but i'm away from the computer and so i depend on SSH i.e. if the system doesn't boot, i'm lost...

Can anyone help me to diagnose this problem?

Thanks,
Milos

falko 29th May 2007 13:36

You must change /etc/lilo.conf manually and run
Code:

lilo
afterwards, then you must reboot. There's no other way...

milos 29th May 2007 23:44

Thanks, Falko

I did it, but i must have made some error, because it didn't boot afterwards... :(

Good news is that i learned how to use my provider's Rescue System, it worked perfectly, yeah! :)

So, now that my server is back from the dead, can i ask you a favor to tell me what should i add in the lilo.conf?
This is my lilo.conf:
Code:

boot=/dev/sda
root=/dev/sda2
map=/boot/map
delay=20
default=Standardkernel

image=/boot/vmlinuz
        label=Standardkernel
        read-only
        initrd=/boot/initrd.img

This was what i added (and it didn't work):
Code:

image=/boot/vmlinuz-2.6.18-openvz-amd64
        label=OpenvzKernel
        read-only
        initrd=/boot/initrd.img

And, finally, here's the contents of /boot directory:
Code:

server1:~# dir /boot
boot.0800                      map
boot.0810                      patches-2.6.18-openvz-amd64
config-2.6.18-4-amd64          System.map-2.6.18-4-amd64
config-2.6.18-openvz-amd64      System.map-2.6.18-openvz-amd64
initrd.img                      vmlinuz
initrd.img-2.6.18-4-amd64      vmlinuz-2.6.18-4-amd64
initrd.img-2.6.18-4-amd64.bak  vmlinuz-2.6.18-openvz-amd64
initrd.img-2.6.18-openvz-amd64

Many thanks in advance!

falko 30th May 2007 17:12

Please use initrd.img-2.6.18-openvz-amd64 instead of initrd.img (
Code:

initrd=/boot/initrd.img-2.6.18-openvz-amd64
). And set default to OpenvzKernel.

milos 30th May 2007 20:54

It works! Thanks! :)

milos 30th May 2007 23:16

Sorry, wrong template, my mistake :)
You may delete this message. Thanks again!


All times are GMT +2. The time now is 19:27.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.