Can't update image-2.6.26-1-686_2.6.26-13lenny2
 

Hello,
can someone help me.
I can't update the new image-2.6.26-1-686_2.6.26-13lenny2

with security update

E: /var/cache/apt/archives/linux-
image-2.6.26-1-686_2.6.26-13lenny2_i386.deb: fehlgeschlagen in buffer_write(fd) (10, ret=-1)

or with aptitude

Vorkonfiguration der Pakete ...
(Lese Datenbank ... 126387 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereiten zum Ersetzen von linux-image-2.6.26-1-686 2.6.26-13 (durch .../linux-image-2.6.26-1-686_2.6.26-13lenny2_i386.deb) ...
The directory /lib/modules/2.6.26-1-686 still exists. Continuing as directed.
Done.
Entpacke Ersatz für linux-image-2.6.26-1-686 ...
dpkg: Fehler beim Bearbeiten von /var/cache/apt/archives/linux-image-2.6.26-1-686_2.6.26-13lenny2_i386.deb (--unpack):
fehlgeschlagen in buffer_write(fd) (10, ret=-1): Backend dpkg-deb während »./lib/modules/2.6.26-1-686/kernel/drivers/hwmon/dme1737.ko«: Auf dem Gerät ist kein Speicherplatz mehr verfügbar
dpkg-deb: Unterprozess paste mit Signal (Datenübergabe unterbrochen (broken pipe)) getötet
Running postrm hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.26-1-686
Found kernel: /boot/vmlinuz-2.6.18-6-686
Found kernel: /boot/vmlinuz-2.6.18-4-686
Updating /boot/grub/menu.lst ... done

fehlgeschlagen in buffer_write = Failure in Buffer_write

Auf dem Gerät ist kein Speicherplatz mehr verfügbar = On the equipment no storage location is more available


so .. are you out of disk space somewhere ?

How can I make disk space free?
 

Much Thanks!
I have differnt partions for all. There is space on disk but I think not in the parition for the image. I don't know but I think there are old Images. Is it possible to delete them and how?

Hmm hard to tell what's going on from those screenshots.. it looks like / is full but you have som many other partitions, I don't understand why / would have that much data in it..

could you post the output of the following command here ?

df -h

Thanks! I have got the answer. I have removed with aptitude the kernel 2.6.18-6-686 and 2.6.18-4-686
Now I have enough disk space. Than I have installed
linux-image 2.6.26-libre2-1-686 because I thought that libre use a little less disk space. What do you think is libre stabil?

Here is the output from df -h

stephanoppermann:/home/stephan# df -h
Dateisystem Größe Benut Verf Ben% Eingehängt auf
/dev/sdb1 259M 178M 67M 73% /
tmpfs 506M 0 506M 0% /lib/init/rw
udev 10M 140K 9,9M 2% /dev
tmpfs 506M 0 506M 0% /dev/shm
/dev/sdb9 219G 92G 117G 44% /home
/dev/sdb8 373M 11M 343M 3% /tmp
/dev/sdb5 4,6G 2,8G 1,6G 65% /usr
/dev/sdb6 2,8G 384M 2,3G 15% /var

yes the libre kernel would likely be smaller. and if you don't run into any issues with devices not working due to missing firmware, you should be good to go.

From what I can see it looks like the libre kernel has all the non-free binary firmware blobs removed from it. Debian is working towards this in their mainline kernels, but it's a slow process.


When you uninstalled those kernels did you also go through your system looking for any old initrd.img or vmlinuz files sitting in /boot that you no longer need ? and did you check /usr/src for header files left over from the kernel versions you removed ?

I always do a manual check since purging the old kernels doesn't necessarily remove everything.


Glad to hear you got it all sorted out. Enjoy !!

The old initrd.img or vmlinuz files was remove by aptitude. I have also delete one bak file with mc.
I think I have no problems with missing firmware.
It is all very well.
Thanks a lot!