Target disk space check failure while flashing by SDK Manager

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

I am flashing Jetson Xavier NX with Ubuntu 20.04 host machine and SDK Manager 2.1. Following the official guide, I receive an error in Step 3. After the board flashed with the system and rebooted, the SDK Manager attempted to verify Jatson’s system readiness by checking disk space, internet connection, and APK access. The disk space check has failed (see error.png).

My Jetson has 16 GB memory, but only 15 GB is required for standard installation. It is not clear why SDK Manager is looking for ~16 GB of available space after the OS is installed. Hence, there is 7 GB of free space on the Jetson left after the reboot. Also, whatever components I choose in SDK Manager, it always shows 15 GB space required on the target (see size.png).

How can I proceed with installation?

[EDIT]: Uploaded images.

error
error1260×810 153 KB

size
size1260×1620 144 KB

3

The internal 16GB eMMC is not enough for both L4T OS and JetPack SDK.
You need an extra storage device like NVMe SSD or USB drive for them.

Also, I don’t see any of your attachments.

4

Thanks for your prompt reply. I have updated the post.

I’ll try to add a USB drive. Will I need to set it somewhere or specify the installation path?

5

SDK Manager lets you select what storage device you want to use:
https://docs.nvidia.com/sdk-manager/install-with-sdkm-jetson/index.html

6

I tried a USB drive, and it did not work. If I chose USB in “5. Storage Device” in phase 5 of Step 3. SDK Manager will attempt to install OS, and Jetson will stack during the reboot. However, if I look into the USB, it is empty after that, as it was before the attempt.

Does the USB drive need to be formatted explicitly before installation?

Also, how can I find out how much memory the installation will take? Consequently, how big an NVMe card do I need?

7

What is your stack here?
Provide the log, please.

8

I mean, Jetson will stuck. Jetson will be disconnected from the host computer at about 96% OS install completion, and the cooler will be spun at high rpm for an endless amount of time without any sign on the Jetson screen. The SDK Manager terminal tab will show:

INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...
INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...
INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...
INFO: Flash Jetson Linux - flash: Waiting for target to boot-up...

And then

INFO: Flash Jetson Linux - flash: ...RTNETLINK answers: Permission denied
INFO: Flash Jetson Linux - flash: RTNETLINK answers: Permission denied
INFO: Flash Jetson Linux - flash: ...RTNETLINK answers: Permission denied
INFO: Flash Jetson Linux - flash: RTNETLINK answers: Permission denied
INFO: Flash Jetson Linux - flash: ...RTNETLINK answers: Permission denied

After that, the SDK Manager will show a failure message.

sdkm-2024-04-30-17-14-12.log (583.4 KB)

9

Check your sudo sysctl -a | grep disable_ipv6 and see if IPv6 is not allowed (=1).

10

The output is 0 for the NIC connected to the Jetson.

11

There should be multiple entries related to IPv6.
Are they all 0?
Or can you find another host PC and try again?

12

The rest of the entries related to IPv6 show 1.

13

Then please modify /etc/sysctl.conf and make them all zero.
Actually you can easily find this solution with Google.

14

I need more time to try this. Could you tell me why we need to enable IPv6?

15

It’s used by the flashing script and there is no why.

16

The reason for my question is that I could flash the Jetson’s internal memory but could not do so on USB with the same settings.

17

They use different mechanism.
For flashing into USB/NVMe, the script establishes ssh connection between the host and the device, which is over IPv6, after the device boots into kernel, and writes image into it.

18

Thank you for the explanation. I will try this and come back soon.

19

So, I went through the following steps:

  • Check IPv6 status sudo sysctl -a | grep disable_ipv6

  • Change all interfaces IPv6 to 0 in /etc/sysctl.conf

  • Activated changes with sysctl -p

  • Check the status again with sudo sysctl -a | grep disable_ipv6

At this point, all interfaces in the output show 0. Then, I proceeded with the installation. The installation went as before, spinning the Jetson’s fan on the reboot without booting and exiting with failure.

Do you have any clue on what is going on?

Log (604.9 KB)

20

It’s a different issue now.
Dump the serial console log, please:

21

Finally, here is the serial console log. Also, could you please elaborate more on what is the “different issue”?

Log (71.1 KB)