Hi team, since Dec 2014 I have been running several ipfire boxes based on pcengines apu 1d4 hardware and continuously updated since then - with only minor intermittent issues, everything was running fine. This week, after the update to Core Level 142 , I noticed the message Filesystem full: /dev/sda1 Free=9% ! on the admin web interface. The status of the partitions is as follows: **Device** **Mounted on** **Size** **Used** **Free** **Percentage** devtmpfs /dev 1999M 1M 1999M 1% tmpfs /dev/shm 2008M 1M 2008M 1% tmpfs /run 2008M 1M 2008M 1% /dev/sda3 / 1952M 1383M 452M 76% /dev/sda1 /boot 64M 55M 6M 91% /dev/sda4 /var 11958M 1556M 9772M 14% none /var/lock 8M 1M 8M 1% none /var/log/vnstat 2008M 1M 2008M 1% none /var/log/rrd 2008M 46M 1963M 3% What’s the recommended action in this case, is there a way to clean up sda1, try to change the partition sizes or should I perform a clean install of ipfire with different partition sizes after backing up the settings? Thanks in advance for you help, stay safe, stay healthy! Greetings from Berlin! M.

@sucram, PAE is advisable, even with less than 4 GB RAM, because it reduces the risk of spurious executables being run. I run it with 2 GB RAM. Your installation is rather old, if you have only 64 MB in /boot and simply won’t cope with contemporary kernels. A backup followed by fresh install is the only advisable way forward

I think I had something similar. I ended up making a backup and rebuilding the IPFire box. [image] Core 139 - Filesystem full Update Trouble Just updated from core 138 to 139 and I ran into an Filesystem full issue. This error popped up on the Home/Main page: [54%20PM%20a] This is what I see: [46%20PM] So I’ve run out of space on /dev/sda3. From the above disk usage I think I need to clean everywhere but not /boot and not /var. Does that sound right? I’ve been using IPFire on the same device since the core 110s (110 to 119). Did this partition increase over the years? And it is time to start with a fresh build?

Thanks Jon, I will consider it! Best, M.

maybe you have lots of files on your boot partition that don’t belong. This will list all of boot: ls -alR /boot

Hi Jon, the biggest files on that partition are in /boot itself: [root@ipfire-berlin ~]# ls -la /boot total 50860 drwxr-xr-x 4 root root 4096 Mar 18 22:07 . drwxr-xr-x 22 root root 4096 Mar 17 2019 .. -rw-r--r-- 1 root root 163993 Mar 12 13:13 config-4.14.173-ipfire -rw-r--r-- 1 root root 163611 Mar 12 13:02 config-4.14.173-ipfire-pae drwxr-xr-x 5 root root 4096 Mar 18 22:06 grub -rw-r--r-- 1 root root 17758560 Mar 12 13:17 initramfs-4.14.173-ipfire.img -rw-r--r-- 1 root root 18329428 Mar 18 22:08 initramfs-4.14.173-ipfire-pae.img drwx------ 2 root root 16384 Jul 21 2014 lost+found -rw-r--r-- 1 root root 951 Feb 28 2015 old-grub-config -rw-r--r-- 1 root root 2772897 Mar 12 13:13 System.map-4.14.173-ipfire -rw-r--r-- 1 root root 2821141 Mar 12 13:02 System.map-4.14.173-ipfire-pae -rw-r--r-- 1 root root 4942784 Mar 12 13:13 vmlinuz-4.14.173-ipfire -rw-r--r-- 1 root root 4997088 Mar 12 13:02 vmlinuz-4.14.173-ipfire-pae Can any of those be removed without causing damage? Best, M.

Marcus, I dont have the -pae files in /boot … my /dev/sda1 is 110M but yours is 64M

Thanks Rodney. I have just read https://forum.ipfire.org/viewtopic.php?t=23109 (in German) which comes to the same conclusion. Best, M.

Filesystem full: /dev/sda1 after update to 142

Installing & Running IPFire Update Trouble

jon (Jon) 20 March 2020 18:17 2

I think I had something similar. I ended up making a backup and rebuilding the IPFire box.