This issue shows up every once in a while, and the only remedy is to have repo admins fix it on the server side. Please advise if this is the case here.
This is happening on jetson nano orin 8gb dev edition, whilst trying to flash it with DP6.0 via the sdkmanager. I saw an error message in the terminal view, then logged in into the board and ran this -
# apt-get clean && apt-get update
<...>
Reading package lists... Done
E: Failed to fetch https://repo.download.nvidia.com/jetson/t234/dists/r36.2/main/binary-arm64/Packages.gz File has unexpected size (7202 != 11996). Mirror sync in progress? [IP: 23.62.46.152 443]
Hashes of expected file:
- Filesize:11996 [weak]
- SHA256:d7957f2c0c1606ef17954a7872b3df0488c216ba308360595d71719a4a9334de
- SHA1:356847f5167c8c123d9338696a84abdf00045457 [weak]
- MD5Sum:7272fce34f8beda71519dcd32664091d [weak]
Release file created at: Sat, 20 Jan 2024 07:00:47 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.
root@ubuntu:~# cat /etc/apt/sources.list.d/nvidia-l4t-apt-source.list
<...>
deb https://repo.download.nvidia.com/jetson/common r36.2 main
deb https://repo.download.nvidia.com/jetson/t234 r36.2 main
root@ubuntu:~#
Switching from repo.download.nvidia.com to repo.download.nvidia.cn works, however it does not feel to be secure to be using a communist version of cuda et al -
I flashed it twice with sdkmanager, and got the same error. Is there a cleaner way of flashing it?
This is reported in: <…>
Looks like the problem you linked to is due to lack of support for apt upgrade in DP6.0. The one I am dealing with blocks apt update from doing anything at all. There is a step in the sdkmanager’s workflow where it runs apt to fetch packages, and fails. My attempt to run apt update simply reproduces the same error.
Hi,
We will try to reproduce the issue. For information, when the message is printed, are you able to successfully flash the image and boot the system? Or it halts in flashing?
I’m facing the same issue. As usual it seems specific to some mirrors. AFAICT Nvidia uses Akamai’s CDN and the issue seems to be specific to some mirrors. You’re having issues with 23.62.46.152 and I’m having issues with 23.48.165.11 both of which are located in the UK. I suggest you switch to a different ip address like so: