Failed to fetch

[ric96]

apt-get update is giving me this:

Code: Select all

W: Failed to fetch http://archive.raspberrypi.org/debian/dists/wheezy/main/binary-armhf/Packages Hash Sum mismatch

I have tried most of the solutions provided in the forums but with no effect.
This is also happening on a fresh install so maybe something is not right on the other end?
although i can access the url on my browser

[ShiftPlusOne]

I can confirm that everything is okay on this end.

If you wget http://archive.raspberrypi.org/debian/d ... f/Packages and run md5sum on the file, what do you get?

[ric96]

I can confirm that everything is okay on this end.

If you wget http://archive.raspberrypi.org/debian/d ... f/Packages and run md5sum on the file, what do you get?

Code: Select all

pi@raspberrypi ~ $ md5sum Packages
0d3a0062c754cf52cdfc71da18cc8a31  Packages
pi@raspberrypi ~ $ 

[ShiftPlusOne]

Hmm... was fine when I checked a few minutes ago, now I am seeing a problem. I'll take a closer look.

[ShiftPlusOne]

Oh, derp.... second time I was looking at the Raspbian Release file and comparing it to the Raspberry Pi Packages file.

So no, everything is fine here.

You should see "0d3a0062c754cf52cdfc71da18cc8a31 596299 main/binary-armhf/Packages" in http://archive.raspberrypi.org/debian/d ... zy/Release

[ric96]

So, any suggestions, because i am facing this on a fresh install which is weird.

[plugwash]

I've seen issues like this reported before. The most plausible explanation I could come up with for some users experiancing hash sum mismatches on Packages files while most users reported things were fine was a forced proxy with incorrect cache behaviour.

Try installing apt-transport-https and changing the url in /etc/apt/sources.list.d/raspi.list to use https.

[ric96]

I've seen issues like this reported before. The most plausible explanation I could come up with for some users experiancing hash sum mismatches on Packages files while most users reported things were fine was a forced proxy with incorrect cache behaviour.

Try installing apt-transport-https and changing the url in /etc/apt/sources.list.d/raspi.list to use https.

Nope, nothing

[ric96]

Odd, the jessie repo loads well.
Still facing issues with wheezy repo tho

[ric96]

Bump
Anyone?

[DougieLawson]

Try again, Mr Plugwash has found a couple of bad mirrors and disabled them.

[fatima21]

The most plausible explanation I could come up with for some users experiancing hash sum mismatches on Packages files while most users reported things were fine was a forced proxy with incorrect cache behaviour.

[ric96]

Try again, Mr Plugwash has found a couple of bad mirrors and disabled them.

Have been trying all day now, fresh installs, old installs, noobs, berry boot. Nothing...

[ric96]

I also tried to change network by hooking up my phone and enabling usb tethering. Nothig

[plugwash]

Try again, Mr Plugwash has found a couple of bad mirrors and disabled them.

Please pay more attention dougie, this thread is about raspberrypi.org not raspbian.org.

[ric96]

Try again, Mr Plugwash has found a couple of bad mirrors and disabled them.

Please pay more attention dougie, this thread is about raspberrypi.org not raspbian.org.

Any mirrors i can try??
And also any ETA on jessie?

[ShiftPlusOne]

Try again, Mr Plugwash has found a couple of bad mirrors and disabled them.

Please pay more attention dougie, this thread is about raspberrypi.org not raspbian.org.

Any mirrors i can try??
And also any ETA on jessie?

Yeah, neither of those queries are related to raspbian.org.

Getting a jessie image out is up to us. Plugwash has had his repo ready for jessie for a long time.

[ric96]

...And it solved itself. Its problems like these that get on my nerves, you try hard to debug and troubleshoot and Poof! One fine morning it decides to solve itself...!!! I actually do hope that that someone from the inside did something to solve it.
Anyways, thnx for the help...!

[ShiftPlusOne]

There was an update pushed to the server, but the files on that server were fine. Maybe there was a hickup on the CDN which was resolved by prodding the server a little.

[ric96]

There was an update pushed to the server, but the files on that server were fine. Maybe there was a hickup on the CDN which was resolved by prodding the server a little.

guessed so, maybe the previous update, by-chance, had issue with cdn and new update is working normally.

[ric96]

again ... uugh..,
on raspbian as well as on raspbian-ua-net

[ric96]

Bump.
Anyone?
This is happening very frequently and its getting frustrating...