SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
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.
I've just downloaded SuSE 10.0 from this site: ww.opensuse.org/Released_Version (it seems I need at least five posts before posting a url, so add one more w) and burnt the images to five disks, then I inserted the first disk and rebooted. It started up the installation program okay, but when it got to the media check page and I went through the disks, it reported 'MD5SUM wrong' on all except disk 5.
So, rather than risking a faulty installation, I thought I'd come here.
I have an Intel Celeron processor and I downloaded the x86 ISOs.
Any thoughts? And what is MD5SUM, anyway?
edit: Sorry, originally I said it was 'MS5SUM'. Is it possible to change the thread heading?
md5sum is a checksum program that verifies the integrity of files. I am surprised that you had bad checksums on several disks.
Either you got corrupted downolads or your burner corrupted the data when burning the disks. Do you still have the .iso files? If so you should be able to download the checksum files (.md5) from the same place you grabbed the images. Put them in the same directory as the images. Then verify that the md5sums are accurate:
In linux- go to the terminal in that directory and type md5sum -c *.md5
It should tell you if the checksums are ok or not.
In windows, you will need to download a program to do the checksum. Quickpar can do it, there are probably a few others that can as well.
If the checksums are ok, then your burner must have corrupted the data. If they are not ok, then try downloading the iso's again.
I don't currently have a working version of Linux, so I will have to use Quickpar. Is this the program you are referring to? http://www.quickpar.org.uk/ If so, how do I use it? There are no checksum 'files' where I downloaded the ISOs, but there is a series of text for each downloadable file under the link 'MD5SUMS' http://ftp.opensuse.org/pub/opensuse...SS/iso/MD5SUMS.
I read somewhere that this has something to do with how your software "pads" the .iso when it burns it to disk. If you can, do the MD5SUM on the .iso images you downloaded. If the image MD5's are OK, chances are that you're good to go...
In my early newbie days, I went through this with Suse 9.3 telling me my downloaded CD's were no good. It had taken me days to download the .iso images, so unilke you, I went ahead blindly and installed anyway. Hey, it craps out, so what... nothing to lose and everything to win. Surprisingly, I achieved 100% success with two different machines and many "learning curve" installs . I finally ditched the CD's a couple of months ago when I migrated to Suse10.
Do the MD5sums on your downloaded .iso's, and if they're OK, I'd give the install a go. Just click "Next" when 'Install' asks if you want to verfiy the CD's.
I actually found md5summer right after posting last, and it verified that the ISOs are fine, so I tried burning them again, using different software and at a slower speed, and some of them still screwed up in the pre-install check. So far I have burned three verified disks, and eight 'faulty' disks, and they're all CD-Rs!
Good suggestion, tskears. Unfortunately I've (rather foolishly) thrown away all the 'faulty' disks, and I have none left. Tomorrow I'll pick up a pack of CD-RWs and try for the final two disks.
I'm tempted to think it's a problem with the pre-install disk check, since the md5sums turn out fine in md5summer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.