[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problems with dvd+rw-tools 6 and Pioneer drive

My attempts to burn data DVD's with k3b and dvd+rw-tools were not
going well (I saw errors like
:-? the LUN appears to be stuck writing LBA=30310h, retry in 47ms
and got I/O errors when attempting to read the resulting disks.)
See the thread at
for details.

As implied in thread in question the fatal failures [like "retry in 0 ms" and failure to close disc/session at the end of recording] are indeed fixed in dvd+rw-tools 6.0. Remaining "appears to be stuck" are pure warnings, which can be safely ignored. growisofs normally attempts to hide them and shows them only when it appears abnormal from a viewpoint of cautious programmer such as myself. The last part means that if I at some point feel that it's 100% appropriate to just hide this warnings and that they add no value whatsoever to troubleshooting, I will just remove them. But till then you have to/can simply ignore them.

First, although the drive and media supposedly can do 16x, and
mediainfo says they can do 12x, and v 5 of dvd tools said 12x,

Maximum speed for particular media is between your firmware and media manufacturer and is beyond application control. In other words if dvd+rw-mediainfo says 12x is max, no application will make it run in 16x in *your* unit even if emballage says it's 16x.

this version says 6x is the speed. While slow and reliable is better than
fast and unreliable, I'd prefer fast and reliable :)  Also, it's not
apparent to me where the decision to go with 6x is getting made.

K3b sends -speed argument unconditionally and it apparently gets misinterpreted. This is apparently second similar report, so I'll have to look into it...

Second, one of the 2 successful burns showed this in the log
   1605632/4079517696 ( 0.0%) @0.0x, remaining 804:15 RBU 100.0%
:-? the LUN appears to be stuck writing LBA=310h, keep retrying in 94ms
   1605632/4079517696 ( 0.0%) @0.0x, remaining 931:14 RBU 100.0%

Both show a very slow startup, though I gather this may be normal.

Yes, it is normal.

I see the code is littered with special cases for Pioneer drives.  Are
they defective, or just weird?

Pioneer apparently adheres to Mt.Fuji specification, which slightly diverges from MMC specification, the one growisofs was originally coded after [and the one a lot of manufacturers adhere to]. Drives are not defective, rather "weird," but it's their conscious choice we have to simply deal with. This divergence between specifications is the very reason for fatal failure to close disk/session at the end of recording [as discussed at the end on http://fy.chalmers.se/~appro/linux/DVD+RW/hcn.html]. As for fatal failure in the middle of recording with "retry in 0ms," this one is just a firmware bug [which appears in newer >8x drives as code was working flawlessly till they started to appear on the market]. A.

Reply to: