-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 29 October 2002 05:58 pm, Bret Hughes wrote: > I am trying to verify a copy of a purchased RHL 7.3 cd set. > > I burned the first cd and it appears to work (boots up ok anyway) but I > can't seem to verify the md5 sum and get a number I have any where > elase so I am assuming that there is a problem. If I try to verify the > origianl disk against the iso checksum from the redhat site I don't get > the same number either. > > what am I doing wrong?
I had a similar problem before replacing my burner. Using the old burner, I was never able to calculate the md5sum of any disk I had burned. With a new burner, I've had no problem at all. My understanding is that the old disk added run out sectors at the end of the track. Any attempt to calculate the md5sum would fail (eventually) with I/O errors. > the command I am running to calculate the md5sum is : > > dd if=/dev/cdrom bs=2048 count=329956 | md5sum Here is my iso file: [mfratoni@paradox dist-8.0]$ md5sum slinky-v0.3.3.iso 20997b8342c528f36f1791606ebfddbf slinky-v0.3.3.iso Here is the burned disk (unmounted) in /dev/cdrom: [mfratoni@paradox dist-8.0]$ md5sum /dev/cdrom 20997b8342c528f36f1791606ebfddbf /dev/cdrom Here is what you tried to do above: mfratoni@paradox dist-8.0]$ dd if=/dev/cdrom bs=2048 count=12656 | md5sum 12656+0 records in 12656+0 records out 20997b8342c528f36f1791606ebfddbf - One note, if you use xcdroast, turn off the 'pad data tracks' option. I have yet to find a way to make it stay off, and have to uncheck it each time I burn a disk. (Most of the time, I just use cdrecord from the command line, which defaults to no padding.) If you allow the track to be padded, the md5sum will not match the iso. > not sure where I got the count. I found the reference in the archives. [mfratoni@paradox dist-8.0]$ ll slinky-v0.3.3.iso - -rw-r--r-- 1 root root 25919488 Oct 27 16:58 slinky-v0.3.3.iso So, 25919488 / 2048 Gives us our count value of 12656 This method worked, even with my old burner. Another possibility is using 'readcd' though in my case, due to the extra runout sectors, I had to reduce the sector count by 15 to get a useful value. This is from a mail Michael Schwendt sent to help me with reading my badly burned disks: $ readcd 11 <RETURN> n <RETURN> disk.out <RETURN> <RETURN> <reduce total number of sectors by 15> <RETURN> <RETURN> You can then run md5sum on the disk.out file. Not exactly straight forward, but it does work. Hope something in there helps. ;) - -- - -Michael pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/ - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9v0ssn/07WoAb/SsRAozaAJ4lZ3ded2pHfNciAOIkea+OR+dn9ACgrxBr Jmnwxst9LXUNQpKv0PPQpQM= =hALC -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
