Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

Somehow my kernels got messed up. I am not sure what to make of this message from synaptic.

Any ideas what it implies and what I need to do in order to fix it?

This is the gui pop up and

E: linux-image-3.5.0-21-lowlatency: subprocess installed post-installation script returned error exit status 2
E: initramfs-tools: subprocess installed post-installation script returned error exit status 1

This is the log from its terminal

(Reading database ... 602507 files and directories currently installed.)
Preparing to replace linux-headers-lowlatency 3.5.0.22.20 (using .../linux-headers-lowlatency_3.5.0.22.20_amd64.deb) ...
Unpacking replacement linux-headers-lowlatency ...
Preparing to replace linux-image-lowlatency 3.5.0.22.20 (using .../linux-image-lowlatency_3.5.0.22.20_amd64.deb) ...
Unpacking replacement linux-image-lowlatency ...
Setting up initramfs-tools (0.103ubuntu0.2) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-3.5.0-21-lowlatency (3.5.0-21.19) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-3.5.0-21-lowlatency
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.5.0-21-lowlatency /boot/vmlinuz-3.5.0-21-lowlatency
Error! Bad return status for module build on kernel: 3.5.0-21-lowlatency (x86_64)
Consult /var/lib/dkms/crystalhd/0.0~git20110715.fdd2f19/build/make.log for more information.
Error! Bad return status for module build on kernel: 3.5.0-21-lowlatency (x86_64)
Consult /var/lib/dkms/blcr/0.8.4/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.5.0-21-lowlatency /boot/vmlinuz-3.5.0-21-lowlatency
update-initramfs: Generating /boot/initrd.img-3.5.0-21-lowlatency
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.5.0-21-lowlatency with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.5.0-21-lowlatency.postinst line 1010.
dpkg: error processing linux-image-3.5.0-21-lowlatency (--configure):
 subprocess installed post-installation script returned error exit status 2
No apport report written because MaxReports has already been reached
                                                                    Setting up linux-headers-lowlatency (3.5.0.22.20) ...
Setting up linux-image-lowlatency (3.5.0.22.20) ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.5.0-22-lowlatency
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.5.0-22-lowlatency with 1.
dpkg: error processing initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports has already been reached
                                                                    Errors were encountered while processing:
 linux-image-3.5.0-21-lowlatency
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up initramfs-tools (0.103ubuntu0.2) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-3.5.0-21-lowlatency (3.5.0-21.19) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
The link /initrd.img is a dangling linkto /boot/initrd.img-3.5.0-21-lowlatency
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 3.5.0-21-lowlatency /boot/vmlinuz-3.5.0-21-lowlatency
Error! Bad return status for module build on kernel: 3.5.0-21-lowlatency (x86_64)
Consult /var/lib/dkms/blcr/0.8.4/build/make.log for more information.
Error! Bad return status for module build on kernel: 3.5.0-21-lowlatency (x86_64)
Consult /var/lib/dkms/crystalhd/0.0~git20110715.fdd2f19/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.5.0-21-lowlatency /boot/vmlinuz-3.5.0-21-lowlatency
update-initramfs: Generating /boot/initrd.img-3.5.0-21-lowlatency
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.5.0-21-lowlatency with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.5.0-21-lowlatency.postinst line 1010.
dpkg: error processing linux-image-3.5.0-21-lowlatency (--configure):
 subprocess installed post-installation script returned error exit status 2
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.5.0-22-lowlatency
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.5.0-22-lowlatency with 1.
dpkg: error processing initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 linux-image-3.5.0-21-lowlatency
 initramfs-tools
share|improve this question
    
Looks like you ran out of space on your /boot partition... gzip: stdout: No space left on device –  Bruno Pereira Jan 14 '13 at 11:54
    
Thanks, I am able to read the messages but I am trying to derive meaning from them here. –  Magpie Jan 14 '13 at 12:07
1  
Just that is enough to make the installation of a new kernel fail. If you delete previous un-used kernel images do you have any other issues? Please create space by removing old kernel images or by increasing the size of your boot partition and try again. –  Bruno Pereira Jan 14 '13 at 13:16
    
yeah I saw what you meant actually but it was not straight forward to delete the kernels I had to duck and dive a bit. I still feel like the system is not stable yet so I will check I have fixed it properly before I speak too soon in an answer though! –  Magpie Jan 14 '13 at 18:20
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.