| chadwick |
03-22-2008 01:04 AM |
update-initramfs is failing on debian testing upgrade
I'm having some weird problems upgrading the debian testing installation on my T60 laptop.
apt-get install -f (where -f means "Fix; attempt to correct a system with broken dependencies in place.")
returns the following:
Code:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up initramfs-tools (0.91e) ...
update-initramfs: Generating /boot/initrd.img-2.6.22-3-686
gzip: stdout: No space left on device
update-initramfs: failed for /boot/initrd.img-2.6.22-3-686
dpkg: error processing initramfs-tools (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-2.6.22-3-686:
linux-image-2.6.22-3-686 depends on initramfs-tools (>= 0.55) | yaird (>= 0.0.12-8) | linux-initramfs-tool; however:
Package initramfs-tools is not configured yet.
Package yaird is not installed.
Package linux-initramfs-tool is not installed.
Package initramfs-tools which provides linux-initramfs-tool is not configured yet.
dpkg: error processing linux-image-2.6.22-3-686 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
initramfs-tools
linux-image-2.6.22-3-686
E: Sub-process /usr/bin/dpkg returned an error code (1)
I'm stuck in trying to understand what's going on.
For starters, I have no idea why it's saying no space left if
df -h
says:
Code:
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 4.6G 3.6G 817M 82% /
tmpfs 506M 0 506M 0% /lib/init/rw
udev 10M 140K 9.9M 2% /dev
tmpfs 506M 0 506M 0% /dev/shm
/dev/sda1 18G 11G 7.2G 60% /mnt/sda1
/dev/sda3 46M 42M 2.0M 96% /boot
/dev/sda9 56G 36G 17G 69% /home
/dev/sda7 464M 375M 66M 86% /opt
/dev/sda6 1.9G 521M 1.3G 30% /usr/local
overflow 1.0M 320K 704K 32% /tmp
Unless it has something to do with /tmp being only a meg in size? Is it really supposed to be that small?
I don't remember coming across that overflow fs before. |
