Re: First case, check if wodim reliably spoils the optical media
Hi,
> Executing 'reserve track' command on Bus 2 Target 0, Lun 0 timeout 40s
> CDB: 53 00 00 00 00 00 0C 65 40 00
> Errno: 5 (Input/output error), reserve track scsi sendcmd: retryable error
> CDB: 53 00 00 00 00 00 0C 65 40 00
> status: 0x0 (GOOD STATUS)
> cmd finished after 43.701s timeout 40s
This looks like a timeout. The kernel was told to become impatient
after 40 seconds. It did after 43.7 seconds.
Maybe the 40 seconds are just not long enough for your drive to get
the track reservation done.
There is a wodim option to set this timeout threshhold.
>From man wodim:
timeout=#
Set the default SCSI command timeout value to # seconds. The
default SCSI command timeout is the minimum timeout used for
sending SCSI commands. If a SCSI command fails due to a time-
out, you may try to raise the default SCSI command timeout above
the timeout value of the failed command. If the command runs
correctly with a raised command timeout, please report the bet-
ter timeout value and the corresponding command to the author of
the program. If no timeout option is present, a default timeout
of 40 seconds is used.
I see the same text in man cdrecord. So Joerg Schilling might be
interested in learning a better value ... if there is any.
---------------------------------------------------------------------------
So repeat the wodim experiment with additional option
timeout=200
I am really curious of a run of cdrskin with option -dao and no
-multi on the problematic drive. libburn timeout is 200 seconds.
(No option timeout= in cdrskin. Maybe it is now time to introduce it ?)
Probably no RESERVE TRACK command was issued in the previous successful
cdrskin run. With -dao there surely will be one. -dao will not work
together with -multi.
The message output of a successful 1500 MB write run with option -V is
quite large and obscures the normal messages. Nevertheless it would
be interesting if wodim or cdrskin fails.
Have a nice day :)
Thomas
Reply to: