I was able to fix it. I didn't even think about my /etc/config/fstab. I had anon_mount off. With it on I can now use my USB

@ckielstra Since there is no other suggestions I have 2 thing you could look at. /etc/config/fstab allows you to set up mount points with the various configs. I use one for the sdcard on my devices to set up the mount point and the file system type. The docs refer to an additional "options" option which can be used to set mount options. I expect this includes the ro option but I have not tried it. The USB hotplug script is executed when you insert a USB device, you could add your own script to remount in read only mode. This is a hack you could use in the absence of a better solution.

@TypeSeven see the changelog: https://github.com/OnionIoT/source/blob/openwrt-18.06/CHANGELOG.md

@Denis-Ber Omega2+ FW: v0.2.1 b199 -rw-r--r-- 1 root root 61 Oct 18 19:23 /etc/fstab -rw-r--r-- 1 root root 61 Oct 18 19:23 /rom/etc/fstab BTW According to the official Onion Omega2 Documentation you should edit the '/etc/config/mountd' file. If you’d like to change where the MicroSD card is mounted on the filesystem, we’ve written a guide covering how to do so for both MicroSD cards and USB drives. Good luck.

@ice-long you might want to think about doing the procedure described in the documentation. https://docs.onion.io/omega2-docs/boot-from-external-storage.html

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.

@Alexandr-Didenko @Lazar-Demin You may have to restart in safe mode, then mount the file system to remove files.

@Ghent-The-Slicer said in Using SD card on Omega2 not plus: It is not possible. In addition to the missing socket, there are other components missing, some are under the shield. Care to elaborate? Not much should be required, so this is a bit surprising, unless it's an intentional disabling. That said, USB-based storage could be another option - but it should be kept in mind that neither is robust in the face of unexpected shutdowns/reboots - one of the real strengths of these platforms over the computationally far more powerful and hardly more expensive raspberry pi, is that they don't depend on a fragile SD card. If you could boot a pi W from an SPI flash, it's questionable if there would be a market for MT7688 systems at all.

Hi @Harold-Clements I have the same problem, but I have no answer that works see: https://community.onion.io/topic/1536/installing-samba-client-cifs https://community.onion.io/topic/105/anyone-was-able-to-install-samba-client-cifs

I succed to put the exec and read permissions for files and folders with the line option in fstab "option options 'rw,sync,uid=65534,gid=65534,umask=0000'" but it's impossible to put write permissions make import the umask. I use nobody user's and nothing changes.

@rupert-chandler To use f2fs you'd need the kmod for it. I do not think the official firmware has the f2fs kmod installed by default.

@Richard-Berg thanks! I saw now on my other omega2, the default driver on original firmware is: ralink_eeprom_api , mt76x8, ralink_gdma. On /etc/config/wireless the configuration for wifi device is: 'ralink' I don't know, but I will test more then I tell you. Thanks in advance!

Hi @Janus-Sanders, hmmm, installing a package on the Omega shouldn't crash it... Can you give us a little bit more description on what happened? This way we might be able to figure out what the issue might be and hopefully resolve it in the future. Thanks!