I previously set up my Omega 2+ to boot from an SD card using the instructions here:

Booting from External Storage

It worked fine when I did it before upgrading to OpenWRT18.

After upgrading to OpenWRT18, I had to do it again, and I followed the same instructions, precisely, as far as I can tell.

However, after rebooting, this file:

/etc/config/fstab

reverts to what it was initially, even though I edited it as the last step before rebooting (and I checked, it is being saved properly before I reboot).

After rebooting, the file system looks exactly as it did before I started:

Filesystem                Size      Used Available Use% Mounted on
/dev/root                 7.8M      7.8M         0 100% /rom
tmpfs                    29.3M     84.0K     29.2M   0% /tmp
/dev/mtdblock6            6.6M      6.6M         0 100% /overlay
tmpfs                    29.3M    116.0K     29.2M   0% /tmp/root
overlayfs:/tmp/root      29.3M    116.0K     29.2M   0% /
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mmcblk0p1           14.5G     40.0M     13.7G   0% /mnt/mmcblk0p1

And the relevant part of /etc/config/fstab goes back to what it was before I edited. Before rebooting, I changed it to this:

config mount
        option target '/overlay'
        option uuid 'c4f1e098-785d-412a-af16-491e184650ff'
        option enabled '1'

But after rebooting, it goes back to:

config mount
        option target '/mnt/mmcblk0p1'
        option uuid 'c4f1e098-785d-412a-af16-491e184650ff'
        option enabled '0'

Anyone know why it keeps reverting to what it was before I reboot? I want to install Node but I can't because there is not enough space. My 2+ is useless without more space.

@Jeff-Seese Thank you, I will try that!

@Thomas-McCarthy said in Can no longer boot from external storage after update to OpenWRT18:

Anyone know if there will be an update to let us boot from an external device with OpenWRT18?

A factory reset, followed by repeating the entire process, hasn't solved the problem.

I did notice this during the boot process:

[   15.408335] block: attempting to load /etc/config/fstab
[   15.415885] block: unable to load configuration (fstab: Entry not found)
[   15.422871] block: no usable configuration

...but I don't know if that is significant. /etc/config/fstab does exist once the device has booted, but it still contains what I pasted above.

I thought it might be related to the fact that my SD card is apparently partitioned (that "p1" at the end of the device name seems to be the clue that my Omega sees partition 1).

I reformatted the drive so now it only has one partition (and the device name is now mmcblk0), but the end result is the same, once I reboot, /etc/config/fstab is reset to what it was before I edited it.

I previously set up my Omega 2+ to boot from an SD card using the instructions here:

Booting from External Storage

It worked fine when I did it before upgrading to OpenWRT18.

After upgrading to OpenWRT18, I had to do it again, and I followed the same instructions, precisely, as far as I can tell.

However, after rebooting, this file:

/etc/config/fstab

reverts to what it was initially, even though I edited it as the last step before rebooting (and I checked, it is being saved properly before I reboot).

After rebooting, the file system looks exactly as it did before I started:

Filesystem                Size      Used Available Use% Mounted on
/dev/root                 7.8M      7.8M         0 100% /rom
tmpfs                    29.3M     84.0K     29.2M   0% /tmp
/dev/mtdblock6            6.6M      6.6M         0 100% /overlay
tmpfs                    29.3M    116.0K     29.2M   0% /tmp/root
overlayfs:/tmp/root      29.3M    116.0K     29.2M   0% /
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mmcblk0p1           14.5G     40.0M     13.7G   0% /mnt/mmcblk0p1

And the relevant part of /etc/config/fstab goes back to what it was before I edited. Before rebooting, I changed it to this:

config mount
        option target '/overlay'
        option uuid 'c4f1e098-785d-412a-af16-491e184650ff'
        option enabled '1'

But after rebooting, it goes back to:

config mount
        option target '/mnt/mmcblk0p1'
        option uuid 'c4f1e098-785d-412a-af16-491e184650ff'
        option enabled '0'

Anyone know why it keeps reverting to what it was before I reboot? I want to install Node but I can't because there is not enough space. My 2+ is useless without more space.

Has anyone come across this error after installing this version of npm?

Error: Cannot find module 'internal/util/types'

I cannot install any packages via npm because of this.

Thanks!

Hi All,

I have been trying to get IPFS (the JavaScript implementation of IPFS, JS-IPFS) running on my Omega2+, just to see if I could do it.

I have reached a point where I could use some advice. Note: I have pretty much no idea what I am doing.

I tried to just install it (the project is here: https://github.com/ipfs/js-ipfs) with npm.

First issue: out of memory:

[ 709.942633] Out of memory: Kill process 1648 (npm) score 504 or sacrifice child

So I made a swap file so I could continue the install, and I had success, sort of:

root@Omega-6CD5:/# npm install ipfs --global
WARN engine ipfs@0.33.1: wanted: {"node":">=6.0.0","npm":">=3.0.0"} (current: {"node":"4.3.1","npm":"2.14.12"})

OK, so apparently js-ipfs needs nodejs of 6 or higher, and an updated npm as well.

This is where I really don't know what I am doing. I figured I would follow instructions on cross-compiling and make a binary of a newer nodejs myself. I am using a Mac, so I installed Docker, and pulled the omega2-source, but when I ran "make" I got this:

make -r world: build failed. Please re-run make with -j1 V=s to see what's going on
/root/source/include/toplevel.mk:198: recipe for target 'world' failed
make: *** [world] Error 1
root@2cb6caf89911:~/source#

So, now I have no idea what to do next. If I understand correctly, I need to complete this step before I can attempt to cross-compile newer versions of nodejs and npm. At this point I am just following instructions I have found on the web like a trained monkey.

Thank you!

Here are some photos:

Photos

Thank you!

I have been able to use my Omega with the Expansion Dock with no problem, but the Mini Dock is giving me problems. Random characters I type end up in my Terminal as weird-looking ? characters. It's not any particular key, as you can see in my screenshot, and it only happens with the Mini Dock. Do I have a bum Mini Dock?

Terminal Screenshot