Bug#424596: linux-image-2.6.18-4-amd64: Running lilo after upgrade seems to hang
Package: linux-image-2.6.18-4-amd64
Version: 2.6.18.dfsg.1-12etch2
Severity: important
While upgrading the kernel, the process seems to hang when running lilo.
Screen output:
-------------------------------------------------------------------------
Setting up linux-image-2.6.18-4-amd64 (2.6.18.dfsg.1-12etch2) ...
Hmm. The package shipped with a symbolic link /lib/modules/2.6.18-4-amd64/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/2.6.18-4-amd64/source
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.18.dfsg.1-12etch1 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.18.dfsg.1-12etch1 was configured last, according to dpkg)
You already have a LILO configuration in /etc/lilo.conf
Running boot loader as requested
Testing lilo.conf ...
Testing successful.
Installing the partition boot sector...
Running /sbin/lilo ...
----------------------------------------------------------------
I have investigated this by running lilo manually, and this is the output:
-------------------------------------------------------------
Reference: disk "/dev/sde" (8,64) 0840
LILO wants to assign a new Volume ID to this disk drive. However, changing
the Volume ID of a Windows NT, 2000, or XP boot disk is a fatal Windows error.
This caution does not apply to Windows 95 or 98, or to NT data disks.
Is the above disk an NT boot disk? [Y/n]n
--------------------------------------------------------------------------
So apparently the upgrade doesn't catch lilo asking questions interactively,
and waits forever as a result.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Reply to: