Re: [Cdw-devel] Bugs prior to 0.5 release

[<cdw...@li...>]

On Wed, Jul 14, 2010 at 03:40:30PM -0800, cdw...@li... wrote:
>On Wed, Jul 14, 2010 at 03:23:36PM -0800, cdw...@li... wrote:
>>On Wed, Jul 14, 2010 at 03:12:42PM -0800, cdw...@li... wrote:
>>>14) Time Time Until Completion dialog doesn't seem correct with growisofs.
>>>
>>>although I see within stderr:
>>>cdw_growisofs_pr_handle_writing_data():669: INFO: submatch 15, minutes
>>>remaining: "34" -> 34
>>>cdw_growisofs_pr_handle_writing_data():676: INFO: submatch 16, seconds
>>>remaining: "02" -> 2
>>>cdw_growisofs_pr_handle_writing_data():711: INFO: progress_string = "0.1/2.6
>>>MB"
>>>cdw_growisofs_pr_handle_writing_data():716: INFO: done / total = 0.051933 /
>>>2.596674 (task: burn from files)
>>>cdw_growisofs_pr_handle_writing_data():742: INFO: ETA: minutes = 34, seconds =
>>>2 -> string = "ETA: 34:02"
>>>cdw_growisofs_pr_handle_writing_data():655: INFO: submatch 6, decimal part of
>>>percentage: "3" -> 3
>>>cdw_growisofs_pr_handle_writing_data():662: INFO: submatch 7, fractional part
>>>of percentage: "0" -> 0
>>>cdw_growisofs_pr_handle_writing_data():669: INFO: submatch 15, minutes
>>>remaining: "24" -> 24
>>>cdw_growisofs_pr_handle_writing_data():676: INFO: submatch 16, seconds
>>>remaining: "06" -> 6
>>>cdw_growisofs_pr_handle_writing_data():711: INFO: progress_string = "0.1/2.6
>>>MB"
>>>cdw_growisofs_pr_handle_writing_data():716: INFO: done / total = 0.077900 /
>>>2.596674 (task: burn from files)
>>>cdw_growisofs_pr_handle_writing_data():742: INFO: ETA: minutes = 24, seconds =
>>>6 -> string = "ETA: 24:06"
>>>
>>>I know a 3.2M file doesn't take this long to write.  And then I see ETA jump down
>>>from 34 minutes to approximately 5 minutes (guessing) during the writing.
>>>
>>> ... SNIP ...
>>>
>>>syslog is dumping this:
>>>
>>>14 15:04:30 [kernel] sr 1:0:0:0: [sr0] Unhandled sense code
>>>Jul 14 15:04:30 [kernel] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
>>>Jul 14 15:04:30 [kernel] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
>>>Jul 14 15:04:30 [kernel] sr 1:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error
>>>Jul 14 15:04:30 [kernel] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
>>>Jul 14 15:04:30 [kernel] end_request: I/O error, dev sr0, sector 0
>>>Jul 14 15:04:30 [kernel] Buffer I/O error on device sr0, logical block 0
>>>Jul 14 15:04:40 [kernel] sr 1:0:0:0: [sr0] Unhandled sense code
>>>Jul 14 15:04:40 [kernel] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
>>>Jul 14 15:04:40 [kernel] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current]
>>>Jul 14 15:04:40 [kernel] sr 1:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error
>>>Jul 14 15:04:40 [kernel] sr 1:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
>>>Jul 14 15:04:40 [kernel] end_request: I/O error, dev sr0, sector 0
>>>Jul 14 15:04:40 [kernel] Buffer I/O error on device sr0, logical block 0
>>>
>>>
>>>Seems like redundant duplicate errors, including the last error.
>>>
>>>At this point, I just usually toss the RW media -- seems it only lasts sometimes a few writes. :-/
>>>
>>>Or am I dumb and not realizing something???
>>
>>
>>... I forgot to add, it looks like the write was successful via commandline, but a long one for 3.2M!!!
>>
>>    2981888/3330048 (89.5%) @0.0x, remaining 1:51 RBU   1.1% UBU 100.0%
>>    3014656/3330048 (90.5%) @0.0x, remaining 1:40 RBU   1.0% UBU 100.0%
>>    3014656/3330048 (90.5%) @0.0x, remaining 1:40 RBU   1.0% UBU 100.0%
>>    3014656/3330048 (90.5%) @0.0x, remaining 1:40 RBU   1.0% UBU 100.0%
>>builtin_dd: 1632*2KB out @ average 0.0x1352KBps
>>/dev/dvdrw: flushing cache
>>/dev/dvdrw: writing lead-out
>>/dev/dvdrw: reloading tray
>>
>>real    20m17.912s
>>user    0m0.015s
>>sys     0m0.272s
>>
>>
>>Mounting the medium fails with similar syslog.
>
>And, it's interesting to note here, growisofs is now calling "DVD+RW format"?
>
>$ growisofs -dvd-compat -Z /dev/dvdrw=/tmp/tmp.iso
>Executing 'builtin_dd if=/tmp/tmp.iso of=/dev/dvdrw obs=32k seek=0'
>/dev/dvdrw: restarting DVD+RW format...
>/dev/dvdrw: "Current Write Speed" is 2.5x1352KBps.
>builtin_dd: 1632*2KB out @ average 0.8x1352KBps
>/dev/dvdrw: flushing cache
>/dev/dvdrw: writing lead-out
>/dev/dvdrw: reloading tray
>
>
>I'm pretty sure this DVD+RW disc is an official coaster now.

Ok. Another DVD+RW, using command line growisofs, seems toasted?
# mount /dev/sr0 /mnt/dvd
mount: /dev/sr0: can't read superblock

I've found it's growisofs calling media reload (disc eject) too.  So this is
likely the reason CDW ejects, then reloads, then ejects a DVD.

Think I'm just going to reboot and see if this is a dvdrom driver issue or this
is just old media.  I'm curious as to your insite, whether the only way we can
see if a media is good is via md5sum checking after a write?  In other words,
we don't know if a media is good, even though syslog has errors (this last
write attempt showed no errors until trying to mount).

-- 
Roger
http://rogerx.freeshell.org/