Slate AX rebooted with r/o filesystem and not functioning anymore

After running a Slate AX with 4.5 firmware for maybe 4 days …
Upon a reboot, it would not reconnect to WiFi, and while looking at the logs, I see many errors of not being able to access files.

After opening an ssh session, it looks like the root file system has been mounted read only :
root@GL-AXT1800:~# mount
mtd:ubi_rootfs 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/ubi0_2 on /overlay type ubifs (ro,noatime)
overlayfs:/overlay on / type overlay (rw,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)
bpffs on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,noatime,mode=700)
pstore on /sys/fs/pstore type pstore (rw,noatime)
root@GL-AXT1800:~#

Which seems to be making many things fail :

[ 32.466324] UBIFS error (ubi0:2 pid 6): make_reservation: cannot reserve 160 bytes in jhead 1, error -30
[ 32.466362] UBIFS error (ubi0:2 pid 6): ubifs_write_inode: can’t write inode 1230, error -30
[ 32.474964] UBIFS error (ubi0:2 pid 6): make_reservation: cannot reserve 160 bytes in jhead 1, error -30
[ 32.483298] UBIFS error (ubi0:2 pid 6): ubifs_write_inode: can’t write inode 1231, error -30

I cannot export complete logs, as it looks like it writes the logs on the filesystem first so is failing on r/o filesystem.

I also tried to do a firmware reset, but it did not do anything - as the filesystem is r/o I guess.

Repeater mode is also not functioning anymore, either with a known network or scanning.

I attempted to remount /overlay forcing rw permissions, but it would still not let me write on the filesystem.

Any idea how to get out of the situation … which is basically brick’ing the router.

Thanks !
–A.

Update on my own question/issue :slight_smile:

After trying many different things, I ended up doing a uboot firmware update.
I didn’t get any suggestion from support to potentially understand/resolve … but the uboot update fixed it, obviously. Hopefully it won’t keep happening.