Then I'd reboot. But today, I noticed that after doing this, luci will be gone. That means I can no longer get to the webUI until I reinstall luci again. And round and round like this. Now luci is up and running now and I don't want to do it again. So I kindly ask. I've tried both versions of luci with and without ssl, same problem. I have run this a couple of times as well:
@eduperez thanks. that's the thing. i cannot set it up without
and when i got that command run and installed, luci goes away, which means i cannot go to 'mount' and finish the setup for exroot. it's a catch-22 situation.
some update.
so i started over again, and reflashed the router.
installed nano and luci-ssl, no issues.
but when i tried to install the files for exroot, got these problems, at some point. See image, as it's perhaps easier:
@eduperez can someone please show/tell how to do this:
An easy way to free up some RAM is to delete the symlinks to /etc/modules.d/20-cfg80211, /etc/modules.d/21-mac80211, /etc/modules.d/2*-ath* and /etc/modules.d/[4-9]-
You have still not said what hardware you are using.
ubus call system board
If there is a squashfs option for your device, that will be more space efficient and make this easier to achieve.
Beyond that, the best option here is to use image builder to add/remove packages. You can do this with the firmware selector using the "Customize installed packages" option.
The WDR4300 has an 8MB flash chip, so the report of 64MB disk space means that you are running on a RAM disk. That happens if the overlay is full, it didn't mount properly, or the initramfs image is being used instead of the squashfs.
Whatever the case is, start by re-flashing the sysupgrade image and do not save settings. This should show about 1.5 MB of free internal disk space from a clean start.
There really isn't a good way to recover from overfilling the jffs. Reformat it and start over by re-flashing the whole OS.
Do not install any more packages than actually necessary for extroot. If you pre-format your USB stick with ext4, you don't need anything more than this (which will fit):
It tells us what hardware and what image you are running. This is very relevant (from the hardware, we can determine the amount of space available, from the image we can understand which version and which image type which relates to space utilization).