Core 139 - Filesystem full

21

It wasn’t too bad! The IPFire backup/restore made the rebuild very easy! Now I have LOTS of space available:

[root@ipfire ~]# df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        1.9G  4.0K  1.9G   1% /dev
tmpfs           1.9G     0  1.9G   0% /dev/shm
tmpfs           1.9G  480K  1.9G   1% /run
/dev/sda4        58G  1.5G   53G   3% /				<<<<
/dev/sda1       110M   31M   71M  31% /boot
/dev/sda2        32M  242K   32M   1% /boot/efi
/var/lock       8.0M   12K  8.0M   1% /var/lock

I still have some custom items to restore like pmacct and a few scripts I added for OpenVPN.

Things restored that I didn’t expect:

  • Public key based authentication (SSL key for console, sftp, scp, etc.)
  • Fireinfo profile ID

Things that didn’t start (not Enabled):

  • Intrusion Prevention System (IPS)
    • Ruleset Settings - had to click Save.
    • Settings - had to click Save.
  • OpenVPN
    • was running on system before rebuild
    • I need to look into it…

The above is an FYI for others. Not a complaint in any way shape or form!

I updated the Intel J1900 (Qotom Q1900G4) BIOS firmware but it did not make any difference is the listed Processor Vulnerability Mitigations. (yes, I was hoping!) So I’m not sure if it will help anything. I was unable to locate a change log for the BIOS upgrade.

1 Like
22

Jon I’m a newbie with the same problem. Can you explain what you did to run the script?

23

Hi Julian - Welcome the the IPFire Community!

I loading up the git file in an editor, then I deleted everything ABOVE the line +#!/bin/bash.

and every thing from #!/bin/bash down I deleted all of the + at the beginning of each line. Then I saved the file and transferred it to IPFire.

Keep in mind this git is part of the current build. It is located at /usr/local/bin/filesystem-cleanup. And there is a “dry run” available that will not change or delete files.

[root@ipfire ~]# filesystem-cleanup --dry-run

Searching in /usr/lib/sse2...
find: ‘/usr/lib/sse2’: No such file or directory
Searching in /usr/lib...
Searching in /lib...

[root@ipfire ~]#

Hope that helps!

24

Thank you very much Jon for your quick reply.

25

@jpaulina68

This does not quite compute. If you are a newbie then your installation should not have accumulated dross in /usr/lib. Additionally, your installation should have assigned larger starting partitions.

What core did you initially install and what CPU architecture ?

26

Rodney interesting point of view and judgement.
A former colleague of my installed the firewall for me and use to maintain it.
Now a days I have to do it myself.
If I have ask to much in this group sorry for that!

27

The only long-term solution is to have larger partitions and the practical approach is to save backups to a USB stick then re-install, using the latest core.

If you are not confident of the installation process then you could practice on another PC

2 Likes
28

I think I will install a virtuaal machine to pratice

29

You would need two NIC in the physical machine for that to proceed. A USB-Ethernet dongle suffices as one NIC.

Getting a VM IPFire actually working is more complicated.

2 Likes
30

I just notice that .