I have an external hard drive on my Jetson AGX Orin, but this drive is often suddenly not detected

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
,
1

The external hard disk on my Jetson AGX Orin often suddenly shows up with “Input/output error”, then I use the “fdisk -l” command to find out that the external hard disk cannot be detected, and I have to unplug it again to get it to work.
Next, I used the “fdisk -l” command to find out that the external hard disk was not detected, and the “tail -f /var/log/syslog” command to check the logs for errors:

Jan  7 14:48:33 ubuntu kernel: [1788001.876822] EXT4-fs error (device sda1): __ext4_find_entry:1579: inode #2: comm node: reading directory lblock 0
Jan  7 14:48:33 ubuntu kernel: [1788001.888074] EXT4-fs error (device sda1): __ext4_find_entry:1579: inode #2: comm node: reading directory lblock 0
Jan  7 14:48:36 ubuntu kernel: [1788004.628241] EXT4-fs error: 4 callbacks suppressed
Jan  7 14:48:36 ubuntu kernel: [1788004.628254] EXT4-fs error (device sda1): __ext4_find_entry:1579: inode #1048591: comm node: reading directory lblock 0
Jan  7 14:48:36 ubuntu kernel: [1788004.644655] EXT4-fs error (device sda1): __ext4_find_entry:1579: inode #1048591: comm node: reading directory lblock 0
Jan  7 14:48:39 ubuntu kernel: [1788007.591881] EXT4-fs error (device sda1): __ext4_find_entry:1579: inode #2: comm node: reading directory lblock 0
Jan  7 14:48:39 ubuntu kernel: [1788007.603344] EXT4-fs error (device sda1): __ext4_find_entry:1579: inode #2: comm node: reading directory lblock 0
Jan  7 14:48:39 ubuntu kernel: [1788007.618789] EXT4-fs error (device sda1): __ext4_find_entry:1579: inode #2: comm node: reading directory lblock 0

I found that the external hard disk worked fine after I unplugged it again. But after a few days, the same error occurs again!

2

Hi,

If you are designing a custom base board, then it means some adaptation configurations are needed.
Otherwise, your board may not work fine.

For Orin AGX series, you could refer to below document
https://docs.nvidia.com/jetson/archives/r36.3/DeveloperGuide/HR/JetsonModuleAdaptationAndBringUp/JetsonAgxOrinSeries.html?highlight=universal%20serial%20bus#jetson-agx-orin-platform-adaptation-and-bring-up
(please be aware that above link is for rel-36.3/jetpack6.0)

This document includes below configuration

  1. pinmux change & GPIO configuration
  2. EEPROM change as most custom boards do not have an EEPROM on it.
  3. Kernel porting
  4. PCIe configuration
  5. USB configuration
  6. MGBE configuration
  7. RGMII configuration

Thanks!

5

It’s not a setup problem, in fact the external drive works fine, it’s just that it’s often not detected.

6

Please share the info first.

  1. Which jetpack version are you using
  2. Which carrier board are you using (NV devkit/Custom board)
  3. Does this issue happen to other kind of drive?
  4. Is there any software application running to trigger this error?

If you don’t know what is the meaning of the questions here, please ask. Do not reply when you don’t understand the question.

7
  1. 5.1.3
  2. NV devkit
  3. I haven’t tested it yet because I don’t have any other drive on hand. I am in the process of determining if this drive is the problem so I can decide to replace the existing drive.
  4. Most of the time this happens I’m not running any applications.
8

Is this still an issue to support? Any result can be shared?

9

Eventually, I realized it was my own hard drive.

11

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.