Always loses the external USB drive

I have an Jetson Nano with 4 GB and Ubunto 18.04.
The System keeps losing the external drive after a few days.
I’ve already replaced the power supply
Does anyone know the problem

What do you mean with losing the external drive?
Does dmesg show anything when it’s plugged in?
Have you re-flashed the device?

I also wonder if there are more details on what you mean by loses?

  • Does the drive require remount?
  • Does the drive require reboot (have you tried both)?
  • Does the drive require formatting?
  • Is the drive USB3?
  • Is this a third party carrier board, versus developer’s kit?
  • Which L4T release (use “head -n 1 /etc/nv_tegra_release”)?

It might be inconvenient, but if you could run this with serial port logging (which goes to another computer), then you could capture the logs as they occur and the serial console will save them (you could run “dmesg --follow” on the serial console while it logs to the host PC).

I have to say right away, I’m not a professional yet
the drive is extern USB3 Samsung with 1 TB SSD , formatting with EXT4.
The drive is there for a few days and suddenly gone.
After restarting the Nano, it’s back

Is the drive powered by the USB wire, or is it powered with an external power supply? The latter is much more useful for debugging, and if you have a choice (and if it is not already externally powered), then try evaluating after the drive has its own independent power source. Note that if the drive does not have that possibility, then you can use an external USB HUB which has its own external power (the USB drive would then inherit the power off of the externally powered HUB).

Note that the micro-USB port on the dev kit Nanos actually functions in device mode, and makes available a serial UART. That UART can be attached to a serial console program running on another computer (I like gtkterm on Linux, many people use minicom; on Windows, if you can figure out which COM port it is, then something like PuTTY can do this). This is an actual text-only fully interactive console, and you could log in to this, and run the command “dmesg --follow”. As a result, you’d see any log messages as they occur. What’s more important is that this port has very few requirements, and often works even when the rest of the system is crashing and burning. The serial console program itself can be told to log the entire session, so you don’t need to copy anything…you could just attach the log to the forum here. Having this run and log from before the time you even start booting up (there is useful logging during boot before Linux ever runs), and including the moment the drive fails, is quite useful. For serial console information see:

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