Ssh connection refused while flashing

Hello,

I am trying to update Jetpack version to a newest one on Jetson Orin Nano. This is my setup:

  • Host machine on native Ubuntu 22.04,
  • Jetson Orin Nano in Force Recovery Mode,
  • Trying to flash NVMe 128 GB (although 256 is recommended I am trying this)
  • Jetson connected to Host machine with USB cable which was before used for flashing AGX and should work,
  • Jetson connected with ethernet cable to router with access to internet,
  • Host machine connected to the same router with Wi-Fi,
  • Jetson is visible by Host Machine.

I tried flashing with SDK manager and also flashing manually following NVIDIA guides. Both times I am getting this error

16:10:54 INFO: Flash Jetson Linux - flash: Device should have booted into initrd kernel now. However, the host cannot connect to its ssh server
16:10:54 INFO: Flash Jetson Linux - flash: Command failed: sshpass -p root ssh root@fc00:1:1:0::2. Check your network setting (VPN, firewall,...) to make sure the device can ssh root@fc00:1:1:0::2

which I think is the reason of the flashing process. I am flashing while connected to my home network. Here is the full log from the recent flashing attempt:
SDKM_logs_JetPack_6.2_Linux_for_Jetson_Orin_Nano_8GB_2025-02-14_15-48-52.zip (226.5 KB)

I tried to debug the connectivity to the Jetson, however my experience in computer networks is just very basic and don’t know how to continue. Some things I tried:

$ ping fc00:1:1:0::2
PING fc00:1:1:0::2(fc00:1:1::2) 56 data bytes
64 bytes from fc00:1:1::2: icmp_seq=1 ttl=64 time=0.525 ms
64 bytes from fc00:1:1::2: icmp_seq=2 ttl=64 time=0.516 ms
^C
--- fc00:1:1:0::2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1017ms
rtt min/avg/max/mdev = 0.516/0.520/0.525/0.004 ms 
$ ssh root@fc00:1:1:0::2
ssh: connect to host fc00:1:1::2 port 22: Connection refused
$ traceroute fc00:1:1:0::2
traceroute to fc00:1:1:0::2 (fc00:1:1::2), 30 hops max, 80 byte packets
 1  fc00:1:1::2 (fc00:1:1::2)  0.426 ms  0.336 ms  0.289 ms

I also tried accessing ssh with the user I created and failed.

I am not sure why SDK manager is trying to access this IPv6 address. I just booted up the Jetson Nano device to look at it’s ifconfig and don’t see it anywhere. Moreover, I can see that eth0 has IPv4 address that I can even ssh to as my user! I don’t want to share the output of the ssh as I don’t know if there’s any sensitive information.

However, I discovered that I can ssh only to my user with the password I created and SDK manager is trying to access as root user which I also tried to ssh to, but failed. My question is now what am I missing? What can I do to flash the device?

Thanks in advance for any tips.

1 Like

Hi @matej.kunda

I am a bit confused. You mentioned that you weren’t able to access your device but then you mentioned that you were able to do so? Can you explain this better?

Please test disabling your firewall when performing your tests; to do so, run on your host computer:

sudo ufw disable

You could also try restarting the network service on your Jetson device by running:

sudo systemctl restart systemd-networkd

For what I check on the logs, you were able to flash your device correctly. When you mention that you didn’t, you mean for the extra packages that are installed later on the Jetson?

Regards,

Ricardo González Víquez
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com
Website: www.ridgerun.com

Hello,

to clarify. I was not able to access Jetson device on the address that SDK manager tried (IPv6), but I manually tried with IPv4 address that I found with ifconfig and I could ssh without problems.

Please test…

Thanks for the advices, I will try both and write the result.

For what I check on the logs, you were able to flash your device correctly. When you mention that you didn’t, you mean for the extra packages that are installed later on the Jetson?

The flashing process results in a fail, both with SDK manager and manual flash. The Jetson device has still the same old Jetpack version and was not re-written with the newest one.

Hi,

Please try ricardo.gonzalez1 mentioned command to disable the firewall and run sdk manager again

sudo ufw disable

Thanks

Hello,

I tried both commands. I checked firewall status on my host machine and it was disabled also before, but I ran the command again to make sure. I also restarted the network service on my Jetson. The process still fails with the same error:

11:00:33 INFO: Flash Jetson Linux - flash: Command failed: sshpass -p root ssh root@fc00:1:1:0::2. Check your network setting (VPN, firewall,...) to make sure the device can ssh root@fc00:1:1:0::2

Here are the full logs:
SDKM_logs_JetPack_6.2_Linux_for_Jetson_Orin_Nano_8GB_2025-02-17_10-37-31.zip (228.3 KB)

SDK manager is trying the same IPv6 address with root user. I don’t know how to proceed.

Edit:
What I tried in the meantime:

  • In Jetson /etc/ssh/sshd_config I set the AddressFamily settinng to any
  • Address fc00:1:1:0::2 is not reachable by any means
  • Again, in Jetson sshd_config I set the line PermitRootLogin yes, PasswordAuthentication yes, and PubkeyAuthentication yes.

Nothing from these settings helped. I am trying to access the router settings to look into that, however I don’t have direct access to it so it’s a bit complicated to do so.

Hello @matej.kunda

I don’t think your problem is related to your network environment or to any issue regarding the ssh connection. When flashing a Jetson device, some additional packages are installed by accessing the machine on ssh, but the flashing process doesn’t need network access to your device.

There are ways to install the additional packages after flashing the device. So I want to ask you if you are sure that your device is not being flashed. If it is not, then we can work on helping you to flash your device. If it is being flashed correctly, then we can also help you install the additional packages after flashing the device.

Regards,

Ricardo González Víquez
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com
Website: www.ridgerun.com

Hello @ricardo.gonzalez1

I am also suspicious of this activity, since I already flashed AGX last week and it was failing also when installing the additional SDK components. I resolved this by not installing it with SDK manager, but manually with sudo apt install nvidia-jetpack.

However, the Nano version flashing looks different. Even when I unchecked the SDK components it still wants to access the SSH.

So I want to ask you if you are sure that your device is not being flashed.

I am sure, when I launch the Jetson device, it is still on Ubuntu 20.04 and I can see the old files on my desktop which would be gone after reflash. The SDK manager after the process displays “Installation failed” and on the Details page I can see that the step “Flash Jetson Linux” failed. Also in the logs I see:

4:20:31 INFO: Flash Jetson Linux - flash: ***************************************
14:20:31 INFO: Flash Jetson Linux - flash: * *
14:20:31 INFO: Flash Jetson Linux - flash: * Step 3: Start the flashing process *
14:20:31 INFO: Flash Jetson Linux - flash: * *
14:20:39 INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...
14:20:40 INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...
14:20:41 INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...
14:20:42 INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...
14:20:43 INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...
14:20:56 INFO: Flash Jetson Linux - flash: Waiting for device to expose ssh ...Waiting for device to expose ssh ...Run command: flash on fc00:1:1:0::2
14:22:18 INFO: Flash Jetson Linux - flash: Device should have booted into initrd kernel now. However, the host cannot connect to its ssh server
14:22:18 INFO: Flash Jetson Linux - flash: Command failed: sshpass -p root ssh root@fc00:1:1:0::2. Check your network setting (VPN, firewall,...) to make sure the device can ssh root@fc00:1:1:0::2
14:22:18 INFO: Flash Jetson Linux - flash: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
14:22:18 INFO: Flash Jetson Linux - flash: link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
14:22:18 INFO: Flash Jetson Linux - flash: inet 127.0.0.1/8 scope host lo
14:22:18 INFO: Flash Jetson Linux - flash: valid_lft forever preferred_lft forever
14:22:18 INFO: Flash Jetson Linux - flash: inet6 ::1/128 scope host
14:22:18 INFO: Flash Jetson Linux - flash: valid_lft forever preferred_lft forever
14:22:18 INFO: Flash Jetson Linux - flash: 2: enp0s31f6: mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
14:22:18 INFO: Flash Jetson Linux - flash: link/ether 18:db:f2:04:0b:07 brd ff:ff:ff:ff:ff:ff
14:22:18 INFO: Flash Jetson Linux - flash: 3: wlp1s0: mtu 1500 qdisc noqueue state UP group default qlen 1000
14:22:18 INFO: Flash Jetson Linux - flash: link/ether b8:08:cf:41:06:52 brd ff:ff:ff:ff:ff:ff
14:22:18 INFO: Flash Jetson Linux - flash: inet 192.168.68.106/24 brd 192.168.68.255 scope global dynamic noprefixroute wlp1s0
14:22:18 INFO: Flash Jetson Linux - flash: valid_lft 3946sec preferred_lft 3946sec
14:22:18 INFO: Flash Jetson Linux - flash: inet6 fe80::8fcb:e09b:e7a3:dfea/64 scope link noprefixroute
14:22:18 INFO: Flash Jetson Linux - flash: valid_lft forever preferred_lft forever
14:22:18 INFO: Flash Jetson Linux - flash: 9: enxf66f5dd4d957: mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
14:22:18 INFO: Flash Jetson Linux - flash: link/ether f6:6f:5d:d4:d9:57 brd ff:ff:ff:ff:ff:ff
14:22:18 INFO: Flash Jetson Linux - flash: inet6 fc00:1:1::1/64 scope global
14:22:18 INFO: Flash Jetson Linux - flash: valid_lft forever preferred_lft forever
14:22:18 INFO: Flash Jetson Linux - flash: inet6 fe80::f46f:5dff:fed4:d957/64 scope link
14:22:18 INFO: Flash Jetson Linux - flash: valid_lft forever preferred_lft forever
14:22:18 INFO: Flash Jetson Linux - flash: inet6 fe80::2/64 scope link
14:22:18 INFO: Flash Jetson Linux - flash: valid_lft forever preferred_lft forever
14:22:18 INFO: Flash Jetson Linux - flash: Cleaning up...
14:22:18 ERROR: Flash Jetson Linux - flash: [exec_command]: /bin/bash -c /home/danielkonecny/.nvsdkm/replays/scripts/JetPack_6.2_Linux/NV_L4T_FLASH_JETSON_LINUX_COMP.sh; [error]: rpcbind: another rpcbind is already running. Aborting
14:22:18 INFO: Flash Jetson Linux - flash: [ Component Install Finished with Error ]
14:22:18 INFO: Flash Jetson Linux - flash: [host] [ 7.23 GB used. Disk Avail on Partition /dev/nvme0n1p6: 82.00 GB ]
14:22:18 INFO: Flash Jetson Linux - flash: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 22m21s ]
14:22:18 ERROR: Flash Jetson Linux - flash: command terminated with error
14:22:18 SUMMARY: Flash Jetson Linux - flash: First Error: Installation failed.

That is the end of the log, so I suppose it failed on that SSH error…

After that

If it is being flashed correctly, then we can also help you install the additional packages…

Thanks for the support, if you meant the nvidia-jetpack package I was able to install it also before on AGX, so I hope there will be no different problems.

Based on your log provided.

{"partition":"/dev/nvme0n1p6","type":"fuseblk","requiredMB":16457.773025512695,"freeMB":96335.9921875}

It appears that your Ubuntu installation is on a partition with the fuseblk format. Please create a new partition formatted as ext4 and install the SDK on that partition.

Thanks

Thanks a lot @DavidDDD for the suggestion. Are you talking about the Ubuntu installation on Jetson? If so, can I format the whole NVMe to ext4, or does it need to have a Jetpack system installed in order to flash correctly? My Jetson kit does not have an SD card slot, so the Jetpack is only installed on the NVMe SSD.

No. I mean your host partition format is fuseblk , but sdk maanger need installed inext4.
You could use command lsblk -o NAME,FSTYPE,SIZE,TYPE,MOUNTPOINT to check.

Thanks

Hi all!

Thanks DavidDDD for the tip. Reformatting the disk helped. Maybe it would be beneficial for the SDK manager to check the partition format before installing so it does not run into these types of errors. Marking as solved.

2 Likes

Hello @DavidDDD,

would it be possible to somewhere submit a feature request for the SDK manager to check if the partition is formatted as ext4?