I haven't seen the resulting bootfailure yet, currently I can only explain it
by noexec tmp and thus not precache run.
I had the same problem; mounting /tmp as noexec was indeed the cause.
--
-Eli
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Am Sonntag, 11. Juli 2010, 18:13:15 schrieb maximilian attems:
is the /tmp on your box mounted noexec?
please sent output of:
cat /proc/mounts
/dev/mapper/_dev_dm_6 /home/calvin ext3
rw,relatime,errors=continue,data=ordered 0 0
/dev/mapper/_dev_sdb1 /mnt/backup ext3
* maximilian attems m...@stro.at [Sun Jul 11, 2010 at 06:13:15PM +0200]:
On Thu, 08 Jul 2010, Bastian Kleineidam wrote:
--- /usr/share/initramfs-tools/scripts/local-premount/resume~
2010-07-07 23:13:20.0 +0200
+++ /usr/share/initramfs-tools/scripts/local-premount/resume
tags 588466 moreinfo -patch
stop
On Thu, 08 Jul 2010, Bastian Kleineidam wrote:
all my newly built kernels failed to boot with the following message:
[...]
kinit: No resume image, doing normal boot...
E: /scripts/local-premount/resume failed with return 255
Kernel panic - not syncing:
Package: klibc-utils
Version: 1.5.18-1
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
all my newly built kernels failed to boot with the following message:
[...]
kinit: No resume image, doing normal boot...
E: /scripts/local-premount/resume failed with return 255
Bastian Kleineidam dixit:
Attached patch
Hrm, interesting… exit statuses range from 0 to 255, and
“exit -1” is a syntax error (except in things like GNU
bash, of course… where it’s actually the same as “exit
255”). You might want to change this.
bye,
//mirabilos (still hoping to be able to
6 matches
Mail list logo
