Bananian

No space on /boot error when performing apt-get upgrade

4 1650
dmuk  
Hi, I don't know what created the initrd.img-3.4.104-bananian file but the apt-get upgrade process fails when it needs to modify it due to the lack of space on /boot.

Can it be removed or do I need to increase space on /boot ?

I'm running Bananian 15.04 (upraded from 15.01).

Many thanks,
Dave

--------------------------------
Processing triggers for initramfs-tools ...
ln: failed to create hard link `/boot/initrd.img-3.4.104-bananian.dpkg-bak' => `/boot/initrd.img-3.4.104-bananian': Operation not permitted
update-initramfs: Generating /boot/initrd.img-3.4.104-bananian

gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.4.104-bananian with 1.
dpkg: error processing initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)


Filesystem      Size  Used Avail Use% Mounted on
/dev/mmcblk0p1   20M   15M  5.2M  75% /boot

drwxr-xr-x  3 root root   16384 Jun 13 14:31 .
drwxr-xr-x 22 root root    4096 May 16 09:20 ..
-rwxr-xr-x  1 root root  101134 Apr  6 18:53 config-3.4.104-bananian
drwxr-xr-x 10 root root    2048 Apr  7 06:20 fex
-rwxr-xr-x  1 root root 3263444 Apr 11 16:13 initrd.img-3.4.104-bananian
-rwxr-xr-x  1 root root   50928 Apr 11 22:54 script.bin
-rwxr-xr-x  1 root root 1831135 Apr  6 18:53 System.map-3.4.104-bananian
-rwxr-xr-x  1 root root     378 Apr 10 14:38 uEnv.txt
-rwxr-xr-x  1 root root     378 Sep  5  2014 uEnv.txt.video-acc-off
-rwxr-xr-x  1 root root     331 Sep  3  2014 uEnv.txt.video-acc-on
-rwxr-xr-x  1 root root 4798424 Apr 11 16:13 uImage
-rwxr-xr-x  1 root root 4798424 Apr  6 18:53 vmlinuz-3.4.104-bananian

Do not mount /dev/mmcblk0p1 at boot.

You can delete all "*-bananian" files on /dev/mmcblk0p1, umount it and do the upgrade again.

dmuk  
Bananian replied at Tue Jul 14, 2015 02:24
Do not mount /dev/mmcblk0p1 at boot.

You can delete all "*-bananian" files on /dev/mmcblk0p1, umoun ...

Thanks for the reply and apologies for the late response.

-rwxr-xr-x 1 root root  101134 Apr  6 18:53 config-3.4.104-bananian
-rwxr-xr-x 1 root root 3263444 Jun  8 10:08 initrd.img-3.4.104-bananian
-rwxr-xr-x 1 root root 1831135 Apr  6 18:53 System.map-3.4.104-bananian
-rwxr-xr-x 1 root root 4798424 Apr  6 18:53 vmlinuz-3.4.104-bananian

-rwxr-xr-x 1 root root 4798424 Apr 11 16:13 uImage

"uImage" is binary identical to vmlinuz-3.4.104-bananian.

Are the "*-bananian" files used to create "uImage" and can now be discarded ? - just trying to understand what the relationship is between these files

Thanks,
Dave

These files are in the deb package for the kernel and will be places in /boot. That is why mmcblk0p1 should not be mounted at /boot.

A hook script copies the UImage to it's location

dmuk  
Many thanks Bananian - removing those files fixed the problem.

You have to log in before you can reply Login | Sign Up

Points Rules