Jetpack 3.3 installation error (tar: write error)

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

I have a problem to install Jetpack 3.3 on TX2 board.

This is the log data

Creating symlinks for weston, wayland-demos, libinput and wayland-ivi-extention modules
Adding symlinks for NVIDIA systemd services
Copying USB device mode filesystem image to /home/dhong/Downloads/64_TX2/Linux_for_Tegra/rootfs
Disabling NetworkManager-wait-online.service
Disable the ondemand service by changing the runlevels to ‘K’
Extracting the firmwares and kernel modules to /home/dhong/Downloads/64_TX2/Linux_for_Tegra/rootfs
Extracting the kernel headers to /home/dhong/Downloads/64_TX2/Linux_for_Tegra/rootfs/usr/src
tar: write error
Adding symlink /home/dhong/Downloads/64_TX2/Linux_for_Tegra/rootfs/lib/modules/4.4.38-tegra/build → /usr/sr$
Installing Image into /boot in target rootfs
Installing the board *.dtb files into /boot in target rootfs
Success!

After writing the data in TX board, I couldn’t find any drivers and utilities.
Do anyone know how to solve “tar: write error”?

I used Ubuntu 16.04 (native, not VM).
The host has enough disk space.

2

Hi dhong,

Could you description more detail about your steps?
After completed JetPack install, what’s drivers and utilities you don’t find?

Thanks!

3

From “/home/dhong/Downloads/64_TX2/Linux_for_Tegra/rootfs/”, what is the output of:

df -H -T .

(the “.” is important)

It sure looks like you ran out of space long before everything was ready. You probably need 35GB to 40GB of free space at minimum.

4

The installation steps are same as what in the guide. After installation and flashing, TX2 doesn’t have most of packages such as opencv, visionworks, monitor utility and etc.
When the installation software was running, I saw some 404 (not found) too.

Filesystem Type Size Used Avail Use% Mounted on
/dev/sda1 ext4 251G 22G 217G 10% /

I think the host has enough space. 217GB
The host system is 16.04.5 version. I will try downgrade to 16.04 early version.
If you have any idea, let me know. Thanks,

5

The 16.04.5 version shouldn’t matter (you will probably do work you don’t need to do if you downgrade).

Keep in mind that you can flash separately from any package install. JetPack can have flash unchecked and extra packages added at a later date (but you’d need to manually tell JetPack what the IP address is).

Are you able to run JetPack again, without flash, and install packages?

Flash uses only the micro-B USB cable in recovery mode. Packages are added via wired ethernet and do not use the USB cable, nor recovery mode. Sometimes it is as simple as ssh wanting the user to confirm the connection is trusted (try an ordinary command line ssh to the Jetson). Sometimes it is a proxy or firewall or router config issue.

6

Flash is ok. The problem is Target installation.
Host installation doesn’t make any issue.

I reinstalled ubuntu and ran jetpack again but it still didn’t work.

Tar write error during target installation and it skips rest of the procedure.
If tar: write error is solved, the installation will work.

7

Host install is because the host might be used for training or debugging. Samples are cross compiled on host before copy to Jetson, so host needs some of the tools if installing samples to Jetson.

You might try completely removing everything in the host’s JetPack directory and downloading it and starting again. Sometimes older or different versions in the same directory cause problems, and even the same version, it something got truncated, might not ever work. I have no other suggestions.

8

linuxdev, you’re right.
I understand the installation procedure.

tar: write error is for source file. it doesn’t affect the system.
Support packages are installing on TX2 by SSH now.

FYI, flash is two steps. One is bootloader and file system. The other is support package, cuda, opencv, visionwork, tensorRT and etc. The first one is transferred by USB and the second is by network(eth). That’s why jetpack asked ip address. If the second step fails at first time, deselect Flash OS image and run again.

Thanks for helping.