On Wed, Mar 21, 2007 at 09:40:15AM +0100, Svante Signell wrote: > > Yes, if you could generate a new initrd for 2.6.18-4-686 on your system > > using yaird, that would be appreciated. If you don't have anywhere that you > > can upload it yourself, then for starters please send the output of zcat > > <initrd-file> | cpio -t for the -3- and -4- versions of the initrd.
> Attached! Ok, nothing out of the ordinary there. I wonder if this could have been simply a problem of a full filesystem at the time you first tried to generate the initramfs...? The error message certainly sounds like a case of a corrupt initramfs -- "Failed to execute /init" certainly points to a problem in the initramfs itself, not to a problem accessing the root filesystem, because the initramfs is the only place you have an absolute path of "/init", and if you've just regenerated an initramfs with yaird and it *does* have a /init in it, I'm not sure what all we can do to debug this after the fact. Are you willing to try installing the initramfs you just generated for -4 and trying to boot with it, to see whether the error is still reproducible for you? My best guess is that it won't be, but better to know for sure instead of guessing. :) Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
