Flashing linux on nvme ssd fails at mount of NFS server

Hey all. I am trying to Flash my new Jetson AGX Orin dev kit with a newly installed nvme ssd in the m2 slot (Samsung 990 Pro 2TB) and it fails at nfs mount.

Relevant log snippet:

20:55:57.635 - Info: Waiting for device to expose ssh ...
20:55:57.638 - Info: Run command: flash on fc00:1:1:0::2
20:55:57.638 - Info: 
20:55:57.835 - Info: SSH ready
20:55:57.835 - Info: 
20:58:58.433 - Info: mount.nfs: Connection timed out
20:58:58.433 - Info: 
20:58:58.436 - Info: Flash failure
20:58:58.436 - Info: 
20:58:58.438 - Info: Either the device cannot mount the NFS server on the host or a flash command has failed. Debug log saved to /tmp/tmp.8LOvVMA6TS. You can access the target's terminal through "sshpass -p root ssh root@fc00:1:1:0::2" 
20:58:58.438 - Info: 
20:58:59.500 - Info: Cleaning up...
20:58:59.500 - Info: 
20:58:59.578 - Error: [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FLASH_JETSON_LINUX_COMP.ferros.sh; [error]: 130032 blocks

this is from the NV_L4T_FLASH_JETSON_LINUX_COMP.log

I was able to successfully flash the build in eMMC memory that update the unit originally, but I have been unable to repeat the process for the nvme sdd.

Host Machine: Ubuntu 20.04 (distro BlackBuntu)
SDK Manager: 2.1.0-11682
image

SDKM_logs_JetPack_6.0_(rev._2)_Linux_for_Jetson_AGX_Orin_modules_2024-07-24_20-45-41.zip (496.9 KB)

Hi,
Please try this:

Jetson AGX Orin FAQ
Q: I get a USB timeout error during flash Orin. How to resolve that?

Hi there. Thanks for the reply! I had tried that previously to no avail. I did try it again and it also failed at the same point along with a different usb port. I verified my connection after failure

[07:04:18]-[root@ferros-buntu]/home/ferros -> lsusb | grep NVIDIA
Bus 002 Device 003: ID 0955:7035 NVIDIA Corp. Linux for Tegra

[07:27:01]-[root@ferros-buntu]/home/ferros -> cat /sys/module/usbcore/parameters/autosuspend
-1


Would it be a decent idea to throw vanilla Ubuntu 22 on a raspberry pi and use that as the host?

Hi,
Please try to flash Jetpack 5.1.3. Would like to check if this version can be flashed.

Tried with 5.1.3 and got a failure at the same point. I’m going to spin up an old laptop with Ubuntu 22.04 and see if that will work

17:42:01.074 - Info: Waiting for device to expose ssh ...
17:42:11.158 - Info: ...
17:42:12.278 - Info: RTNETLINK answers: File exists
17:42:12.278 - Info: 
17:42:12.281 - Info: RTNETLINK answers: File exists
17:42:12.281 - Info: 
17:42:12.297 - Info: Waiting for device to expose ssh ...
17:42:12.301 - Info: Run command: flash on fc00:1:1:0::2
17:42:12.301 - Info: 
17:42:12.503 - Info: SSH ready
17:42:12.503 - Info: 
17:45:13.552 - Info: mount.nfs: Connection timed out
17:45:13.552 - Info: 
17:45:13.555 - Info: Flash failure
17:45:13.555 - Info: 
17:45:13.555 - Info: Cleaning up...
17:45:13.555 - Info: 
17:45:13.726 - Error: [exec_command]: /bin/bash -c /tmp/tmp_NV_L4T_FLASH_JETSON_LINUX_COMP.ferros.sh; [error]: 84856 blocks

SDKM_logs_JetPack_5.1.3_Linux_for_Jetson_AGX_Orin_modules_2024-07-26_17-15-13.zip (440.5 KB)

Try to get serial console log during flashing and that log will give more specific error details…

So I lose the ability to access serial logs when the device reboots into recovery mode. /ttyACM0 just disappears from /dev/ and doesn’t come back. Definitely something about losing connection when in booting into recovery mode.

checking the USB connection, when not in recovery I get the Linux for Tegra, and when in recovery mode i get APX

[14:00:42]-[ferros@ferros-buntu]~/.local/share/Trash/expunged -> lsusb | grep NVIDIA
Bus 002 Device 006: ID 0955:7035 NVIDIA Corp. Linux for Tegra
[14:01:56]-[ferros@ferros-buntu]~/.local/share/Trash/expunged -> lsusb | grep NVIDIA
Bus 001 Device 029: ID 0955:7023 NVIDIA Corp. APX

I did a watch command to make sure the autosuspend config value doesn’t revert with the reboots and it doesn’t

I’m still working on finding some kind of secondary computer that can run vanilla ubuntu 22.04. I have a side drive that has 256gb of free space so will probably try partition that out and make it bootable to ubuntu 22.

So worked just fine using vanilla Ubuntu 22.04. Thanks for all the help!

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