Bad md5sum on SUSE-9.3-Prof-i386-CD1.iso?
Mates, I have dlded SUSE-9.3-Prof-i386-CD1.iso from 2 different mirrors. Each time the checksum is the same, but does *not* match the published checksum. Is this a known problem? [david@bonza scripts]$ cat MD5SUMS 44959bbe1055f1c16bac1e2abcc2d270 SUSE-9.3-Prof-i386-CD1.iso ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 43f7c0f15e2f3abf2704986c01fdcf90 SUSE-9.3-Prof-i386-CD2.iso b41d051c8cc6d955f4755f039b19da03 SUSE-9.3-Prof-i386-CD3.iso 5519222959efb69184474c5934d33ec3 SUSE-9.3-Prof-i386-CD4.iso 488467804038d955a8f47735fa60aaff SUSE-9.3-Prof-i386-CD5.iso 04d2ebe4e0b8b00bc83cdc180a79e667 SUSE-9.3-Eval-DVD.iso [david@bonza scripts]$ md5sum SUSE-9.3-Prof-i386-CD1.iso 0e7ab1893c357ee0954e951c8cf7bdb1 SUSE-9.3-Prof-i386-CD1.iso ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -- David C. Rankin, J.D., P.E. RANKIN LAW FIRM, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com --
On Wednesday 06 July 2005 16:47, david rankin wrote:
I have dlded SUSE-9.3-Prof-i386-CD1.iso from 2 different mirrors. Each time the checksum is the same, but does *not* match the published checksum. Is this a known problem?
It is now ;)
[david@bonza scripts]$ cat MD5SUMS 44959bbe1055f1c16bac1e2abcc2d270 SUSE-9.3-Prof-i386-CD1.iso
Odd indeed. The one I downloaded yesterday has the same as yours:
[david@bonza scripts]$ md5sum SUSE-9.3-Prof-i386-CD1.iso 0e7ab1893c357ee0954e951c8cf7bdb1 SUSE-9.3-Prof-i386-CD1.iso
So, it needs someone from SuSE to determine whether it's the ISO or the MD5SUMS file which is wrong. -- Bill
William Gallafent wrote on Wednesday, July 06, 2005 10:55 AM On Wednesday 06 July 2005 16:47, david rankin wrote:
I have dlded SUSE-9.3-Prof-i386-CD1.iso from 2 different mirrors. Each time the checksum is the same, but does *not* match the published checksum. Is this a known problem?
It is now ;)
[david@bonza scripts]$ cat MD5SUMS 44959bbe1055f1c16bac1e2abcc2d270 SUSE-9.3-Prof-i386-CD1.iso
Odd indeed. The one I downloaded yesterday has the same as yours:
[david@bonza scripts]$ md5sum SUSE-9.3-Prof-i386-CD1.iso 0e7ab1893c357ee0954e951c8cf7bdb1 SUSE-9.3-Prof-i386-CD1.iso
So, it needs someone from SuSE to determine whether it's the ISO or the MD5SUMS file which is wrong.
-- Bill
Here is some additional information I found regarding the checksum issue. It is quoted from the forums.suselinuxsupport.de list: <quote> With regards to paul1974's problem with CD1 (of the 5cd set). IMHO I reckon you'd be ok downloading from any of the official mirrors. I haven't worked out yet why there are 2 different MD5 sums for disc1, but the 2nd MD5 signature showed up at about the same time as this 2.3gb DVD iso. Does your's match this: 0e7ab1893c357ee0954e951c8cf7bdb1 SUSE-9.3-Prof-i386-CD1.iso This above was the orginal MD5 offered on the mirrors before most changed to this: 44959bbe1055f1c16bac1e2abcc2d270 SUSE-9.3-Prof-i386-CD1.iso I've downloaded this disc a couple of times now and always (so far) had the 1st MD5 (0e7-etc....) Did and install and on my sons i386 rig and everythings working great. The only thing it did that I wasn't expecting was an automatic reboot after installing disc1, not sure if this is normall of not. Be interested to learn what MD5 your getting. </quote> -- David C. Rankin, J.D., P.E. --
At 12:25 PM 7/6/05, david rankin wrote:
William Gallafent wrote on Wednesday, July 06, 2005 10:55 AM On Wednesday 06 July 2005 16:47, david rankin wrote:
I have dlded SUSE-9.3-Prof-i386-CD1.iso from 2 different mirrors. Each time the checksum is the same, but does *not* match the published checksum. Is this a known problem?
It is now ;)
[david@bonza scripts]$ cat MD5SUMS 44959bbe1055f1c16bac1e2abcc2d270 SUSE-9.3-Prof-i386-CD1.iso
Odd indeed. The one I downloaded yesterday has the same as yours:
[david@bonza scripts]$ md5sum SUSE-9.3-Prof-i386-CD1.iso 0e7ab1893c357ee0954e951c8cf7bdb1 SUSE-9.3-Prof-i386-CD1.iso
So, it needs someone from SuSE to determine whether it's the ISO or the MD5SUMS file which is wrong.
-- Bill
Here is some additional information I found regarding the checksum issue. It is quoted from the forums.suselinuxsupport.de list:
<quote>
With regards to paul1974's problem with CD1 (of the 5cd set). IMHO I reckon you'd be ok downloading from any of the official mirrors. I haven't worked out yet why there are 2 different MD5 sums for disc1, but the 2nd MD5 signature showed up at about the same time as this 2.3gb DVD iso.
Does your's match this:
0e7ab1893c357ee0954e951c8cf7bdb1 SUSE-9.3-Prof-i386-CD1.iso
This above was the orginal MD5 offered on the mirrors before most changed to this:
44959bbe1055f1c16bac1e2abcc2d270 SUSE-9.3-Prof-i386-CD1.iso
I've downloaded this disc a couple of times now and always (so far) had the 1st MD5 (0e7-etc....)
Did and install and on my sons i386 rig and everythings working great. The only thing it did that I wasn't expecting was an automatic reboot after installing disc1, not sure if this is normall of not. Be interested to learn what MD5 your getting.
</quote>
I downloaded 9.3 on the weekend: $ ls -l total 3504148 -rw-r--r-- 1 fbax fbax 361 Jul 1 09:40 MD5SUMS -rw-r--r-- 1 fbax fbax 729452544 Jul 1 9:27 SUSE-9.3-Prof-i386-CD1.iso -rw-r--r-- 1 fbax fbax 708636672 Jun 27 12:10 SUSE-9.3-Prof-i386-CD2.iso -rw-r--r-- 1 fbax fbax 731060224 Jun 27 12:10 SUSE-9.3-Prof-i386-CD3.iso -rw-r--r-- 1 fbax fbax 701726720 Jun 27 12:10 SUSE-9.3-Prof-i386-CD4.iso -rw-r--r-- 1 fbax fbax 713834496 Jun 27 12:10 SUSE-9.3-Prof-i386-CD5.iso $ cat MD5SUMS 44959bbe1055f1c16bac1e2abcc2d270 SUSE-9.3-Prof-i386-CD1.iso 43f7c0f15e2f3abf2704986c01fdcf90 SUSE-9.3-Prof-i386-CD2.iso b41d051c8cc6d955f4755f039b19da03 SUSE-9.3-Prof-i386-CD3.iso 5519222959efb69184474c5934d33ec3 SUSE-9.3-Prof-i386-CD4.iso 488467804038d955a8f47735fa60aaff SUSE-9.3-Prof-i386-CD5.iso 04d2ebe4e0b8b00bc83cdc180a79e667 SUSE-9.3-Eval-DVD.iso $ md5sum SUSE-9.3-Prof-i386-CD1.iso 0e7ab1893c357ee0954e951c8cf7bdb1 SUSE-9.3-Prof-i386-CD1.iso Install also did a reboot after installing CD1. First ever SUSE install, so can't otherwise comment on differences. I downloaded from two mirrors and had the same md5 error with both.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2005-07-06 at 12:45 -0400, Frank Bax wrote:
Install also did a reboot after installing CD1. First ever SUSE install, so can't otherwise comment on differences.
I think that's normal, I have seen that on other versions. First it installs a minimal system from the 1st CD, boots from hard disk, and then continues the install, but with the system already running. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCzCL0tTMYHG2NR9URApGiAJ4gkb7rteQ9UsTmKcjeAgetcgD0owCfTu7P 8TGfY+8nsDU/LGJ/02zgTQM= =Na5F -----END PGP SIGNATURE-----
On 7/6/05, Carlos E. R.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Wednesday 2005-07-06 at 12:45 -0400, Frank Bax wrote:
Install also did a reboot after installing CD1. First ever SUSE install, so can't otherwise comment on differences.
I think that's normal, I have seen that on other versions. First it installs a minimal system from the 1st CD, boots from hard disk, and then continues the install, but with the system already running.
- -- Cheers, Carlos Robinson
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFCzCL0tTMYHG2NR9URApGiAJ4gkb7rteQ9UsTmKcjeAgetcgD0owCfTu7P 8TGfY+8nsDU/LGJ/02zgTQM= =Na5F -----END PGP SIGNATURE-----
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Yes, I can confirm that is the way that SUSE installs with the CDs.
david rankin wrote:
Mates,
I have dlded SUSE-9.3-Prof-i386-CD1.iso from 2 different mirrors. Each time the checksum is the same, but does *not* match the published checksum. Is this a known problem?
[david@bonza scripts]$ cat MD5SUMS 44959bbe1055f1c16bac1e2abcc2d270 SUSE-9.3-Prof-i386-CD1.iso ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 43f7c0f15e2f3abf2704986c01fdcf90 SUSE-9.3-Prof-i386-CD2.iso b41d051c8cc6d955f4755f039b19da03 SUSE-9.3-Prof-i386-CD3.iso 5519222959efb69184474c5934d33ec3 SUSE-9.3-Prof-i386-CD4.iso 488467804038d955a8f47735fa60aaff SUSE-9.3-Prof-i386-CD5.iso 04d2ebe4e0b8b00bc83cdc180a79e667 SUSE-9.3-Eval-DVD.iso
[david@bonza scripts]$ md5sum SUSE-9.3-Prof-i386-CD1.iso 0e7ab1893c357ee0954e951c8cf7bdb1 SUSE-9.3-Prof-i386-CD1.iso ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I got the CDs from USC last night, but didn't check the sums until this afternoon. CD1 gave the same md5sum as you report here. Assuming an ftp error, I downloaded the image file again, and the new file gave the same md5sum as stated in the sums file. However, this thread made me think the other, more likely, possibility. I just checked the records for both of these ftp connections (I still have those console sessions open) , and see the following: MD5SUMS was changed on July 1, but the CD1 image file remained at the June 27 version until after I completed my ftp session last night. Today, the image file has been updated, and shows a July 1 date. The file size has remained unchanged.
On 7/6/05, Darryl Gregorash wrote:
david rankin wrote:
Mates,
I have dlded SUSE-9.3-Prof-i386-CD1.iso from 2 different mirrors. Each time the checksum is the same, but does *not* match the published checksum. Is this a known problem?
[david@bonza scripts]$ cat MD5SUMS 44959bbe1055f1c16bac1e2abcc2d270 SUSE-9.3-Prof-i386-CD1.iso ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 43f7c0f15e2f3abf2704986c01fdcf90 SUSE-9.3-Prof-i386-CD2.iso b41d051c8cc6d955f4755f039b19da03 SUSE-9.3-Prof-i386-CD3.iso 5519222959efb69184474c5934d33ec3 SUSE-9.3-Prof-i386-CD4.iso 488467804038d955a8f47735fa60aaff SUSE-9.3-Prof-i386-CD5.iso 04d2ebe4e0b8b00bc83cdc180a79e667 SUSE-9.3-Eval-DVD.iso
[david@bonza scripts]$ md5sum SUSE-9.3-Prof-i386-CD1.iso 0e7ab1893c357ee0954e951c8cf7bdb1 SUSE-9.3-Prof-i386-CD1.iso ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I got the CDs from USC last night, but didn't check the sums until this afternoon. CD1 gave the same md5sum as you report here. Assuming an ftp error, I downloaded the image file again, and the new file gave the same md5sum as stated in the sums file. However, this thread made me think the other, more likely, possibility.
I just checked the records for both of these ftp connections (I still have those console sessions open) , and see the following:
MD5SUMS was changed on July 1, but the CD1 image file remained at the June 27 version until after I completed my ftp session last night. Today, the image file has been updated, and shows a July 1 date. The file size has remained unchanged.
Are you saying that the original CD1 on the ftp server was wrong? And that those of us that downloaded a copy should do so again? Thanks, Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century
Greg Freemyer wrote:
MD5SUMS was changed on July 1, but the CD1 image file remained at the
June 27 version until after I completed my ftp session last night. Today, the image file has been updated, and shows a July 1 date. The file size has remained unchanged.
Are you saying that the original CD1 on the ftp server was wrong?
How in **** should I know? I said it has changed, no more, and no less.
And that those of us that downloaded a copy should do so again?
Did you have any installation issues that you have been unable to resolve? Replies only to the list, please. I don't need a personal copy.
Greg Freemyer
Are you saying that the original CD1 on the ftp server was wrong?
No.
And that those of us that downloaded a copy should do so again?
No ;-) See my other email - we just made a small change: Offering md5sum calculation after download and that's all, no need to download again... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
"david rankin"
Mates,
I have dlded SUSE-9.3-Prof-i386-CD1.iso from 2 different mirrors. Each time the checksum is the same, but does *not* match the published checksum. Is this a known problem?
[david@bonza scripts]$ cat MD5SUMS 44959bbe1055f1c16bac1e2abcc2d270 SUSE-9.3-Prof-i386-CD1.iso ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 43f7c0f15e2f3abf2704986c01fdcf90 SUSE-9.3-Prof-i386-CD2.iso b41d051c8cc6d955f4755f039b19da03 SUSE-9.3-Prof-i386-CD3.iso 5519222959efb69184474c5934d33ec3 SUSE-9.3-Prof-i386-CD4.iso 488467804038d955a8f47735fa60aaff SUSE-9.3-Prof-i386-CD5.iso 04d2ebe4e0b8b00bc83cdc180a79e667 SUSE-9.3-Eval-DVD.iso
[david@bonza scripts]$ md5sum SUSE-9.3-Prof-i386-CD1.iso 0e7ab1893c357ee0954e951c8cf7bdb1 SUSE-9.3-Prof-i386-CD1.iso ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
We exchanged the CD1 on the 1st of July, and it seems that the MD5SUM has been updated but the CD not :-(. The only change between the CD isos is that the new one will offer automatically a MD5 checksum of the media - the older one not. Just use the CD you downloaded, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (8)
-
Andreas Jaeger -
Carlos E. R. -
Darryl Gregorash -
david rankin -
Frank Bax -
Greg Freemyer -
martin mcleod -
William Gallafent