CJ Kucera wrote:
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:
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.
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.
/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: [Optiarc ][DVD RW AD-7170A ][1.02]
GET [CURRENT] CONFIGURATION:
Mounted Media: 2Bh, DVD+R Double Layer
Media ID: RITEK/D01
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: 2.4x1385=3324KB/[EMAIL PROTECTED] -> 4026160]
Speed Descriptor#0: 00/4026160 [EMAIL PROTECTED]/s [EMAIL PROTECTED]/s
READ DVD STRUCTURE[#0h]:
Media Book Type: 00h, DVD-ROM book [revision 0]
Legacy lead-out at: 2013088*2KB=4122804224
DVD+R DOUBLE LAYER BOUNDARY INFORMATION:
L0 Data Zone Capacity: 2013088*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: partial/complete
Track Start Address: 0*2KB
Free Blocks: 0*2KB
Track Size: 4026160*2KB
FABRICATED TOC:
Track#1 : [EMAIL PROTECTED]
Track#AA : [EMAIL PROTECTED]
Multi-session Info: [EMAIL PROTECTED]
READ CAPACITY: 4026160*2048=8245575680
That disc was burnt somewhere around 2x. Presumably it had given me a
note about burning at 2.4x at the beginning of the burn.
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...
-CJ
--
E. Robert Bogusta
It seemed like a good idea at the time
