I locked myself out of an AR300M and did the 6 second reset to show firmware mode and uploaded new firmware. 2 times now on 2 different devices the space dropped from the 100mb to 6mb this device has a 16 + 128 configuration. The first time I thought I had received a bad device, the second time however I was paying more attention and am not sure how to get the space back.
Filesystem Size Used Available Use% Mounted on /dev/root 8.0M 8.0M 0 100% /rom tmpfs 61.1M 268.0K 60.8M 0% /tmp /dev/mtdblock5 6.3M 356.0K 5.9M 6% /overlay overlayfs:/overlay 6.3M 356.0K 5.9M 6% / tmpfs 512.0K 0 512.0K 0% /dev /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/mtdblock5 on /overlay type jffs2 (rw,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) debugfs on /sys/kernel/debug type debugfs (rw,noatime)
You’re booted from NOR flash.
GL-AR300M Series - GL.iNet Docs describes how to switch back to NAND firmware.
With NAND flash, that line should look something like
/dev/ubi0_1 on /overlay type ubifs (rw,noatime,assert=read-only,ubi=0,vol=1)
note “ubi” and “ubifs” instead of “mtdblock” and “jffs2”
Edit: The GL.iNet boot loader likely detected three “failed boots” and switched over to NOR boot so that you could access the device. Many people, including I, consider this a good feature, though it requires a sharp eye to see the change. I miss it myself on several devices I work with, GL.iNet and otherwise.
Thanks, That fixed it.