dpkg: error processing /var/cache/apt/archives/linux-image-2.6.18-5-486_2.6.18.dfsg.1-13etch6_i386.deb (--unpack):

["Mathieu Malaterre" <mathieu.malaterre@gmail.com>]

Hi there,

  Has anyone seen this issue before (*). I am running a linux debian
stable (etch).

Thanks


(*)
(Reading database ... 66650 files and directories currently installed.)
Preparing to replace linux-image-2.6.18-5-486 2.6.18.dfsg.1-13etch4
(using .../linux-image-2.6.18-5-486_2.6.18.dfsg.1-13etch6_i386.deb)
...
The directory /lib/modules/2.6.18-5-486 still exists. Continuing as directed.
Done.
Unpacking replacement linux-image-2.6.18-5-486 ...
dpkg: error processing
/var/cache/apt/archives/linux-image-2.6.18-5-486_2.6.18.dfsg.1-13etch6_i386.deb
(--unpack):
 failed in buffer_write(fd) (9, ret=-1): backend dpkg-deb during
`./lib/modules/2.6.18-5-486/kernel/drivers/md/dm-mod.ko': No space
left on device
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Running postrm hook script /sbin/update-grub.
Your /etc/kernel-img.conf needs to be updated. Read grub's NEWS.Debian[1]
file and follow its instructions.

 1. /usr/share/doc/grub/NEWS.Debian.gz


You shouldn't call /sbin/update-grub. Please call /usr/sbin/update-grub instead!

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: /vmlinuz-2.6.22-3-486
Found kernel: /vmlinuz-2.6.21-2-486
Found kernel: /vmlinuz-2.6.18-5-486
Found kernel: /vmlinuz-2.6.18-4-486
Found kernel: /vmlinuz-2.6.15-1-486
Updating /boot/grub/menu.lst ... done

Preparing to replace libpam0g 0.79-4 (using .../libpam0g_0.79-5_i386.deb) ...
Unpacking replacement libpam0g ...
Errors were encountered while processing:
 /var/cache/apt/archives/linux-image-2.6.18-5-486_2.6.18.dfsg.1-13etch6_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


-- 
Mathieu