I downloaded ubuntu-12.04-desktop-amd64.iso from http://releases.ubuntu.com/precise/

This page also has a link to file showing the respective MD5 hashes for each file

The page shows

128f0c16f4734c420b0185a492d92e52 *ubuntu-12.04-desktop-amd64.iso

But when I checked my downloaded ISO using the md5sum program I get

57876b3740ee89e75c8fefc93a7ceee6 *ubuntu-12.04-desktop-amd64.iso

I also downloaded the ISO via BitTorrent using http://releases.ubuntu.com/precise/ubuntu-12.04-desktop-amd64.iso.torrent

This time using md5sum for this file shows the correct hash 128f0c16f4734c420b0185a492d92e52, but the ISO is 732MB, not 698MB as shown on the release page.

What could be happening here?


So, firstly, sorry for the confusion here. Fundamentally it came down to a communication glitch between the release team and our sysadmins.

Around release time, we push many of our images out to Amazon's CloudFront service to keep our bandwidth use under control. releases.ubuntu.com is managed directly by the release team, but the images on CloudFront are pushed by our sysadmins, and we have to push there well in advance to make sure everything's in place. The sysadmins pushed the most recent daily build at the time, but after that we had to respin images for some serious bugs, and we forgot to let the sysadmins know about this so that they could update CloudFront. As a result, you were getting out-of-date versions.

We've pushed updated images to CloudFront now, and all should be well, although I'm going to check things over manually just to make sure.

  • 2
    How does one know if a out-of-date image was used for installation? What would be the implications of installing a system from an outdated image? – user57929 Apr 28 '12 at 21:10
  • I think that if you download updates, you should be ok. – Pisu May 1 '12 at 21:27

Trust the md5 and not the size. My download matches your size and the md5 has from the site as well.

  • I agree that the md5 should be trusted - I don't know if it's possible for two different size files to have the same md5, but I think the odds are pretty low. – Marty Fried May 1 '12 at 19:53
  • No, two different size files can not have the same MD5... at least that is the theory. – cprofitt May 2 '12 at 1:21
  • Well, by "pretty low", I meant slightly less than minuscule. In theory, I believe it is possible; there's only 2^128 combinations, which is a fairly big number, but it is finite... in theory. :) – Marty Fried May 2 '12 at 1:35

I had the same thing happen with Ubuntu 12.04 and Lubuntu 12:04, both downloaded via Torrents.

First time it has ever happened to me. I had already decided to just delete the file and download again, but I had to step away from the computer for a while. When I came back, Transmission reported a corrupted section. I deleted, downloaded again, MD5SUM matched, installed. The weird thing is that it happened twice the same day, with different files. Perhaps there's something wrong with my network or something.


Your initial download was incomplete or corrupted. BitTorrent verifies the downloaded data to make sure it is correct, which you have verified with md5sum. The size difference is just the Megabyte vs. Mebibyte issue.

  • No, this was a genuine complete image, just an old one. My answer explains the true situation. Though you're right about MB/MiB. – Colin Watson Apr 26 '12 at 15:59
  • 1
    @ColinWatson, either way, there was still something wrong with the first download, and now it's right ;) – psusi Apr 26 '12 at 16:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.