Jetson Nano on reComputer J1010 Stops Working After Two Months – Errors on Boot and Module Misalignment

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

I am using a reComputer J1010, which had been working normally for two months, running two 7-hour shifts per day. The system was handling tasks across five different threads and was also storing information in my internal SQL database. It only saved three columns per row: two numeric values and one string.

After two months, the reComputer suddenly stopped working. When I connected it via HDMI, the console displayed the following errors:

tegradc tegradc .1:dpd enable lookup fail:-19
imx219 7-0010 imx219_board_setup: error during i2c read probe (-121)
imx219 7-0010 board setup fail
imx219 8-0010 imx219_board_setup: error during i2c read probe (-121)
imx219 8-0010 board setup fail
JBD2: journal transaction 10565870 on mmcblk0p1-8 is corrupt
EXT4-fs (mmcblk0p1): error loading journal
mount: /mnt: mount(2) system call failed: Structure needs cleaning.
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this Shell
bash-4.4:

Please note that the reComputer was only using the eMMC, without an SD card. Additionally, I found that the Jetson Nano module was loose on its motherboard. These are typically secured with fasteners and two support screws, but the screws were missing, causing the Jetson module to be slightly raised off the board (not completely detached, just lifted). However, the Jetson module could not have fully detached during operation, as it was housed in an enclosure that prevented it from coming loose entirely.

Another detail is that the reComputer is subject to vibration during operation. Connections to the reComputer were made via its USB port and through the pins used to connect it to the Jetson UPS.

I have ruled out electrical issues, as I tested the Jetson module on a different motherboard with only a power connection and HDMI, but the problem persists. Sudden shutdowns can also be ruled out because the system had a UPS, and at the end of each shift, the reComputer was powered off first, followed by the UPS.

I am seeking to understand the root cause of this issue and how to prevent it from happening again. Additionally, I would like to know if I can recover the stored data and whether it is possible to get the system working again.

P.S.: I read on a forum that deleting the 4GB.swp file could resolve the issue, but I could not locate the file.

Imagen de WhatsApp 2024-10-01 a las 10.30.37_c2dfe190
Imagen de WhatsApp 2024-10-01 a las 10.30.37_c2dfe1901600×1200 181 KB

2

I don’t know about that loosing module or vibration. But from your screenshot, it looks like filesystem corrupted. Better reflashing the board.

3

Thank you for your response. I understand that the filesystem might be corrupted, but could you help me understand why this could have happened in my specific case? The reComputer was running for two months without issues, performing tasks across five threads and storing minimal data in an internal SQL database (only three columns per row).

I’m particularly interested in understanding what might have caused the filesystem corruption.

Any insights into why this could have happened and how to prevent it in the future would be greatly appreciated!

4

It is unlikely to know the reason with such information.