# md5sum /home/KNOPPIX_V6.0.1CD-2009-02-08-DE/KNOPPIX_V6.0.1CD-2009-02-08-DE.iso.md5
22b394f2fd4c54987a6ac3cbef3db0c4 /home/KNOPPIX_V6.0.1CD-2009-02-08-DE/KNOPPIX_V6.0.1CD-2009-02-08-DE.iso.md5

And the file KNOPPIX_V6.0.1CD-2009-02-08-DE.iso.md5 contains
41b318b4476476a4e17a7020fff4e5cc *KNOPPIX_V6.0.1CD-2009-02-08-DE.iso

Is this corrupted or not ? If not why , coz i feel its corrupted

Obviously it is corrupt (they should be same)

vibinlakshman:

Q-"Is this corrupted or not ? If not why , coz i feel its corrupted"

Comment:

Checksums are simple arithmetical values intended to quickly compare equality between two files. If part of the given value is not congruent to the one generated from your second file (copy) they are indeed unequal and therefore, as a matter of course, in order to avoid problem, another copy should be obtained one that can return digitally equal value to the original.

Hope this helps.

Hi,
If the data that you present in your post is correct then why are you checking the md5sum on the '/home/KNOPPIX_V6.0.1CD-2009-02-08-DE/KNOPPIX_V6.0.1CD-2009-02-08-DE.iso.md5' which is text file that contains the sum for the iso. This file is used to do a md5sum on the iso that you want/downloaded. No need to check the text file for hash. Read 'man md5sum'.

Oops i didnt get that .. So can i shoot a doubt plz ..
From my knowledge md5sum means both the values in the file and what i got while performing md5sum with the iso should be equal
But i need to know in any circumstances whether it cant be equal .?

But how did it give different values , i'm confused ?

from you output provided you should use md5sum in this fashion after cd to the directory that contains the knoppix ISO you downloaded:
man md5sum should indicate the flag to tell md5sum to check the files against the sum(s) in the .md5; that is where i got the -c switch;

Will it take too long ..? Coz i'm facing long time after this command is executed

yes, it generates an md5sum hash of the ISO to compare with the one recorded in the .md5 file.
it really is size dependent, the larger the iso the longer to calculate the sum to compare with the one in the .md5 file

Hi,

The difference in the sum will indicate that your download was indeed corrupted so a new download would be necessary. You could even download from a different mirror to get the file.

Time of the md5sum check will depend on your system. When you do a md5sum on the file you are computing the check on a byte level. So the time will be dependent on the size of the file and the power of your system. Patience!

I would check the md5sum. If you downloaded the cd/dvd iso then be sure to check the md5sum for the original iso. From the cli;

If the iso md5 is OK then you should try 'CdromMd5sumsAfterBurning''.

This way you will know if the burn was OK! You might need to change your burn speed to a lower value.

This will check the download iso with the known md5sum that you also get with the iso.