Comment 2 for bug 478754

Revision history for this message
Ernst Rohlicek jun. (ernst-rohlicek) wrote :

I seem to be in the same situation - installation fails in "select and install software" step.

Boot from CDROM, tried in expert mode and in normal mode.

It says that "something" has failed - it only showd the failed command ... the whole dpkg output in a text field would be great in such an unexpected case.

Anyways, created debug logs and entered the shell.

The last entry I saw failing was the linux-headers-2.6.31-pae package so I ran the command it showed me in the error window during installation: "chroot /target --install --force-...something /media/cdrom0/[...]/linux-headers-2.6.31-[...].deb" and ran that command there in the shell.

To my astonishment, it gave up with the following:

~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 222312 144 222168 0% /dev
/dev/sr0 655944 655944 0 100% /cdrom
/dev/sda1 19528876 605744 17946384 3% /target
/dev/sda1 19528876 605744 17946384 3% /dev/.static/dev
tmpfs 222312 144 222168 0% /target/dev
/dev/sr0 655944 655944 0 100% /target/media/cdrom0
/usr/bin # chroot /target/ dpkg --force-all --install /media/cdrom0/pool/main/l/linux/linux-headers-2.6.31-14-generic-pae_2.6.3
1-14.48_i386.deb
(Reading database ... 14458 files and directories currently installed.)
Unpacking linux-headers-2.6.31-14-generic-pae (from .../linux-headers-2.6.31-14-generic-pae_2.6.31-14.48_i386.deb) ...
dpkg: error processing /media/cdrom0/pool/main/l/linux/linux-headers-2.6.31-14-generic-pae_2.6.31-14.48_i386.deb (--install):
 unable to create `/usr/src/linux-headers-2.6.31-14-generic-pae/include/config/nf/nat/proto/udplite.h.dpkg-new' (while processing `./usr/src/linux-headers-2.6.31-14-generic-pae/include/config/nf/nat/proto/udplite.h'): No space left on device
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
 /media/cdrom0/pool/main/l/linux/linux-headers-2.6.31-14-generic-pae_2.6.31-14.48_i386.deb
/usr/bin #

... which in my opinion makes no sense.

Only thing I could think of are too strong or unlucky compilation flags for dpkg or the running kernel or file system code, something I had sometimes in a custom-compiled Gentoo system.

Will try to attach my full syslog output I transfered out via USB storage.