Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Dave Platt [EMAIL PROTECTED] wrote: The problem is that they have called wodim cdrecord and provided (or in some cases not) different functionality. Obviously distributions thought people wouldn't use it if people knew it was another program. I feel the same way as I do when I order coke and get pepsi, it's a scam. I can't speak for the people who put together the distributions, but I'm not at all convinced about the Obviously. I suspect that the larger motivation was Don't break existing scripts, don't break existing GUI front-end applications. They definitely broke existing GUI as the original cdrecord works while wodim does not work in many cases. The Authors from k3b even started to look for the original cdrecord to be able to use this instead of the plagiat. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Joerg Schilling wrote: Dave Platt [EMAIL PROTECTED] wrote: The problem is that they have called wodim cdrecord and provided (or in some cases not) different functionality. Obviously distributions thought people wouldn't use it if people knew it was another program. I feel the same way as I do when I order coke and get pepsi, it's a scam. I can't speak for the people who put together the distributions, but I'm not at all convinced about the Obviously. I suspect that the larger motivation was Don't break existing scripts, don't break existing GUI front-end applications. They definitely broke existing GUI as the original cdrecord works while wodim does not work in many cases. I can't say many cases, but there are some burners which work better (ie produce useful burns) with cdrecord from Joerg. That said, in most cases wodim will work with good media and hardware. The Authors from k3b even started to look for the original cdrecord to be able to use this instead of the plagiat. Fewer complaints to them, I would think. -- Bill Davidsen [EMAIL PROTECTED] Woe unto the statesman who makes war without a reason that will still be valid when the war is over... Otto von Bismark
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Thomas Schmitt wrote: Hi, Andy Polyakov wrote: Could you explain why writing a new program should help to fix the hostile habbit of some Linux kernel developers? I see this as a more complex system of animosity. To exchange one component might change that system completely. But for now, the official Linux world rather settled with wodim. So the quarrel ended anyway. The problem is that they have called wodim cdrecord and provided (or in some cases not) different functionality. Obviously distributions thought people wouldn't use it if people knew it was another program. I feel the same way as I do when I order coke and get pepsi, it's a scam. -- Bill Davidsen [EMAIL PROTECTED] Woe unto the statesman who makes war without a reason that will still be valid when the war is over... Otto von Bismark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
The problem is that they have called wodim cdrecord and provided (or in some cases not) different functionality. Obviously distributions thought people wouldn't use it if people knew it was another program. I feel the same way as I do when I order coke and get pepsi, it's a scam. I can't speak for the people who put together the distributions, but I'm not at all convinced about the Obviously. I suspect that the larger motivation was Don't break existing scripts, don't break existing GUI front-end applications. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
mkisofs $OPTS -V $1 $2|cdrecord driveropts=layerbreak=2086912 $COMCD 2086912 blocks = 4076 MiB Track 01: 4075 of 8124 MB written (fifo 99%) [buf 99%] 8.2x.cdrecord: faio_wait_on_buffer for writer timed out. cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 1F D7 E9 00 00 1F 00 write track data: error after 4273948672 bytes The 1F in CDB means 31 blocks are to be written by this WRITE10 command. The 1F D7 E9 means write address is 2086889. (Confirmed by: 4273948672 / 2048 == 2086889) The write size of 31 blocks seems systematic: 2086889 % 31 == 0 The man page of cdrecord says: The manual layer break value needs to be a mul- tiple of the ECC sector size which is 16 logical 2048 byte sectors in case of DVD 2086912 - 2086889 == 23 The failing write command is 31 blocks long and thus touches both layers. Couldn't agree more. The unit in question obviously crashes (power cycle is required to bring it back, i.e. reboot of unit) if write request crosses layer break position. What I'd like to see is dvd+rw-mediainfo output for growisofs recording that failed at 98%. It should be noted that growisofs reserves for possibility of resuming DVD+R DL recording. If file set (or preformatted image) is not changed in any way, then in most cases it would be possible to re-run the exact command and complete recording. I'd also like to see output from beginning of failed growisofs recording... As always... Rob and CJ: what are your magic layer break values which made cdrecord work on DVD+R DL ? As far as I understood the default value reported by unit, the one that would be used if application didn't set layer break position. It sounds as if their units can't handle arbitrary layer break positions and has to be reminded about what it said itself. I don't think it's related... A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Thomas Schmitt [EMAIL PROTECTED] wrote: The 1F in CDB means 31 blocks are to be written by this WRITE10 command. The 1F D7 E9 means write address is 2086889. (Confirmed by: 4273948672 / 2048 == 2086889) The write size of 31 blocks seems systematic: 2086889 % 31 == 0 The man page of cdrecord says: The manual layer break value needs to be a mul- tiple of the ECC sector size which is 16 logical 2048 byte sectors in case of DVD 2086912 - 2086889 == 23 The failing write command is 31 blocks long and thus touches both layers. It may be that this has been forgotten in cdrecord's code (it was planned ;-) if it works with other drives, then other drives do not follow the worst possible firmware documented by the MMC standard. Looks like cdrecord needs some additional code to verify that a write command does not cross a layer boundary. BTW: this is not easy to implement in a clean way! Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hi, Andy Polyakov wrote: The unit in question [Gregoire's] obviously crashes (power cycle is required to bring it back, i.e. reboot of unit) if write request crosses layer break position. It sounds as if their [Rob's and CJ's] units can't handle arbitrary layer break positions and has to be reminded i wrote: 2086912 - 2086889 == 23 The failing write command [of cdrecord with Gregoire's drive] is 31 blocks long and thus touches both layers. Joerg Schilling wrote: It may be that this has been forgotten in cdrecord's code (it was planned ;-) if it works with other drives, then other drives do not follow the worst possible firmware documented by the MMC standard. So the current consolidated theory would be about like this: - Problem number 1: Rob and CJ have drives which do not like any other layer break address than the one which is their default. Thus growisofs and cdrecord fail if their automatically computed layer breaks get set. The remedy is to enforce the drive's default layer break address and override the programs' computations. (This would mean that cdrskin has no problem with those drives. I would appreciate confirmation.) - Problem number 2: Gregoire's drive does not like if cdrecord's 31-block aligned write command touches both layers together by a single write command. It seems not to have a general layer break setting problem, because growisofs with its automatic layer break and its 16-block aligned write commands only fails much after the layer break. (One could verify this therory by aligning the manual layer break to a multiple of 496.) - Problem number 3: Gregoire's drive has a yet obsure problem with drive-media compatibility which shows up with growisofs and cdrskin but not with Nero. I am still clueless what preparations Nero could do to increase that compatibility. If 496-alignment allows cdrecord to cross the layer break, then it would be interesting to see whether it has write errors, too. - Let me add another growisofs problem report which i got from a scdbackup user: With DVD+R DL, growisofs seems to read the size of the ISO image and to announce that size for the write run. If scdbackup adds its checksum list and (superstitious) padding, then the write run aborts less than 32 blocks after the end of the ISO image. mkisofs reports: 3916389 extents written (7649 MB) growisofs -Z /dev/...=/dev/fd0 reports: :-[ [EMAIL PROTECTED] failed with SK=5h/END OF USER AREA ENCOUNTERED ON That is 27 sectors after the end of the image (in the the data tail added by scdbackup). The same growisofs command works well with DVD+R and sequential DVD-RW. So the rigid size curb seems to be a speciality with the handling of DVD+R DL in growisofs. In a further attempt, cdrskin wrote the whole stream to DVD+R DL with no error messages. (The readability of the media was mediocre, though. I/o errors with several payload files. So the user went back to single layer media. Elsewise i would now advise him to set a maximum manual layerbreak by -use-the-force-luke=break:size ) - Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hi, _all_ other OS forbid to send SCSI commands from a normal user account. There are obviously workarounds for that restriction. As soon as the demand occurs i will try to learn. In worst case i would propose some client-server architecture. Another approach would be to create a new interface level inside libburn and to make use of an external MMC library rather than of our own MMC command functions. (I have seen man pages for MacOS describing such a thing.) There would still remain a lot of own functionality above its SCSI oriented source modules mmc.c, spc.c, sbc.c. Please start explaining why you did not use libscg which grants portability for software that likes to send SCSI commands to arbitrary targets. That is because the reason for starting cdrskin was my wish to have a CD burn program which has no hostile relationship with Linux kernel people. Zero cdrecord ancestry is a design goal. (We have had enough clones, hadn't we ?) My DVD adventures came only later. It would indeed be worthwhile to implement on libscg an application which makes full use of contemporary DVD specs. But actually, i leave that to you. It is not bad to have multiple burn programs. They allow us to explore drive peculiarities. If only Nero had the politeness to misburn one or two of Gregoire's DVD+R DL. Grrr. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
So the current consolidated theory would be about like this: - Problem number 1: - Problem number 2: - Problem number 3: - Agreed. Let me add another growisofs problem report which i got from a scdbackup user: With DVD+R DL, growisofs seems to read the size of the ISO image and to announce that size for the write run. If scdbackup adds its checksum list and (superstitious) padding, then the write run aborts less than 32 blocks after the end of the ISO image. mkisofs reports: 3916389 extents written (7649 MB) growisofs -Z /dev/...=/dev/fd0 reports: :-[ [EMAIL PROTECTED] failed with SK=5h/END OF USER AREA ENCOUNTERED ON That is 27 sectors after the end of the image (in the the data tail added by scdbackup). 3916389 % 16 = 5 or 32-27, so if recording was folded in the middle of iso image, then 27 would indeed be maximum possible padding (well, it could have been 16-5=11 if amount of ECC blocks in padded image would be even). Question is if above is actually complete growisofs command line? Point is that growisofs does *not* set layer break, if you don't pass -dvd-compat [or -dvd-video], and without it shouldn't be a problem to pad iso image with additional data... In other words, 'growisofs -Z /dev/...=/dev/fd/0' should have actually worked, while 'growisofs -dvd-compat /dev/...=/dev/fd/0' would work as described above. Elsewise i would now advise him to set a maximum manual layerbreak by -use-the-force-luke=break:size Yes. One can even argue that growisofs should recognize break:+size, which would reserve for size padding, as well as break:max... A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Thomas Schmitt [EMAIL PROTECTED] wrote: Hi, Cdrskin in addition is based on a library that is based on specific security holes in Linux. Could you describe those holes ? I mentioned already: _all_ other OS forbid to send SCSI commands from a normal user account. The only exception is MS-WIN with ASPI (a ISV product) installed. Porting it to other platforms will result in insufficient privilleges for sending SCSI commands So you can predict properties of future software with yet undefined target operating systems ? Of course I can predict what will happen if you port to known other OS. I did this port alrready, so I know what I am talking about I am not sure whether the lib is prepared for this. You could learn. It is open source. There is a low probabilty that you can learn from software that itself did avoid to learn from other existing implementaions. Please start explaining why you did not use libscg which grants portability for software that likes to send SCSI commands to arbitrary targets. After you did, it may make sense to give futher answers. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hi, Question is if above is actually complete growisofs command line? It comes out of a wrapper script that converts cdrecord options into runs of dvd+rw-tools. The write command is supposed to be: growisofs \ -use-the-force-luke \ -use-the-force-luke=bufsize:16m \ -use-the-force-luke=noload \ -Z /dev/...=/dev/fd/0 Eventually there is also option speed=... Point is that growisofs does *not* set layer break, if you don't pass -dvd-compat [or -dvd-video] Hmm. That would also make questionable my argumentation about Problem 2. So if growisofs did not issue a layer break position then Gregoire's drive may or may not have Problem 1. But in Gregoire's scripts i do read -dvd-compat. So probably the theory about number 2 still stands. As for scdbackup: I am quite sure that the failed growisofs run for scdbackup was not with -dvd-compat or any other option which causes a fixed size. The growisofs wrapper works fine for sequential DVD-RW where such a setting would cause the same error. Obvious is the relation of error position, error message and size of the plain ISO image. Regrettably i cannot get that user to make more experiments which each eat up one DL media. The problem will have to wait for the next occasion to show up. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [cdwrite] Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Gregoire Favre [EMAIL PROTECTED] wrote: Hello, I have tried with mkisofs $OPTS -V $1 $2|cdrecord driveropts=layerbreak=2086912 $COMCD tsize=$SIZEs - Which I am not sure of the syntax... I don't fully understand cdrecord man page. Unfortunately : Track 01: 4041 of 8124 MB written (fifo 100%) [buf 99%] 8.4x. 61.66% done, estimate finish Thu May 15 22:44:57 2008 Track 01: 4051 of 8124 MB written (fifo 99%) [buf 99%] 8.4x. 61.78% done, estimate finish Thu May 15 22:44:56 2008 Track 01: 4061 of 8124 MB written (fifo 99%) [buf 99%] 8.3x. 61.90% done, estimate finish Thu May 15 22:44:55 2008 Track 01: 4070 of 8124 MB written (fifo 99%) [buf 99%] 8.5x. 62.02% done, estimate finish Thu May 15 22:44:55 2008 Track 01: 4075 of 8124 MB written (fifo 99%) [buf 99%] 8.2x.cdrecord: faio_wait_on_buffer for writer timed out. cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 1F D7 E9 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 00 00 Sense Key: 0x0 No Additional Sense, Segment 11 Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 255.841s timeout 100s cdrecord: No such device or address. Cannot send SCSI cmd via ioctl. This is the first useful error message. It finally lead to the underlying problem. When I started to add Dual Layer support to cdrecord, I intended to follow the standard that requires to align writes at the layer break. It got somehow forgotten during the work and several people reported that cdrecord worked fine for them. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Question is if above is actually complete growisofs command line? It comes out of a wrapper script that converts cdrecord options into runs of dvd+rw-tools. The write command is supposed to be: growisofs \ -use-the-force-luke \ -use-the-force-luke=bufsize:16m \ -use-the-force-luke=noload \ -Z /dev/...=/dev/fd/0 Eventually there is also option speed=... Then it's very strange... Point is that growisofs does *not* set layer break, if you don't pass -dvd-compat [or -dvd-video] Hmm. That would also make questionable my argumentation about Problem 2. No, not at all. So if growisofs did not issue a layer break position then Gregoire's drive may or may not have Problem 1. But in Gregoire's scripts i do read -dvd-compat. Right... So probably the theory about number 2 still stands. But in either case problem 2 is about WRITE command crossing layer break position. As far as I understand it doesn't matter where is is, default or explicitly set [to lower value]. As for scdbackup: I am quite sure that the failed growisofs run for scdbackup was not with -dvd-compat or any other option which causes a fixed size. The growisofs wrapper works fine for sequential DVD-RW where such a setting would cause the same error. Not necessarily. The only case that would cause the same error is if minimally blanked DVD-RW so that DAO gets engaged or DAO is explicitly engaged on command line. If DVD-RW media is fully blanked or formatted for restricted overwrite, the you will not suffer from this problem (unless of course image really fills the media till the very edge, so there is not place for your additional data). Obvious is the relation of error position, error message and size of the plain ISO image. Regrettably i cannot get that user to make more experiments which each eat up one DL media. The problem will have to wait for the next occasion to show up. As usual collect versioning information, dvd+rw-mediainfo for resulting recording, exact command line and exact output. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hi, Andy Polyakov wrote: Question is if above is actually complete growisofs command line? Very good question, indeed. Somehow -dvd-compat sneaked into the growisofs_wrapper of scdbackup since i made the last round of media tests. The command line is most probably this: growisofs -use-the-force-luke \ -dvd-compat \ -use-the-force-luke=bufsize:16m \ -use-the-force-luke=noload \ -Z /dev/sr0=/dev/fd/0 which is well entitled to assume the ISO size as full image size if no other hint is available. Sorry for confusing. -- So there remains one big riddle: Why does Nero show no write errors on Gergoire's drive ? Is it more modest in speed ? it would be possible to re-run the exact command and complete recording. Can it be that Nero catches the error and immediately does such a re-start ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Question is if above is actually complete growisofs command line? Very good question, indeed. Somehow -dvd-compat sneaked into the growisofs_wrapper of scdbackup since i made the last round of media tests. The command line is most probably this: growisofs -use-the-force-luke \ -dvd-compat \ -use-the-force-luke=bufsize:16m \ -use-the-force-luke=noload \ -Z /dev/sr0=/dev/fd/0 which is well entitled to assume the ISO size as full image size if no other hint is available. Note that in last post I've said ... the only case that would cause the same error... It holds true even for -dvd-compat recordings. I.e. -dvd-compat would cause the problem in question *only* in DVD+R DL and DVD-R[W] DAO context. It will still allow you to pad DVD+R, DVD-R Incremental, even DVD-R DL recordings, not to mention rewritables... A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [cdwrite] Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Thomas Schmitt wrote: Problem number 1: Rob and CJ have drives which do not like any other layer break address than the one which is their default. ... (This would mean that cdrskin has no problem with those drives. I would appreciate confirmation.) Yeah, no problem. I'm heading out for the weekend, but I'll make the time to run some tests in the beginning of next week. -CJ -- WOW: Flemmy| Happiness isn't good enough for me! I [EMAIL PROTECTED] | demand euphoria! 24.24.2.3171 | - Calvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
- Problem number 1: Rob and CJ have drives which do not like any other layer break address than the one which is their default. Thus growisofs and cdrecord fail if their automatically computed layer breaks get set. The remedy is to enforce the drive's default layer break address and override the programs' computations. (This would mean that cdrskin has no problem with those drives. I would appreciate confirmation.) There is also possibility that some/their units require layer break to be set and to be set to value embossed into media information zone. I mean not setting layer break might fail too, just as setting it to non-default value. I know it sounds crazy, as unit knows where to set layer break, and shouldn't need a reminder, but stranger things were observed... Cheers. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Thomas Schmitt [EMAIL PROTECTED] wrote: Hi, _all_ other OS forbid to send SCSI commands from a normal user account. There are obviously workarounds for that restriction. As soon as the demand occurs i will try to learn. In worst case i would propose some client-server architecture. ASPI is no workaround, it undermines the privileges of the basic host system. Please start explaining why you did not use libscg which grants portability for software that likes to send SCSI commands to arbitrary targets. That is because the reason for starting cdrskin was my wish to have a CD burn program which has no hostile relationship with Linux kernel people. Zero cdrecord ancestry is a design goal. (We have had enough clones, hadn't we ?) Could you explain why writing a new program should help to fix the hostile habbit of some Linux kernel developers? It is not bad to have multiple burn programs. They allow us to explore drive peculiarities. If only Nero had the politeness to misburn one or two of Gregoire's DVD+R DL. Grrr. I'll write a fix for cdrecord soon, tghen he may try again ;-) Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Thomas Schmitt [EMAIL PROTECTED] wrote: It is most likely a combination od 2 and 3. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hi,
Andy Polyakov wrote:
[-dvd-compat] will still allow you to pad DVD+R,
DVD-R Incremental, even DVD-R DL recordings,
not to mention rewritables..
Yeah. That's why this development glitch could
stay undetected for quite a while.
It is harmless if the image comes from a regular
disk file, i understand from reading your builtin_dd().
I am currently testing the new stable and
unstable uploads of scdbackup. Now there are
precautions that -dvd-compat and -Z ...=/dev/fd/0
will not get together again.
Andy Polyakov wrote:
There is also possibility that some/their units require layer break to be set
but stranger things were observed...
Hm. I shall prepare libburn for explicite setting
of that address.
For now i left it out because the specs
do not call it mandatory by any means
and because i do not fully understand the
consequences.
(E.g. may i set the L0 capacity to hundred MB
and still write the full 4+ GB on L1 ? Do i
need to call RESERVE TRACK ? ...)
Joerg Schilling wrote:
It [Gregoire's problem] is most likely a combination
od 2 and 3.
Yep. Quite surely Gregoire's drive has a problem with 2,
the write command which touches both layers.
As for number 3, the write error far after the
layer break, anything is possible.
I estimate the probability for the observation
that 2 runs of growisofs and cdrskin failed and
6 runs of Nero succeed by incident as about 1/28 :
The first hit has probability 2/8, the second 1/7.
One can hardly state that this is not suspicious
of being systematic.
Could you explain why writing a new program should
help to fix the hostile habbit of some Linux kernel
developers?
I see this as a more complex system of animosity.
To exchange one component might change that
system completely.
But for now, the official Linux world rather settled
with wodim. So the quarrel ended anyway.
Joerg Schilling wrote:
I'll write a fix for cdrecord soon, tghen he may try again ;-)
You make me curious.
What precaution in cdrecord might avoid or
compensate a 3 0C 00 WRITE ERROR ?
The usual list of causes is
{bad media, automounter interference, bad drive}
Do you know more ?
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
[-dvd-compat] will still allow you to pad DVD+R, DVD-R Incremental, even DVD-R DL recordings, not to mention rewritables.. Yeah. That's why this development glitch could stay undetected for quite a while. It is harmless if the image comes from a regular disk file, i understand from reading your builtin_dd(). Correct. There is also possibility that some/their units require layer break to be set but stranger things were observed... Hm. I shall prepare libburn for explicite setting of that address. For now i left it out because the specs do not call it mandatory by any means and because i do not fully understand the consequences. (E.g. may i set the L0 capacity to hundred MB and still write the full 4+ GB on L1 ? No. How much you can write to L1 will always be less or equal to L0 capacity. Do i need to call RESERVE TRACK ? ...) No. I.e. not according to specification. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Thomas Schmitt [EMAIL PROTECTED] wrote: Could you explain why writing a new program should help to fix the hostile habbit of some Linux kernel developers? I see this as a more complex system of animosity. To exchange one component might change that system completely. But for now, the official Linux world rather settled with wodim. So the quarrel ended anyway. They will stop doing this stupid move after they realized that this move did create them dozens of unfixed bugs and that there is no maintanance for wodim. Wodim development stopped more than a year ago on May 6th 2007. The changes that have been made later just try to hide this fact. All wodim changes in total made after May 6th 2007 sum up to less than what I change in cdrtools in a lazy week. Look e.g. at https://bugs.launchpad.net/ubuntu/+source/cdrkit None of the problems listed there is present if you use the unmodifies offcial cdrtools. Some Linux people are strange. They e.g. complain about compile problems with star on some Linux distributions (calling star junk) but forget that these problems are a result of the fact that star support Linux specific features. If those Linux distros would be installed in a consistent way, the compile problems would go away. GNU tar on the other side does not support _any_ Linux specific feature. It seems that the reason why some people don't like my software is because I am supporting Linux too well ;-) What we need is people who understand why problems occur and that help educating others to avoid to repeat the same mistakes ever and ever again. Libscg is based on 22 years of experiences with SCSI transport on many _different_ platforms. This is why it is portable ;-) Joerg Schilling wrote: I'll write a fix for cdrecord soon, tghen he may try again ;-) You make me curious. What precaution in cdrecord might avoid or compensate a 3 0C 00 WRITE ERROR ? Now that we know a primary problem, let us asume that the drive reports incorrect error messages and try again ;-) Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
On Fri, May 16, 2008 at 03:34:52PM +0200, Joerg Schilling wrote: I'll write a fix for cdrecord soon, tghen he may try again ;-) Oh great :-) I am quiete used to cdrecord which I would be pleased to be able to use for DVD+R DL also ! Thank. -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hi, i wrote: the official Linux world rather settled with wodim. Joerg Schilling wrote: They will stop doing this stupid move after they realized that this move did create them dozens of unfixed bugs and that there is no maintanance for wodim. What maintenance would it need for its core purpose to write CDs ? If ever then i expect that i needs to be adapted to some future new kernel interface. For DVD it is usual to employ growisofs. My own backup tool still prefers it over any other burn program for DVD when it comes to automatic choice. (But it has to operate it correctly. Pffft.) What precaution in cdrecord might avoid or compensate a 3 0C 00 WRITE ERROR ? Now that we know a primary problem, let us asume that the drive reports incorrect error messages and try again ;-) Problem number 2 can occur only if the burn program does not align its writes to 16 block boundaries. Both, growisofs and cdrskin do align to 16. Both did not show the error at the end of L0 but substantially within L1. Problem 2 and 3 are clearly distinct. I expect cdrecord to run into 3 after 2 is solved. If 3 does not happen, then i want to know why. But happen and not happen is a matter of measurement and statistics. We still have a probability of about 4% that all observations around problem 3 are just statistical noise. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Thomas Schmitt [EMAIL PROTECTED] wrote: Hi, i wrote: the official Linux world rather settled with wodim. Joerg Schilling wrote: They will stop doing this stupid move after they realized that this move did create them dozens of unfixed bugs and that there is no maintanance for wodim. What maintenance would it need for its core purpose to write CDs ? If ever then i expect that i needs to be adapted to some future new kernel interface. They added a lot of bugs that are not in the original software. You thus cannot think about cdrecord but talk about wodim. Cdrecord would not soon need new CD related features but wodim is also based on a 3+ year old cdrecord version that misses features that are present in cdrecord for a while. Look at the bug list I send you to find the obvious problems. It nicely also shows up many bugs cdrkit added to it's mkisofs version: e.g. broken support for Joliet, broken support for UTF-8 based locales and a broken implementation for files 4 GB. Of course, the real problem is that there have been changes in libscg and wodim that are a result of a hostile attitude against a platform-neutral CLI and a result of denying the need for extended privileges to write CDs/DVDs. These changes make wodim harder to use than the original and hide problems that are reported early in the original - in wodim the resulting problems are reported late and in a hard to classify way. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hello,
just burned a DVD+R DL with a little script (included) which fails with:
97.77% done, estimate finish Thu May 15 10:21:30 2008
97.89% done, estimate finish Thu May 15 10:21:30 2008
:-[ [EMAIL PROTECTED] failed with SK=3h/WRITE ERROR]: Input/output error
:-( write failed: Input/output error
What does that mean ?
I wanted to use cdrecord, but for an unknown reason it always stop a
4070Mb (and -dummy don't work, so everytime it a DVD+R DL destroyed...).
Thank for all idea :-)
--
Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org
http://picasaweb.google.com/Gregoire.Favre
#!/bin/bash
if [ -z $2 ]; then
echo usage : $0 DVD_title DVD_dir [write speed]
echo That will write a DVD with video structure if there a VIDEO_TS.
echo And without video structure if without VIDEO_TS dir
exit
fi
UDF=`find $2 -size +2G|wc -w`
unlock() {
cdrdao unlock --device 2,0,0 --driver generic-mmc sleep 1
}
sync
ulimit -l unlimited
if [ $UDF -eq 0 ]; then
COM=-f -J -r -graft-points
if [ -z $3 ]; then
COMCD=-v dev=2,0,0 -dao fs=1000m
else
COMCD=-speed=$3 -v dev=2,0,0 -dao fs=1000m
fi
VIDEO=`ls $2|grep -i VIDEO_TS 2 /dev/null |wc -w`
if [ $VIDEO -eq 0 ]; then
OPTS=$COM
SIZE=`mkisofs -f -J -r -graft-points -quiet -print-size -V $1
$2`
else
OPTS=$COM -dvd-video
SIZE=`mkisofs -f -J -r -graft-points -quiet -print-size
-dvd-video -V $1 $2`
fi
mkisofs $OPTS -V $1 $2|cdrecord $COMCD tsize=$SIZEs -
else
COM=-iso-level 3 -udf -f -J -r -graft-points
if [ -z $3 ]; then
COMCD=-v dev=2,0,0 -dao fs=1000m
else
COMCD=-speed=$3 -v dev=2,0,0 -dao fs=1000m
fi
VIDEO=`ls $2|grep -i VIDEO_TS 2 /dev/null |wc -w`
DL=`find $2 -size +4489M|wc -w`
if [ $DL -eq 0 ]; then
if [ $VIDEO -eq 0 ]; then
OPTS=$COM
SIZE=`mkisofs -iso-level 3 -udf -f -J -r -graft-points
-quiet -print-size -V $1 $2`
else
OPTS=$COM -dvd-video
SIZE=`mkisofs -iso-level 3 -udf -f -J -r -graft-points
-quiet -print-size -dvd-video -V $1 $2`
fi
mkisofs $OPTS -V $1 $2|cdrecord $COMCD tsize=$SIZEs -
else
if [ $VIDEO -eq 0 ]; then
growisofs -Z /dev/sr0 -f -J -r -graft-points
-dvd-compat -iso-level 3 -udf -V $1 $2
else
growisofs -Z /dev/sr0 -f -J -r -graft-points
-dvd-compat -iso-level 3 -udf -dvd-video -V $1 $2
fi
fi
fi
#unlock
eject /dev/sr0
eject -t /dev/sr0
sleep 8
mount /mnt/cdrom
ls -alh /mnt/cdrom
DF
umount /mnt/cdrom
sleep 1
eject /dev/sr0
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Gregoire Favre [EMAIL PROTECTED] wrote: Hello, just burned a DVD+R DL with a little script (included) which fails with: 97.77% done, estimate finish Thu May 15 10:21:30 2008 97.89% done, estimate finish Thu May 15 10:21:30 2008 :-[ [EMAIL PROTECTED] failed with SK=3h/WRITE ERROR]: Input/output error :-( write failed: Input/output error What does that mean ? I wanted to use cdrecord, but for an unknown reason it always stop a 4070Mb (and -dummy don't work, so everytime it a DVD+R DL destroyed...). You did not use cdrecord here. Cdrecord would print a more readable/complere error message. This is most likely growisofs. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
On Thu, May 15, 2008 at 03:04:13PM +0200, Joerg Schilling wrote: You did not use cdrecord here. Cdrecord would print a more readable/complere error message. This is most likely growisofs. Yes and no : cdrecord just freeze itself and afterthat I don't get my burner again... I have to power down the computer in order to have access to my drive again (a simple reboot isn't enough). I tried nero linux : http://nerolinux.nero.com and I have to admit it works perfectly !!! So my hardware and media are compatible :-) Is there anything wrong in my script ? I use the following version which always fails for me : Cdrecord-ProDVD-ProBD-Clone 2.01.01a38 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2008 Jörg Schilling If there are bugs in cdrecord that I can help solve I agree to loose a few others DVD+R DL. In case needed, here the result of a just burned DVD : dvd+rw-mediainfo /dev/sr0 INQUIRY:[LITE-ON ][DVDRW LH-20A1S ][9L09] GET [CURRENT] CONFIGURATION: Mounted Media: 2Bh, DVD+R Double Layer Media ID: RICOHJPN/D01 Current Write Speed: 8.0x1385=11080KB/s Write Speed #0:8.0x1385=11080KB/s Write Speed #1:6.0x1385=8310KB/s Write Speed #2:4.0x1385=5540KB/s Write Speed #3:2.4x1385=3324KB/s GET [CURRENT] PERFORMANCE: Write Performance: 3.2x1385=4432KB/[EMAIL PROTECTED] - 11.9x1385=16496KB/[EMAIL PROTECTED] Speed Descriptor#0:00/4167519 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#1:00/4167519 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#2:00/4167519 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#3:00/4167519 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s READ DVD STRUCTURE[#0h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at:2083760*2KB=4267540480 DVD+R DOUBLE LAYER BOUNDARY INFORMATION: L0 Data Zone Capacity: 2083760*2KB, can no longer be set READ DISC INFORMATION: Disc status: complete Number of Sessions:1 State of Last Session: complete Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: invisible Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size:4167520*2KB ROM Compatibility LBA: 262144 FABRICATED TOC: Track#1 : [EMAIL PROTECTED] Track#AA : [EMAIL PROTECTED] Multi-session Info:[EMAIL PROTECTED] READ CAPACITY: 4167520*2048=8535080960 Or cdrecord -minfo dev=2,0,0 Cdrecord-ProDVD-ProBD-Clone 2.01.01a38 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2008 Jörg Schilling scsidev: '2,0,0' scsibus: 2 target: 0 lun: 0 Linux sg driver version: 3.5.34 Using libscg version 'schily-0.9'. Device type: Removable CD-ROM Version: 5 Response Format: 2 Capabilities : Vendor_info: 'LITE-ON ' Identifikation : 'DVDRW LH-20A1S ' Revision : '9L09' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Using generic SCSI-3/mmc-3 DVD+R driver (mmc_dvdplusr). Driver flags : NO-CD DVD MMC-3 SWABAUDIO BURNFREE FORCESPEED Supported modes: PACKET SAO LAYER_JUMP WARNING: Phys disk size 16384000 differs from rzone size 4167520! Prerecorded disk? WARNING: Phys start: 196608 Phys end 16580607 Mounted media class: DVD Mounted media type: DVD+R/DL Disk Is not erasable data type:standard disk status: complete session status: complete BG format status: none first track: 1 number of sessions: 1 first track in last sess: 1 last track in last sess: 1 Disk Is unrestricted Disk type: DVD, HD-DVD or BD Track Sess Type Start Addr End Addr Size == 1 1 Data 0 41675194167520 Last session start address: 0 Last session leadout start address: 4167520 And from an empty one dvd+rw-mediainfo /dev/sr0 INQUIRY:[LITE-ON ][DVDRW LH-20A1S ][9L09] GET [CURRENT] CONFIGURATION: Mounted Media: 2Bh, DVD+R Double Layer Media ID: RICOHJPN/D01 Current Write Speed: 8.0x1385=11080KB/s Write Speed #0:8.0x1385=11080KB/s Write Speed #1:6.0x1385=8310KB/s Write Speed #2:4.0x1385=5540KB/s Write Speed #3:2.4x1385=3324KB/s GET [CURRENT] PERFORMANCE: Write Performance: 3.2x1385=4432KB/[EMAIL PROTECTED] - 0] Speed Descriptor#0:00/0 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#1:00/0 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#2:00/0 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#3:00/0 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s READ DVD STRUCTURE[#0h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at:2086912*2KB=4273995776 DVD+R DOUBLE LAYER BOUNDARY INFORMATION: L0 Data Zone Capacity: 2086912*2KB, can still be set READ DISC INFORMATION: Disc status: blank Number of Sessions:1 State of Last Session: empty Next Track: 1 Number
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hi, 97.89% done, estimate finish Thu May 15 10:21:30 2008 :-[ [EMAIL PROTECTED] failed with SK=3h/WRITE ERROR]: Input/output error What does that mean ? The drive responded to the computer and told it that writing to the given sector failed. This would normally be a case of poor drive-media compatibility. The failing sector is at byte 4066352 * 2048 = 8,327,888,896 i.e. 200 MB below the promised capacity of 4167520 sectors. I tried nero linux : http://nerolinux.nero.com and I have to admit it works perfectly !!! The (possibly expensive) question with this observation is whether it stands a larger number of tries with Nero and counter tries with growisofs. If you do extensive experiments and comparisons then i would like to submit to the competition my own program cdrskin in version 0.4.4 or later. (Earlier won't do DL) I don't think that it (or Nero) is better prepared against write errors. But nevertheless it handles DVD+R DL a bit different than growisofs. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
On Thu, May 15, 2008 at 04:27:25PM +0200, Thomas Schmitt wrote: Hello :-) If you do extensive experiments and comparisons then i would like to submit to the competition my own program cdrskin in version 0.4.4 or later. (Earlier won't do DL) I don't think that it (or Nero) is better prepared against write errors. But nevertheless it handles DVD+R DL a bit different than growisofs. Oh, I always thought cdrskin was to burn pictures (or lighscribe) ontop of CD/DVD... nice to learn I was wrong ;-) Before I make a make install in it source dir (I alreay compiled cdrskin-0.4.6.pl00.tar.gz) and possibly mess my gentoo install, is there a way to simply start it from it source directory ? I would like to just try to burn one big file into a DVD+R DL (about 8Gb), what command using cdrskin would you recommend ? Thank you very much, -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
On Thu, May 15, 2008 at 04:27:25PM +0200, Thomas Schmitt wrote:
If you do extensive experiments and comparisons then
i would like to submit to the competition my own program
cdrskin in version 0.4.4 or later. (Earlier won't do DL)
OK, just copied cdskin to my path and tried a burn with the attached
script :
...
Track 01: 4195 of 8138 MB written (fifo 100%) [buf 99%] 4.0x. 63.83% done,
estimate finish Thu May 15 17:11:50 2008
Track 01: 4204 of 8138 MB written (fifo 100%) [buf 98%] 4.0x. 63.96% done,
estimate finish Thu May 15 17:11:51 2008
Track 01: 4211 of 8138 MB written (fifo 100%) [buf 99%] 4.0x.cdrskin: FATAL
: SCSI error on write(2156064,16): key=3 asc=0Ch ascq=00h
cdrskin: thank you for being patient since 733 seconds
Track 01: Total bytes read/written: 4415651840/4415619072 (2156064 sectors).
Writing time: 733.401s
Cdrskin: fifo had 2668112 puts and 2156111 gets.
Cdrskin: fifo was 0 times empty and 154046 times full, min fill was 99%.
Min drive buffer fill was 57%
cdrskin: burning failed
cdrskin: FATAL : burning failed.
eject: CD-ROM tray close command failed: Input/output error
mount: No medium found
Any other ideas ?
Thank.
--
Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org
http://picasaweb.google.com/Gregoire.Favre
#!/bin/bash
if [ -z $2 ]; then
echo usage : $0 DVD_title DVD_dir [write speed]
echo That will write a DVD with video structure if there a VIDEO_TS.
echo And without video structure if without VIDEO_TS dir
exit
fi
UDF=`find $2 -size +2G|wc -w`
unlock() {
cdrdao unlock --device 2,0,0 --driver generic-mmc sleep 1
}
sync
ulimit -l unlimited
if [ $UDF -eq 0 ]; then
COM=-f -J -r -graft-points
if [ -z $3 ]; then
COMCD=-v dev=2,0,0 -dao fs=1000m
else
COMCD=-speed=$3 -v dev=2,0,0 -dao fs=1000m
fi
VIDEO=`ls $2|grep -i VIDEO_TS 2 /dev/null |wc -w`
if [ $VIDEO -eq 0 ]; then
OPTS=$COM
SIZE=`mkisofs -f -J -r -graft-points -quiet -print-size -V $1
$2`
else
OPTS=$COM -dvd-video
SIZE=`mkisofs -f -J -r -graft-points -quiet -print-size
-dvd-video -V $1 $2`
fi
mkisofs $OPTS -V $1 $2|cdrecord $COMCD tsize=$SIZEs -
else
COM=-iso-level 3 -udf -f -J -r -graft-points
if [ -z $3 ]; then
COMCD=-v dev=2,0,0 -dao fs=1000m
else
COMCD=-speed=$3 -v dev=2,0,0 -dao fs=1000m
fi
VIDEO=`ls $2|grep -i VIDEO_TS 2 /dev/null |wc -w`
DL=`find $2 -size +4489M|wc -w`
if [ $DL -eq 0 ]; then
if [ $VIDEO -eq 0 ]; then
OPTS=$COM
SIZE=`mkisofs -iso-level 3 -udf -f -J -r -graft-points
-quiet -print-size -V $1 $2`
else
OPTS=$COM -dvd-video
SIZE=`mkisofs -iso-level 3 -udf -f -J -r -graft-points
-quiet -print-size -dvd-video -V $1 $2`
fi
mkisofs $OPTS -V $1 $2|cdrecord $COMCD tsize=$SIZEs -
else
if [ $VIDEO -eq 0 ]; then
OPTS=$COM
SIZE=`mkisofs -iso-level 3 -udf -f -J -r -graft-points
-quiet -print-size -V $1 $2`
#growisofs -Z /dev/sr0 -f -J -r -graft-points
-dvd-compat -iso-level 3 -udf -V $1 $2
else
#growisofs -Z /dev/sr0 -f -J -r -graft-points
-dvd-compat -iso-level 3 -udf -dvd-video -V $1 $2
OPTS=$COM -dvd-video
SIZE=`mkisofs -iso-level 3 -udf -f -J -r -graft-points
-quiet -print-size -dvd-video -V $1 $2`
fi
mkisofs $OPTS -V $1 $2|cdrskin $COMCD tsize=$SIZEs -
fi
fi
#unlock
eject /dev/sr0
eject -t /dev/sr0
sleep 8
mount /mnt/cdrom
ls -alh /mnt/cdrom
DF
umount /mnt/cdrom
sleep 1
eject /dev/sr0
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
On Thu, May 15, 2008 at 04:27:25PM +0200, Thomas Schmitt wrote:
By the way, I got :
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata3.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
ata3.00: status: { DRDY }
ata3: soft resetting link
ata3: port is slow to respond, please be patient (Status 0xd0)
dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2
dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2
ata3: softreset failed (device not ready)
ata3: hard resetting link
ata3: port is slow to respond, please be patient (Status 0x80)
ata3: COMRESET failed (errno=-16)
ata3: hard resetting link
ata3: port is slow to respond, please be patient (Status 0x80)
dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2
dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2
dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2
dvb_frontend_ioctl: FESTATE_RETUNE: fepriv-state=2
ata3: COMRESET failed (errno=-16)
ata3: limiting SATA link speed to 1.5 Gbps
ata3: hard resetting link
ata3: COMRESET failed (errno=-16)
ata3: reset failed, giving up
ata3.00: disabled
ata3: EH complete
--
Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org
http://picasaweb.google.com/Gregoire.Favre
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Gregoire Favre [EMAIL PROTECTED] wrote: On Thu, May 15, 2008 at 04:27:25PM +0200, Thomas Schmitt wrote: Hello :-) If you do extensive experiments and comparisons then i would like to submit to the competition my own program cdrskin in version 0.4.4 or later. (Earlier won't do DL) I don't think that it (or Nero) is better prepared against write errors. But nevertheless it handles DVD+R DL a bit different than growisofs. Oh, I always thought cdrskin was to burn pictures (or lighscribe) ontop of CD/DVD... nice to learn I was wrong ;-) This has been discussed several times already. cdrskin is a Linux only program and for this reason not a competitor to e.g. cdrecord as cdrecord works on any platform. Cdrskin in addition is based on a library that is based on specific security holes in Linux. Porting it to other platforms will result in insufficient privilleges for sending SCSI commands and I am not sure whether the lib is prepared for this. The typical _users_ of such a lib are expected to be GUIs. These GUIs are non-portable from using the libs because other platforms all need special privileges to send SCIS commands and X-applications that make use of such extended privilleges are classified to be a security problem. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Gregoire Favre [EMAIL PROTECTED] wrote: On Thu, May 15, 2008 at 04:27:25PM +0200, Thomas Schmitt wrote: If you do extensive experiments and comparisons then i would like to submit to the competition my own program cdrskin in version 0.4.4 or later. (Earlier won't do DL) OK, just copied cdskin to my path and tried a burn with the attached script : ... I asume that cdrecord works also? Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
On Thu, May 15, 2008 at 05:20:31PM +0200, Joerg Schilling wrote: I asume that cdrecord works also? If you speak about single layer DVD, yes, cdrecord works just perfectly :-) But if we speak about DVD+R DL no it has the same behaviour than cdrskin. -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hi, I would like to just try to burn one big file into a DVD+R DL (about 8Gb), what command using cdrskin would you recommend ? In general it should work on DVD with the same options as cdrecord accepts for DVD and some options known from cdrecord with CD. Well, meanwhile you found out yourself: COMCD=-speed=$3 -v dev=2,0,0 -dao fs=1000m ... mkisofs $OPTS -V $1 $2|cdrskin $COMCD tsize=$SIZEs - This should be ok. Track 01: 4211 of 8138 MB written (fifo 100%) [buf 99%] 4.0x.cdrskin: FATAL : SCSI error on write(2156064,16): key=3 asc=0Ch ascq=00h That's the same write error as with growisofs. Only at a different sector address. From the specs: 3 0C 00 WRITE ERROR More is not explained by this code. The address is suspiciously near the layer break address. The error occurs at 2156064 * 2048 = 4415619072 bytes Media capacity of both layers together is reported as: Free Blocks: 4173824*2KB The error spot is 69152 blocks = 140 MB _after_ the middle of this size. That is much more than any buffer delay in the drive could cause. So i can see no systematic correlation between layer break and error spot. (The layer break is what mainly distinguishes DVD+R DL from all other widely used DVD media.) To me it looks like bad media. If only Nero would be so nice to produce a misburn too ... (The cdrecord error which you reported on May 9 happens quite exactly at half image size and issues an error code 0 00 03 which is not listed in MMC-5 specs. So that error is still suspicious of systematic correlation with the layer break.) ata3: limiting SATA link speed to 1.5 Gbps ata3: hard resetting link ata3: COMRESET failed (errno=-16) ata3: reset failed, giving up ata3.00: disabled I am not a kernel expert. Hard to say whether this documents the cause or the consequences of the write error. Any other ideas ? cdrskin announces the size to the drive in advance if -dao is given or the size is known. With -tao or with unknown size, it would start a write run with unannounced size. (Here it deviates much from cdrecord on DVD.) So you could try this: COMCD=-speed=$3 -v dev=2,0,0 -tao fs=1000m ... mkisofs $OPTS -V $1 $2|cdrskin $COMCD - But i do not really expect that this is the decisive difference. If it works, i would suspect it to be a lucky incident, as i suspect with Nero. You may check whether my prediction is correct that the next error will happen at a different sector address or that some write runs even succeed completely. (I believe your growisofs run nearly made it.) You should verify that Nero really reproducibly can write the full media without errors. Verify whether the image file on disk is really identical to the image on media: diff /dev/sr0 disk_file If you can get different media, try them. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hi, Cdrskin in addition is based on a library that is based on specific security holes in Linux. Could you describe those holes ? Porting it to other platforms will result in insufficient privilleges for sending SCSI commands So you can predict properties of future software with yet undefined target operating systems ? I am not sure whether the lib is prepared for this. You could learn. It is open source. Actually the system dependent code is consolidated in two source modules which implement some defined interfaces. Inside its interface implementations, the system adapters are free and obliged to act as the host system demands it for CD/DVD/BD burning. So the adapter implementation on Linux is indeed Linux-centric - and that is good so. The typical _users_ of such a lib are expected to be GUIs. [...] classified to be a security problem. My own apps on top of libburn are command line programs: cdrskin and xorriso. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Gregoire Favre [EMAIL PROTECTED] wrote: On Thu, May 15, 2008 at 05:20:31PM +0200, Joerg Schilling wrote: I asume that cdrecord works also? If you speak about single layer DVD, yes, cdrecord works just perfectly :-) But if we speak about DVD+R DL no it has the same behaviour than cdrskin. If you get a write error, this is an incompatibility of the drive and the medium. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Joerg Schilling wrote: Gregoire Favre [EMAIL PROTECTED] wrote: On Thu, May 15, 2008 at 05:20:31PM +0200, Joerg Schilling wrote: I asume that cdrecord works also? If you speak about single layer DVD, yes, cdrecord works just perfectly :-) But if we speak about DVD+R DL no it has the same behaviour than cdrskin. If you get a write error, this is an incompatibility of the drive and the medium. That is likely to be true, but I was able to avoid this behavior with manual layer break. Thoughts on that? Media are expensive, tricks to save them cheap. -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Thomas Schmitt wrote: Hi, I would like to just try to burn one big file into a DVD+R DL (about 8Gb), what command using cdrskin would you recommend ? In general it should work on DVD with the same options as cdrecord accepts for DVD and some options known from cdrecord with CD. Well, meanwhile you found out yourself: COMCD=-speed=$3 -v dev=2,0,0 -dao fs=1000m ... mkisofs $OPTS -V $1 $2|cdrskin $COMCD tsize=$SIZEs - This should be ok. Track 01: 4211 of 8138 MB written (fifo 100%) [buf 99%] 4.0x.cdrskin: FATAL : SCSI error on write(2156064,16): key=3 asc=0Ch ascq=00h That's the same write error as with growisofs. Only at a different sector address. From the specs: 3 0C 00 WRITE ERROR More is not explained by this code. The address is suspiciously near the layer break address. The error occurs at 2156064 * 2048 = 4415619072 bytes Media capacity of both layers together is reported as: Free Blocks: 4173824*2KB The error spot is 69152 blocks = 140 MB _after_ the middle of this size. That is much more than any buffer delay in the drive could cause. So i can see no systematic correlation between layer break and error spot. (The layer break is what mainly distinguishes DVD+R DL from all other widely used DVD media.) To me it looks like bad media. If only Nero would be so nice to produce a misburn too ... (The cdrecord error which you reported on May 9 happens quite exactly at half image size and issues an error code 0 00 03 which is not listed in MMC-5 specs. So that error is still suspicious of systematic correlation with the layer break.) ata3: limiting SATA link speed to 1.5 Gbps ata3: hard resetting link ata3: COMRESET failed (errno=-16) ata3: reset failed, giving up ata3.00: disabled I am not a kernel expert. Hard to say whether this documents the cause or the consequences of the write error. Any other ideas ? cdrskin announces the size to the drive in advance if -dao is given or the size is known. With -tao or with unknown size, it would start a write run with unannounced size. (Here it deviates much from cdrecord on DVD.) So you could try this: COMCD=-speed=$3 -v dev=2,0,0 -tao fs=1000m ... mkisofs $OPTS -V $1 $2|cdrskin $COMCD - But i do not really expect that this is the decisive difference. If it works, i would suspect it to be a lucky incident, as i suspect with Nero. You may check whether my prediction is correct that the next error will happen at a different sector address or that some write runs even succeed completely. (I believe your growisofs run nearly made it.) I suspect that layer break is a (the?) cause here, if it would be possible to specify the break a percent or two short of half the advertised capacity, I suspect it would work, based on some attempts I made a few months ago (with older versions of all the software). It's not clear how the layer break is determined if it isn't specified, the method was explained in conflicting ways in what I read, so I assumed that the break didn't happen by itself, even with a single large ISO image. Is it intended that butning an 8.2GB image would just work? I tried the current versions of various software (va36 of cdrecord, I believe) and none worked without specifying a break. You should verify that Nero really reproducibly can write the full media without errors. Verify whether the image file on disk is really identical to the image on media: diff /dev/sr0 disk_file If you can get different media, try them. -- E. Robert Bogusta It seemed like a good idea at the time -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
On Thu, May 15, 2008 at 03:24:17PM -0400, Rob Bogus wrote: If you get a write error, this is an incompatibility of the drive and the medium. That is likely to be true, but I was able to avoid this behavior with manual layer break. Maybe it's what nero does ? Could you tell us how you do this ? -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [cdwrite] Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Rob Bogus wrote: Is it intended that butning an 8.2GB image would just work? I tried the current versions of various software (va36 of cdrecord, I believe) and none worked without specifying a break. Hello - FWIW, it seems like we may have run up against the same thing. I started a thread a little while ago [1] about burning DL discs, the upshot being that at the time, I seemed to only be able to (successfully) burn DL discs if I manually specified a layer break. I hadn't yet taken the time to try programs other than growisofs and cdrecord, though, or media other than my current batch. It seems as though the manual-layerbreak trick has worked fine thus far, though. I've also been told it's a media/drive compatibility issue, which could certainly be the case, though the discs I've burnt with a manual layerbreak work fine for me. Anyway, it's interesting that it's not just me it's happening for. What hardware/media have yuou found you've needed that for? My drive identifies as Optiarc DVD RW AD-7170A (IDE), and my current DL media is Memorex 8x (don't have much more information about the media than that). Also, did you have that problem with media other than 8x? When I had been burning with slower media, I never ran into problems with it. -CJ [1] http://lists.debian.org/cdwrite/2008/04/msg00080.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hi, I suspect that layer break is a (the?) cause here, It is the natural suspect indeed. But the traces do not really point to it. so I assumed that the break didn't happen by itself, even with a single large ISO image. I have three DVD+R DL user reports so far: Two say that burning DVD+R DL by cdrskin works without error. Gregoire reports about write errors with growisofs (sets layer break) and cdrskin (does not set it). Both write errors occured clearly _after_ the middle address of the media and of the pre-announced image size. This is hardly to explain by layer break problems. The reported cdrecord error is not such a write error. It happens in the middle of the image. Looks very different than growisofs or cdrskin. Is it intended that butning an 8.2GB image would just work? I read the specs that way and i implemented it in libburn that way. Now i need feedback. The count is 2.5 : 0.5 so far. With the half points not being fully decided yet: Gregoire's cdrskin error happened 140 MB after the middle of the media. But it was an error. Regrettably i cannot buy DVD+R DL in reasonably small amounts at reasonable prices. So interested users will have to put at stake own media, unless a sponsor sends me some. :)) I was able to avoid this behavior with manual layer break. How strong is the statistical base with that observation ? How many failures without manual layer break and how many successes with it ? Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hello, is there something that could be learnt from 6/6 sucesses when using nero ? (I use md5sum to test result if someone know a faster way, I am interested...). With growisofs, it was alsmost complete, cdrskin and cdrecord seemed to be able to wrote only half of my file. Maybe I should retry one with growisofs ? I have tried two different burners : both lite on ones, I only got Prodye double black 8.5GB 240 min double layer 8x DVD+R DL medias here. Thanks, -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [cdwrite] Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hello, I have tried with mkisofs $OPTS -V $1 $2|cdrecord driveropts=layerbreak=2086912 $COMCD tsize=$SIZEs - Which I am not sure of the syntax... I don't fully understand cdrecord man page. Unfortunately : Track 01: 4041 of 8124 MB written (fifo 100%) [buf 99%] 8.4x. 61.66% done, estimate finish Thu May 15 22:44:57 2008 Track 01: 4051 of 8124 MB written (fifo 99%) [buf 99%] 8.4x. 61.78% done, estimate finish Thu May 15 22:44:56 2008 Track 01: 4061 of 8124 MB written (fifo 99%) [buf 99%] 8.3x. 61.90% done, estimate finish Thu May 15 22:44:55 2008 Track 01: 4070 of 8124 MB written (fifo 99%) [buf 99%] 8.5x. 62.02% done, estimate finish Thu May 15 22:44:55 2008 Track 01: 4075 of 8124 MB written (fifo 99%) [buf 99%] 8.2x.cdrecord: faio_wait_on_buffer for writer timed out. cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 1F D7 E9 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 00 00 Sense Key: 0x0 No Additional Sense, Segment 11 Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 255.841s timeout 100s cdrecord: No such device or address. Cannot send SCSI cmd via ioctl. write track data: error after 4273948672 bytes cdrecord: A write error occured. cdrecord: Please properly read the error message above. cdrecord: No such device. prevent/allow medium removal: scsi sendcmd: no error CDB: 1E 00 00 00 00 00 status: 0x0 (GOOD STATUS) cmd finished after 0.000s timeout 100s cdrecord: No such device. test unit ready: scsi sendcmd: no error CDB: 00 00 00 00 00 00 status: 0x0 (GOOD STATUS) cmd finished after 0.000s timeout 100s Writing time: 813.160s Average write speed 7.6x. Min drive buffer fill was 90% Fixating... cdrecord: No such device. flush cache: scsi sendcmd: no error CDB: 35 02 00 00 00 00 00 00 00 00 status: 0x0 (GOOD STATUS) cmd finished after 0.000s timeout 1000s cdrecord: No such device. flush cache: scsi sendcmd: no error CDB: 35 02 00 00 00 00 00 00 00 00 status: 0x0 (GOOD STATUS) cmd finished after 0.000s timeout 1000s cmd finished after 0.000s timeout 1000s Trouble flushing the cache cdrecord: Cannot fixate disk. Fixating time:0.000s cdrecord: No such device. prevent/allow medium removal: scsi sendcmd: no error CDB: 1E 00 00 00 00 00 status: 0x0 (GOOD STATUS) cmd finished after 0.000s timeout 100s cdrecord: fifo had 83313 puts and 67320 gets. cdrecord: fifo was 0 times empty and 23469 times full, min fill was 99%. Hard... -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WRITE@LBA=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)
Hi, is there something that could be learnt from 6/6 sucesses Probably yes. I will re-read the specs about the layer break and any variation which could be tried with DVD+R DL. With growisofs, it was alsmost complete, cdrskin and cdrecord seemed to be able to wrote only half of my file. The error codes received by growisofs and cdrskin are different from those received by cdrecord. Also, the cdrecord problem occurs quite near to the suspected layer break address. The cdrskin failure shows substantial distance to that address and growisofs even much more. I'd say the problem with cdrecord is a different one. Maybe I should retry one with growisofs ? Oh yes. (Although i'd like to see more cdrskin attempts. But growisofs had the better introduction.:)) -- The newest mail from Gregoire gives me opportunity to substantiate my opinion about cdrecord having a systematic problem that is different from the one with cdrskin and growisofs: mkisofs $OPTS -V $1 $2|cdrecord driveropts=layerbreak=2086912 $COMCD 2086912 blocks = 4076 MiB Track 01: 4075 of 8124 MB written (fifo 99%) [buf 99%] 8.2x.cdrecord: faio_wait_on_buffer for writer timed out. cdrecord: Input/output error. write_g1: scsi sendcmd: no error CDB: 2A 00 00 1F D7 E9 00 00 1F 00 write track data: error after 4273948672 bytes The 1F in CDB means 31 blocks are to be written by this WRITE10 command. The 1F D7 E9 means write address is 2086889. (Confirmed by: 4273948672 / 2048 == 2086889) The write size of 31 blocks seems systematic: 2086889 % 31 == 0 The man page of cdrecord says: The manual layer break value needs to be a mul- tiple of the ECC sector size which is 16 logical 2048 byte sectors in case of DVD 2086912 - 2086889 == 23 The failing write command is 31 blocks long and thus touches both layers. That might be contrary to MMC-5 4.3.7.5.3, Dual Layer Recording: Crossing the Layers: Since DVD+R DL format follows the DVD+R format, there is only one pre-condition when crossing the layers: Crossing the layers shall occur at an ECC block boundary. [I.e. multiple of 16] A typical example of crossing the layers during recording is shown in Figure 54. [...] When a write command requires more capacity than remains on layer 0, the write continues on layer 1 [...] That last sentence leaves room for interpretation. -- Gregoire: what happens if you choose a layer break that is a multipe of 31 and 16 = 496 ? I.e. divide the size of your image by 2 * 2048 = 4096, round up to the next multiple of 496 and use that as layer break. Rob and CJ: what are your magic layer break values which made cdrecord work on DVD+R DL ? Hard... But makes it more exciting. (Neither cdrskin nor growisofs write 31 blocks per command to DVD. We write 16 blocks.) Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
