Your message dated Sat, 25 Dec 2010 20:36:05 +0100
with message-id <[email protected]>
and subject line Re: Bug#532049: readlink error in mkinitramfs-kpkg
has caused the Debian Bug report #532049,
regarding readlink error in mkinitramfs-kpkg
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
532049: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532049
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-2.6.26-2-686
Version: 2.6.26-15
Hi, I tried to install Debian Sid and then Debian Testing using the
daily (today, 6 june) netinst CDRom (i386). I get a first crash in
deboostrap (see #532047), but it was easy to workaround this crash: just
restart "install base system" installer step. But then the kernel
installation failed :-/ And without kernel, it's difficult to finish the
installation... Here are the last lines of syslog before the error:
...
Jun 6 01:17:49 in-target: Dépaquetage de linux-image-2.6.26-2-686 (à
partir de .../linux-image-2.6.26-2-686_2.6.26-15_i386.deb) ...
Jun 6 01:17:49 debconf: Obsolete command TITLE Configuration de
linux-image-2.6.26-2-686 called
Jun 6 01:17:50 in-target: Done.
Jun 6 01:17:51 in-target: Sélection du paquet linux-image-2.6-686
précédemment désélectionné.
Jun 6 01:17:51 in-target: Dépaquetage de linux-image-2.6-686 (à partir
de .../linux-image-2.6-686_2.6.26+17+lenny1_i386.deb) ...
Jun 6 01:17:52 in-target: Paramétrage de linux-image-2.6.26-2-686
(2.6.26-15) ...
Jun 6 01:17:52 debconf: Obsolete command TITLE Configuration de
linux-image-2.6.26-2-686 called
Jun 6 01:17:52 in-target: Running depmod.
Jun 6 01:17:52 in-target: Running mkinitramfs-kpkg.
Jun 6 01:17:52 in-target: Deprecation WARNING: use update-initramfs(8)
Jun 6 01:17:52 in-target: dpkg : avertissement : option obsolète
« --print-installation-architecture », veuillez utiliser
« --print-architecture » à la place.
Jun 6 01:17:52 in-target: dpkg : avertissement : option obsolète
« --print-installation-architecture », veuillez utiliser
« --print-architecture » à la place.
Jun 6 01:17:52 in-target: readlink:
Jun 6 01:17:52 in-target: opérande manquante
Jun 6 01:17:52 in-target:
Jun 6 01:17:52 in-target: Pour en savoir davantage, faites: « readlink
--help ».
Jun 6 01:17:52 in-target: mkinitramfs-kpkg failed to create initrd image.
Jun 6 01:17:52 in-target: Failed to create initrd image.
Jun 6 01:17:52 in-target: dpkg : erreur de traitement de
linux-image-2.6.26-2-686 (--configure) :
Jun 6 01:17:52 in-target: le sous-processus script post-installation
installé a retourné une erreur de sortie d'état 9
Jun 6 01:17:52 in-target: dpkg : des problèmes de dépendances empêchent
la configuration de linux-image-2.6-686 :
Jun 6 01:17:52 in-target: linux-image-2.6-686 dépend de
linux-image-2.6.26-2-686 ; cependant :
Jun 6 01:17:52 in-target: Le paquet linux-image-2.6.26-2-686 n'est pas
encore configuré.
Jun 6 01:17:52 in-target: dpkg : erreur de traitement de
linux-image-2.6-686 (--configure) :
Jun 6 01:17:52 in-target: problèmes de dépendances - laissé non configuré
Jun 6 01:17:52 in-target: Des erreurs ont été rencontrées pendant
l'exécution :
Jun 6 01:17:52 in-target: linux-image-2.6.26-2-686
Jun 6 01:17:52 in-target: linux-image-2.6-686
Jun 6 01:17:52 in-target: E: Sub-process /usr/bin/dpkg returned an error
code (1)
Jun 6 01:17:52 base-installer: error: exiting on error
base-installer/kernel/failed-install
I think that the error is just "readlink: missing operand", error from
mkinitramfs-kpkg.
I tried different options to install the kernel (version
linux-image-2.6-686 or linux-image-2.6-2-686, big initrd or small
initrd, ...), but it doesn't fix the issue.
Victor
--- End Message ---
--- Begin Message ---
Version: 0.98.5
On Mon, 29 Jun 2009, Sebastian Fontius wrote:
>
> This is what "mount" shows regarding to /:
>
> rootfs on / type rootfs (rw)
>
> This is what
> /usr/share/initramfs-tools/hook-functions:dep_add_modules() does at the
> beginning:
>
> local block minor root FSTYPE root_dev_path x
>
> # findout root block device + fstype
> eval "$(mount | awk '/\/dev\// {if ($3 == "/") {print "root=" $1
> "\nFSTYPE=" $5; exit}}')"
>
> Running this against the output of mount does nothing, hence $root and
> $FSTYPE remain empty.
this got fixed in initramfs-tools 0.98.5. In the case of an empty root,
mkinitramfs tries to fallback to /proc/mounts. If that fails you get
a correct warning since 0.97.1 and no readlink invocation.
> A few lines later
> /usr/share/initramfs-tools/hook-functions:dep_add_modules() does this:
>
> root="$(readlink -f ${root})"
>
> As $root is empty this results in the error message
>
> readlink: missing operand
> Try `readlink --help' for more information.
>
> After fiddeling around with the postinst of the kernel 2.6.26-2-ixp4xx
> I found out that it is calling mkinitramfs-kpkg like this:
>
> # mkinitramfs-kpkg -o /boot/initrd.img-2.6.26-2-ixp4xx.new
> /lib/modules/2.6.26-2-ixp4xx
> readlink: missing operand
> Try `readlink --help' for more information.
> mkinitramfs: missing root /sys entry
> mkinitramfs: workaround is MODULES=most
> mkinitramfs: Error please report the bug
>
> The mkinitramfs error is not shown during install. The mentioned
> workaround is probably not a good idea as the initrd will possibly be
> too big to fit in the 8 minus something MiB of an NSLU2 (but may work
> on a machine not having those constraints).
>
> Now as to _why_ mount says rootfs is mounted on / I have no idea. I
> think (but I am not sure) that the output of mount always looked like
> this. I always thought it curious, but I never really did anything
> about it, as everything worked just fine.
>
> My /etc/fstab looks like this regarding to /:
>
> LABEL=oberon-root / ext3
> nodiratime,noatime,acl,user_xattr,errors=remount-ro 0 1
>
> And running vol_id from udev on /dev/corsair2048p1 (my / partition
> renamed by an udev rule) yields this:
>
> $ /sbin/vol_id /dev/corsair2048p1
> ID_FS_USAGE=filesystem
> ID_FS_TYPE=ext3
> ID_FS_VERSION=1.0
> ID_FS_UUID=72869be7-ab5d-46bd-87cf-33b2cde134a4
> ID_FS_UUID_ENC=72869be7-ab5d-46bd-87cf-33b2cde134a4
> ID_FS_LABEL=oberon-root
> ID_FS_LABEL_ENC=oberon-root
> ID_FS_LABEL_SAFE=oberon-root
>
> This is the relevant part of the udev rule used for renaming:
>
> # Corsair Flash Voyager
> SUBSYSTEMS=="scsi", KERNEL=="*[0-9]", ATTRS{model}=="Flash Voyager",
> ATTRS{vendor}=="Corsair", ATTRS{rev}=="1100", ATTRS{max_sectors}=="240",
> NAME+="corsair2048p%n"
> SUBSYSTEMS=="scsi", KERNEL=="*", ATTRS{model}=="Flash Voyager",
> ATTRS{vendor}=="Corsair", ATTRS{rev}=="1100", ATTRS{max_sectors}=="240",
> NAME+="corsair2048%n"
>
> I guess my combination of renaming the / device via udev and using the
> label for mounting / is the culprit. Seeing this I think this bug
> should be reassigned to initramfs-tools ir udev. But then again,
> previous kernel updates _never_ failed to install, so this bug should
> probably stay where it is.
>
thanks a lot for your detailed feedback. It helped to nail the case.
happy christmas vacations and sorry for the time it took to check
everything.
--
maks
--- End Message ---
