On Monday 11 November 2002 22:06, Chris Carlen wrote:
Hi: [SuSE 8.1]
I use mkisofs and cdrecord in a little script to backup selected dirs in my home. I had it set up on 7.3 and it worked great. Now on 8.1 I am having terrible problems getting a checksum agreement using md5sum on the .iso vs. the disk.
I updated the cdrecord that came out of the box with the 1.11.a28-33 that I downloaded from Suse's updates for 8.1. (7.3 has cdrecord version 1.11.a06-6.) That got me some agreement on my test script, then when I run the main backup script, it fails.
I booted to SuSE 7.3 and ran the same script using the same disk (just to be sure it wasn't the disk) and the backup checksums agreed.
What the heck is wrong with cdrecord?
I would advise anybody burning CDs on 8.1 to try some md5sums, and behold. It is very strange, as you can fail to get a valid md5sum agreement, and you can still mount the disk and read files. But then you will go to get some file one day, and *that* one will give an IO error. Problems like this are what made me add the md5sum commands to my backup operation, in order to be sure after a burn that all data on the disk agreed with the image.
Here is my script:
#!/bin/bash echo We are in the full.CD-RW.backup.script! CDRW_SCSI_DEV=0,0,0 CDRW_DEV_PATH=/dev/cdrecorder mkisofs -o ~/cd-rw/full.backup.iso -R -J -v -graft-points \ -path-list ~/backup.scripts/full.backup.dir.list cdrecord dev=$CDRW_SCSI_DEV -v blank=fast speed=10 -dao ~/cd-rw/full.backup.iso echo \n md5sum ~/cd-rw/full.backup.iso md5sum $CDRW_DEV_PATH echo \n echo Press Enter or close when done... read REPLY exit
Good day Chris, I have only suggestions. Try without -dao. It shouldn't be needed when you burn an ISO. I do it that way, and it works fine for me. Have you tried to make a table of MD5 sums for all of the files in the directories, in stead of juste one for the ISO? That is what I do to see if the files on the mounted CD matches what was on the hard drive before I made the ISO that went on the CD. Best regards :o) Johnny :o)