FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
313 views 5 comments
by anonymous

Hello,

We have a RUT955 which is unable to take changes. From the CLI we see the ROM is full and the filesystem has become read-only.

df

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 9920      9920         0 100% /rom
tmpfs                    62416      4092     58324   7% /tmp
/dev/mtdblock6            4096      4000        96  98% /overlay
overlayfs:/overlay        4096      4000        96  98% /
tmpfs                      512         0       512   0% /dev
/dev/mtdblock7             576       404       172  70% /log

mount

/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
/dev/mtdblock6 on /overlay type jffs2 (rw,noatime)
overlayfs:/overlay on / type overlay (ro,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,noatime,mode=700)
/dev/mtdblock7 on /log type jffs2 (rw,relatime)

rm: can't remove 'messages.old': Read-only file system

What should we do to set the filesystem back to rw and cleanup? What could be the rout case of this?

Firmware version: RUT9_R_00.07.01.4

Regards.

Bastiaan

1 Answer

0 votes
by anonymous

Hello,

If you refer to /dev/root, it is read only, and it is normal for it to have no available space. It contains all the basic files, like busyboxdropbear or iptables. It also includes default configuration files used when booting.

Your user space partition overlayfs:/overlay is full and thus, might impact device's functionality and performance. 

Remove any unnecessary packages, files from the device. 

Also, I would strongly suggest to update your device's firmware to the latest with Keep settings set to off. Be aware that this will remove your current configuration.

Best regards,

by anonymous

Hello,

Thank you for your reply. I'm trying to delete files from overlayfs:/overlay like /user/var/log/messages.old but that does not work as it is also in ro mode. How can I make overlayfs:/overlay rw again?

What are safe things to delete? (One I got in rw state).

Thanks, regards

by anonymous

Could you execute the command below and post its output?

  • du /overlay/

It will provide more insight into what is eating up your space.

Best regards,

by anonymous
Yes, here it is:

+13     /overlay/upper/etc/easy-rsa

1       /overlay/upper/etc/iproute2

1       /overlay/upper/etc/certificates/status

1       /overlay/upper/etc/certificates

5       /overlay/upper/etc/rms_mqtt

88      /overlay/upper/etc/config

20      /overlay/upper/etc/strongswan.d/charon

34      /overlay/upper/etc/strongswan.d

1       /overlay/upper/etc/hotplug.d/iface

1       /overlay/upper/etc/hotplug.d

1       /overlay/upper/etc/ppp

0       /overlay/upper/etc/hostapd

1       /overlay/upper/etc/openvpn

1       /overlay/upper/etc/profile.d

9       /overlay/upper/etc/init.d

13      /overlay/upper/etc/ddns

3       /overlay/upper/etc/rc.d

7       /overlay/upper/etc/vuci-uploads

1       /overlay/upper/etc/crontabs

1096    /overlay/upper/etc/profiles

1       /overlay/upper/etc/dropbear

83      /overlay/upper/etc/mosquitto

11      /overlay/upper/etc/ssl

1       /overlay/upper/etc/opkg/keys

1       /overlay/upper/etc/opkg

0       /overlay/upper/etc/uci-defaults/old

0       /overlay/upper/etc/uci-defaults/linux

0       /overlay/upper/etc/uci-defaults

1600    /overlay/upper/etc

1631    /overlay/upper/usr/var/log

1631    /overlay/upper/usr/var

1       /overlay/upper/usr/share/rpcd/acl.d

1       /overlay/upper/usr/share/rpcd

1       /overlay/upper/usr/share/vuci/menu.d

1       /overlay/upper/usr/share/vuci

284     /overlay/upper/usr/share/mobifd

286     /overlay/upper/usr/share

582     /overlay/upper/usr/lib/mdcollectd

27      /overlay/upper/usr/lib/lua/api/services

27      /overlay/upper/usr/lib/lua/api

8       /overlay/upper/usr/lib/lua/luci/tools

8       /overlay/upper/usr/lib/lua/luci

35      /overlay/upper/usr/lib/lua

51      /overlay/upper/usr/lib/ddns

29      /overlay/upper/usr/lib/opkg/info

135     /overlay/upper/usr/lib/opkg

893     /overlay/upper/usr/lib

165     /overlay/upper/usr/sbin

2974    /overlay/upper/usr

0       /overlay/upper/log

0       /overlay/upper/.ssh

58      /overlay/upper/www/views/services

58      /overlay/upper/www/views

58      /overlay/upper/www

4632    /overlay/upper

0       /overlay/work/work

0       /overlay/work

4632    /overlay/

(PS, isnt there a way to past code on this community forum?)
by anonymous

I have removed messages.old from /overlay/upper/usr/var/log, and now I have free space in /overlay:

Filesystem           1K-blocks      Used Available Use% Mounted on

/dev/root                10048     10048         0 100% /rom

tmpfs                    62432      3412     59020   5% /tmp

/dev/mtdblock6            3904      2648      1256  68% /overlay

overlayfs:/overlay        3904      2648      1256  68% /

tmpfs                      512         0       512   0% /dev

/dev/mtdblock7             576       420       156  73% /log

The system now behaves normal again, should I create more free space?
by anonymous

Unless you intend to install additional packages, you can leave the system as is.

Otherwise, you can remove /overlay/upper/etc/profiles contents as well.

Best regards,