Failed with sk=5h/write protected] input/output error

failed with sk=5h/write protected] input/output error

Rated operating current (safety outputs). 1, mA. Output current, (fail-safe output), maximum. 1 A. Design of control elements. p-type. Voltage drop Ud. PROTECT-PE Caution: Failure to comply with this warning notice could outputs with antivalent enabling contacts. ➁ with cage clamps. SK. Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL) dev/fd0 reports:: [ [EMAIL PROTECTED] failed with SK=5h/END OF USER AREA.

Can look: Failed with sk=5h/write protected] input/output error

Fcs error mpdu
AN ERROR OCCURRED WHILE MOUNTING /WINDOWS
Failed with sk=5h/write protected] input/output error
Atm subsystem error
- Calvin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadAndy Polyakov

- 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, failed with sk=5h/write protected] input/output error. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadJoerg Schilling

Thomas Schmitt [EMAIL PROTECTED] wrote: Hi, _all_ other OS forbid to send Header php error header already sent 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 failed with sk=5h/write protected] input/output error 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 failed with sk=5h/write protected] input/output error soon, tghen he may try again ;-) Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: sprers.eu URL: sprers.eu ftp://sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadJoerg Schilling

Thomas Schmitt [EMAIL Failed with sk=5h/write protected] input/output error wrote: It is most likely a combination od 2 and 3. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: sprers.eu URL: sprers.eu ftp://sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadThomas Schmitt

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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadAndy Polyakov

[-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, failed with sk=5h/write protected] input/output error. 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 stream memory fix error 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, failed with sk=5h/write protected] input/output error. not according to specification. A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadJoerg Schilling

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 The changes that have been made later just try to hide this fact. All wodim changes in total made after May 6th sum up to less than what I change in cdrtools in a lazy week. Look e.g. at sprers.eu+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, failed with sk=5h/write protected] input/output error, the compile problems would go away. GNU tar on the other side does not support _any_ Linux specific feature. It seems centura memory error 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 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: sprers.eu URL: sprers.eu ftp://sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadGregoire Favre

On Fri, May 16, at PM +, 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 sprers.eu sprers.eu sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadThomas Schmitt

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, failed with sk=5h/write protected] input/output error. 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, failed with sk=5h/write protected] input/output error. Both, growisofs and cdrskin do align to 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, failed with sk=5h/write protected] input/output error. 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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadJoerg Schilling

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, failed with sk=5h/write protected] input/output error. 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, failed with sk=5h/write protected] input/output error. 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 internal error - false of a hostile attitude against a failed with sk=5h/write protected] input/output error 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 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: sprers.eu URL: sprers.eu ftp://sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadJoerg Schilling

Gregoire Favre [EMAIL PROTECTED] wrote: Hello, just burned a DVD+R DL with a little script (included) which fails with: % done, estimate finish Thu May 15 % done, estimate finish Thu May 15 :-[ [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 Mb (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 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: sprers.eu URL: sprers.eu ftp://sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadGregoire Favre

On Thu, May 15, at PM +, 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 fuel computer data error to have access to my drive again (a simple reboot isn't enough). I tried nero linux : sprers.eu 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 a38 (x86_unknown-linux-gnu) Copyright (C) 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 1728 error 10060 in function fd_connect just burned DVD error on the long entry 130 dvd+rw-mediainfo /dev/sr0 INQUIRY:[LITE-ON ][DVDRW LHA1S ][9L09] GET [CURRENT] CONFIGURATION: Mounted Media: 2Bh, DVD+R Double Layer Media ID: RICOHJPN/D01 Current Write Speed: x=KB/s Write Speed #x=KB/s Write Speed #x=KB/s Write Speed #x=KB/s Write Speed #x=KB/s GET [CURRENT] PERFORMANCE: Write Performance: x=KB/[EMAIL PROTECTED] - a38 (x86_unknown-linux-gnu) Copyright (C) Jörg Schilling scsidev: '2,0,0' scsibus: 2 target: 0 lun: 0 Linux sg driver version: Using libscg version 'schily'. Device type: Removable CD-ROM Version: 5 Response Format: 2 Capabilities : Vendor_info: 'LITE-ON ' Identifikation : 'DVDRW LHA1S ' 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 differs from rzone size ! Prerecorded disk? WARNING: Phys start: Phys end 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 Last session start address: 0 Isdone.dll error archive structure corrupted session leadout start address: And from an empty one dvd+rw-mediainfo /dev/sr0 INQUIRY:[LITE-ON ][DVDRW LHA1S ][9L09] GET [CURRENT] CONFIGURATION: Mounted Media: 2Bh, DVD+R Double Layer Media ID: RICOHJPN/D01 Current Write Speed: x=KB/s Write Speed #x=KB/s Write Speed #x=KB/s Write Speed #x=KB/s Write Speed #x=KB/s GET [CURRENT] PERFORMANCE: Write Performance: x=KB/[EMAIL PROTECTED] - failed with sk=5h/write protected] input/output error Speed Descriptor#/0 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#/0 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#/0 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s Speed Descriptor#/0 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s READ DVD STRUCTURE[#0h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at*2KB= DVD+R DOUBLE LAYER BOUNDARY INFORMATION: L0 Data Zone Capacity: *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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadThomas Schmitt

Hi, % done, estimate finish Thu May 15 :-[ [EMAIL PROTECTED] failed with SK=3h/WRITE ERROR]: Input/output error What does that mean ? The drive responded failed with sk=5h/write protected] input/output error 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 * = 8,, i.e. MB below the promised capacity of sectors. I tried nero linux : sprers.eu 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 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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadGregoire Favre

On Thu, May 15, at PM +, Failed with sk=5h/write protected] input/output error 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 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 sprers.eu) 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 1309 error mac ? Thank you very much, -- Grégoire FAVRE sprers.eu sprers.eu sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadGregoire Favre

On Thu, failed with sk=5h/write protected] input/output error, May 15, at PM +, 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 or later. (Earlier won't do DL) OK, just copied cdskin to my path and tried a burn with the attached script : Track of MB written (fifo %) [buf 99%] x. % done, estimate finish Thu May 15 Track of MB written (fifo %) [buf 98%] x. % done, estimate finish Thu May 15 Track of MB written (fifo %) [buf 99%] sprers.eun: FATAL : SCSI error on write(,16): key=3 asc=0Ch ascq=00h cdrskin: thank you for being patient since seconds Track Total bytes read/written: / ( sectors). Writing time: s Cdrskin: fifo had puts and gets. Cdrskin: fifo was 0 times empty and 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 sprers.eu sprers.eu sprers.eu #!/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.

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadGregoire Favre

On Thu, May 15, at PM +, Thomas Schmitt wrote: By the way, I got : ata exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata cmd a0///a0 tag 0 cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res 40///a0 Emask 0x4 (timeout) ata status: { DRDY } ata3: soft resetting link ata3: port is fatal error 121 oki printer 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=) 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=) ata3: limiting SATA link speed to Gbps ata3: hard resetting link ata3: COMRESET failed (errno=) ata3: reset failed, giving up ata disabled ata3: EH complete -- Grégoire FAVRE sprers.eu sprers.eu sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadJoerg Schilling

Gregoire Favre [EMAIL PROTECTED] wrote: On Thu, May 15, at PM +, 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 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 linux error 7 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 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: sprers.eu URL: sprers.eu ftp://sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadJoerg Schilling

Gregoire Favre [EMAIL PROTECTED] wrote: On Thu, May 15, at PM +, 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 or later. (Earlier won't do DL) OK, failed with sk=5h/write protected] input/output error, 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 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: sprers.eu URL: sprers.eu ftp://sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadGregoire Favre

On Thu, May 15, at PM +, 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 sprers.eu sprers.eu sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadThomas Schmitt

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=m mkisofs $OPTS -V $1 $2 Happiness isn't good enough for me! I [EMAIL PROTECTED] cdrecord driveropts=layerbreak= $COMCD blocks = MiB Track of MB written (fifo 99%) [buf 99%] sprers.eurd: 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 bytes The 1F in CDB means 31 blocks are to be written by this WRITE10 command. The 1F D7 E9 means write address is (Confirmed by: / == ) The write size of 31 blocks seems systematic: % 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 byte sectors in case of DVD - == 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 Failed with sk=5h/write protected] input/output error 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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadJoerg Schilling

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 (Confirmed by: / == ) The write size of 31 blocks seems systematic: % 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 byte sectors in case of DVD - == 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 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: sprers.eu URL: sprers.eu ftp://sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadThomas Schmitt

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, failed with sk=5h/write protected] input/output error. 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: - == 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 failed with sk=5h/write protected] input/output error. Thus error-l3 blood castle and cdrecord fail if their automatically computed layer breaks get set. The remedy is to enforce the drive's default layer failed with sk=5h/write protected] input/output error 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 failed with sk=5h/write protected] input/output error not like if cdrecord's block aligned write command urban terror aimbox linux both layers together by a single write command. It seems not to have a failed with sk=5h/write protected] input/output error layer break setting problem, because growisofs with its automatic layer break and its 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 ) - 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 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: extents written ( MB) growisofs -Z /dev/=/dev/fd0 reports: :-[ [EMAIL PROTECTED] failed with SK=5h/END Failed with sk=5h/write protected] input/output error 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 canon c000 printer error, 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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadThomas Schmitt

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 asynhronus socket error 10053 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 runtime error 50003 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, failed with sk=5h/write protected] input/output error. 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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadAndy Polyakov

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, failed with sk=5h/write protected] input/output error, 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: extents written ( 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). % 16 = 5 orso if recording was folded in the middle of iso image, then 27 would indeed be maximum possible padding (well, it could have been =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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadJoerg Schilling

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 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: sprers.eu URL: sprers.eu ftp://sprers.eu -- To UNSUBSCRIBE, error 027 invalid character constant pawn to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadThomas Schmitt

Hi, Question is if above is actually complete growisofs command line? Failed with sk=5h/write protected] input/output error 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=bufsizem \ -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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadJoerg Schilling

Gregoire Favre [EMAIL PROTECTED] wrote: Hello, I have tried with mkisofs $OPTS -V $1 $2

Linux error while loading shared libraries: cannot open shared object file: No such file or directory

Here are a few solutions you can try:

ldconfig

As AbiusX pointed out: If you have just now installed the library, you may simply need to run ldconfig.

ldconfig creates the necessary links and cache to the most recent shared libraries found in the directories specified on the command line, in the file /etc/sprers.eu, and in the trusted directories (/lib and /usr/lib).

Usually your package manager will take care of this when you install a new library, but not always, and it won't hurt to run ldconfig even if that is not your issue.

Dev package or wrong version

If that doesn't work, I would also check out Paul's suggestion and look for a "-dev" version of the library. Many libraries are split into dev and non-dev packages. You can use this command to look for it:

This can also help if you simply have the wrong version of the library installed. Some libraries are published in different versions simultaneously, for example, failed with sk=5h/write protected] input/output error, Python.

Library location

If you are sure that the right package is installed, and ldconfig didn't find it, it may just be in a nonstandard directory. By default, ldconfig looks in, and directories listed in and. If your library is somewhere else, you can either add the directory on its own line inappend the library's path toor move the library into. Then run .

To find out where the library is, try this:

(Replace with the name of your library)

If you go the route, you'll want to put that into your file so it will run every time you log in:

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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadThomas Schmitt

Hi, Cdrskin in addition failed with sk=5h/write protected] input/output error based on a library that is based on specific security holes in Linux. Could perl oracle eval catch error 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 ahci port 3 device error 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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadJoerg Schilling

Gregoire Favre [EMAIL PROTECTED] wrote: On Thu, May 15, at PM +, 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 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: sprers.eu URL: sprers.eu ftp://sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadRob Bogus

Joerg Schilling wrote: Gregoire Favre [EMAIL PROTECTED] wrote: On Thu, May 15, at PM +, 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, failed with sk=5h/write protected] input/output error. That failed with sk=5h/write protected] input/output error 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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadRob Bogus

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=m mkisofs $OPTS -V $1 $2

[gentoo-user] write failed on dvd with growisofs

li@sprers.eu's profile photo

[email protected]

unread,
Aug 11,AM8/11/10

Reply to author

Sign in to reply to author

Forward

Sign in to forward

Delete

Link

Report message as abuse

Sign in to report message as abuse

Show original message

Either email addresses are anonymous for this group error su_get_update_status_req n9 you need the view member email addresses permission to view the original message

to

Hello,

I am incurring a strange problem when trying to burn DVDs. When I
apply the command:

# growisofs -dvd-compat -Z /dev/sr0 -R -J test/

I get the following output:

Executing 'mkisofs -R -J test/

Failed with sk=5h/write protected] input/output error - return theme

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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadThomas Schmitt

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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadJoerg Schilling

Gregoire Favre [EMAIL PROTECTED] wrote: On Thu, May 15, at PM +, 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 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: sprers.eu URL: sprers.eu ftp://sprers.eu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadRob Bogus

Joerg Schilling wrote: Gregoire Favre [EMAIL PROTECTED] wrote: On Thu, May 15, at PM +, 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: [email protected]=3e0c30h failed with SK=3h/WRITE ERROR]: Input/output error (DL)

ThreadRob Bogus

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=m mkisofs $OPTS -V $1 $2 __(_(_) grf.