Bug#610462: update-initramfs: failed for /boot/initrd.img-2.6.32-5-686 (errorcode 127)
Package: initramfs-tools
Version: 0.98.7
Severity: important
Tags: squeeze
The error I'm encountering looks like bug 600453, although I
have a "normal" root and boot partition, and that was closed for
version 0.98.5. I include the relevant
sections of $(mount) and /etc/fstab below. I seem to have this problem
since 29 september; booting 2.6.32-3 ever since. Sorry I didn't report
this earlier (now that I've tried $(reportbug) once I'll react sooner)
~ $ mount
/dev/sda3 on / type ext4 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sda1 on /boot type ext2 (rw)
Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core)
Locale: LANG=nl_NL@euro, LC_CTYPE=nl_NL@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Versions of packages initramfs-tools depends on:
ii cpio 2.11-4 GNU cpio -- a program to manage ar
ii findutils 4.4.2-1+b1 utilities for finding files--find,
ii klibc-utils 1.5.20-1 small utilities built with klibc f
ii module-init-tools 3.12-1 tools for managing Linux kernel mo
ii udev 164-3 /dev/ and hotplug management daemo
Versions of packages initramfs-tools recommends:
ii busybox 1:1.17.1-8 Tiny utilities for small and embed
Versions of packages initramfs-tools suggests:
pn bash-completion <none> (no description available)
-- no debconf information
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110118201143.9288.58440.reportbug@l1d">http://lists.debian.org/20110118201143.9288.58440.reportbug@l1d
01-18-2011, 07:15 PM
maximilian attems
Bug#610462: update-initramfs: failed for /boot/initrd.img-2.6.32-5-686 (errorcode 127)
tags 610462 moreinfo
stop
On Tue, Jan 18, 2011 at 09:11:43PM +0100, steff wrote:
>
> The error I'm encountering looks like bug 600453, although I
> have a "normal" root and boot partition, and that was closed for
> version 0.98.5. I include the relevant
> sections of $(mount) and /etc/fstab below. I seem to have this problem
> since 29 september; booting 2.6.32-3 ever since. Sorry I didn't report
> this earlier (now that I've tried $(reportbug) once I'll react sooner)
please post full update-initramfs error.
currently it is unclear to me what trouble you are seeing.
thank you.
--
maks
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110118201518.GA20262@vostochny.stro.at">http://lists.debian.org/20110118201518.GA20262@vostochny.stro.at
01-18-2011, 07:22 PM
steff
Bug#610462: update-initramfs: failed for /boot/initrd.img-2.6.32-5-686 (errorcode 127)
update-initramfs: failed for /boot/initrd.img-2.6.32-5-686
On Tue, Jan 18, 2011 at 9:15 PM, maximilian attems <max@stro.at> wrote:
tags 610462 moreinfo
stop
On Tue, Jan 18, 2011 at 09:11:43PM +0100, steff wrote:
>
> The error I'm encountering looks like bug 600453, although I
> have a "normal" root and boot partition, and that was closed for
> version 0.98.5. I include the relevant
> sections of $(mount) and /etc/fstab below. I seem to have this problem
> since 29 september; booting 2.6.32-3 ever since. Sorry I didn't report
> this earlier (now that I've tried $(reportbug) once I'll react sooner)
please post full update-initramfs error.
currently it is unclear to me what trouble you are seeing.
thank you.
--
maks
01-18-2011, 07:28 PM
maximilian attems
Bug#610462: update-initramfs: failed for /boot/initrd.img-2.6.32-5-686 (errorcode 127)
On Tue, Jan 18, 2011 at 09:22:20PM +0100, steff wrote:
> Sorry.
>
> ~ $ update-initramfs -u
> update-initramfs: Generating /boot/initrd.img-2.6.32-5-686
> update-initramfs: failed for /boot/initrd.img-2.6.32-5-686
>
hmmm not seen that in a long time.
please post output of:
mkinitramfs -o /tmp/fooo -k 2.6.32-5-686
and output of:
df -h
thank you.
--
maks
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110118202810.GB20262@vostochny.stro.at">http://lists.debian.org/20110118202810.GB20262@vostochny.stro.at
01-18-2011, 07:33 PM
Michael Prokop
Bug#610462: update-initramfs: failed for /boot/initrd.img-2.6.32-5-686 (errorcode 127)
* steff <steff.helsen@gmail.com> [Tue Jan 18, 2011 at 09:22:20PM +0100]:
What does 'sh -x /usr/sbin/mkinitramfs -o /tmp/foo' display?
regards,
-mika-
01-20-2011, 03:27 PM
Steff
Bug#610462: update-initramfs: failed for /boot/initrd.img-2.6.32-5-686 (errorcode 127)
Op Thu, 20 Jan 2011 16:59:09 +0100 schreef maximilian attems:
> any update?
Sorry, the mail below bounced from Mika's mail, but not from 610462@bugs.debian.org, so I assumed you had had it.
Sorry again for wasting your time, and thanks again for the help.
steff
----
Op Tue, 18 Jan 2011 21:33:57 +0100 schreef Michael Prokop:
Found the culprit, between the chair and the keyboard as usual. I backup my config files using rcs. removing the RCS folder mentioned below makes everything run smooth again.
Thanks both for the quick help, and sorry for the burden.
A replay of the finish:
> What does 'sh -x /usr/sbin/mkinitramfs -o /tmp/foo' display?
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110120162739.BC6833406BC@ava.intern.ulyssis.org" >http://lists.debian.org/20110120162739.BC6833406BC@ava.intern.ulyssis.org
11-23-2011, 02:26 PM
Michael Prokop
Bug#610462: update-initramfs: failed for /boot/initrd.img-2.6.32-5-686 (errorcode 127)
tags 610462 + pending
tags 610462 + patch
thanks
* Steff [Thu Jan 20, 2011 at 05:27:39PM +0100]:
> Sorry, the mail below bounced from Mika's mail, but not from
> 610462@bugs.debian.org, so I assumed you had had it.
> Sorry again for wasting your time, and thanks again for the help.
[...]
> Found the culprit, between the chair and the keyboard as usual. I
> backup my config files using rcs. removing the RCS folder
> mentioned below makes everything run smooth again.
> Thanks both for the quick help, and sorry for the burden.
[...]
Even though this is kind of EBKAC (thanks to Steff for the debugging
output) I'd like to make sure a user is notified about such a
situation. Therefore I just prepared a branch addressing this issue
for review and inclusion: