Bug#389328: linux-image post install hangs when LILO detects new drive and waits for input

[jef_e <jef_e@deadlazlosplace.com>]

Package: linux-image-2.6.16-2-k7
Version: 2.6.16-2-k7

	However, this probably applies to all kernels, as it's the post-install
that seems problematic. It seems that redirecting

	I just installed a few new drives, and decided to pull in a new kernel
to get md support (the old kernel was home built and didn't have it.
System has since been repurposed and doesn't need a custom kernel any
longer).

	I ran apt-get install linux-image-2.6.16-2-k7, and it grabbed all the
dependencies. Once it gets to running lilo, the installation hangs:

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  ...


	A ps shows the following running:

root      3346  0.1  1.8  30824  9700 pts/0    S+   23:17   0:00 apt-get
install linux-image-2.6.16-2-k7
root      3494  0.0  0.6   4944  3176 pts/0    S+   23:19   0:00
/usr/bin/dpkg --status-fd 13 --configure mdadm busybox libklibc
klibc-utils libvolume-id0 udev initramfs-tools linux-image-2.6.16-2-k7
root      3584  0.1  1.7  10896  9256 pts/0    S+   23:19   0:00
/usr/bin/perl -w /usr/share/debconf/frontend
/var/lib/dpkg/info/linux-image-2.6.16-2-k7.postinst configure
root      3591  0.0  0.5   4188  2716 pts/0    S+   23:19   0:00
/usr/bin/perl /var/lib/dpkg/info/linux-image-2.6.16-2-k7.postinst configure
root      5464  0.0  0.2   2368  1068 pts/0    S+   23:19   0:00 sh -c
/sbin/lilo >/var/log/lilo_log.3591 2>&1
root      5465  0.0  0.2   2372  1092 pts/0    S+   23:19   0:00 /bin/sh
-e /sbin/lilo
root      5466  0.0  0.1   2272   736 pts/0    S+   23:19   0:00
/sbin/lilo.real


	I checked the log file /var/log/lilo_log.3591 and it seems that lilo is
waiting for input.



klaatu:~# more /var/log/lilo_log.3591


Reference:  disk "/dev/hde"  (33,0)  2100

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]
klaatu:~#

And of course I can't answer the question while it's hanging here.


Breaking out of the installer and running lilo by hand allows me to
answer, and rerunning the installer seems to make apt happy.

I"m not sure how to best fix this other than to also display what is
getting logged? The combination of events is probably fairly rare.

jef