Bug#348613: post-installalation script fails on upgrade.
Package: kernel-image-2.4.27-2-k7
Version: 2.4.27-10sarge1
When attempting to do an apt-get upgrade on my Debian Sarge/i386 system,
I get the following:
trashcan:~# apt-get upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up kernel-image-2.4.27-2-k7 (2.4.27-10sarge1) ...
You are attempting to install a kernel version that is the same as
the version you are currently running (version 2.4.27-2-k7). The modules
list is quite likely to have been changed, and the modules dependency
file /lib/modules/2.4.27-2-k7/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.
rm: cannot remove directory `/tmp/mkinitrd.WSzDfV/initrd/dev': Directory
not empty
Failed to create initrd image.
dpkg: error processing kernel-image-2.4.27-2-k7 (--configure):
subprocess post-installation script returned error exit status 9
Errors were encountered while processing:
kernel-image-2.4.27-2-k7
E: Sub-process /usr/bin/dpkg returned an error code (1)
trashcan:~#
A directoruy listing of the directory given in the error above showes
that it is infact empty:
trashcan:/boot# ls -fl /tmp/mkinitrd.WSzDfV/initrd/dev
total 2
drwxr-xr-x 3 root root 1024 2006-01-18 10:59 .
drwxr-xr-x 3 root root 1024 2006-01-18 10:59 ..
A listing of my boot directory gives the following:
trashcan:/boot# ls -l
total 15077
-rw-r--r-- 1 root root 44973 2004-12-01 21:11 config-2.4.27-1-k7
-rw-r--r-- 1 root root 44973 2005-08-17 21:26 config-2.4.27-2-k7
drwxr-xr-x 2 root root 1024 2006-01-18 11:02 grub
-rw-r--r-- 1 root root 4214784 2005-01-05 14:17 initrd.img-2.4.27-1-k7
-rw-r--r-- 1 root root 4120576 2005-07-03 20:59 initrd.img-2.4.27-2-k7
-rw-r--r-- 1 root root 4136960 2006-01-18 10:59 initrd.img-2.4.27-2-k7.new
drwxr-xr-x 2 root root 12288 2004-12-22 01:27 lost+found
-rw-r--r-- 1 root root 531171 2004-12-01 21:34 System.map-2.4.27-1-k7
-rw-r--r-- 1 root root 531579 2005-08-17 22:37 System.map-2.4.27-2-k7
-rw-r--r-- 1 root root 863025 2004-12-01 21:34 vmlinuz-2.4.27-1-k7
-rw-r--r-- 1 root root 863813 2005-08-17 22:37 vmlinuz-2.4.27-2-k7
I suspect that the kernel itself has been upgraded, but the initrd file
not recreated.
Please let me know what I should do next as I am afraid that my kernel
being left in an unconfigured state may cause problems if the system
reboots.
Regards,
Ned Lukies
Reply to: