On Thu, Oct 18, 2007 at 06:37:14PM -0400, Richard Carter wrote: > Hi Andrew and Johannes, > > My reply of a few hours ago had the wrong subject! Sorry for the mix up. no problem. > > Here is the output copied from aptitude" its amazing how people don't actually read their apt output (not directed *specifically* at you, btw). I know it's intimidating but if you persevere the info you need is usually there. THat's why we need the *complete* output... so here's your lesson in reading apt output: > > redcube:/home/robin# aptitude upgrade > Reading package lists... Done > Building dependency tree... Done > Reading extended state information > Initializing package states... Done > Reading task descriptions... Done > Building tag database... Done > The following packages will be upgraded: > linux-image-2.6.18-5-amd64 > 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Need to get 0B/16.8MB of archives. After unpacking 8192B will be > used. package is already downloaded, so there's nothing to get > Do you want to continue? [Y/n/?] Y > Preconfiguring packages ... > (Reading database ... 180396 files and directories currently installed.) > Preparing to replace linux-image-2.6.18-5-amd64 2.6.18.dfsg.1-13etch3 (using > ... > /linux-image-2.6.18-5-amd64_2.6.18.dfsg.1-13etch4_amd64.deb) ... this tells you which version of a package is being replaced and by what version. > The directory /lib/modules/2.6.18-5-amd64 still exists. Continuing as > directed. the destination directory already exists, but since you told it to do this, it will continue. This is because you already have a package with this name. You're just upgrading the package in place. > Done. > Unpacking replacement linux-image-2.6.18-5-amd64 ... this is obvious. its unpacking the .deb > dpkg: error processing /var/cache/apt/archives/linux- > image-2.6.18-5-amd64_2.6.18 .dfsg.1-13etch4_amd64.deb > (--unpack): > failed in buffer_write(fd) (9, ret=-1): backend dpkg-deb during > `./lib/modules/ 2.6.18-5-amd64/kernel/sound/pci/emu10k1/snd- > emu10k1.ko': No space left on device and there is your error. your /lib partition is full (or at least appears to be full). and this probably means that / is full. check the output of df. > dpkg-deb: subprocess paste killed by signal (Broken pipe) > Running postrm hook script /sbin/update-grub. > You shouldn't call /sbin/update-grub. Please call /usr/sbin/update-grub > instead! > a little note about the moving of update from /sbin to /usr/sbin > 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.18-5-amd64 > Found kernel: /vmlinuz-2.6.18-4-amd64 > Updating /boot/grub/menu.lst ... done typical grub output. > > Errors were encountered while processing: > /var/cache/apt/archives/linux- > image-2.6.18-5-amd64_2.6.18.dfsg.1-13etch4_amd64. deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > A package failed to install. Trying to recover: > redcube:/home/robin# and finally the report of the results of your actions. So, by reading the apt output, you can determine exactly which package had the problem. and by scrolling back through the output, you can read what ahppened to that package. You've got no room (or apparently no room, anyway) in /lib. THere's a good possibility that /lib is part of the same partition as / and so your / partition is probably full. hth A
Attachment:
signature.asc
Description: Digital signature