Hello, I am currently trying to reset the Jetson Orin Nano Developer Kit, but I encountered a flash failure using SDK Manager.
I mistakenly installed CUDA 12.2 with incorrect steps when enabling the CUDA for OpenCV on this Orin Nano Developer Kit.
Subsequently, the uninstallation of CUDA failed, and I received an error indicating that the file could not be deleted, as shown in the following log.
dpkg: error processing package libcufile-12-2 (--remove):
unable to delete control info file '/var/lib/dpkg/info/libcufile-12-2.postinst': Bad message
Errors were encountered while processing:
libcufile-12-2
However, since I confirmed that this file does not actually exist in the directory, I reluctantly attempted recovery.
Unfortunately, an error occurred again when attempting recovery with SDK Manager.
In response to this error, I tried the following:
Ubuntu 20.04 PC: Disable USB suspend feature.
Windows PC - WSL Ubuntu 20.04: Change the host.
Windows PC - WSL Ubuntu 18.04: Change the Ubuntu version.
Windows PC - WSL Ubuntu 22.04: Change the Ubuntu version.
Tried all versions of Jetpack.
By the way, the cable I am currently using is a USB 2.0 cable, and I previously succeeded in auto mode flash on Ubuntu 18.04 host PC.
All of the above attempts resulted in a similar error.
I have attached the log for your reference.
I would appreciate it if you could let me know if there are any solutions.
Thank you very much. SDKM_logs_2023-12-12_10-53-20.zip (449.5 KB)
So you try to reflash the device with SDM manager but fail to due to the libcufile error?
If yes, can SDK manager detect your device when connecting with USB?
I’m not sure if it’s the cause of the libcufile error, but the SDK manager can detect the device when connected via USB.
By the way, the Jetson boots up normally when powered on, but due to the libcufile error, the CUDA environment is corrupted, and Jetpack is identified as missing.
Thank you for your response.
Yes, I have already tried reinstalling Jetpack, but I couldn’t proceed due to an error indicating that Jetpack is broken.
As a result of this error, almost all functions and installations have ceased to work properly.
Hi,
I apologize for the delay in responding as I didn’t notice your message earlier.
I’ve been attempting to recover the Jetson for a while now.
I managed to prepare another Ubuntu host for recovery, and despite encountering the same error, I miraculously succeeded in recovering it.
Strangely, this host produces the same error with any Jetson device (I have three Jetson Orin Nano developer kits), but recovery is almost always successful.
However, unlike before, the devices no longer boot to the initial setup screen but start up in a pre-configured state. Moreover, some old settings seem to remain.
I suspect that these errors might be related to the issue.
I also considered resolving the issue by reinstalling components via Ethernet, as you proposed.
However, I apologize for being unable to recreate the same situation.
Nevertheless, it’s an approach I’m definitely interested in trying should the issue arise again in the future.
Currently, I’m more interested in finding a solution to resolve the errors during Jetson’s recovery. If you think it’s better to change the topic, please let me know.
This time you can flash and install components successfully but the device cannot boot up.
If yes, could you share a screenshot or picture of the system stuck at?
I believe my English may have caused some confusion, for which I apologize.
My Jetson is now able to boot up after recovery.
The issue is no longer urgent, but I still have some questions.
Firstly, the behavior after this recovery is different from when I did a recovery in September.
In September, after a successful flash, it used to go to the initial setup screen, but now it goes directly to the login screen.
I would like to know if this is normal behavior.
Also, when flashing the Jetson, a lot of errors occurred, yet it ultimately succeeded.
I’m not sure if this is the cause, but some old settings seem to have partially remained.
For example, the language settings are mixed up. This is different from the flash I did in September.
Is this phenomenon related to the errors during flashing?
Additionally, I would like to know the possible causes of these errors and any potential problems they might cause.
As an additional note, It’s puzzling that on a different host with the same version of Linux, the same errors are happening, yet the outcomes differ. If possible, I’m seeking clarification on what might be problematic with the host.
Thank you .
※No errors occurred during the September recovery on the same host.
It sounds like you have set up the default setting with the below script before:
tools/l4t_create_default_user.sh
JetPack provides the tool to set up the default setting (ex. user name).
It only needs to be executed once and can remember the setting for the following flashing.
If you want to remove the setting, please delete the unpacked L4T folder and untar it again.