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: [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: [cdwrite] Re: More Dual-Layer burning oddities
Thomas Schmitt wrote: > Probably CJ Kucera did not test cdrskin or xorriso yet. > I assume he is happy with his cdrecord workaround. Yeah, sorry - I've been meaning to, but I've been pretty busy. I figured I'd just wait until I had occasion to burn another DL disc before trying other things out, which doesn't come along too often. I'll definitely post to let you know what I find once I do, though. > (Has it been verified that it is not just a > deceiving coincidence of capricious > drive+media compatibility effects ?) Nope; I've still got what's left of my current DL spindle to coasterize/burn first, then I'll go try a different brand. And, again, I'll be sure to let the list know. :) Thanks! -CJ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: More Dual-Layer burning oddities
Joerg Schilling wrote: > Then you try to revert what cdrecord does. And this will cause long fixating > times Sorry, don't know what you mean here. I didn't notice any longer fixating time than I've usually seen. -CJ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: More Dual-Layer burning oddities
Joerg Schilling wrote: > So you either have a problem with the medium or with the drives firmware. > Cdrecord computes and uses the right value automatically. Yeah, could be. For now I'm just going to content myself with setting the layer break manually. Clearly you know more about cdrecord internals than I do - I had just assumed from the manpage that using the manual 'layerbreak' option caused the drive to burn in a different mode, which happens to work for me. > What value do you use for the layerbreak? I actually used the value given to me by either cdrecord or growisofs (I forget which one had told me what value it had been using), which was just half of the disc in 2k blocks. In this particular case it was 2035696. > It is a well known problem that some media is unreadable on the second > layer. Yeah, I don't doubt that. The discs I burnt by specifying layerbreak manually seem to work fine, though, so I'm happy enough with that. -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: More Dual-Layer burning oddities
Joerg Schilling wrote: > Are you talking about DVD+ or DVD-? I was talking about my DVD+R/DL discs. > It seems that you confused the cdrecord man page: > > - Layer jump is not available for DVD+ > - Layer jump is not yet implemented for DVD- as the drive I owned > did not like it when I tried to implement it. Here's the relevant bits from my cdrecord manpage on my current version (Cdrecord-ProDVD-ProBD-Clone 2.01.01a38) - I suppose I should have mentioned the version to begin with: > layerbreak >Switch a drive with DVD-R/DL medium into layer jump >recording recording mode and use automatic layer break >position set up. > > layerbreak=value >Set up a manual layer break value for DVD-R/DL and >DVD+R/DL. To me, that implies that layerbreak=value would work for a DVD+R/DL, and plain "layerbreak" would only work for DVD-R/DL. I had just been asking if that was actually the case, or just sort of a typo. > Please explain your problem! > Cdrecord does the right thing with DVD+R without the need for a manual > layer break. A manual layer break is only needed for DVD-Video. I thought that I had. DVD+R/DL discs burned without "layerbreak=value" on my box result in discs which are unreadable past the layer break (at least, I assume that's where it fails, since it's at just about half the size of the disc). Once I threw in a manual layerbreak, the discs that I burnt worked properly. I didn't mention this in the original email, but I haven't yet run any tests on a different batch of discs, to see if it was just the media requiring that flag for me. -CJ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: More Dual-Layer burning oddities
Andy Polyakov wrote: > So it sounds like your unit failed to record data at out-most edge? If it's > really does not depend on media, then I'd say that your unit is > deteriorating and you should consider replacing it... That could be, of course... I burn DL media so infrequently that I really can't eliminate media as a possible factor. The media's still expensive enough that I tend to avoid it if possible. I'll wait until I've had a chance to get another batch of different media, but I'll certainly consider replacing the drive if I'm still having difficulty then. > 'Layer jump' is DVD-R/DL recording mode and it's not supported by growisofs > for reasons discussed at http://fy.chalmers.se/~appro/linux/DVD+RW/-RW/. Ah, interesting, thanks for the link, and for the other info. -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]
More Dual-Layer burning oddities
Hello list - back in January I wrote in about some issues I was having with dual-layer DVD burning, which ended up being solved by a firmware update on my burner. [1] Just recently, I started having issues again, where the burning process (both with growisofs and cdrecord) would *seem* to burn fine, but there'd be an error during the layer flip which caused the disc to be unreadable at that point (ie: halfway through the disc). After a whole lot of investigation and coasters, I found out that I could make use of cdrecord's 'layerbreak' driveropt to result in a disc that was actually readable. I've got two questions about this: 1) The cdrecord manpage mentions that using 'layerbreak' will cause the drive to burn using the 'layer jump' method, as opposed to 'sequential recording.' Is there a way to tell growisofs to do the same thing? I'd rather use growisofs, simply because it avoids the need to create a .iso first, though of course if that's impossible then I'll just use cdrecord. 2) I originally tried using 'layerbreak' without specifying the actual break point, which just resulted in the message "cdrecord: Bad layer break value ''" - I had to manually supply the break point, at which time it burnt properly. The manpage only mentions DVD-R/DL in the section that deals with 'layerbreak' without a specified breakpoint. Does that mean that DVD+R/DL just doesn't support having the breakpoint automatically detected? Thanks! -CJ [1] http://lists.debian.org/cdwrite/2008/01/msg00095.html -- 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: Dual-Layer DVD Burn Failure
Rob Bogus wrote: >My man page says the format is "-speed=2" for that, although I would >expect the program to whine if it didn't know what you meant. Ah, yes, that's what I meant, and what I was actually using. Chalk that up to a transcription error while writing the email. :) >This is one of the rare times I would agree with Joerg that trying >cdrecord is desirable, even though there may be a need to create a huge >ISO image and burn from that. I have not had a problem with either >program, but without some effort I can't tell you which drives and media >I've been using, as I'm not on the right machines. Yeah, no worries. As I just put through, it turns out that a firmware upgrade on the burner itself did the trick. Thanks for the suggestion, though. -CJ -- WOW: Flemmy| "The ships hung in the sky in much the same [EMAIL PROTECTED] |way that bricks don't." - Douglas Adams, 24.24.2.3171 | _The Hitchhiker's Guide To The Galaxy_ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Dual-Layer DVD Burn Failure
CJ Kucera wrote: > So, any ideas would be appreciated. I suppose I could go see if there's > an updated firmware for my drive, perhaps that's what's needed here... Well, I wish I would have thought of that before putting that whole post together, instead of right at the end before I sent it off. I upgraded my drive's firmware from 1.02 to 1.04, and it burned the disc properly. So, clearly my firmware just needed a kicking. Works like a charm now. Thanks anyway, CJ -- WOW: Flemmy| "The ships hung in the sky in much the same [EMAIL PROTECTED] |way that bricks don't." - Douglas Adams, 24.24.2.3171 | _The Hitchhiker's Guide To The Galaxy_ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Dual-Layer DVD Burn Failure
Hello - I'm having some issues burning a dual-layer DVD. Yesterday I burnt my last DVD+R DL disc (Memorex 2.4x) so I got another pack of essentially the same, though this was rated at 8x. It looks like that's the one difference between the two packs of discs. Now, whenever I try to burn to these new discs, I get the following, apparently right around the layer split: > 50.08% done, estimate finish Thu Jan 10 12:28:35 2008 > :-[ [EMAIL PROTECTED] failed with SK=3h/ASC=73h/ACQ=03h]: Input/output error > :-( write failed: Input/output error I know that this corresponds to "POWER CALIBRATION AREA ERROR" but that doesn't help much... I've found plenty of other references to this error online, but it looks like all of those are happening at LBA=0h, right at the start of the disc, not at the layer transition. Since my previous discs were just 2.4x, they were getting burnt at a slower rate. I can't get these discs to burn at anything other than 4.1x, though. I've tried "-speed 1" and "-speed 2" but growisofs always reports: > /dev/dvd: splitting layers at 2061632 blocks > /dev/dvd: "Current Write Speed" is 4.1x1352KBps. > 0.12% done, estimate finish Thu Jan 10 18:26:46 2008 Nothing shows up in dmesg during the burn process. Mostly I'd just really like to find a way to force the burn process to go slower. It seems that the most major thing that's changed is that it's trying to burn faster, which I don't really care about. If I could get it to burn at 2x (I'd even settle for 1x at this point) and have it work, I'd be fine with that. The new, blank discs look like this with dvd+rw-mediainfo: > # dvd+rw-mediainfo /dev/dvd > INQUIRY:[Optiarc ][DVD RW AD-7170A ][1.02] > GET [CURRENT] CONFIGURATION: > Mounted Media: 2Bh, DVD+R Double Layer > Media ID: RITEK/S04 > Current Write Speed: 6.1x1385=8467KB/s > Write Speed #0:6.1x1385=8467KB/s > Write Speed #1:5.1x1385=7056KB/s > Write Speed #2:4.1x1385=5645KB/s > Write Speed #3:3.1x1385=4234KB/s > Write Speed #4:2.0x1385=2822KB/s > Write Speed #5:1.0x1385=1411KB/s > GET [CURRENT] PERFORMANCE: > Write Performance: 4.0x1385=5540KB/[EMAIL PROTECTED] -> 4173824] > Speed Descriptor#0:00/4173824 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s > Speed Descriptor#1:00/4173824 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s > Speed Descriptor#2:00/4173824 [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 of Tracks: 1 > READ TRACK INFORMATION[#1]: > Track State: blank > Track Start Address: 0*2KB > Next Writable Address: 0*2KB > Free Blocks: 4173824*2KB > Track Size:4173824*2KB > ROM Compatibility LBA: 0 > READ CAPACITY: 0*2048=0 It looks like under the "Speed Descriptor" sections that the slowest the disc will support is 4.0x... Is there any way to override that? After the (failed) burn, the disc looks like this: > # dvd+rw-mediainfo /dev/dvd > INQUIRY:[Optiarc ][DVD RW AD-7170A ][1.02] > GET [CURRENT] CONFIGURATION: > Mounted Media: 2Bh, DVD+R Double Layer > Media ID: RITEK/S04 > Current Write Speed: 6.1x1385=8467KB/s > Write Speed #0:6.1x1385=8467KB/s > Write Speed #1:5.1x1385=7056KB/s > Write Speed #2:4.1x1385=5645KB/s > Write Speed #3:3.1x1385=4234KB/s > Write Speed #4:2.0x1385=2822KB/s > Write Speed #5:1.0x1385=1411KB/s > GET [CURRENT] PERFORMANCE: > Write Performance: 4.0x1385=5540KB/[EMAIL PROTECTED] -> 4123264] > Speed Descriptor#0:00/4123264 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s > Speed Descriptor#1:00/4123264 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s > Speed Descriptor#2:00/4123264 [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: 2061632*2KB, can no longer be set > READ DISC INFORMATION: > Disc status: appendable > Number of Sessions:1 > State of Last Session: incomplete > "Next" Track: 1 > Number of Tracks: 1 > READ TRACK INFORMATION[#1]: > Track State: invisible > Track Start Address: 0*2KB > Next Writable Address: 2061632*2KB > Free Blocks: 2061632*2KB > Track Size:4123264*2KB > ROM Compatibility LBA: 0 > READ CAPACITY: 0*2048=0 The last 2.4x disc that I had burnt successfully yesterday looks like so: > # dvd+rw-mediainfo /dev/dvd > INQUIRY:
