During the installation process I am getting the following errors: 13:14:43 INFO: File System and OS - target_image: Installing extlinux.conf into /boot/extlinux in target rootfs
13:14:43 INFO: File System and OS - target_image: mkdir: cannot create directory ‘/home/mdavis/nvidia/nvidia_sdk/JetPack_6.2.1_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/rootfs/boot/extlinux/’: Permission denied
13:14:43 INFO: File System and OS - target_image: mkdir: cannot create directory ‘rootfs/opt/nvidia’: Permission denied
13:14:43 INFO: File System and OS - target_image: mkdir: cannot create directory ‘rootfs/opt/nvidia’: Permission denied
13:14:43 ERROR: File System and OS - target_image: [exec_command]: /bin/bash -c /home/mdavis/.nvsdkm/replays/scripts/JetPack_6.2.1_Linux/NV_L4T_FILE_SYSTEM_AND_OS_COMP.sh; [error]:
13:14:43 INFO: File System and OS - target_image: [ Package Install Finished with Error ]
13:14:43 INFO: File System and OS - target_image: [host] [ 5.86 GB used. Disk Avail on Partition /dev/sda2: 721.57 GB ]
13:14:43 INFO: File System and OS - target_image: [ NV_L4T_FILE_SYSTEM_AND_OS_COMP Install took 4m19s ]
13:14:43 ERROR: File System and OS - target_image: command error code: 11
13:14:43 ERROR: File System and OS - target_image: command terminated with error
13:14:43 SUMMARY: File System and OS - target_image: Installation failed.
*** Please note that this reply is generated by LLM automatically ***
I see that you’re experiencing errors during the installation process on your Jetson Orin Nano. Unfortunately, you haven’t provided the specific error messages you’re encountering. However, I can try to help you troubleshoot based on common issues that others have faced.
From the context, I notice that there are several topics related to booting issues, camera problems, and installation errors on the Jetson Orin Nano. Here are a few potential causes and solutions:
Boot issues: Some users have reported booting problems, such as a black screen or fan stopping after boot. This could be due to a faulty installation or a hardware issue. Try re-flashing the device or checking the hardware connections.
Camera problems: There are several topics related to camera issues on the Jetson Orin Nano, such as CSI-0 with MIPI 4 lane not working properly or IMX219 not detected. Make sure that your camera sensor is properly connected and configured.
Installation errors: Some users have reported errors during the installation process, such as “flash.idx is not found” or “ERROR: might be timeout in USB write.” Try re-downloading the installation files or checking the USB connection.
To better assist you, could you please provide more details about the errors you’re experiencing, such as:
The exact error messages you’re seeing
The installation process you’re following (e.g., JetPack, SDKManager, etc.)
Any custom configurations or modifications you’ve made to the device
This information will help me provide a more specific and accurate solution to your problem.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
The exact errors were provided in the log output. It is trying to create some folders and getting permission errors. I’m guessing the installation script doesn’t have “sudo” in front of the commands, and unfortunately it deletes and tries to recreate them every time it runs.
Have you ever manually unpacked any of the flash content, or was it all entirely via JetPack/SDK Manager? If you manually unpacked something as root (using sudo) at the wrong time (part of manual install uses sudo, other parts do not), then this would cause incorrect permissions.
If the media you have mounted there is from a second filesystem, e.g., your home directory is on one disk and the content at a certain point which is failing is from a different disk, then it might be related to the second disk mount.
Also a VM might change what happens.
Some of the commands must use sudo to preserve certain filesystem attributes.
For reference, JetPack 6.2.1 corresponds to L4T R36.4.4.
While I still have not got this working on my development laptop, I located another Ubuntu machine that was just set up clean, it worked. It would still be good to figure out why it’s not working on my dev machine, there isn’t really anything unusual about it.
In the previous reply showing disks, where is the actual location you flash from? The only ext4 filesystem I see is for a snap install of firefox. However, the df -H -T does show ext4, so I guess it is more a question of what the home directory is on the host PC? I mention it because that (which names “~/nvidia/nvidia_sdk/...”) combined with this confuses me:
That should probably be ok since it is all running ext4, but it seems like an odd filesystem combination.
Was sdkmanager ever run as root/sudo? If so, then this would account for a permissions issue. If this isn’t it, then it is possible that any involvement of the snap shown in this is an issue, although I don’t see any indication that this was actually part of the flash (snap has its own security):
Docker is though very likely to be an issue. Docker is designed as a container and if the issue was not part of the other mentioned issues, then Docker was probably missing something needed to make access possible. I’m not really a Docker guy, but it would be easy for some configuration detail to block access to parts of the needed filesystem. Docker is a container and not really a VM, but they both have a lot in common, and VMs are almost always trouble.
I was running everything from my home directory. I have no idea why it’s so odd, this machine started with Ubuntu 18 or something like that and has been upgraded over the years.
Just to be clear, I wasn’t actually running any of this in Docker, I just mentioned it because I saw several references to Docker during the install.
In that case I don’t know why you had permission errors. Glad the other computer works, but if I had to use the one which failed, then I’d probably recursively delete the “~/nvidia/nvidia_sdk/JetPack...version../” which was for the release you used, and let it reinstall. This would let it set up permissions again. It is a bit perplexing as to what specific content it claimed issues with permissions on, and without that exact information I don’t think it can be answered.