Re: problem burning DVD-R with PX708A
I've finally had the time to try these DVD-R's which report themselves as MXL
RG01 on another burner (an unknown atapi clone borrowed from a friend) and
then growisofs reported them as 2X DVD-R and burnt them successfully with a
-speed=1.
Then I tried a DVD+R (Mirror 4X DVD+R) with my drive. Here is what it
reported:
-> dvd+rw-mediainfo /dev/dvd
INQUIRY: [PLEXTOR ][DVDR PX-708A ][1.04]
GET [CURRENT] CONFIGURATION:
Mounted Media: 1Bh, DVD+R
Media ID: IS01/001
Current Write Speed: 2.4x1385=3324KB/s
Write Speed #0: 4.0x1385=5540KB/s
Write Speed #1: 2.4x1385=3324KB/s
GET [CURRENT] PERFORMANCE:
Write Performance: 6.0x1385=8310KB/s@[0 -> 385023]
8.0x1385=11080KB/s@[385024 -> 2295103]
Speed Descriptor#0: 02/2295104 R@8.0x1385=11080KB/s W@4.0x1385=5540KB/s
Speed Descriptor#1: 02/2295104 R@8.0x1385=11080KB/s W@2.4x1385=3324KB/s
:-[ READ DVD STRUCTURE#0 failed with SK=5h/ASC=24h/ACQ=00h]: Input/output
error
READ DISC INFORMATION:
Disc status: blank
Number of Sessions: 1
State of Last Session: empty
Number of Tracks: 1
READ TRACK INFORMATION[#1]:
Track State: blank
Track Start Address: 0*2KB
Next Writable Address: 0*2KB
Free Blocks: 2295104*2KB
Track Size: 2295104*2KB
And then
growisofs -Z /dev/dvd=Input.iso
Executing 'builtin_dd if=Input.iso of=/dev/dvd obs=32k seek=0'
/dev/dvd: "Current Write Speed" is 6.1x1385KBps.
0/4669931520 ( 0.0%) @0x, remaining ??:??
5603328/4669931520 ( 0.1%) @1.2x, remaining 138:44
16777216/4669931520 ( 0.4%) @2.4x, remaining 60:05
27983872/4669931520 ( 0.6%) @2.4x, remaining 46:59
and so on.
It actually succeeded, and the disk works all right. But I'm stil surprised
with the mediainfo error and the initial 6.1X speed.
Unfortunately I have no windows to try plextor's own tools. I'd like to see if
they've got some kind of magical option to burn anything regardless of what
the media would report. Do you think the firmware would embed a database of
supported media ??? and require an upgrade for every new product on the
market.
Thanx again for the support. I'm quite sure now it's a drive's issue. I'll
have to keep an eye on their news.
Nynal
Reply to: