Bugzilla – Bug 104035
Media Check fails....
Last modified: 2005-09-05 12:19:48 UTC
During the installation process, I go thru Media Check which is a recommended procedure to avoid installation problems. I start the check. After the check completes, I get a failure message. This is the output.... Identification: SuSE-Linux-CD-i386-10.0 Medium : CD1 Size : 717224 kB Expected MD5: 69add54bff98a2bbb010142764609b2b Result: Failed (MD5: <----not same as above----->) This happens for the OSS version too. However, I see no issues during the installation and the system comes up normally. I could get almost applications to run successfully. Verified with Andreas Jeager and found that he is also facing the same problem.
I cannot reproduce it. (Note: You can use checkmedia utility directly, it's used also by the yast module.) At first I verfied that the ISO image is OK: # checkmedia SUSE-10.0-CD-i386-Beta1-CD1.iso app: SuSE-Linux-CD-i386-10.0 media: CD1 size: 717224 kB md5: 69add54bff98a2bbb010142764609b2b check: 100% check: md5sum ok then I burned the image by k3b (I enabled medium verification after burning - it was OK) # checkmedia /dev/hdb app: SuSE-Linux-CD-i386-10.0 media: CD1 size: 717224 kB md5: 69add54bff98a2bbb010142764609b2b check: 100% check: md5sum ok I verified that in 3 different machines (with different CD drives, even a very old CD drive passed) and no problem have occured. Could you test whether the dowloaded image is correct? Did you enable verification during burning the image? It can also be hardware related.
Looks like the usual padding problem. You should see the kernel logging read errors. Running 'checkmedia' manually will probably show read errors as well.
Yes, wrong padding can also cause this problem. Did you use padding option? How did you burn the image?
Andreas, did you have the same problem?
Yes, had the same problem - but I then found the error messages reading the media, so this was a CD read problem.
I gave to IS&T folks locally here to burn it. I think they are using the Nero burner on windows to burn it. It doesn't have any padding option. Also, I checked with k3b. Where do I specify padding option here ? I will wait till Beta 2 to check this again and then close it.
K3b probably doesn't have padding option, I used the default settings. The only one option which I changed was verifying (I turned it on). And the checks (checkmedia and verification in k3b) were OK.
Please, test with Beta2
The problem will be gone in beta-3. Hopefully.
It is gone for me - if not, pleaes reopen.
Verified this in Beta4. This is working for me now.