Why the need to reload media after burning?

Johnny Ljunggren · 08-21-2008, 11:43 AM

Hi

I've noticed that k3b (and others) need to reload the media to be able to verify the contents.

Could anyone give me a good explanation of why?

The reason I'm asking is that I'm writing an application that need to verify the contents but the application will run on an unattended machine with a locked door where the disc is supposed to come out. Crashing the disc into this door once a day will not be good for the motor I assume. Is there any way to come around this?

trickykid · 08-21-2008, 11:58 AM

Under Settings > Advanced, there's an option to not eject CD's after the burn.

Johnny Ljunggren · 08-22-2008, 12:11 AM

AFAIK that is only after the final burn, not before any verification.

I've done some tests with growisofs directly and when burning to DVD+R the media is unreadable if not reloaded. Even dd if=/dev/dvd.... will only be able to read the first block before bailing out.
Oddly enough burning DVD+RW seems to leave the media in a different state where verifying works directly.

pinniped · 08-22-2008, 12:43 AM

Perhaps the 'eject' is done just to generate a disk insertion event and get the drivers to re-read the disk. It may be a legacy problem which can now be overcome but which people don't feel particularly inclined to fix.