Mailinglist Archive: opensuse (3110 mails)

< Previous Next >
Re: [opensuse] Checksums, openSuSE downloads, md5sum
  • From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
  • Date: Thu, 1 Jan 2009 10:55:12 -0500
  • Message-id: <87f94c370901010755m58061253s366ba3c25b7e72b3@xxxxxxxxxxxxxx>
I find failing md5 tests often indicate hardware problems, so I would
also investigate hardware issues on you PC.

First I'd run memtest from the boot dvd first as an overnight test.


On Thu, Jan 1, 2009 at 10:28 AM, Verner Kjærsgaard <vk@xxxxxxxxxxxxx> wrote:

Carlos E. R. skrev:

Content-ID: <alpine.LSU.2.00.0901011237550.6052@xxxxxxxxxxxxxxxx>

On Thursday, 2009-01-01 at 11:21 +0100, Verner Kjærsgaard wrote:

Hi list,


Same to you :-)

- I'm puzzled by md5sums. I've downloaded openSuSE11 (both 32 and 64 bit
versions) and openSuSE11.1 (32/64 too).

- I get the same odd errors with 11 as with 11.1. This is my situation:

I try to verify the md5sum of openSuSE11(i386/32), it should be

ed6a5b3feb668866df812b1c2aed9d7f openSUSE-11.0-DVD-i386.iso

ed6a5b3feb668866df812b1c2aed9d7f openSUSE-11.0-DVD-i386.iso

Correct, yes.

but using "md5sum openSUSE-11.0-DVD-i386.iso", I get:

a38623810009842eeb1542a2052cfc2d openSUSE-11.0-DVD-i386.iso

This, of course, is wrong. If I do a

yep, wrong.

"md5sum -c openSUSE-11.0-DVD-i386.iso", I get 500+ lines saying the this
or that -rpm file could not be read, general i/o error or so"

Actually, it should be:

md5sum -c MD5SUMS

where "MD5SUMS" is the file containing the text line above, ie, the
checksums and filenames.

Now if I burn an ISO DVD, it verifies correctly when doing the "check
media" before installation (!).


I would report that as a bug.

Installation starts fine, but in some cases breaks later on, but not
always... I use K3B for burning, it reports a sound md5sum.

Well, it reports that it burned correctly the image you gave it, which we
know is bad.

I downloaded the isos from mirrors and directly from SuSE too. I
downloaded from two different locations, albeit to the same PC (my laptop).
I stored the received files (during download) onto the harddisk and also
onto a USB stick.

And all of them have the same (incorrect) checksum?

Same story. As you can tell, I've done quite a few downloads...All the
downloaded files yield the same md5sum (using md5sum without the -c flag),
never mind what media I store onto. And regardless of wherefrom and my
method of downloading.

The same incorrect checksum? All of them? Wow.

By the way, check the image before burning it. If it is incorrect,
don't bother burning.

As of now, I'm not really able to install openSuSE11(1) to anything, as I
can't seem to get this right.


The md5sums listed on the openSuSE web are (of course) correct

what's the correct and proper way of verifying the md5sums?

md5sum -c md5sumfilename

I used wget, firefox directly and a FF-extension called DownThenAll for
downloading. What would be your recommendation?

aria2c (metalink link), from here:

if you want the 11.0 version, or

if you want the new, 11.1 version. Use the comand line program "aria2c",
feeding it the "metalink" link address; for example:

aria2c --max-download-limit=85K --max-upload-limit=12K

you will have to download aria2c first, though.

Info on "metalink":


The reason is that this method should provide a corrected iso file. More
info here:


Another method, as you already have the image, with errors, is to repair
it. Here you have instructions:


-- Cheers,
Carlos E. R.

Thank You!

- so much knowledge and info, so little time :-)
- I'll get on to it right away, first I dig into aria2c. Oil keep you
posted, said the sheik!

Best regards,

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Greg Freemyer
Litigation Triage Solutions Specialist
First 99 Days Litigation White Paper -

The Norcross Group
The Intersection of Evidence & Technology
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups