Fedora - InstallationThis forum is for the discussion of installation issues with Fedora.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Have just downloaded the Fedora Core 3 cd iso files - ran MD5SUM and they all pass.
I then burnt the first ISO file as an image to CD using K3b - it calculated the MD5SUM before burning and this was correct as before. Then on completion of the burn K3b checked and reported the checksum had failed (but does not tell you the value of the failing checksum). Fair enough coasters happen, but out of curiosity I tried booting the PC off the CD - it booted and proceeded to the media test, which when run passed!!!! Which makes me wonder what the media test does! I've since rebooted back to Mandrake 10 and run MD5SUM on /dev/cdrom, which produces a checksum that does not match the expected value - so I can but assume K3b correctly reported the CD checksum fails.
dunno, but I can tell that several people have noticed this - the md5sum of the iso does not match the md5sum of the burned disc, though nothing seems to be different or damaged...
so, my thoughts on this are that the burning process changes the md5sum (so the data is ok, but something in the whole process of burning data to disc creates or removes something that has nothing to do with data itself, so the md5sum is different) so it doesn't match. the other option is, that a lot of people can't get their isos burned well, though they seem to work which sounds a bit odd...
I'm not sure but I could imagine that the md5sum of the disc includes the burned data And something else (well, I'm not a pro on how a cd is actually, bit by bit, burned, but..) like something concerning the fs, so the final "output" is not exactly the same as the iso is. there is always the difference that iso resides in your HD but the data on a cd, which needs a filesystem too, and is a bit different than HD. I'm not sure but might have something to do with this fact...
so, if the media test passed, you should be ok even though the md5sums don't match.
Thank you for the advice. I'm still mystified. I've now used Nero to burn another CD from the original downloaded ISO image. This produces the same MD5SUM as the previously burnt CD. Which is at least consistent. A search on Google has shown this appears to be a recurring issue, see http://twiki.org/cgi-bin/view/Wikile...msAfterBurning
Which suggests the changes in MD5SUM results can be due to padding zeroes added by the writing software. Unfortunately the alternate ways of checking the CD suggested there do not produce pass results on my CD copies.
As for using mkisofs - I've had a go but the options used with it affect the resulting extracted iso file size and hence MD5sum - and none of them match the original downloaded ISO.
Note I've also used dd to extract the ISO and this also does not match up to the original downloaded file - but does match the MD5sum of the cd obtained with md5sum /dev/cdrom.
The only other thing I'm planning to do is try burning at a slow speed.
Victory - though not by a route I like, as it puts me firmly into windows for writing CD's (and CD writing is the one activity that is keeping windows going on my PC).
Further to my last post - I didn't write another CD, as I remembered I had Isobuster installed under windows. Which when I checked, can calculate the MD5sum that would result if an image were to be extracted from the burnt cd. Hey presto this MD5SUM matches the original downloaded MD5SUM.
So until I can find a simple way to calculate this properly under linux I'm going to avoid burning CD's under linux. It can't be that simple as I note Nero does not offer to verify a written image file (admittedly the version I'm using is old).
The easiest way to md5sum your media is through wxisting windows installation. Or if you already have linux installed, md5sum is part of the installation. )
If you are not willing to read (no hard feelings intended), then you can leave linux now and stick to windows.
The link I provided in the previous post explains, that you have to download md5sum.exe and copy it to a folder in the systems PATH variable. one of those is C:\WINDOWS\SYSTEM32
Then you can run it from the command line as the examples shown in the site demonstrate.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.