File System and OS : sudo: unable to execute ./ Permission denied

i have installed the SDKManager

The i follow the procedure starting from STEP1: i want to install the library in the host machine and i want to flash a Jetson TX2. I selected the JetPack 4.3 (and deselect de additional SDK DeepStream).
At the step 2 i leave selected all the target component checkbox, than i accept the terms and condition and go ahead to step 3. As download folder i selected a path on my Data hard drive (that have all permission).
Now a popup asking me to insert my root password appears. I Type the password and continue.
All the stuff start to download and the install but, during the creation of the Jetson OS image, at a certain moment, in the logs the error “File System and OS : sudo: unable to execute ./ Permission denied” appears and the procedure terminate.

Anyone know the reason? Can anybody help me?

I state that, some time ago, i successfully used the sdk to flash by jetson.

The hard drive/partition/directory you point at for the content must be file system type “ext4”. I am guessing that the location is formatted with a Windows style partition, e.g., NTFS or VFAT, or perhaps a FUSE type file system for a Live DVD. If you run the command “df -H -T /where/ever/it/is/at”, does the type show as ext4?


That worked.
Thanks you very much!

Was just caught out by this gotcha too, the SDK manager really needs to somehow check that the drive is EXT4

I agree, but technically you’ll find the requirement for an Ubuntu native install (modifications such as a VM or Windows’ newer Linux subsystem are not listed as supported). An actual Ubuntu native install will always use ext4 anyway (which is nit picking on my part).

There are actually multiple filesystems native to Linux which would do the job, and any of those would work, e.g., XFS or RieserFS or older ext2. Instead of testing for a particular filesystem type it would be nice if the install software tested for the ability to preserve sticky bits, suid bits, so on, but this would be a lot more complicated. My thought is that the most reasonable thing to do is test for ext4 in the “rootfs/” directory, and to have a pop-up warning which can be dismissed if not ext4.

I was running it on native bare metal linux! it’s just that I chose the download location to be on another drive which I share with windows, so it was ntfs, I actually totally forgot it was ntfs because I hardly ever use the windows partition! Anyway just some sort of indication, not even a test, just a little reminder would have saved me several hours of frustration :)

Welcome to the “long list” of people… :P