I’m facing an issue while trying to flash the OS on my Jetson Orin Nano 8GB Developer Kit. I’ve tried flashing with both JetPack 6.0 and 6.1 (as well as 5.x versions), but I’m encountering the same problem:
After the flash process completes, I see the boot screen briefly, but then it shows the message “L4TLauncher is attempting direct boot.” The fan stops and restarts, but the display remains black, with just a blinking cursor on the screen.
I’ve also tried using the SDK Manager to flash the OS, but the process fails during the file system and OS steps. The error message indicates: rpcbind: another rpcbind is already running. Aborting.
I’m experiencing a similar issue while flashing my new Jetson Orin Nano Developer Kit. Initially, I tried flashing the SD card with JetPack 6.1, but it didn’t boot. I later discovered that the UEFI version was 3.0xx instead of 36.xx. I also tried using JetPack 5.1 with the SD card method, but that didn’t work either. Then, I installed SDK Manager on Ubuntu 22.04, and the flashing process reached 99.6% before encountering an rpcbind error.
Can someone provide guidance on how to proceed from here?
Noted. I also experienced the issue with both SD & SSD. The issue persisted across dev kits as well which makes me think it may be a SDK manager level root cause.
Experienced this several times today trying to flash to NVMe. I also ran into a problem with microSD, and that’s why I switched to going straight to NVMe. I’ll try microSD again and see if it’s the same problem.
Of note: Even when it fails, on the serial console, before I reboot, I do get a bash prompt. That made me hope that it had actually succeeded and this error was a red herring. Unfortunately, upon reboot, all I ever get is a kernel panic.
13:49:12.035 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NANO_TARGETS: mount: /tmp/ci-cJClhIvspF: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1, missing codepage or helper program, or other error.
13:49:12.036 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NANO_TARGETS: [ 1823]: l4t_flash_from_kernel: Failed to mount APP partition /dev/mmcblk0p1
I’ve checked the log you shared, please format NVMe SSD as ext4 before use.
For the flashing failed issue, please sharing the log to check details.
We would suggest using standalone x86 Ubuntu as host PC no matter using SDK manager or flash script.
For this issue, please reboot the host PC and remove /etc/exports on the host to check if it could help.
Thanks for the reply. I am not using NVMe SSD. I am using SD card
As a host PC, I am using stand alone Ubuntu 22.04 (it is duel boot laptop with intel i7 processor. No Virtual Machine)
Do you want me to upload serial bus log from the?
In the uploaded zip file, rpcbind error is showing up. is this somehow causing flashing process to fell?
Just verified that the issue persists across multiple host machines (computer running sdk manager). Switched to a new Ubuntu computer and the rpc bind error persisted. I had a successful initial first boot of 6.1 using the new machine, but 6.0 failed, as have all subsequent flashing attempts on the new machine (both 6.0 and 6.1).
Note… I’ve since seemingly resolved the errors specified in the log above by leaving jumper cables in during boot, but am not getting an error related to “the device cannot mount the NFS server on the host or a flash command has failed.” Next line of the logs refers to the rpcbind error.
I already tried formatting the SD card, used an x86-based standalone PC, and also disabled the firewall. it didn’t work with the 64GB SD card however, the issue was resolved when I changed the 64GB SD card to 128GB
thanks though for the the inputs.