2+ boots from usb, but goes into read only mode
-
You would want to check the same /dev/sda1 being mounted at two mount-points:
1:
/dev/sda1 ext4 14.6G 939.1M 12.9G 7%/overlay
2:
/dev/sda1 ext4 14.6G 939.1M 12.9G 7%/tmp/run/mountd/sda1Thanks..
-
@tjoseph1 the example output at bottom of the linked booting from external storage page does as well
Filesystem Size Used Available Use% Mounted on /dev/root 5.5M 5.5M 0 100% /rom tmpfs 29.7M 196.0K 29.5M 1% /tmp /dev/sda1 14.1G 46.7M 13.4G 0% /overlay overlayfs:/overlay 14.1G 46.7M 13.4G 0% / tmpfs 512.0K 0 512.0K 0% /dev /dev/sda1 14.1G 46.7M 13.4G 0% /tmp/run/mountd/sda1
-
@josh-hightower :
I don't think you can mount an ext4 file-system in more than one place. Doing so would corrupt the metadata.Does your application require that you mount a volume at /tmp/run/mountd/sda1 ?
Thanks..
-
@tjoseph1 everything uses paths relative to home. The second mount (/tmp/run/mountd/sda1) is just the automatic one, not manual. But if that were a problem, why would it be in the onion docs?
-
Could you point me to the onion docs.. May be the docs was presenting a special case ? I would like to have a look. Please post the link to the doc..
Thanks ..
-
-
@josh-hightower :
You are right. I saw thedf -hcommand output towards the end of the docs matches the screenshot you provided. May be things were different with b200 firmware, that you have.# df -h shows only two lines pertaining to the sda volume (4.0G) in b233, which are:
Filesystem Type Size Used Available Use% Mounted on
..
/dev/sda1 ext4 4.0G 597.2M 3.2G 16% /overlay
overlayfs:/overlay overlay 4.0G 597.2M 3.2G 16% /Thanks..
-
Since this is an Omega2+ module, can you upgrade to b233 firmware, unless your custom app may have old version dependencies..
The DL link:
http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2p-v0.3.2-b233.binThanks..
-
@tjoseph1 it uses oled, relay, 1 wire sensor, and then everything else if python libs so shouldn't be an issue there. I would assume that the functionality of some of the add ons (like relay) are not being removed even tho the hardware is being stopped? I have not verified it since code changes have been made since the last hardware swap, but the following is in my install script. I know python 2 is at EOL, but i have not migrated the project to python 3 yet.
opkg update opkg install python pyOledExp pyRelayExp python-pip pip insstall pyowm
-
@josh-hightower :
I am not familiar with b200 and it's overlay. I started 3 mo back with b233. Typically a volume is mounted at only one place. If you have another device, you could check the compatibility under b233, before migrating to b233.
-
@tjoseph1 long story short, that flash drive was failing...well more like failed. Forensic images have been taken merged with /overlay and just mounted and other and is a future project to test recovery or repair (have not looked at drive's board yet). Brand new flash drive (usb 3.0 even tho im pretty sure 2+ only supports usb 2) different 2+ and it is running fine. Also forced me to finish the update to my thermostat code to be able to push it to the different 2+. Even with this new drive that is working with 3199, could not get 1AB5 (one referenced to begin with) or my pro to correctly boot off it. Came across this, https://github.com/Pi4IoT/Omega2_External_Storage, which changes 2 flags...have not dug into it but it is mostly the same as the onion docs and it is working. Maybe that has to do with why the other 2 would not boot off it, they just booted and then mounted it. Never saw mtdblock6/7 before, wondering if the new firmware means that page (https://docs.onion.io/omega2-docs/boot-from-external-storage.html) is a little out of date?
Ω-ware: 0.3.2 b233 ----------------------------------------------------- root@Omega-3199:~# df -hT Filesystem Type Size Used Available Use% Mounted on /dev/root squashfs 7.8M 7.8M 0 100% /rom tmpfs tmpfs 60.9M 4.7M 56.3M 8% /tmp /dev/sda1 ext4 28.3G 85.4M 26.8G 0% /overlay overlayfs:/overlay overlay 28.3G 85.4M 26.8G 0% / tmpfs tmpfs 512.0K 0 512.0K 0% /dev /dev/sda1 ext4 28.3G 85.4M 26.8G 0% /mnt/sda1 /dev/mtdblock6 jffs2 22.1M 7.1M 15.0M 32% /mnt/mtdblock6 /dev/mtdblock7 jffs2 512.0K 196.0K 316.0K 38% /mnt/mtdblock7 root@Omega-3199:~#
-
wanted to change post title to "[solved...kinda by using a different 2+/new USB] 2+ boots from usb, but goes into read only mode", but it says that posts can only be edited for 3600 after being posted...is there not a way to mark as "solved"?
-
@josh-hightower should be able to edit the first post and change the title. lemme know if you can't
-
@Lazar-Demin it gives the following error in a red popup bottom right corner
ERROR
You are only allowed to edit posts for 3600 second(s) after posting
