Jetson Orin NX, JetPack 6.2, exec format error

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

Jetson Orin 16GB. JetPack 6.2, flashed with NVIDIA-SDK-Mangager
I boot the system, then run comments as usual. but suddent all executable file format was recongize as mistake. I reboot the system then everything worked well at the beginning. the the error come again…

run file command
zsh: exec format error: file
run ‘ssh’ command
/usr/bin/ssh: 1: failed: not found
/usr/bin/ssh: 2: Jun: not found
/usr/bin/ssh: 3: Jun: not found
/usr/bin/ssh: 4: ������Bh��Bh��B: not found
/usr/bin/ssh: 5: �ک/���vi: not found

run sudo dmsg
/usr/bin/dmesg: 1: e: not found
/usr/bin/dmesg: 45: the: not found

and i click the app icon at the left bar, it cannot start

image
image728×523 49.8 KB

2

Describe the host PC from which the flash took place:

  • Does it use the ext4 filesystem type?
  • Is there a VM or non-Linux filesystem involved?
  • How much space is left on the host if you cd to the “Linux_for_Tegra/” subdirectory, and then run “df -H -T .” (that trailing “.” is important)?
  • Do you still have the file “Linux_for_Tegra/bootloader/system.img.raw” on the host PC?
  • If the Jetson runs well enough to use this command, then what does it say? “uname -r”
3

q1: yes
q2: flash from nvidia-sdk manager, so there may not be any vm or non-Linux filessystem involved
q3: /dev/nvme0n1p2 ext4 1.1T 919G 37G 97% /
q4: 90GB, yes it is 59.1 GB
q5: aarch64

5

37 GB may not be enough. You might want to add another 40 GB or so. There is space used for other things, but consider just the space required for the flash image: If the rootfs partition is 50 GB, then the raw partition, all by itself, requires 50 GB. If that filesystem is to become populated with10 GB of data, then the sparse partition image will be another 10 GB. Then there is the content used to populate that in “Linux_for_Tegra/rootfs/”, and you could use that as an estimate of how large the sparse content will be, but during flash a kernel and device tree and such might be copied into that and possibly bring the size up a small amount. There are also other temporary operations using space, but that partition image (raw plus sparse) is the big one to think of. Sometimes the flash won’t even take place if the flash software thinks not enough is available, but it might also just fail in the middle.

The fact that the raw image still exists tends to say you had enough space. Call it 60 GB; each flash will create that as the raw partition. Now try to mount the raw image via loopback on the host PC just to see if it works (which can tell us if the filesystem is able to mount once copied into the Jetson; make sure to cd to the bootloader/ directory first):

sudo mount -o loop ./system.img.raw /mnt
cd /mnt
ls -aF
df -H -T .
cd -
sudo umount /mnt

If the above allows you to mount the filesystem, look in it, measure that it has some space used and some space available, and then leave and cleanly unmount (umount) it, then the flashed image itself can be considered valid. If the filesystem type shows ext4 (from the df -H -T) then only the content could be invalid, not the image itself. The sparse image is exactly the same in terms of content and simply flashes faster at the cost of losing flexibility.

Note that “uname -r” should have shown a version, and “aarch64”, despite being valid for the architecture, is not what that command should have printed. Does that command show a kernel version?

Have you ever customized the kernel?

Tell us more about the zsh command. Did you run this manually? Were there arguments to running zsh, or was it just the shell itself being started? Did you install this with an apt command?

6

oh, sorry ‘uname -r’ print it as 5.15.148-tegra. I never customized the kernel, I just flashed it and use it.

I set zsh as my default shell, I run it every time the machine start. I install by apt install. I also install oh my zsh.