Hello. Usually attempting to write DVD-R bombs out, after writing can't fixate DVD+R. Increasing timeout helps with fixating, but following error just destroys media. Any stupid mistake on my part? # cdrecord(wodim) dev=1,0,0 -v -data *.iso Track 01: 0 of 2858 MB written.Errno: 5 (Input/output error), write_g1 scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0xFFFFFFFF [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 22.883s timeout 40s write track data: error after 0 bytes wodim: A write error occured. wodim: Please properly read the error message above. Writing time: 32.681s Average write speed 77.7x. Fixating... Fixating time: 22.473s wodim: fifo had 64 puts and 1 gets. wodim: fifo was 0 times empty and 0 times full, min fill was 100%. FreeBSD 8.1-STABLE #0 r213836 amd64 ahci, scbus, da, cd, pass compiled in kernel. best regards, - Jakub Lach -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p29978939.html Sent from the freebsd-stable mailing list archive at Nabble.com.
Forgot to mention device. cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 cd0: <HL-DT-ST DVDRAM GSA-U20N HX11> Removable CD-ROM SCSI-0 device cd0: 150.000MB/s transfers (SATA 1.x, UDMA6, ATAPI 12bytes, PIO 8192bytes) Previously it worked. -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p29978949.html Sent from the freebsd-stable mailing list archive at Nabble.com.
on 16/10/2010 17:26 Jakub Lach said the following:> > Hello. > > Usually attempting to write DVD-R bombs out, after writing can't fixate > DVD+R. > Increasing timeout helps with fixating, but following error just destroys > media. > > Any stupid mistake on my part?And you have hald running? -- Andriy Gapon
On Sat, 16 Oct 2010, Jakub Lach wrote:> > Usually attempting to write DVD-R bombs out, after writing can't fixate > DVD+R. > Increasing timeout helps with fixating, but following error just destroys > media. > > Any stupid mistake on my part? > > # cdrecord(wodim) dev=1,0,0 -v -data *.isoIsn't wodim a branch of the real cdrecord? I can't find it in ports.> Track 01: 0 of 2858 MB written.Errno: 5 (Input/output error), write_g1 > scsi sendcmd: retryable error > CDB: 2A 00 00 00 00 00 00 00 1F 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 00 00 > Sense Key: 0xFFFFFFFF [], Segment 0 > Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 > Sense flags: Blk 0 (not valid) > cmd finished after 22.883s timeout 40sI've had mixed success with cdrecord (sysutils/cdrtools-devel) over the years. Although growisofs is reputed to be less correct, I can't recall it ever having a problem. Oh, and I don't recall hal causing problems lately.
You wrote:># cdrecord(wodim) dev=1,0,0 -v -data *.iso>Track 01: 0 of 2858 MB written.Errno: 5 (Input/output error), write_g1 >scsi sendcmd: retryable error >CDB: 2A 00 00 00 00 00 00 00 1F 00 >status: 0x2 (CHECK CONDITION) >Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >00 00 00 00 00 00 00 00 00 00 00 >Sense Key: 0xFFFFFFFF [], Segment 0 >Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 >Sense flags: Blk 0 (not valid) >cmd finished after 22.883s timeout 40s>write track data: error after 0 bytes >wodim: A write error occured. >wodim: Please properly read the error message above. >Writing time: 32.681s >Average write speed 77.7x.wodim is a dead end from a 6 year old version of cdrecord with the DVD support ripped off and replaced by something broken. But there have been even more bugs added to wodim and it is not under "development" since May 2007. If cdrecord gives the same message, I encourage you to make a kernel bug report. This message is a hint to a serious kernel problem. A sense key value -1 cannot happen, so you need to find out why the SCSI command has not been transported correctly by the kernel. J?rg -- EMail:joerg@schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
Hi, your problem:>Track 01: 0 of 2858 MB written.cdrecord: Input/output error. write_g1: >scsi sendcmd: retryable error >CDB: 2A 00 00 00 00 00 00 00 20 00 >status: 0x2 (CHECK CONDITION) >Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >00 00 00 00 00 00 00 00 00 00 00 >Sense Key: 0xFFFFFFFF [], Segment 0 >Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 >Sense flags: Blk 0 (not valid)=20 >cmd finished after 23.946s timeout 200sis caused by a bug in a driver in the kernel. Status byte == 2 (Check Condition) together with empty sense data and unset sense key is impossible. Cdrecord can only behave in a useful way if SCSI error messages are correctly returned by the kernel. I recommend you to run "scgcheck" in order to find whether the driver yiu are using always behaves incorectly or whether this may be a result os a situation the autor of the driver did not expect. If you don't know how to run scgcheck, you may start with "scgcheck -auto". J?rg -- EMail:joerg@schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
>Ready to start test for failing command? Enter <CR> to continue: >**********> Testing for failed SCSI command. >scgcheck: Input/output error. inquiry: scsi sendcmd: retryable error >CDB: 12 00 00 FF 24 00 >status: 0x0 (GOOD STATUS) >cmd finished after 0.013s timeout 40s >----------> SCSI Transport return != SCG_NO_ERROR (1) >----------> SCSI status byte set to 0 (0x0) >----------> SCSI failed command test FAILEDYou seem to have a general problem with correct error reporting in SCSI with your kernel SCSI transport. Please try to contact the maintainer of this driver. J?rg -- EMail:joerg@schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) joerg.schilling@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
Joerg Schilling-3 wrote:> > You seem to have a general problem with correct error reporting in SCSI > with > your kernel SCSI transport. Please try to contact the maintainer of this > driver. >Thanks for support, I have pinged him already. ragards, - Jakub Lach -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p30086322.html Sent from the freebsd-stable mailing list archive at Nabble.com.