Thomas Schmitt wrote:
Hi,
chi kwan:
Cannot write dvd-r(w) but with dvd+rw is great
dvd-r(w) support of the drive/system is alright using CD/DVD creator comes
with Gnome
Possibly this uses growisofs as burn engine.
(To verify this: have a look with
ps -ef | grep growisofs
while a DVD burn is going on.)
CDB: 2A 00 00 00 00 00 00 00 10 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x30 Qual 0x05 (cannot write medium - incompatible format) Fru
Joerg Schilling:
It looks like your drive does not like the low quality media you are using.
I have sincere doubt that poor media quality
can cause a 5,30,05 error. It clearly belongs
to a family of complaints about media types
and media states:
5 30 00 INCOMPATIBLE MEDIUM INSTALLED
5 30 01 CANNOT READ MEDIUM UNKNOWN FORMAT
5 30 02 CANNOT READ MEDIUM INCOMPATIBLE FORMAT
5 30 03 CLEANING CARTRIDGE INSTALLED
5 30 04 CANNOT WRITE MEDIUM UNKNOWN FORMAT
5 30 05 CANNOT WRITE MEDIUM INCOMPATIBLE FORMAT
5 30 06 CANNOT FORMAT MEDIUM INCOMPATIBLE MEDIUM
5 30 07 CLEANING FAILURE
5 30 08 CANNOT WRITE APPLICATION CODE MISMATCH
5 30 09 CURRENT SESSION NOT FIXATED FOR APPEND
5 30 10 MEDIUM NOT FORMATTED
With poor media i would rather expect
3 73 03 POWER CALIBRATION AREA ERROR
or
3 0C 00 WRITE ERROR
I interpret "INCOMPATIBLE FORMAT" rather as
unsuitable state of the track that begins at
block address 0.
My theory would be strengthened if indeed
growisofs was the burn engine under the Gnome
program which can reliably burn the media.
I interpret this as the burner and media not getting along well,
sometimes showing up with cdrecord because it may in some cases use
different commands depending on the vendor quirks. I've seen similar
messages from certain burners when changing media brand.
It is *not* some general problem with CD-R or DVD-R, I use cdrecord with
then all the time because I burn for several old devices which really
dislike +R media.
Joerg Schilling:
It may be that this is a problem caused by "hald" or it's recent replacement (I
belive it is called "device-kit" or similar) disturbing the write process. You
may like to kill all related processes before tryng to write again.
I agree as long as you say "may be," because I've seen this on older
distributions which predate hal, which are on old software for one
reason or another (technical or political ;-) ).
This may also be caused by Gnome options about media, where an option is
selected to auto-mount certain types of media and the mounter needs to
check the device every so often and see if there is a media and what
kind it is, you can get a "seek zero, read" in the middle of a series of
writes, resulting in an attempt to write over an already-written sector.
Before anyone suggests that this is an OS error, the OS provides tools
by which applications can prevent this, if the applications fail to use
them than the fix lies in the application (and the user who chose the
application). One program is hal, as Joerg noted, but there are others.
--
Bill Davidsen <david...@tmr.com>
Unintended results are the well-earned reward for incompetence.