Hi all,
Is it normal for openwrt system to format itself after i unplugged it from the outlet? This is first time happening to me and it was really sad that i spent days configuring it.
Running 24 revision candidates 5 in case you wondering about update number.
Thanks
No, not normal. There are some circumstances where it would be expected, though -- for example, if you are running an intitramfs image (and not the proper persistent one, usually squashfs). Or if you are completely out of space on your device.
Yes. You should upgrade to 24.10.0 which hit official stable status recently (i.e. no longer in RC).
Of that doesn't fix the problem, let's see the output of:
ubus call system board
df -h
mount
it cant be possible im running out of space. using banana pi r4 with 16gb sdcard is enough i believe.
okeeh my fault not keeping device up to date 
, ty i will asap
also this is the output of these.
root@OpenWrt:~# ubus call system board
{
"kernel": "6.6.69",
"hostname": "OpenWrt",
"system": "ARMv8 Processor rev 0",
"model": "Bananapi BPI-R4",
"board_name": "bananapi,bpi-r4",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "24.10.0-rc5",
"revision": "r28304-6dacba30a7",
"target": "mediatek/filogic",
"description": "OpenWrt 24.10.0-rc5 r28304-6dacba30a7",
"builddate": "1736026537"
}
}
root@OpenWrt:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 46.3M 46.3M 0 100% /rom
tmpfs 1.9G 1.7M 1.9G 0% /tmp
/dev/fitrw 394.5M 394.5M 0 100% /overlay
tmpfs 1.9G 92.0K 1.9G 0% /tmp/root
overlayfs:/tmp/root 1.9G 92.0K 1.9G 0% /
tmpfs 512.0K 0 512.0K 0% /dev
root@OpenWrt:~#
root@OpenWrt:~# mount
/dev/root on /rom type squashfs (ro,relatime,errors=continue)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
/dev/fitrw on /overlay type f2fs (rw,lazytime,noatime,background_gc=on,nogc_merge,discard,discard_unit=block,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,barrier,extent_cache,mode=adaptive,active_logs=6,alloc_mode=reuse,checkpoint_merge,fsync_mode=posix,memory=normal,errors=continue)
tmpfs on /tmp/root type tmpfs (rw,noatime,mode=755)
overlayfs:/tmp/root on / type overlay (rw,noatime,lowerdir=/,upperdir=/tmp/root/upper,workdir=/tmp/root/work,uuid=on,xino=off)
tmpfs on /dev type tmpfs (rw,nosuid,noexec,noatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,noatime)
bpffs on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,noatime,mode=700)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,noatime)
There it is.... totally out of space on the overlay partition.
thats crazy, can i know where the problem is?
alsoo i downloaded the stable release now, is there a way to upgrade without losing the current config? :]
ty
From where I sit, there is no way for me to determine what is consuming the space.
Did you install a bunch of packages? Or are you storing other data (general files, logs, etc.) in the overlay?
It is possible to expand your storage, but before you go that route, you should have some idea of what is consuming this space and have backups as needed.
Yes, but it does depend if you have installed a bunch of packages.
You can simply keep settings across upgrades, or you can use the OpenWrt Upgrade Tool (owut) which can also keep packages by means of requesting a custom firmware image. This will be beneficial to your space issue if you do have a lot of stuff installed because it will move it to squashfs (which is compressed and more efficient, and generally not in your r/w overlay). However, you probably don't have space to install owut, so I'm not sure if that's an option (unless you already installed it).
You should be able to backup your general config as it is right now, so at least you won't loose that.