Verifying CD's
I typically check the md5sum when I download a .ISO, but I'm about to do an upgrade (Mandrake 9.0 to 10.1) and I want to verify the burns are actually good.
A quick check on google finds this thread: http://lists.debian.org/debian-user/.../msg00777.html I've seen the method before, so I tried it, and it errors out after read most of the cd. The md5 doesn't match, possibly for the reasons given in the thread. I then used readcd, which gives the following on two different disks (errors are similar for both cd's): Code:
[caysho@Petrata caysho]$ readcd dev=0,2,0 -f disk1 This got me suspicious - the drive reading the disks in both cases is the burner that created them. I checked a pressed CD (Mandrake 9.0) with readcd, and it was fine. The CDR media is TDK. I haven't done this with other media before. I'm nearly finished the TDK spindle, and I've got some Sony to use next. Am I missing something here ? Or am I just unlucky ? Should I just go through the md5sums of each file ? I don't know where Mandrake keeps these, if they are available. The disks appear to work. I once did a brief install of Mandrake 10.1 on a different machine, and it had a problem finding a file, then it was ok on the second try. I'm tempted to download it again to further verify. The cd with the mp3's work fine in my DVD player (a Sony). |
Done some more searching.
It appears the Sony burner doesn't conform to the SCSI/mmc command set correctly. It always happens during the lead out (I checked by burning 11MB, instead of nearly an entire disk's worth). Various links: http://lists.debian.org/cdwrite/2004/01/msg00328.html http://groups-beta.google.com/group/...3c5d6e3075ac6d http://groups-beta.google.com/group/...d13fcb2b86bff8 If anyone else can confirm my suspicions I'd be grateful. |
All times are GMT -5. The time now is 08:20 PM. |