[SOLVED] Input/output error when attempting to burn iso to dvd

entz · 02-09-2012, 09:20 AM

hello ,

i'm burning a cd with the following command:

Code:

growisofs -dvd-compat -Z /dev/dvd=ubuntu-11.04-desktop-amd64.iso

and i'm getting the following response ...

Quote:

Executing 'builtin_dd if=ubuntu-11.04-desktop-amd64.iso of=/dev/dvd obs=32k seek=0'
/dev/dvd: "Current Write Speed" is 8.2x1352KBps.
1572864/732112896 ( 0.2%) @0.0x, remaining 38:42 RBU 100.0% UBU 2.0%
1572864/732112896 ( 0.2%) @0.0x, remaining 61:55 RBU 100.0% UBU 100.0%
1572864/732112896 ( 0.2%) @0.0x, remaining 92:53 RBU 100.0% UBU 100.0%
1572864/732112896 ( 0.2%) @0.0x, remaining 116:06 RBU 100.0% UBU 100.0%
:-[ WRITE@LBA=300h failed with SK=4h/ASC=44h/ACQ=D9h]: Input/output error
:-( write failed: Input/output error
/dev/dvd: flushing cache
/dev/dvd: closing track
/dev/dvd: closing disc

i've tried brasero before on opensuse without any success

what's going on ?

btw the optical disk is DVD+R

need help

cheers

entz · 02-09-2012, 04:52 PM

hi again,

i've found the solution !!
it turned out that my drive was quite dirty , i used a piece of cotton(usually used for wiping out make-up) to clean the interior of the drive and a Qtip to clean the blue lense of the dvd drive .

btw i've a laptop drive so the cleaning process took 30 seconds .

now it works perfect , as if new !!

one final question , how can i get a consistency check such as a md5sum of the drive the geeky way (i.e using the cli)

regards

onebuck · 02-09-2012, 04:59 PM

Hi,

Look at CdromMd5sumsAfterBurning <- 'Describes some ways to check the validity of a burnt CD, either via the md5sum or via cmp (compare)';

Quote:

excerpt from CdromMd5sumsAfterBurning;
The md5sum of a "burnt" CD can be different than the md5sum of the associated iso file and not indicate an error.
The most widely recognized cause of the problem is the addition of padding bytes by some CD writing software.
I don't know if there are other possible causes, like possibly recording in disk-at-once mode? One suggestion that I haven't tried is to try burning in disk-at-once mode (Windows or Linux) to avoid the problem. Another is to use the -nopad option (Linux) — since I (so far) don't burn CDs in Linux, I haven't tried that either.
This page describes some ways to check the validity of a burnt CD, either via the md5sum or via cmp (compare), why sometimes that md5sum can be incorrect but the CD ok, ways to avoid that problem, and the best ways to check the md5sum of a burnt CD to avoid uncertainty.

HTH!

entz · 02-09-2012, 05:12 PM

Quote:

Originally Posted by onebuck

Hi,

Look at CdromMd5sumsAfterBurning <- 'Describes some ways to check the validity of a burnt CD, either via the md5sum or via cmp (compare)';

HTH!

thanks that was helpful !!

cheers