I’ve downloaded the 32-bit, DVD version of openSUSE 11.2 4 times recently. First I tried the normal site twice, then a mirror, and finally bit torrent. Each time the MD5 checksum doesn’t match. It looks like it’s the same wrong checksum every time. So, in other words, I’m getting the same files, but the checksum on the file doesn’t match the one listed on the site.
Any advice? I’m getting tired of bogging down my internet connection for 5 hours.
BTW, the 64-bit version that I downloaded when 11.2 first came out matches.
Using wget to download went fine for me. Checksums match.
Are you by any chance on a system with a 4GB file size limit? What did you use to download? Please compare the file size of your downloaded file to the official numbers (4’497’694’720 Bytes).
I guess I wasn’t very detailed in my original post. I’m downloading via WinXP and using Firefox to do so (no download tool of any kind other than that built into Firefox). For the torrent, I used uTorrent.
I do not have a 4GB limit. The file size is shown as 4,497,694,720, which is the “official” size.
BTW, I have already gone through the download help, but I didn’t say I did. I also DID do a search, which is why I tried using bitTorrent. However, the other links you provided don’t include any other details of why an MD5 checksum may not match. If you read them, they just say that it is really important that you verify them. If they don’t match, download again. They do not say anything about possible reasons why they might not match.
I’m not sure what you are asking. I tried using the one you posted here, and it appears (without looking carefully) like the same one I found on the openSUSE site. I checked the file using this one, and it again, does not match.
BTW, I just tried using a metalink with the DownThemAll Firefox extension. It says, “The checksums of the download didn’t match. This means the download is corrupt or comprimised, unless the provided checksum was bad in the first place. Therefore it is recommended not to use the downloaded data.”
This was before it downloaded anything. That kind of makes me think that either there is something wrong with the checksum, or somehow the file on the server got corrupted. What do you guys think?
Yippee38 wrote:
> I guess I wasn’t very detailed in my original post.
you are correct, i have found it unwise to assume all suggested means
for success has been followed prior to a problem occurring…
it seems, however, you did everything right–except once downloaded
you need not bog down your connection for another 15 hours (5 hours
each, three more times)–instead, just point a torrent at the iso you
have and it will auto/self correct which ever bits are wrong…
> They do not say anything about possible reasons why
> they might not match.
there are numerous threads which discuss all kinds of reasons of why
the file size might be exactly the same and still the iso’s md5sum may
not match…i don’t them all…it ranges from faulty sectors on the
hard disk the iso is saved to; the type of file system the iso is
saved on; problems encountered in system RAM (it only takes one itty
bitty problem to completely mess up the md5); and others…i forget…
because there are apparently combinations of ISPs, user
hardware/software and user capability/procedures i do recall that more
than one person has been told it is probably best to purchase a disk
from any of a multitude of folks selling them on the net, for very
little…
finally, what md5sum are you getting and what system/program did you
use to calculate it?
Very strange. Bittorrent should be capable of correcting errors in the downloaded image and the download comes from peers, not the download server so there wouldn’t be a central point of failure.
What MD5 checking tool are you using and how are you using it? Have you tried a second tool like say md5deep and does it agree?
Yippee38 wrote:
> I checked the file using this one, and it again, does not match.
>
> BTW, I just tried using a metalink with the DownThemAll Firefox
> extension.
i have no idea what you speak of about firefox or “DownThemAll”
checking md5sum…and, i don’t read anything about that in the
references i gave you…i did read:
-“Microsoft Windows doesn’t include a program for calculating
checksums but a free md5sum/sha1sum checker for several operating
systems can be found at md5deep.sourceforge.net or you can use
QuickPar” (cite: download help)
-"One completely free, MS-Windows application for running the md5
checksum on a number of different operating systems, is here on sourceforge.net: md5deep
Another gui md5 checker for MS-Windows 95/98/NT (it works in Xp as
well even though it doesn’t say so). The file is md5.exe (248kB) and
can be downloaded from MD5 GUI for Windows. It’s under the gpl licence
and you can download the source if you want."
(cite: http://tinyurl.com/yhf65pv)
which of those programs did you use?
and what did it calculate?
The checksum I am getting is “CB28648F43520891DC7CF8C6E78FBADF”. The tool I am using is “MD5 Check Utility v2.31” from TSoft, which appears to be defunct.
I’ve burned several DVDs and was not able to get them to install. That’s why I started checking the MD5 checksums in the first place. I will try one of the “recommended” tools. I did try md5deep, and the documentation for it is lacking. I wasn’t able to get it to run, but I’m in a hurry (otw to work), so didn’t spend a whole lot of time on it.
<edit> I just tried another utility (again, not recommended) and got the same results.
My big concern is why is the checksum not matching on the file on the server? The metafile utility is checking the checksum BEFORE downloading it, and it doesn’t match. Why would that be the case?
Tell uTorrent to “verify” the files… And what are you using to verify the checksum? I’ve noticed that some apps don’t give the correct sum… even when it is the right sum.
Yippee38 wrote:
> The checksum I am getting is “CB28648F43520891DC7CF8C6E78FBADF”.
and, if you point a torrent at THAT file, does it begin downloading
packets? if so, it means it has found packets with errors and is
replacing them…it will do so until all packets are perfect at which
time you should be able to check the sum and smile…
if not, then you may need to buy a disk off the net (or begin checking
RAM, hard drives, etc)…several sellers of such are advertised many
different places on the net…
Just out of interest does the checksum your tools give you match any other image? It’s a very silly suggestion but could you be downloading the wrong image or the wrong version? No, the names wouldn’t match. Forget it.
What about other downloads? Have you tried downloading and checksumming a CD image to check if your downloader is working ok? You can install with the Live CD also, you don’t have to have the whole DVD.
If all else fails, buy a DVD from a duplicator. Or get a Linux clubmate to burn an image, if there’s a club nearby.
There’s a win32 port of the project. Download that and in the command line navigate to the wget binary. Then run wget <url> to download the image straight down.
The download process is similar to what firefox does; but with out all the unneeded web browsing stuff. You also have a dedicated process just to download the file while being able to close your web browser.
First I downloaded again via bitTorrent. Then I used “force re-check” several times with uTorrent (to verify the files) and it did not download anything additional. I’m getting the same checksum on the downloaded file. I then downloaded the network install via direct link and it worked fine. So it’s not my downloader.
I then downloaded the KDE Live install (64-bit) via uTorrent. Those codes matched.
I am having no trouble with any download EXCEPT the 32-bit DVD. Is there any chance somebody else could try downloading it to see if they’re getting a good checksum?