Apt update: Some index files failed to download

System: Jetson Xavier NX, L4T 32.4.3
When I run sudo apt-get update, I get the following error:

Err:20 https://repo.download.nvidia.com/jetson/t194 r32.4/main arm64 Packages
  File has unexpected size (8924 != 15398). Mirror sync in progress? [IP: 95.100.155.115 443]
  Hashes of expected file:
   - Filesize:15398 [weak]
   - SHA256:eb62b57ca6b8ca1f555a517987b0fbfffff27d9c516c76dfe852f0a10050256b
   - SHA1:1d8e84f6a724779378e99039943fd63cb0a47e16 [weak]
   - MD5Sum:b26e12431a4d933c2a2b9d018d3b32f9 [weak]
  Release file created at: Wed, 08 Jul 2020 04:12:06 +0000
Fetched 2,562 B in 2s (1,095 B/s)                   
Reading package lists... Done
E: Failed to fetch https://repo.download.nvidia.com/jetson/t194/dists/r32.4/main/binary-arm64/Packages.gz  File has unexpected size (8924 != 15398). Mirror sync in progress? [IP: 95.100.155.115 443]
   Hashes of expected file:
    - Filesize:15398 [weak]
    - SHA256:eb62b57ca6b8ca1f555a517987b0fbfffff27d9c516c76dfe852f0a10050256b
    - SHA1:1d8e84f6a724779378e99039943fd63cb0a47e16 [weak]
    - MD5Sum:b26e12431a4d933c2a2b9d018d3b32f9 [weak]
   Release file created at: Wed, 08 Jul 2020 04:12:06 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.

Any ideas, what causes the problem?

Hi ronjag,

Your issue looks similar to

May I know your location(country) and when did you try apt-get update?

Hi,
I think I know, what caused the problem. I haven’t set the date and time correctly for my region.
But still, I have the problem, that the time is not updated automatically. And each time, I reboot, I have to set it again. Same discussion as here, but I couldn’t find a solution.

I haven’t set the date and time correctly for my region.

To those who are wondering why this causes a failure, see section under “replay attacks” here:

Apt does require your local time be accurate, or it’ll fail in order to to protect you from replay attacks.

Edit: this may or may not be the root cause in your case. The error is not the usual one for the above mentioned case, so it could be a connection/server hickup, and simply the retry that fixed it.

2 Likes