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

dvd+rw-tools: another CLOSE SESSION failed



Hi.

I encountered an issue when using growisofs 7.1 under debian testing.

Usually, I use the following settings when writing DVD-Rs:

>$ growisofs -speed=4 -Z /dev/sr0 -volid "smth.1" -volset
> "SMTH" -volset-size 1 -volset-seqno 1 -rational-rock -udf -iso-level
> -full-iso9660-filenames ./dir-with-data

I've tried to write BD-R in the same way, and got this error:

> 99.94% done, estimate finish Tue Jan 15 22:55:11 2013
>Total translation table size: 0
>Total rockridge attributes bytes: 15521
>Total directory bytes: 4096
>Path table size(bytes): 24
>Max brk space used 23000
>7029088 extents written (13728 MB)
>builtin_dd: 7029088*2KB out @ average 1.6x4390KBps
>/dev/sr0: flushing cache
>/dev/sr0: closing track
>/dev/sr0: closing session
>:-[ CLOSE SESSION failed with SK=5h/INVALID FIELD IN CDB]:>
>Input/output error /dev/sr0: reloading tray

Despite the error, the disc mounts without any problems, and all files
on it match their md5-checksums. Here is dvd+rw-mediainfo output:

>INQUIRY:                [ASUS    ][BW-12D1S-U      ][E102]
>GET [CURRENT] CONFIGURATION:
> Mounted Media:         41h, BD-R SRM+POW
> Media ID:              VERBAT/IMe
> Current Write Speed:   12.0x4495=53940KB/s
> Write Speed #0:        12.0x4495=53940KB/s
> Write Speed #1:        10.0x4495=44950KB/s
> Write Speed #2:        8.0x4495=35960KB/s
> Write Speed #3:        6.0x4495=26970KB/s
> Write Speed #4:        4.0x4495=17980KB/s
> Write Speed #5:        2.0x4495=8990KB/s
> Speed Descriptor#0:    00/12088319 R@12.0x4495=53940KB/s
> W@12.0x4495=53940KB/s Speed Descriptor#1:    00/12088319
> R@10.0x4495=44950KB/s W@10.0x4495=44950KB/s Speed Descriptor#2:
> 00/12088319 R@8.0x4495=35960KB/s W@8.0x4495=35960KB/s Speed
> Descriptor#3:    00/12088319 R@6.0x4495=26970KB/s
> W@6.0x4495=26970KB/s Speed Descriptor#4:    00/12088319
> R@4.0x4495=17980KB/s W@4.0x4495=17980KB/s Speed Descriptor#5:
> 00/12088319 R@2.0x4495=8990KB/s W@2.0x4495=8990KB/s
>POW RESOURCES INFORMATION:
> Remaining Replacements:16843296
> Remaining Map Entries: 0
> Remaining Updates:     0
>READ DISC INFORMATION:
> Disc status:           appendable
> Number of Sessions:    1
> State of Last Session: incomplete
> "Next" Track:          1
> Number of Tracks:      2
>READ TRACK INFORMATION[#1]:
> Track State:           partial incremental
> Track Start Address:   0*2KB
> Free Blocks:           0*2KB
> Track Size:            7029088*2KB
>READ TRACK INFORMATION[#2]:
> Track State:           invisible incremental
> Track Start Address:   7029088*2KB
> Next Writable Address: 7029088*2KB
> Free Blocks:           5059232*2KB
> Track Size:            5059232*2KB
>FABRICATED TOC:
> Track#1  :             14@0
> Track#AA :             14@12088320
> Multi-session Info:    #1@0
>READ CAPACITY:          12088320*2048=24756879360

And I am very confused by the content of the READ DISC INFORMATION
section. Also, there are several mentions about this error in adjacent
threads, but any solution has not been found. And I'm sure that this
error is exactly the growisofs problem — when I write the same data as
a pre-created image using cdrskin (w/ defectmgt enabled) media-info
output looks like this:

>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 incremental
> Track Start Address:   0*2KB
> Free Blocks:           0*2KB
> Track Size:            7029088*2KB
> Last Recorded Address: 7029087*2KB
>FABRICATED TOC:
> Track#1  :             14@0
> Track#AA :             14@7029088
> Multi-session Info:    #1@0
>READ CAPACITY:          7029088*2048=14395572224

Actually, the BD-Rs stopped being so expensive (due to LTH), so let's
find is the cause of this error.

P.S. For clarity: my Asus drive is a full clone of Pioneer BDR-206BK.

P.S.2. I still do not understand how cdrskin works when Defect
Management enabled. When I use the "blank=format_defectmgt" cdrskin
makes two separate passes: formatting and recording. In growisofs it
looks like a single pass, but it takes the same time. Which approach is
more correct?


Reply to: