Mike Bird wrote:
And that was my 2nd guess, but I have never had a full /boot so I can only read the place where it errored, which was with the modules unpacking.On Tue April 8 2008 15:11:06 Mathieu Malaterre wrote:Has anyone seen this issue before (*). I am running a linux debian stable (etch).Yes. Wou were lucky. Sometimes when /boot is full it silently corrupts the initramfs without any error message. You probably need to make room in /boot, perhaps by deleting an old unused kernel.
you can do a df -h /boot to test. most people put /boot on / if they are not running raid or LVM or have some other reason to hang it alone. If /boot is not on it's own partition, look at a full /
HTH -- Damon L. Chesser damon@damtek.com