Omega2+ install new sw - no space
Bruce Calder last edited by
I use a bunch of RasPi's in my home to do various things but recent SD card issues have encouraged me to try to use my new Omega Onion2, which just arrived. I am having a great deal of difficulty just getting new s/w installed like node-red due to space issues so I'm reaching out to the community for help. I am logged in as root via SSH. Firmware v 0.1.10 (b160).
The node-red install instructions I am using are found here: https://wiki.onion.io/Tutorials/node-red
Ok, so space is the initial issue so I am trying to mount a USB drive but when I try to create a mount point with the "mkdir /mnt/sda1" command as outlined in https://wiki.onion.io/Tutorials/Using-USB-Storage-as-Rootfs. Unfortunately I get "mkdir: can't create directory '/mnt/sda1': Read-only file system".
I read an article that I thought would address this: https://community.onion.io/search?term=overlay read-only&in=titlesposts which says to uncomment a record in the "/etc/opkg/distfeeds.conf" file but of course when I try to save the file I get "/etc/opkg/distfeeds.conf" is read only"
There is nothing in my /etc/fstab file.
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 5632 5632 0 100% /rom
tmpfs 62872 216 62656 0% /tmp
/dev/mtdblock6 25664 25348 316 99% /overlay
overlayfs:/overlay 25664 25348 316 99% /
tmpfs 512 0 512 0% /dev
Any help would be apprecaited!
Douglas Kryder last edited by Douglas Kryder
you seem to be running into the read-only issue that another recent thread is covering,
https://community.onion.io/topic/2381/omega2-how-to-remount-root-with-write-access i think you end up putting most of filesystem onto the overlay so you can write it. there is also another thread that explains how to set-up such an overlay . i do not have the link for that.
Chris Stratton last edited by Chris Stratton
An overlay setup part of the stock configuration. I guess if you knew you were going to change many things you could remove what would only be replaced in the overlay from the initial squashfs image, but that's fairly advanced - either needing an expansion and recreation of the squashfs on another machine, or a rebuild of LEDE from sources.
I do wonder if what's being seen is perhaps a behavior where the jffs2 overlay ends up read only when it becomes full of past changes.
If the changes made are known, a factory reset should get the overlay writeable again and then the USB storage could be set up. It may also be possible to create a mountpoint on some partition which is itself a ramdisk, and so still writeable - but you'd have to re-do that on every boot.