Hello,
I have the following partitions.
Why te /boot partition, after some uptime, reaches the 100% occupation? Why does the 13,97GB partition does not escalate too?
What can I do to make the usage more… equal?
Thank you, Pedro
The boot partition should always be at (or near) 100%, as it is sized to the image and possibly support files (like grub config) that live there. There should never be any files other than those used to boot the device there:
$ find /boot
/boot
/boot/grub
/boot/grub/boot.img
/boot/grub/core.img
/boot/grub/grub.cfg
/boot/vmlinuz
2 Likes
It should never reach this level of allocation, since there's (pretty much) only the kernel file in there, and that's around 6MB.
How are you upgrading?
1 Like
Oops, right, here's my x86:
$ df -h /boot/
Filesystem Size Used Available Use% Mounted on
/dev/sda1 16.0M 6.6M 9.4M 41% /boot
I don't know what but something is writing in /boot partition. It increases with the router uptime until consumes all the space available. So not doubt on this I think.
Any clue? Any troubleshoot starting point?
Thank you, Pedro
If something's writing there, you made that something do it, since nothing does by default.
/boot is usually 16MB, yours is 380MB, we have no idea what you've done, and why you increased the size by a factor of ~25.
3 Likes
I have inumerous folders like this:
/boot/psave/nlbwmon-alt-20221111-0000-savelastalt-save-psave-cron
Inside them I have files similar to;
20221101.db.gz*
2022 20221001.db.gz*
The most recent directory is from May 10 2025. Or it stops writing there with some config or other change or with the full /boot space consuption it is unable to keep writing.
I use nlbwmon but in the configuration I have the /var/lib/nlbwmon defined as the Database directory.
What the evil is this?
/var/lib/nlbwmon is probably the default location, but you might be making backups to /boot using the scheduler (cron).
again, these are your changes, your set up is a black box to us.
btw, if you ever try to upgrade, your disk layout will go to sh-t.
1 Like
This should point to your persistent database storage location.
Post uci show nlbwmon
The output:
nlbwmon.@nlbwmon[0]=nlbwmon
nlbwmon.@nlbwmon[0].refresh_interval='30s'
nlbwmon.@nlbwmon[0].database_directory='/var/lib/nlbwmon'
nlbwmon.@nlbwmon[0].database_generations='10'
nlbwmon.@nlbwmon[0].database_interval='1'
nlbwmon.@nlbwmon[0].database_limit='10000'
nlbwmon.@nlbwmon[0].protocol_database='/usr/share/nlbwmon/protocols'
nlbwmon.@nlbwmon[0].local_network='192.168.0.0/16' '172.16.0.0/12' '10.0.0.0/8' 'lan'
nlbwmon.@nlbwmon[0].netlink_buffer_size='1048576'
nlbwmon.@nlbwmon[0].commit_interval='30m'
post output of cat /etc/cron too, not sure of the filename though.
Pretty well OOTB config, so the problem isn’t with the utility. As @frolic suggests check what cron is doing. I’m pretty sure it should be here: cat /etc/crontabs/root
1 Like
It was under cat /etc/crontabs/root like @RuralRoots said.
Output
59 * * * * /etc/custom/tasks.sh hourly
59 05 * * * /etc/custom/tasks.sh daily
59 05 * * 1 /etc/custom/tasks.sh weekly
0 */6 * * * /etc/custom/shutdown.sh plog psave
59 05 * * 1 /etc/custom/backup.sh
0 */6 * * * /etc/init.d/persistentlucistatistics psave
0 */6 * * * /etc/init.d/persistentnlbwmon psave
0 0 * * * /etc/init.d/acme start
Thank you
those are your custom scripts, you should probably check them, for where the files are stored (well, /boot), and for how long (probably unlimited).
Likely candidates. what is plog/psave?
1 Like
No clue…
This is a RPi4 based image, OpenWRT 22.02.3 from DFRobots - url: https://wiki.dfrobot.com/dfr0767/docs/20896 and download source: https://img.dfrobot.com.cn/wiki/5d303ff74db88f1df9d80a04/54317b71156f96d6b410aca5c956ed33.zip - that I have update to the 22.03.2 version via systemupdate if I recall it right (looooong time ago). It has been working with no problems at all, long uptimes, nothing bad to remark, ony this /boot partition full that I want to solve (but not even this cause any issue on the overall working state).
I will check it as soon as possible.
Thank you.
We know nothing about this dist, you're on your own until you install proper OpenWRT.
It appears you are using firmware that is not from the official OpenWrt project.
When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.
You may find that the best options are:
- Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
- Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
- Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).
If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.
2 Likes
I have found that it is something periodic.
I haven’t been able to directly identify the cron - it is not related to something that runs at X time, it not matches the cron config times - but shure is from there.
/boot/plog is at least referenced in:
- /bin/reboot_history.sh
- /bin/restorefiles-prune.sh
- /bin/rpi-mb-tar-bootfiles.sh
- /bin/sysinfo.sh
/boot/psave is at least referenced in:
- /bin/datapart_destroy.sh
- /bin/rpi-mb-tar-bootfiles.sh
- /bin/rpi-mb-tar-bootfiles.sh-w-upgrade
Question: if I update to the latest openwrt version 25.12.0 will be possible to make backup from the 22.03.2 and restore to the new one?
Thank you.
backup of what ?
we have no idea if your black box "OpenWRT" firmware is forward compatible with the one provided here.
Forget “my image” and the specific settings that can have.
I mean the “normal” backup made via luci interface.
If it was an oficial OpenWRT 22.03.2 release upgraded to 25.12.0, is possible to make a backp / restore of the most configs? Or something deeply changed beteween this two versions?