We have upgraded the community system as part of the upgrade a password reset is required for all users before login in.

Filesystem: root mounted in wrong place (help)

  • Hi. I have noticed that many times when I boot Omega2s+ for first time, the filesystem isn't as it should be.

    df-h commands gives me:

    Filesystem           1K-blocks      Used Available Use% Mounted on
    /dev/root                 6144      6144         0 100% /rom
    tmpfs                    62824      1420     61404   2% /tmp
    tmpfs                    62824     11316     51508  18% /tmp/root
    overlayfs:/tmp/root      62824     11316     51508  18% /
    tmpfs                      512         0       512   0% /dev
    /dev/mtdblock6           24960      5240     19720  21% /rom/overlay
    /dev/mmcblk0p1         3805184      7296   3797888   0% /tmp/run/mountd/mmcblk0p1

    instead of

    Filesystem                Size      Used Available Use% Mounted on
    /dev/root                 6.0M      6.0M         0 100% /rom
    tmpfs                    61.4M      1.4M     60.0M   2% /tmp
    /dev/mtdblock6           24.4M      5.2M     19.2M  21% /overlay
    overlayfs:/overlay       24.4M      5.2M     19.2M  21% /
    tmpfs                   512.0K         0    512.0K   0% /dev
    /dev/mmcblk0p1            3.6G      7.1M      3.6G   0% /tmp/run/mountd/mmcblk0p1

    It mounts overlayfs:overlayfs:/tmp/root to / instead overlayfs:/overlay to /

    Why is this happening and how to fix it? I have also connected SD card to Omega (on dev board) while turning it on, so I can later copy my files to Omega that I'm currently setting up.

    I've lost many hours putting files on omega, to then later on figure out they were put on RAM instead flash, and therefore they doesn't exixt anymore.

    It usualy helps if I put some files to root folder or do update and then reboot, but that is very time consuming, especially if you have a hundred Omegas to setup.

  • It seems sync does the trick.... but I'm not sure if that's the only and shortest way.

Looks like your connection to Community was lost, please wait while we try to reconnect.