Hi there,
yesterday I tried to upgrade my Woody production server to Sarge after
reading and following step by step the relase notes under:
http://www.debian.org/releases/sarge/i386/release-notes/ch-upgrading.en.html
all worked fine untill I rebooted the machine and...ooops! The boot
loader LILO failed with the "LI" code error.
No way to boot the machine. I solved the problem with a knoppix live
cd, I mounted the root partition, chrooted into it, mounted /boot
partition and run "lilo".
After reboot the server was up&running.
But what did it happen? I think there is a bug somewhere.
I post my "ls -l /boot":
total 4513
-rw-r--r-- 1 root root 512 2005-01-25 00:50 boot.0800
lrwxrwxrwx 1 root root 11 2005-01-25 00:48 boot.b -> boot-menu.b
-rw-r--r-- 1 root root 308326 2005-06-09 01:00 coffee.bmp
-rw-r--r-- 1 root root 3342 2005-01-25 00:45 config-2.4.28-bf2.4
-rw-r--r-- 1 root root 26684 2005-02-08 20:06 config-2.4.29
lrwxrwxrwx 1 root root 15 2005-06-09 01:00 debian.bmp ->
/boot/sarge.bmp
-rw-r--r-- 1 root root 153720 2005-06-09 01:00 debianlilo.bmp
-rw------- 1 root root 46080 2005-06-09 14:19 map
-rw-r--r-- 1 root root 23662 2005-06-09 01:00 sarge.bmp
-rw-r--r-- 1 root root 24116 2005-06-09 01:00 sid.bmp
-rw-r--r-- 1 root root 568549 2005-01-25 00:45
System.map-2.4.28-bf2.4
-rw-r--r-- 1 root root 668419 2005-02-08 20:11 System.map-2.4.29
-rw-r--r-- 1 root root 1298076 2005-01-25 00:45 vmlinuz-2.4.28-bf2.4
-rw-r--r-- 1 root root 1477532 2005-02-08 20:11 vmlinuz-2.4.29
and the "/etc/lilo.conf"
# /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', 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'. |
# | |
# +---------------------------------------------------------------+
# Support LBA for large hard disks.
#
lba32
# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81
#disk=/dev/sda
# bios=0x80
# 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/sda
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/sda4
# 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: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b
# 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
timeout=150
# prompt
# single-key
# 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-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
# Boot up Linux by default.
#
default=Linux
image=/vmlinuz
label=Linux
read-only
# restricted
# alias=1
image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2
# 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
other=/dev/sda1
label="Other(sda1)"
I made a typescript's upgrade too but I don't think it's notable, of
course you'll can ask me it.
I would know what packet is involved in the accident so I can fill a
bug ticket.
Thank you.
Michele
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
