I have enabled the option in k3b so that the disk is ejected directly after burning. This makes that the after-burning verification is done with a re-inserted disk. The verification still fails.
I found on the web two methods to calculate the checksum. Only method 1 gives the same value for the checksum as calculated from the .iso file. I'm wondering which method k3b is using ....
I have enabled the option in k3b so that the disk is ejected directly after burning. This makes that the after-burning verification is done with a re-inserted disk. The verification still fails.
I found on the web two methods to calculate the checksum. Only method 1 gives the same value for the checksum as calculated from the .iso file. I'm wondering which method k3b is using ....
method 1: dd if=$cd bs=$blocksize count=$blockcount conv=notrunc, noerror | md5sum
method 2: md5sum $cd
$cd is the device: example /dev/sr0
$blocksize and $blockcount are taken from the output of isoinfo