Fix for filesystem issue? [RESOLVED]
-
While working on a short ruby script the other night, I noticed the following message:
ls -l
[ 160.430000] jffs2: warning: (2158) jffs2_do_read_inode_internal: Truncating ino #167 to 1928 bytes failed because it only had 1906 bytes to start with!Possibly related:
- started using Samba server to copy script files to backup
- attempted to set Samba to allow write-mode, but was unsuccessful
- discovered that the Omega does not boot while hooked up to a small Hall Effect sensor more info here
oupgrade --check
Device Firmware Version: 0.1.4 b330
Checking latest version online...
Repo Firmware Version: 0.1.4 b330
Comparing version numbers
Device firmware is up to date!opkg update
Package liboniondebug version 0.4-1 has no valid architecture, ignoring.
Downloading http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/packages/base/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_base.
Downloading http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/packages/base/Packages.sig.
Signature check passed.
Downloading http://repo.onion.io/omega/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_onion.
Downloading http://repo.onion.io/omega/packages/Packages.sig.
Signature check passed.
Downloading http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/packages/packages/Packages.gz.
Updated list of available packages in /var/opkg-lists/chaos_calmer_packages.
Downloading http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/packages/packages/Packages.sig.
Signature check passed.
Collected errors:- pkg_state_status_from_str: Internal error: state_status=instaure:
- parse_from_stream_nomalloc: Missing new line character at end of file!
On Boot, I'm seeing a few of these messages:
[ 30.940000] jffs2: notice: (340) check_node_data: wrong data CRC in data node at 0x004991a4: read 0x37eea6d, calculated 0xa7519f7c.
[ 31.060000] jffs2: notice: (340) check_node_data: wrong data CRC in data node at 0x00498dfc: read 0xc2ad57a, calculated 0x30f7c754.
-
@R-H133 Haven't seen this before, pretty strange!
I don't think your Samba share would be the cause.
The sensor causing the Omega to not boot up is likely related to the GPIOs that you were using. Which GPIOs were you connecting to the sensor? See this post for more details.Regarding the jffs2 error, can you please try doing a factory restore and seeing if it continues to happen?
Let me know how it goes!
-
Lazar - Thanks for the quick reply.
Filesystem - I did a factory reset and I do not see the issue any more. I'll watch it for a bit to see if it pops up again.
GPIOs - I see the same behavior as the post you referenced, only I'm using GPIO 14 and 23. If they're connected to the Expansion Dock when I plug in the USB (to power it all), the amber light on the Omega will remain dark and not light up. If I disconnect them, the Omega still does not appear to boot. If I unplug the USB and the wires, I can plug the USB back in and boot the Omega without issue.
The side circuit is for a Hall Effect sensor. I'm using the +5v / GND pins from the Expansion dock to power this side circuit.
I also have the Omega hooked up to a Sunfounder 4-relay module, connected to GPIOs 6 and 7, and to the +5v / GND pins. This circuit does not prevent the Omega from booting.
-
@R-H133 Glad to hear it worked out! Can you please add [RESOLVED] to the topic title?
I think GPIO 14 is causing the issues you're seeing with the Hall Effect sensor. Try experimenting with other GPIOs.
Also, you don't need to unplug the USB and wires, you can try toggling the Power Switch on the Expansion Dock.
-
@Lazar-Demin - Also resolved on the GPIO issue. Using GPIO 23 and 26 allows the Omega to boot just fine even while connected.
-
@R-H133 glad to hear it all worked out!
