topic Re: /boot full in Expedition Discussions

/boot full

Bernd — Sun, 12 Apr 2020 12:28:03 GMT

Hi all,

my expedition version is 1.1.7. The dashboard says that /boot is running out of space and suggests to do "sudo apt-get autoremove -f". Unfortunately, this is not working:

expedition@expedition:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 719M 0 719M 0% /dev
tmpfs 148M 4.6M 144M 4% /run
/dev/mapper/Expedition--vg-root 18G 7.7G 9.1G 46% /
tmpfs 740M 0 740M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 740M 0 740M 0% /sys/fs/cgroup
/dev/sda1 472M 470M 0 100% /boot
tmpfs 148M 0 148M 0% /run/user/1000
expedition@expedition:~$ sudo apt-get autoremove -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done


The following additional packages will be installed:
linux-image-4.4.0-177-generic linux-modules-4.4.0-177-generic
Suggested packages:
fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools
The following NEW packages will be installed:
linux-image-4.4.0-177-generic linux-modules-4.4.0-177-generic
0 upgraded, 2 newly installed, 0 to remove and 233 not upgraded.
9 not fully installed or removed.
Need to get 0 B/18.9 MB of archives.
After this operation, 67.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 405645 files and directories currently installed.)
Preparing to unpack .../linux-modules-4.4.0-177-generic_4.4.0-177.207_amd64.deb ...
Unpacking linux-modules-4.4.0-177-generic (4.4.0-177.207) ...
dpkg: error processing archive /var/cache/apt/archives/linux-modules-4.4.0-177-generic_4.4.0-177.207_amd64.deb (--unpack):
cannot copy extracted data for './boot/System.map-4.4.0-177-generic' to '/boot/System.map-4.4.0-177-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to unpack .../linux-image-4.4.0-177-generic_4.4.0-177.207_amd64.deb ...
Unpacking linux-image-4.4.0-177-generic (4.4.0-177.207) ...
dpkg: error processing archive /var/cache/apt/archives/linux-image-4.4.0-177-generic_4.4.0-177.207_amd64.deb (--unpack):
cannot copy extracted data for './boot/vmlinuz-4.4.0-177-generic' to '/boot/vmlinuz-4.4.0-177-generic.dpkg-new': failed to write (No space left on device)
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/linux-modules-4.4.0-177-generic_4.4.0-177.207_amd64.deb
/var/cache/apt/archives/linux-image-4.4.0-177-generic_4.4.0-177.207_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
expedition@expedition:~$

What can I do?

Re: /boot full

azuniga — Sun, 12 Apr 2020 14:53:19 GMT

Hello,

On your expedition dashboard GUI what does your disk usage look like? If you are full or close to being full you should resize the VM.

Re: /boot full

Bernd — Sun, 12 Apr 2020 15:47:58 GMT

Hi,

I am not sure if I understand your reply. In other partitions I have plenty of space - about 50% free. Just /boot is full.

Is it possible to enlarge the /boot partition? If yes, how?

Re: /boot full

Bernd — Sun, 12 Apr 2020 16:28:12 GMT

I took all my courage and deleted some old initrd.img-4.4.0-* files in /boot.

After that, there was plenty of room to clean up further...

Re: /boot full

azuniga — Sun, 12 Apr 2020 16:38:21 GMT

Okay that's great! I guess what I was asking is the total disk size given to expedition. Also the latest version of expedition is 1.1.66 I did notice you are running an older version. But I am glad you were able to resolve your own problem.

Patch notes can be found here if you were interested in upgrading.

https://live.paloaltonetworks.com/t5/Expedition-Articles/Expedition-Release-Notes-for-Hotfixes/ta-p/216299

Re: /boot full

Bernd — Mon, 13 Apr 2020 12:48:15 GMT

It turned out that just removing the old /boot/initrd.img-4.4.0- files was only a temporary workaround.

Today /boot was nearly full again.

Today I tried

sudo apt-get purge linux-image-4.4.0-...

for the older images. This should not only remove the initrd.img-4.4.0- files, but everything what belongs to the image and clean everything up.

I hope this will last for longer ...