Acknowledgement sent
to Wichert Akkerman <[email protected]>:
New Bug report received and forwarded. Copy sent to Debian Kernel Team <[email protected]>.
(Tue, 30 Dec 2008 17:21:04 GMT) (full text, mbox, link).
Subject: linux-image-2.6.26-1-686: upgrade from etch to lenny fails in postinst
Date: Tue, 09 Dec 2008 00:14:27 +0100
Package: linux-image-2.6.26-1-686
Version: 2.6.26-11
Severity: important
An upgrade of machine with a fairly basic install fails mysteriously:
one:/home/wichert# dpkg --configure linux-image-2.6.26-1-686
Setting up linux-image-2.6.26-1-686 (2.6.26-11) ...
Running depmod.
Running mkinitramfs-kpkg.
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
initrd.img(/boot/initrd.img-2.6.26-1-686
) points to /boot/initrd.img-2.6.26-1-686
(/boot/initrd.img-2.6.26-1-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.26-1-686.postinst line 569.
vmlinuz(/boot/vmlinuz-2.6.26-1-686
) points to /boot/vmlinuz-2.6.26-1-686
(/boot/vmlinuz-2.6.26-1-686) -- doing nothing at /var/lib/dpkg/info/linux-image-2.6.26-1-686.postinst line 569.
Running postinst hook script update-grub.
Searching for GRUB installation directory ... found: /boot/grub
User postinst hook script [update-grub] exited with value 1
dpkg: error processing linux-image-2.6.26-1-686 (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
linux-image-2.6.26-1-686
running update-grub by hand seems to work fine, so I have no idea what is
happning here.
Wichert.
-- Package-specific info:
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686-bigmem (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.26-1-686 depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii initramfs-tools [linux-initra 0.92j tools for generating an initramfs
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.26-1-686 recommends:
ii libc6-i686 2.7-16 GNU C Library: Shared libraries [i
Versions of packages linux-image-2.6.26-1-686 suggests:
ii grub 0.97-47 GRand Unified Bootloader (Legacy v
pn linux-doc-2.6.26 <none> (no description available)
-- debconf information:
linux-image-2.6.26-1-686/preinst/abort-overwrite-2.6.26-1-686:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.26-1-686/postinst/bootloader-error-2.6.26-1-686:
linux-image-2.6.26-1-686/postinst/depmod-error-initrd-2.6.26-1-686: false
linux-image-2.6.26-1-686/prerm/removing-running-kernel-2.6.26-1-686: true
linux-image-2.6.26-1-686/postinst/old-system-map-link-2.6.26-1-686: true
linux-image-2.6.26-1-686/preinst/abort-install-2.6.26-1-686:
linux-image-2.6.26-1-686/preinst/lilo-has-ramdisk:
linux-image-2.6.26-1-686/preinst/bootloader-initrd-2.6.26-1-686: true
linux-image-2.6.26-1-686/prerm/would-invalidate-boot-loader-2.6.26-1-686: true
linux-image-2.6.26-1-686/preinst/elilo-initrd-2.6.26-1-686: true
linux-image-2.6.26-1-686/postinst/kimage-is-a-directory:
linux-image-2.6.26-1-686/postinst/old-dir-initrd-link-2.6.26-1-686: true
linux-image-2.6.26-1-686/postinst/create-kimage-link-2.6.26-1-686: true
linux-image-2.6.26-1-686/preinst/lilo-initrd-2.6.26-1-686: true
linux-image-2.6.26-1-686/postinst/old-initrd-link-2.6.26-1-686: true
linux-image-2.6.26-1-686/preinst/overwriting-modules-2.6.26-1-686: true
linux-image-2.6.26-1-686/postinst/depmod-error-2.6.26-1-686: false
linux-image-2.6.26-1-686/postinst/bootloader-test-error-2.6.26-1-686:
linux-image-2.6.26-1-686/preinst/failed-to-move-modules-2.6.26-1-686:
linux-image-2.6.26-1-686/preinst/initrd-2.6.26-1-686:
Acknowledgement sent
to Bastian Blank <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <[email protected]>.
(Wed, 31 Dec 2008 17:24:03 GMT) (full text, mbox, link).
Subject: How to avoid device name related kernel panics after dist(/automated
kernel)-upgrade
Date: Sun, 30 Aug 2009 10:23:07 +0000
On Sun, Sep 12, 2004 at 12:23:32PM +0300, Martin-?ric Racine wrote:
> Package: grub
> Severity: important
>
> I have been wondering for a long time why the menu.lst gets automatically
updated on a single host out of my whole
> i386 cluster. The answer seems to be that update-grub won't
automatically run whenever upgrading or removing
> kernel-images, because the following hooks are missing in
/etc/kernel-img.conf:
>
> # Update the GRUB menu
> postrm_hook = /sbin/update-grub
> postinst_hook = /sbin/update-grub
>
> Given how Debian standardizes on GRUB starting with Sarge, it would be
important that GRUB's installation scripts add
> the above lines to /etc/kernel-img.conf automatically, upon installing or
upgrading GRUB. This would be easy to
> implement and would save the end-user a lot of troubles, thus making
Debian more user-friendly.
Dear Debian Developers.
you receive this mail because I just cant get a clear view how to solve my
following problem and to which bug it belongs to. Please dont bite my head
(filing a new bug probably would be even worse).
In the hope to get a clearing answer I CC debian-devel.
Applying a recent security update of linux-2.6 (DSA-1872-1) in lenny the
system suddenly seemed unbootable (at least for a person without any debian
skills).
The reason was a _silent_ reconfiguration of device names.
My wish:
* please provide a (half) automated, maybe interactive, way to verify the
configuration of fstab / menu.lst (and related) in any matching postinst
script
* in #debian-devel i got the hint to switch from device names to UUIDs - is
there a way to provide this automatically?
* will UUIDs according to rfc4122 ever be default in debian?
To me this problem doesn't seem to be grub specific, or do LILO and GRUB2
have a solution for it?
#271269 grub - how to deal with /etc/kernel-img.conf and update-grub on
kernel-image changes
"Maybe dpkg triggers is the answer (we have a separate bug for that,
IIRC)."
#499176 grub - should fail verbosely when root device cannot be found
"update-grub needs to identify the current root in order
to construct grub.cfg / menu.lst. fstab was not reliable, so it's no
longer
being used."
#510223 grub - linux-image-2.6.26-1-686: upgrade from etch to lenny fails
in postinst
"update-grub is supplied by grub, this looks like #499176."
Please do whateever you think should be done (except punching me :)
Have a nice day!
kardan
Acknowledgement sent
to Felix Zielcke <[email protected]>:
Extra info received and forwarded to list. Copy sent to Grub Maintainers <[email protected]>.
(Sun, 30 Aug 2009 11:03:12 GMT) (full text, mbox, link).
Subject: Re: Bug#510223: How to avoid device name related kernel panics
after dist(/automated kernel)-upgrade
Date: Sun, 30 Aug 2009 12:51:03 +0200
Am Sonntag, den 30.08.2009, 10:23 +0000 schrieb
[email protected]:
> My wish:
> * please provide a (half) automated, maybe interactive, way to verify
> the
> configuration of fstab / menu.lst (and related) in any matching
> postinst
> script
> * in #debian-devel i got the hint to switch from device names to UUIDs
> - is
> there a way to provide this automatically?
> * will UUIDs according to rfc4122 ever be default in debian?
>
> To me this problem doesn't seem to be grub specific, or do LILO and
> GRUB2
> have a solution for it?
GRUB 2 always uses UUIDs except for LVM devices or if
GRUB_DISABLE_LINUX_UUID=true is set in /etc/default/grub.
GRUB Legacy only uses UUIDs when menu.lst is freshly created on a lenny
system or if you change the kopt parameter yourself and then run
update-grub.
The Debian-Installer team has an UUID goal for Squeeze:
http://wiki.debian.org/DebianInstaller/SqueezeGoals
--
Felix Zielcke
Proud Debian Maintainer
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.