Wer kann helfen?

[Chrischnian]

Hey Leute
also nach meinen letzten Problem das ich nach einen Update mit APT hatte wollte ich dies nun mal wiederholen und vielleicht andere auch damit zu helfen!!

Mein altes Posting: http://www.debianforum.de/forum/viewtop ... highlight=

So ich habe damals dann die Kiste neu installiert und da ich heute Abend auch einen neuen Rechner bekomme gehe ich nun keine große Gefahr ein, da ich sowieso neu installieren wollte.

Ich habe gerade ein APT-GET UPDATE und danach ein APT-GET UPGRADE gemacht.
Diesmal habe ich die ganzen Meldungen mit geschreiben

Hier mal schnell die Meldungen:

Code: Alles auswählen

Richte kernel-image-2.6.8-1-386 ein (2.6.8-10) ...

 You are attempting to install a kernel version that is the same as
 the version you are currently running (version 2.6.8-1-386). The modules
 list is quite likely to have been changed, and the modules dependency
 file /lib/modules/2.6.8-1-386/modules.dep needs to be re-built. It can
 not be built correctly right now, since the module list for the
 running kernel are likely to be different from the kernel installed.
 I am creating a new modules.dep file, but that may not be
 correct. It shall be regenerated correctly at next reboot.

 I repeat: you have to reboot in order for the modules file to be
 created correctly. Until you reboot, it may be impossible to load
 some modules. Reboot as soon as this install is finished (Do not
 reboot right now, since you may not be able to boot back up until
 installation is over, but boot immediately after). I can not stress
 that too much. You need to reboot soon.

Please Hit return to continue.
Not touching initrd symlinks since we are being reinstalled (2.6.8-5)
Not updating image symbolic links since we are being updated (2.6.8-5)
A new kernel image has been installed, and usually that means
that some action has to be taken to make sure that the new
kernel image is used next time the machine boots. Usually,
this entails running a ``bootloader'' like SILO, loadlin, LILO,
ELILO, QUIK, VMELILO, ZIPL, or booting from a floppy.   (Some
boot loader, like grub, for example, do not need to be run on
each new image install, so please ignore this if you are using
such a boot loader).

A new kernel image has been installed at /boot/vmlinuz-2.6.8-1-386
 (Size: 1066kB)


 Initial rootdisk image: /boot/initrd.img-2.6.8-1-386 (Size: 4184kB)

Symbolic links, unless otherwise specified, can be found in /

LILO sets up your system to boot Linux directly from your hard
disk, without the need for booting from a boot floppy.


WARNING
If you are keeping another operating system or another version
of Linux on a separate disk partition, you should not have LILO
install a boot block now. Wait until you read the LILO documentation.
That is because installing a boot block now might make the other
system un-bootable. If you only want to run this version of Linux,
go ahead and install the boot block here. If it does not work, you
can still boot this system from a boot floppy.

You already have a LILO configuration in /etc/lilo.conf
Install a boot block using the existing /etc/lilo.conf? [Yes] Yes
Testing lilo.conf ...
An error occurred while running lilo in test mode, a log is
available in /var/log/lilo_log.24121. Please edit /etc/lilo.conf
manually and re-run lilo, or make other arrangements to boot
your machine.
         Please hit return to continue
_________
	 
workstation:/var/log# cat lilo_log.24121
Fatal: open /initrd.img: No such file or directory
workstation:/var/log#

Mein Problem ist nun folgendes was muss ich machen damit der Rechner danach wieder normal startet?

Da ich die Probleme wie ich sie davor hatte umgehen möchte!!

Kann mir jemand Tipps geben?

Gruß

Chris

[rotwein]

Hallo,

Poste bitte mal den Abschnitt aus der /etc/lilo.conf der den neuen und deinen alten Kernel betreffen. Vielleicht sieht man dann ja mehr.

Gruß rotwein

[steos]

Folgendes sollte genügen: Zur Sicherheit

Code: Alles auswählen

...# /usr/sbin/lilo 

aufrufen und Rechner rebooten. Die Pfade in Lilo sollten sich aufgrund des Ersetzen des alten Kernels durch einen neuen nicht ändern; die Symlinks werden deswegen offenbar nicht umgesetzt:

Not touching initrd symlinks since we are being reinstalled (2.6.8-5)
Not updating image symbolic links since we are being updated (2.6.8-5)

Poste aber sicherheitshalber deine /etc/lilo.conf.

Bei GRUB entfällt der neuerliche Aufruf des Bootmanagers (= narrensicher; einer der Gründe warum ich GRUB und nicht Lilo einsetze ):

(Some boot loader, like grub, for example, do not need to be run on each new image install, so please ignore this if you are using such a boot loader).

dpkg nimmt bei GRUB alle notwendigen Änderungen von selbst vor, ich nehme an, das gilt auch für Lilo.

You are attempting to install a kernel version that is the same as the version you are currently running (version 2.6.8-1-386). The modules list is quite likely to have been changed, and the modules dependency file /lib/modules/2.6.8-1-386/modules.dep needs to be re-built. It can not be built correctly right now, since the module list for the running kernel are likely to be different from the kernel installed.

dpkg muß diese Warnung ausgeben, da sie Module des alten Kernels bei der Installation des neuen ersetzt werden müssen. Nachdem der alter Kernel aber noch läuft, kann dieser nach der Installation des neuen Kernels seine Module nicht mehr finden -> s' kracht. Deswegen _muß_ man stets nach Installation eines neuen Kernels durchbooten.

[Chrischnian]

Hier mal meine lilo.conf

Code: Alles auswählen

# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt' (if you have created it), or   |
# | install a new kernel.  The computer will most likely fail to  |
# | boot if a kernel-image post-install script or you don't       |
# | remember to run `lilo'.                                       |
# |                                                               |
# +---------------------------------------------------------------+

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda2

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: text, bmp, and menu
# Look in lilo.conf(5) manpage for details
#
#install=menu

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
#       prompt
#       delay=100
#       timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
vga=normal

# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWTO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""

# If you used a serial console to install Debian, this option should be
# enabled by default.
# serial=

#
# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
        label=Linux
        read-only
#       restricted
#       alias=1

        initrd=/initrd.img

image=/vmlinuz.old
        label=LinuxOLD
        read-only
        optional
#       restricted
#       alias=2

        initrd=/initrd.img.old


# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
#       label=HURD
#       restricted
#       alias=3