Re: [newbie] Comparing md5sums in 10.0
Marek Pawinski wrote: I picked this up, i don't know if it pertains to the issue: Bad Md5sums? (maybe not) Just burned a CD from an ISO image and the md5sum doesn't match? The CD may be just fine... what you may be experiencing is padding which alters the md5sum. Before throwing away the CD and cursing, try this: cmp /dev/cdrom ISO_image For example, I got a bad md5sum from my 9.2beta1 CD1: $ dd if=/dev/cdrom | md5sum 1333216+0 records in 1333216+0 records out e82309091ad6b44a1218dc6f33c3b058 - It should be: 7a0479dc917d35bd822cecb558c8d432 So, I tried: $ cmp /dev/cdrom /ISO/Mandrake/MandrakeLinux-9.2beta1-CD1.i586.iso cmp: EOF on /ISO/Mandrake/MandrakeLinux-9.2beta1-CD1.i586.iso The EOF on the ISO image means that the CD image is an EXACT copy PLUS padding. An EOF on /mnt/cdrom would have meant the CD was incomplete. Just to prove the CD was really OK, I issued this piped string of commands: $ dd if=/dev/cdrom | head -c 682575872 | md5sum 1333162+0 records in 1333161+0 records out 7a0479dc917d35bd822cecb558c8d432 - Got the correct md5sum... :^) BTW, 682575872 is simply the length of that particular ISO image. So, more generically, we can use this pipe stream: dd if=/dev/cdrom | head -c `stat --format=%s ISO_image` | md5sum i.e., $ dd if=/dev/cdrom | head -c `stat --format=%s /ISO/Mandrake/MandrakeLinux-9.2beta1-CD1.i586.iso` | md5sum 1333162+0 records in 1333161+0 records out 7a0479dc917d35bd822cecb558c8d432 - For the purists, the size can be passed as an argument to dd like this (not verified): dd if=/dev/cdrom bs=`stat --format=%s ISO_image` | md5sum Marek Hi Marek, I've been giving your CL examples a try today, been a bit busy lately, anyway this is how it worked for me. cmp /dev/scd0 /mnt/Win-g/disc3.iso cmp: EOF on /mnt/Win-g/disc3.iso Now this result surprized me. I used cdrecord to create the installation CD I don't remember using any command that would of added padding to the burnt disc. I use -dao almost without exception, nothing else that adds Zero's etc between data tracks. But still this says I did. I just wondered why ? and what would it return if an exact copy ? then, dd if=/dev/scd0 | head -c 669016064 | md5sum 5ad870e696953f4bbd0a91936873890e - 1306673+0 records in 1306672+0 records out which agrees with, 5ad870e696953f4bbd0a91936873890e disc3.iso the correct md5sum I note you can pass the iso file size direct to head CL OK, so everything looks fine so far. Now for the problem, dd if=/dev/scd0 bs=`stat --format=%s /mnt/Win-g/disc3.iso` | md5sum 1+1 records in 1+1 records out 526cfebe2c2da7c6e464bed37969e4c9 - OK, I did something obvious wrong. but what ? By the way, NICE ! I like it. John Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
Miark wrote: On Tue, 26 Oct 2004 12:09:07 -0500, Tom wrote: Yes, but in newer Mandrake versions the CD drives are seen as dev=ATA:0,0,0 I use 0,0,0 for example only, 'cdrecord dev=ATA -scanbus' will return the actual numbers. The ATA device (burner) is linked to the numbers. EG, on my system dev=ATA:1,1,0 = /dev/hdd So 'md5sum /dev/hdd' returns the md5sum on the CD. BUT, it will not be correct unless you use the -dao option when burning the iso to CD. I burn on the CL using, 'cdrecord -v -eject driveropts=burnfree speed=16 dev=ATA:1,1,0 -dao name_of.iso' Hi Tom, At your suggestion, I tried using the following cdrecord command: cdrecord -v -dao dev=ATA:1,0,0 speed=8 gracetime=2 driveropts=burnfree but the md5sums of the ISO file and /dev/hdc were still different. Any other thoughts? Miark gracetime=# Set the grace time before starting to write to # seconds. Values below 2 seconds are not allowed. I bet that changes the md5sum ??? John Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
Adolfo Bello wrote: On Tue, 2004-10-26 at 10:18 +0100, John Richard Smith wrote: Then, making sure the CD you just burned isn't mounted: in terminal, dd if=/dev/scd0 bs=2048 count=n | md5sum - (note the - on the end, don't leave it off. change the /dev/scd0 to whatever device setting your drive is on your system. and where n is the number of sectors calculated above. All 3 md5sums should agree, ie, the published, your iso file, and the CD. If they don't agree you have either a duff write, or duff iso file. Hope this helps you, John `md5sum /dev/scd0` works fine here, no matter if the CD is mounted or not. Adolfo It can work, but not always, it depends upon how the CD was written in the first place. How the device is set up to be mounted. John Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Tue, 26 Oct 2004 10:18:17 +0100, John wrote: ls -l iso image file Divide the size of the ISO image file by 2048 to get the number of sectors, and record that sum (=n, hereafter) If it comes out to a decimal, do I round up? Then, making sure the CD you just burned isn't mounted: Why not? The following command works regardless. in terminal, dd if=/dev/scd0 bs=2048 count=n | md5sum - (note the - on the end, don't leave it off. It still comes out different. Although I think I forgot to double-check the sectors written by cdrecord. Perhaps my burner is starting to lose its mind. Miark Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
Miark wrote: On Tue, 26 Oct 2004 10:18:17 +0100, John wrote: ls -l iso image file Divide the size of the ISO image file by 2048 to get the number of sectors, and record that sum (=n, hereafter) If it comes out to a decimal, do I round up? It doesn't. The sectors in question are the number of sectors on the disc. So whatever amount of bytes on a disc it will always come out a whole sector number. The spiral of the lazer track begins on the inner circumference and winds itself out to the outer. That spiral is devided up into so many sectors. So byte 1 is in sector 1 , byte 2049 is in sector 2, etc At least that is how I understand it. I don't pretend to be an expert. in terminal, dd if=/dev/scd0 bs=2048 count=n | md5sum - (note the - on the end, don't leave it off. It still comes out different. Although I think I forgot to double-check the sectors written by cdrecord. Then I suspect you have a failed disc write. If you did the above right and it still gives a wrong md5sum something is wrong somewhere. At this stage I would begin to suspect media next. Maybe the choice of media/burner match is not a good one. It does happen. I have to say that I have never yet had such a problem, but I know others have. I cannot say whether that is more a problem of the user or the media. I tend to believe the user is more at fault than the media, but that could be my wrong assumption on my part and until I experience the same it is very difficult to arrive at a sound conclusion. The dye that is used on some media is not necessarily the best type of dye/media for your burner. The frequency of the lazers may vary, or the intensity of the lazer may not be adequate for safe reliable burns, who knows, I don't. But they are variables and could be a cause of concern. The situation is not made better by the device manufacturers who in my experience don't want to suggest any particular make/specification for their burners. Basically it's left to the user to resolve. So right now I'd double check what you have just done above, and if you are satisfied it is still not coming out right I think I would beg borrow or acquire some different makes of media to see if it makes any difference. John Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
John Richard Smith wrote: Miark wrote: On Tue, 26 Oct 2004 10:18:17 +0100, John wrote: ls -l iso image file Divide the size of the ISO image file by 2048 to get the number of sectors, and record that sum (=n, hereafter) If it comes out to a decimal, do I round up? It doesn't. The sectors in question are the number of sectors on the disc. So whatever amount of bytes on a disc it will always come out a whole sector number. The spiral of the lazer track begins on the inner circumference and winds itself out to the outer. That spiral is devided up into so many sectors. So byte 1 is in sector 1 , byte 2049 is in sector 2, etc At least that is how I understand it. I don't pretend to be an expert. in terminal, dd if=/dev/scd0 bs=2048 count=n | md5sum - (note the - on the end, don't leave it off. It still comes out different. Although I think I forgot to double-check the sectors written by cdrecord. Then I suspect you have a failed disc write. If you did the above right and it still gives a wrong md5sum something is wrong somewhere. At this stage I would begin to suspect media next. Maybe the choice of media/burner match is not a good one. It does happen. I have to say that I have never yet had such a problem, but I know others have. I cannot say whether that is more a problem of the user or the media. I tend to believe the user is more at fault than the media, but that could be my wrong assumption on my part and until I experience the same it is very difficult to arrive at a sound conclusion. The dye that is used on some media is not necessarily the best type of dye/media for your burner. The frequency of the lazers may vary, or the intensity of the lazer may not be adequate for safe reliable burns, who knows, I don't. But they are variables and could be a cause of concern. The situation is not made better by the device manufacturers who in my experience don't want to suggest any particular make/specification for their burners. Basically it's left to the user to resolve. So right now I'd double check what you have just done above, and if you are satisfied it is still not coming out right I think I would beg borrow or acquire some different makes of media to see if it makes any difference. John Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com I picked this up, i don't know if it pertains to the issue: Bad Md5sums? (maybe not) Just burned a CD from an ISO image and the md5sum doesn't match? The CD may be just fine... what you may be experiencing is padding which alters the md5sum. Before throwing away the CD and cursing, try this: cmp /dev/cdrom ISO_image For example, I got a bad md5sum from my 9.2beta1 CD1: $ dd if=/dev/cdrom | md5sum 1333216+0 records in 1333216+0 records out e82309091ad6b44a1218dc6f33c3b058 - It should be: 7a0479dc917d35bd822cecb558c8d432 So, I tried: $ cmp /dev/cdrom /ISO/Mandrake/MandrakeLinux-9.2beta1-CD1.i586.iso cmp: EOF on /ISO/Mandrake/MandrakeLinux-9.2beta1-CD1.i586.iso The EOF on the ISO image means that the CD image is an EXACT copy PLUS padding. An EOF on /mnt/cdrom would have meant the CD was incomplete. Just to prove the CD was really OK, I issued this piped string of commands: $ dd if=/dev/cdrom | head -c 682575872 | md5sum 1333162+0 records in 1333161+0 records out 7a0479dc917d35bd822cecb558c8d432 - Got the correct md5sum... :^) BTW, 682575872 is simply the length of that particular ISO image. So, more generically, we can use this pipe stream: dd if=/dev/cdrom | head -c `stat --format=%s ISO_image` | md5sum i.e., $ dd if=/dev/cdrom | head -c `stat --format=%s /ISO/Mandrake/MandrakeLinux-9.2beta1-CD1.i586.iso` | md5sum 1333162+0 records in 1333161+0 records out 7a0479dc917d35bd822cecb558c8d432 - For the purists, the size can be passed as an argument to dd like this (not verified): dd if=/dev/cdrom bs=`stat --format=%s ISO_image` | md5sum Marek Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
Marek Pawinski wrote: I picked this up, i don't know if it pertains to the issue: Bad Md5sums? (maybe not) Just burned a CD from an ISO image and the md5sum doesn't match? The CD may be just fine... what you may be experiencing is padding which alters the md5sum. Before throwing away the CD and cursing, try this: cmp /dev/cdrom ISO_image For example, I got a bad md5sum from my 9.2beta1 CD1: $ dd if=/dev/cdrom | md5sum 1333216+0 records in 1333216+0 records out e82309091ad6b44a1218dc6f33c3b058 - It should be: 7a0479dc917d35bd822cecb558c8d432 So, I tried: $ cmp /dev/cdrom /ISO/Mandrake/MandrakeLinux-9.2beta1-CD1.i586.iso cmp: EOF on /ISO/Mandrake/MandrakeLinux-9.2beta1-CD1.i586.iso The EOF on the ISO image means that the CD image is an EXACT copy PLUS padding. An EOF on /mnt/cdrom would have meant the CD was incomplete. Just to prove the CD was really OK, I issued this piped string of commands: $ dd if=/dev/cdrom | head -c 682575872 | md5sum 1333162+0 records in 1333161+0 records out 7a0479dc917d35bd822cecb558c8d432 - Got the correct md5sum... :^) BTW, 682575872 is simply the length of that particular ISO image. So, more generically, we can use this pipe stream: dd if=/dev/cdrom | head -c `stat --format=%s ISO_image` | md5sum i.e., $ dd if=/dev/cdrom | head -c `stat --format=%s /ISO/Mandrake/MandrakeLinux-9.2beta1-CD1.i586.iso` | md5sum 1333162+0 records in 1333161+0 records out 7a0479dc917d35bd822cecb558c8d432 - For the purists, the size can be passed as an argument to dd like this (not verified): dd if=/dev/cdrom bs=`stat --format=%s ISO_image` | md5sum Marek Marek, This is very interesting. I did not know of the cmp command. You have to be in the directory of the iso image I take it when you compare it to the bytes on the disc ? I'll have a go at this tomorrow. As you say it's padding that quite often corrupts the md5sums John Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
Miark wrote: What do you do to verify discs? Do you still have the iso file ? Yes. Miark OK, simple enough. First check iso image file md5sum, you probably know how to do this anyway,but, In a terminal, cd path to iso image file directory enter md5sum iso image file check the return against the published md5sum. then you need to know the iso image file size to the last byte. so, ls -l iso image file Divide the size of the ISO image file by 2048 to get the number of sectors, and record that sum (=n, hereafter) Then burn the iso image file contents to CD. I use cdrecord, I like the data output, and note, cdrecord will publish your sector count it should agree with the above sector calculation, watch the script carefully, it flashes by. Then, making sure the CD you just burned isn't mounted: in terminal, dd if=/dev/scd0 bs=2048 count=n | md5sum - (note the - on the end, don't leave it off. change the /dev/scd0 to whatever device setting your drive is on your system. and where n is the number of sectors calculated above. All 3 md5sums should agree, ie, the published, your iso file, and the CD. If they don't agree you have either a duff write, or duff iso file. Hope this helps you, John Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Tue, 2004-10-26 at 10:18 +0100, John Richard Smith wrote: Then, making sure the CD you just burned isn't mounted: in terminal, dd if=/dev/scd0 bs=2048 count=n | md5sum - (note the - on the end, don't leave it off. change the /dev/scd0 to whatever device setting your drive is on your system. and where n is the number of sectors calculated above. All 3 md5sums should agree, ie, the published, your iso file, and the CD. If they don't agree you have either a duff write, or duff iso file. Hope this helps you, John `md5sum /dev/scd0` works fine here, no matter if the CD is mounted or not. Adolfo Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
Miark wrote: This is exactly what used to work for me. The only difference I see is that with kernel 2.6 I'm no longer using scsi emulation. so I'm checking /dev/hdc instead of /dev/scd0. I wonder if that has anything to do with it. Miark Of course, the 2.6 kernels don't use scsi-emulation, so you device is /dev/hd(x) where (x) is your drive letter. But it will sometimes error, because , at least this is how I understand it, it depends upon how the data is written to disc. So sometimes using it will cause a perfectly good disc write error. The example I use ensures no wrong md5sums on perfectly good disc writes. John Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Tuesday 26 October 2004 04:56 am, Adolfo Bello wrote: On Tue, 2004-10-26 at 10:18 +0100, John Richard Smith wrote: Then, making sure the CD you just burned isn't mounted: in terminal, dd if=/dev/scd0 bs=2048 count=n | md5sum - (note the - on the end, don't leave it off. change the /dev/scd0 to whatever device setting your drive is on your system. and where n is the number of sectors calculated above. All 3 md5sums should agree, ie, the published, your iso file, and the CD. If they don't agree you have either a duff write, or duff iso file. Hope this helps you, John `md5sum /dev/scd0` works fine here, no matter if the CD is mounted or not. Adolfo Yes, but in newer Mandrake versions the CD drives are seen as dev=ATA:0,0,0 I use 0,0,0 for example only, 'cdrecord dev=ATA -scanbus' will return the actual numbers. The ATA device (burner) is linked to the numbers. EG, on my system dev=ATA:1,1,0 = /dev/hdd So 'md5sum /dev/hdd' returns the md5sum on the CD. BUT, it will not be correct unless you use the -dao option when burning the iso to CD. I burn on the CL using, 'cdrecord -v -eject driveropts=burnfree speed=16 dev=ATA:1,1,0 -dao name_of.iso' _Do_Not_ use options like -pad or -data. For speed I suggest 1/3 of the lesser capability, your burner or media speed. My Plextor is 52x, media is 52x, so I use speed=16 Actually I use an alias, alias biso='cdrecord -v -eject driveropts=burnfree speed=16 dev=ATA:1,1,0 -dao' So simply 'biso name_of.iso' does the job! ... and I always check the md5sum of the burned CD. As always, I disdain the use of GUI apps for burning any kind of CD's, but particularly for .iso images. Use the CL and you'll know exactly what is going on. Y'allsMMV ;) -- Tom Brinkman Corpus Christi, Texas Proud to be an American Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Tue, 26 Oct 2004 10:18:17 +0100, John wrote: OK, simple enough... Simple? I'll have to try this after work when I have a half-hour to kill ;-) Miark Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Tue, 26 Oct 2004 05:56:29 -0400, Adolfo wrote: On Tue, 2004-10-26 at 10:18 +0100, John Richard Smith wrote: Then, making sure the CD you just burned isn't mounted: in terminal, dd if=/dev/scd0 bs=2048 count=n | md5sum - (note the - on the end, don't leave it off. change the /dev/scd0 to whatever device setting your drive is on your system. and where n is the number of sectors calculated above. All 3 md5sums should agree, ie, the published, your iso file, and the CD. If they don't agree you have either a duff write, or duff iso file. `md5sum /dev/scd0` works fine here, no matter if the CD is mounted or not. This is exactly what used to work for me. The only difference I see is that with kernel 2.6 I'm no longer using scsi emulation. so I'm checking /dev/hdc instead of /dev/scd0. I wonder if that has anything to do with it. Miark Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Tue, 2004-10-26 at 12:09 -0500, Tom Brinkman wrote: On Tuesday 26 October 2004 04:56 am, Adolfo Bello wrote: On Tue, 2004-10-26 at 10:18 +0100, John Richard Smith wrote: Then, making sure the CD you just burned isn't mounted: in terminal, dd if=/dev/scd0 bs=2048 count=n | md5sum - (note the - on the end, don't leave it off. change the /dev/scd0 to whatever device setting your drive is on your system. and where n is the number of sectors calculated above. All 3 md5sums should agree, ie, the published, your iso file, and the CD. If they don't agree you have either a duff write, or duff iso file. Hope this helps you, John `md5sum /dev/scd0` works fine here, no matter if the CD is mounted or not. Adolfo Yes, but in newer Mandrake versions the CD drives are seen as dev=ATA:0,0,0 I use 0,0,0 for example only, 'cdrecord dev=ATA -scanbus' will return the actual numbers. The ATA device (burner) is linked to the numbers. EG, on my system dev=ATA:1,1,0 = /dev/hdd So 'md5sum /dev/hdd' returns the md5sum on the CD. BUT, it will not be correct unless you use the -dao option when burning the iso to CD. I burn on the CL using, 'cdrecord -v -eject driveropts=burnfree speed=16 dev=ATA:1,1,0 -dao name_of.iso' _Do_Not_ use options like -pad or -data. For speed I suggest 1/3 of the lesser capability, your burner or media speed. My Plextor is 52x, media is 52x, so I use speed=16 Actually I use an alias, alias biso='cdrecord -v -eject driveropts=burnfree speed=16 dev=ATA:1,1,0 -dao' So simply 'biso name_of.iso' does the job! ... and I always check the md5sum of the burned CD. As always, I disdain the use of GUI apps for burning any kind of CD's, but particularly for .iso images. Use the CL and you'll know exactly what is going on. Y'allsMMV ;) I always use CLI to burn my CDs too. cdrecord -v -eject speed=8 dev=1,0,0 -dao archivo.iso What is new to me is the use of dev=ATA:1,0,0. I'll try it in next burn. Using Mandrake 10 fully updated. Thanks, Adolfo Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
Adolfo Bello wrote: I always use CLI to burn my CDs too. cdrecord -v -eject speed=8 dev=1,0,0 -dao archivo.iso What is new to me is the use of dev=ATA:1,0,0. I'll try it in next burn. Using Mandrake 10 fully updated. Thanks, Adolfo dev=ATA:1,0,0 is only for the 2.6 kernels where the devices are set up as ATA devices. dev=1,0,0 is for most 2.4 kernels where the device is scsi-emulated. I use much the same cdrecord Cl as you. Whilst I'm not against the GUI front ends, when it comes to burning ISO's to disc I prefer the CL. For one thing you get a good script to see what is really going on.Otherwise when things go wrong you don't know why. John Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Tue, 2004-10-26 at 20:23 +0100, John Richard Smith wrote: dev=ATA:1,0,0 is only for the 2.6 kernels where the devices are set up as ATA devices. dev=1,0,0 is for most 2.4 kernels where the device is scsi-emulated. I use much the same cdrecord Cl as you. Whilst I'm not against the GUI front ends, when it comes to burning ISO's to disc I prefer the CL. For one thing you get a good script to see what is really going on.Otherwise when things go wrong you don't know why. John What calls my attention is that I've been using kernel 2.6.3 for about 8 months, and have burned tons of CDs with it without using the ATA thing. I suspect it has something to do with the fact that I use an external USB DVD/RW drive. BTW, nice trick your way of checking md5sums. Good to have it at hand. Adolfo Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Tue, 26 Oct 2004 12:09:07 -0500, Tom wrote: Yes, but in newer Mandrake versions the CD drives are seen as dev=ATA:0,0,0 I use 0,0,0 for example only, 'cdrecord dev=ATA -scanbus' will return the actual numbers. The ATA device (burner) is linked to the numbers. EG, on my system dev=ATA:1,1,0 = /dev/hdd So 'md5sum /dev/hdd' returns the md5sum on the CD. BUT, it will not be correct unless you use the -dao option when burning the iso to CD. I burn on the CL using, 'cdrecord -v -eject driveropts=burnfree speed=16 dev=ATA:1,1,0 -dao name_of.iso' Hi Tom, At your suggestion, I tried using the following cdrecord command: cdrecord -v -dao dev=ATA:1,0,0 speed=8 gracetime=2 driveropts=burnfree but the md5sums of the ISO file and /dev/hdc were still different. Any other thoughts? Miark Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Mon, 25 Oct 2004 12:07:32 -0400 Miark [EMAIL PROTECTED] wrote: When I burn a CD in MDK 10.0 from the commandline or with K3b, then compare the md5sums of the iso file and /dev/hdc, they are _always_ different, even if the CD works fine. Is there something weird with 10.0, or is this a subtle sign of burner problems to come, or what? Miark I'd rather say it's something with your cd burner. I'm using 10.0off and have no problems when comparing md5sums of iso and cd. -- Cezary 'Thereidos' Morga caesar(at)os.pl priv / thereidos(at)gmail.com Registered Linux User No. 362185 http://counter.li.org GG# 169903 ICQ# 328-700-565 Jabber: thereidos(at)ebox.pl Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
Miark wrote: When I burn a CD in MDK 10.0 from the commandline or with K3b, then compare the md5sums of the iso file and /dev/hdc, they are _always_ different, even if the CD works fine. Is there something weird with 10.0, or is this a subtle sign of burner problems to come, or what? Miark Not at all. When burn to disc, the md5sums include the lead in and lead out and so will inevitably result in different md5sums. The trick is to get it to md5sum the data on the disc only. John Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Monday 25 October 2004 11:54 am, John Richard Smith wrote: Miark wrote: When I burn a CD in MDK 10.0 from the commandline or with K3b, then compare the md5sums of the iso file and /dev/hdc, they are _always_ different, even if the CD works fine. Is there something weird with 10.0, or is this a subtle sign of burner problems to come, or what? Miark Not at all. When burn to disc, the md5sums include the lead in and lead out and so will inevitably result in different md5sums. The trick is to get it to md5sum the data on the disc only. John There is never a problem eith any of this when I use K3b however I did have to slow down my burn speed to 4X Marc Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
Marc wrote: On Monday 25 October 2004 11:54 am, John Richard Smith wrote: Miark wrote: When I burn a CD in MDK 10.0 from the commandline or with K3b, then compare the md5sums of the iso file and /dev/hdc, they are _always_ different, even if the CD works fine. Is there something weird with 10.0, or is this a subtle sign of burner problems to come, or what? Miark Not at all. When burn to disc, the md5sums include the lead in and lead out and so will inevitably result in different md5sums. The trick is to get it to md5sum the data on the disc only. John There is never a problem eith any of this when I use K3b however I did have to slow down my burn speed to 4X Marc How do you md5sum the disc ? John Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Mon, 25 Oct 2004 17:54:15 +0100, John wrote: When I burn a CD in MDK 10.0 from the commandline or with K3b, then compare the md5sums of the iso file and /dev/hdc, they are _always_ different, even if the CD works fine. Is there something weird with 10.0, or is this a subtle sign of burner problems to come, or what? When burn to disc, the md5sums include the lead in and lead out and so will inevitably result in different md5sums. The trick is to get it to md5sum the data on the disc only. I don't think that's the case for two reasons. First, I've always used this method before, and it's always worked. And second, even if I screwed it up from the commandline, I'm sure K3b would do it correctly when I select the Verify data option. But it always comes up wrong, too. One other thing I considered: crappy media. And make no mistake, I'm using Ritek--the crappiest, most god-awful media on planet. But when I burned to a RW this morning, I had the same problem (burning with K3b, with verification checked). What do you do to verify discs? Miark Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Mon, 25 Oct 2004 12:01:42 -0500, Marc wrote: On Monday 25 October 2004 11:54 am, John Richard Smith wrote: Miark wrote: When I burn a CD in MDK 10.0 from the commandline or with K3b, then compare the md5sums of the iso file and /dev/hdc, they are _always_ different, even if the CD works fine. Is there something weird with 10.0, or is this a subtle sign of burner problems to come, or what? There is never a problem eith any of this when I use K3b however I did have to slow down my burn speed to 4X I've been burning at 8x, but dropping to 4x is a good idea. I'll give that a shot. Miark Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Mon, 25 Oct 2004 18:26:35 +0200, Thereidos wrote: On Mon, 25 Oct 2004 12:07:32 -0400 Miark [EMAIL PROTECTED] wrote: When I burn a CD in MDK 10.0 from the commandline or with K3b, then compare the md5sums of the iso file and /dev/hdc, they are_always_ different, even if the CD works fine. Is there something weird with 10.0, or is this a subtle sign of burner problems to come, or what? Miark I'd rather say it's something with your cd burner. I'm using 10.0off and have no problems when comparing md5sums of iso and cd. What method(s) are you using to generate md5sums for the disc? Miark Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
Miark wrote: One other thing I considered: crappy media. And make no mistake, I'm using Ritek--the crappiest, most god-awful media on planet. But when I burned to a RW this morning, I had the same problem (burning with K3b, with verification checked). If your burner is modern, 8x is not particularly fast. I doubt it is the cause. What do you do to verify discs? Miark Do you still have the iso file ? John Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] Comparing md5sums in 10.0
On Mon, 25 Oct 2004 22:35:39 +0100, John wrote: Miark wrote: One other thing I considered: crappy media. And make no mistake, I'm using Ritek--the crappiest, most god-awful media on planet. But when I burned to a RW this morning, I had the same problem (burning with K3b, with verification checked). If your burner is modern, 8x is not particularly fast. I doubt it is the cause. What do you do to verify discs? Do you still have the iso file ? Yes. Miark Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
