[Debburn-devel] LG CH08LS10 not burning CDs
Thomas Schmitt
scdbackup at gmx.net
Sun Jan 3 10:31:34 UTC 2010
Hi,
> Although it is a DVD-RW, I get:
> Current: 0x001B (DVD+R)
Very strange.
The programs get this info from the drive.
(MMC command 46h GET CONFIGURATION.)
What does
dvd+rw-mediainfo /dev/sr0
tell about it ? (Tray must be already loaded.
It does not load by itself.)
> CDB: A1 01 00 00 00 00 00 00 00 00 00 00
That's MMC command A1h BLANK.
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 05 00 00 00 00 0A A1 00 00 0E 30 05 00 00
> Sense Key: 0x5 Illegal Request, Segment 0
> Sense Code: 0x30 Qual 0x05 (cannot write medium - incompatible format) Fru 0x0
Well, if the drive perceives it as DVD+R then
this complaint is only consequential.
Ok. If you can take this misperception as a
verified fact then the drive is simply mad.
A DVD-RW may appear as profile "DVD-ROM" but
never as "DVD+R". One can set a property named
"Book Type" on writeable DVD. But that should in
no way confuse the MMC Profile detection.
(A Profile is a set of capabilities. Typically
a media type corresponds to one or more
profiles. This depends on what the drive can
do with that media type or state. Some drives
switch to "DVD-ROM" as soon as the media is
closed and not writeable any more. DVD-ROM
drives show any DVD as "DVD-ROM".)
> cdrecord's (not wodim's) take on the disk in question is
> http://paste.debian.net/55489/
It says it was an appendable DVD+R with a track
of about 3 GB on it.
Quite a detailed misperception.
Double check the media type before telling the
dealer this story.
> richih at adamantium:~% time dd if=/dev/sr0 of=/dev/null bs=1M count=100
Whew. I feared i had sabotaged you via an
xterm attack by omitting the of= option.
> 104857600 bytes (105 MB) copied, 13.9257 s, 7.5 MB/s
Hrmpf. The bus speed suffices for at least 6x
(which probably is rather curbed by the drive's
read speed in the inner region of the DVD).
But growisofs shows clear signs of transport
choking. Strange.
> One funny thing I noticed is this:
> Average write speed 111.0x.
Well, that's what comes out if you send 62 kB
over a bus which can do >= 20 MB/s and the
write fails immediately afterwards.
Consolation:
Your burn did not have to suffer for long.
> wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
This can hardly be the cause for the drive
problems.
I have made several successful burns with wodim
despite this message.
More information about the Debburn-devel
mailing list