On Tue, May 30, 2006 at 08:07:04PM +0200, maximilian attems wrote:
:
: > I don't think so, I re-run myself lilo before reboot, and after the
: > first panic I dpkg-reconfigured linux-image so initrd.img was rebuilt
: > and I re-run lilo again. After getting the same result, I started
: > digging in the BTS. Also, if it's a lilo issue, why initrd.img built
: > with yaird works?
:
: please retry,
: the strange thing is that you are reporting that initramfs run,
: but i only saw the error message you posted when lilo was not run
: and that before initramfs get's accessed.
: also you didn't post any message about any root fs trying to be mounted?
I'm unable to get the kernel panic anymore... I've erased the ofending
initrd.img, and the one generated by mkinitramfs-kpkg works.
The bad one used to say:
Begin: Running /scripts/local-premount ...
Attempting manual resume.
Kernel panic - not syncing: I/O error reading memory image
now it says:
Begin: Running /scripts/local-premount ...
Done.
kjournaled starting...
[more messages about ext3 root fs being mounted]
...
We have upgraded to testing versions of everything since yesterday (it
was sarge before) so the problem should be an old version of something
used to build the initrd (but not initramfs-tools, it was upgraded with
the kernel).
Or maybe it was a lilo problem as you have said, but I don't think so.
: what does fstype give on your root
: /usr/lib/klibc/bin/fstype < /dev/md0
root:/boot# /usr/lib/klibc/bin/fstype < /dev/md0
FSTYPE=ext3
FSSIZE=22002466816
root:/boot# df .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/md0 21155372 16547664 3748240 82% /
: also i'd be interested in that initrd.img that doesn't boot.
: please either upload it somewhere or append it to your mail.
Sorry to bother you, but the problem has just vanished and I'm unable to
reproduce it, so I suppose the bug can be closed.
Regards,
--
Roberto Lumbreras .''`.
<rover : :' : debian.org>
Debian Developer `. `'
`-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
