Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Florian Ernst wrote: MicheleM wrote: all worked fine untill I rebooted the machine and...ooops! The boot loader LILO failed with the LI code error. [...] But what did it happen? I think there is a bug somewhere. lilo should have detected it needed to be re-run and should have prompted you about this, unless it was configured otherwise. What does | # grep -A5 'lilo/runme' /var/cache/debconf/config.dat say? I upgraded a machine running lilo and debconf mailed me the following information: Subject: Debconf: Configuring lilo -- Deprecated parameters in LILO configuration Deprecated files have been found on your system. You must update the 'install=' parameter in your LILO configuration file (/etc/lilo.conf) in order to properly upgrade the package. The new 'install=' options are: new: install=bmp old: install=/boot/boot-bmp.b new: install=text old: install=/boot/boot-text.b new: install=menu old: install=/boot/boot-menu.b or boot.b -- Debconf, running at discord.proulx.com [ Debconf was not configured to display this note, so it mailed it to you. ] Reading that message I took care of the problem (by installing grub) before rebooting the system. But I can't help but wonder if something similar occurred with the original poster? It was mailed to me because I had set my debconf to 'critical' only and so it was prevented from showing me a dialog box. Although for something like this it would justify a critical rating. Bob signature.asc Description: Digital signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
This topic may be a few days old, but this is apparently exactly what happened to a server I admin remotely. When I upgraded to the new stable packages, I saw nothing that affected the kernel, therefore rerunning LILO didn't occur to me as something that needed to be done. Hopefully someone reported a bug report on this against LILO since Monday. Since no changes to the kernel should have affected LILO's boot configuration, it should have had no trouble booting up. Why do I have LILO running in the first place? When I installed from the Woody CD a year ago, that's all that was offered to me. I wasn't aware, at the time, of the problems known to occur with LILO and so didn't install grub. Now that I live a couple hundred miles from this machine, but continue to admin it, I wouldn't dare attempt to install a new boot loader unless I was physically present. Clinton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
This topic may be a few days old, but this is apparently exactly what happened to a server I admin remotely. When I upgraded to the new stable packages, I saw nothing that affected the kernel, therefore rerunning LILO didn't occur to me as something that needed to be done. Hopefully someone reported a bug report on this against LILO since Monday. Since no changes to the kernel should have affected LILO's boot configuration, it should have had no trouble booting up. Why do I have LILO running in the first place? When I installed from the Woody CD a year ago, that's all that was offered to me. I wasn't aware, at the time, of the problems known to occur with LILO and so didn't install grub. Now that I live a couple hundred miles from this machine, but continue to admin it, I wouldn't dare attempt to install a new boot loader unless I was physically present. Clinton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
This topic may be a few days old, but this is apparently exactly what happened to a server I admin remotely. When I upgraded to the new stable packages, I saw nothing that affected the kernel, therefore rerunning LILO didn't occur to me as something that needed to be done. Hopefully someone reported a bug report on this against LILO since Monday. Since no changes to the kernel should have affected LILO's boot configuration, it should have had no trouble booting up. Why do I have LILO running in the first place? When I installed from the Woody CD a year ago, that's all that was offered to me. I wasn't aware, at the time, of the problems known to occur with LILO and so didn't install grub. Now that I live a couple hundred miles from this machine, but continue to admin it, I wouldn't dare attempt to install a new boot loader unless I was physically present. Clinton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Hello again, On Thu, Jun 09, 2005 at 02:54:32PM -0700, MicheleM wrote: this is the output: anjuna:~# grep -A5 'lilo/runme' /var/cache/debconf/config.dat Name: lilo/runme Template: lilo/runme Owners: lilo [...] no more. Hm, strange, to me it looks like this question was never asked. I guess it's best to ask the lilo maintainers [EMAIL PROTECTED] about this, or you could send a bugreport against upgrade-reports... I personally don't use lilo myself, so I wouldn't dare venture any deeper into this problem. Cheers, Flo signature.asc Description: Digital signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Hello *, On Thu, Jun 09, 2005 at 08:23:39AM -0700, MicheleM wrote: 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 uprunning. But what did it happen? I think there is a bug somewhere. [...] I made a typescript's upgrade too but I don't think it's notable, of course you'll can ask me it. lilo should have detected it needed to be re-run and should have prompted you about this, unless it was configured otherwise. What does | # grep -A5 'lilo/runme' /var/cache/debconf/config.dat say? Cheers, Flo signature.asc Description: Digital signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
On Thu, Jun 09, 2005 at 08:08:08PM +0200, Florian Ernst wrote: Hello *, 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 uprunning. But what did it happen? I think there is a bug somewhere. [...] I made a typescript's upgrade too but I don't think it's notable, of course you'll can ask me it. lilo should have detected it needed to be re-run and should have prompted you about this, unless it was configured otherwise. What does | # grep -A5 'lilo/runme' /var/cache/debconf/config.dat say? Why do people insist on using LILO? Just install grub, set it up once with symlinks and *never* mess with it again. In case anyone cares, here is my configuration: default 0 timeout 5 color cyan/blue white/blue title Debian GNU/Linux root(hd0,1) kernel /vmlinuz root=/dev/hda3 ro vga=normal ide0=ata66 ide1=ata66 boot title Debian GNU/Linux (recovery mode) root(hd0,1) kernel /vmlinuz root=/dev/hda3 ro single vga=normal ide0=ata66 ide1=ata66 boot title Debian GNU/Linux, OLD root(hd0,1) kernel /vmlinuz.old root=/dev/hda3 ro vga=normal ide0=ata66 ide1=ata66 boot title Debian GNU/Linux, OLD (recovery mode) root(hd0,1) kernel /vmlinuz.old root=/dev/hda3 ro single vga=normal ide0=ata66 ide1=ata66 boot I installed it *one* time to the MBR. I have only since had to mess with it to replace the failed harddrive in the machine. If you have /boot on a separate partition, as I do, you will want to add 'do_symlinks = No' to /etc/kernel-img.conf. Trust me on this. It is really nice to have a boot loader that can actually read your filesystem. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr pgpOSyrM8YMun.pgp Description: PGP signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Hello *, On Thu, Jun 09, 2005 at 04:46:32PM -0400, Roberto C. Sanchez wrote: Why do people insist on using LILO? Just install grub, [...] Advocacy is one thing, trying to find out why a bug has occurred another. Let's try not to mix things up. Cheers, Flo signature.asc Description: Digital signature
Re: Release upgrade from Woody to Sarge failed reboot lilo problem
Hi Flo, this is the output: anjuna:~# grep -A5 'lilo/runme' /var/cache/debconf/config.dat Name: lilo/runme Template: lilo/runme Owners: lilo Name: lilo/upgrade Template: lilo/upgrade Owners: lilo I grep the upgrade's typescript searching for the lilo prompt but this is what I found: anjuna:~# cat /backup/typescript |grep lilo libxaw7 libxerces2-java libxml1 libxml2 lilo links login logrotate lpr libxaw7 libxerces2-java libxml1 libxml2 lilo links login logrotate lpr libxaw7 libxerces2-java libxml1 libxml2 lilo links login logrotate lpr libxaw7 libxerces2-java libxml1 libxml2 lilo links login logrotate lpr Get:493 http://debian.fastweb.it sarge/main lilo 1:22.6.1-6.2 [343kB] Get:494 http://debian.fastweb.it sarge/main mbr 1.1.5-2 [20.4kB] Preparing to replace lilo 1:22.2-3 (using .../lilo_1%3a22.6.1-6.2_i386.deb) ... Unpacking replacement lilo ... Setting up lilo (22.6.1-6.2) ... no more. thanks Flo Mik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
