On Wed, Apr 9, 2008 at 12:32 AM, Damon L. Chesser <damon@damtek.com> wrote:
Mike Bird wrote:
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.
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.
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
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a
subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
What I am reading wrong:
$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/Debian-root
264854 255254 0 100% /
tmpfs 91848 0 91848 0% /lib/init/rw
udev 10240 68 10172 1% /dev
tmpfs 91848 0 91848 0% /dev/shm
/dev/hdb6 233335 49336 171551 23% /boot
/dev/mapper/Debian-home
9913988 3348716 6061672 36% /home
/dev/mapper/Debian-tmp
376197 8274 347853 3% /tmp
/dev/mapper/Debian-usr
4922684 1202764 3469860 26% /usr
/dev/mapper/Debian-var
2955216 261392 2543708 10% /var
everything looks fine, right ?
$ df -h /boot
Filesystem Size Used Avail Use% Mounted on
/dev/hdb6 228M 49M 168M 23% /boot
thx