libburn writes corrupted data

[squisher]

When I write an iso with test/libburner, and verify the files on disc afterwards, I get errors. The same does not happen when the iso is written by wodim. The verify of the libburner burned DVD is much slower than the wodim burned one.

dmesg says:

hdb: BENQ DVD LS DW1655, ATAPI CD/DVD-ROM drive
hdb: selected mode 0x42
hdb: ATAPI 94X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)

syslog says:

Feb  2 23:51:10 alucardo kernel: hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
Feb  2 23:51:10 alucardo kernel: hdb: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 }
Feb  2 23:51:10 alucardo kernel: ide: failed opcode was: unknown
Feb  2 23:51:10 alucardo kernel: ATAPI device hdb:
Feb  2 23:51:10 alucardo kernel:   Error: Medium error -- (Sense key=0x03)
Feb  2 23:51:10 alucardo kernel:   Unrecovered read error -- (asc=0x11, ascq=0x00)
Feb  2 23:51:10 alucardo kernel:   The failed "Read 10" packet command was: 
Feb  2 23:51:10 alucardo kernel:   "28 00 00 20 3b ed 00 00 40 00 00 00 00 00 00 00 "
Feb  2 23:51:10 alucardo kernel: end_request: I/O error, dev hdb, sector 8449972
Feb  2 23:51:10 alucardo kernel: printk: 118 messages suppressed.
Feb  2 23:51:10 alucardo kernel: Buffer I/O error on device hdb, logical block 2112493
Feb  2 23:51:10 alucardo kernel: Buffer I/O error on device hdb, logical block 2112494
Feb  2 23:51:10 alucardo kernel: Buffer I/O error on device hdb, logical block 2112495
Feb  2 23:51:10 alucardo kernel: Buffer I/O error on device hdb, logical block 2112496
Feb  2 23:51:10 alucardo kernel: Buffer I/O error on device hdb, logical block 2112497
Feb  2 23:51:10 alucardo kernel: Buffer I/O error on device hdb, logical block 2112498
Feb  2 23:51:10 alucardo kernel: Buffer I/O error on device hdb, logical block 2112499
Feb  2 23:51:10 alucardo kernel: Buffer I/O error on device hdb, logical block 2112500
Feb  2 23:51:10 alucardo kernel: Buffer I/O error on device hdb, logical block 2112501
Feb  2 23:51:10 alucardo kernel: Buffer I/O error on device hdb, logical block 2112502
Feb  2 23:51:10 alucardo kernel: hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
Feb  2 23:51:10 alucardo kernel: hdb: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 }
Feb  2 23:51:10 alucardo kernel: ide: failed opcode was: unknown
Feb  2 23:51:10 alucardo kernel: ATAPI device hdb:
Feb  2 23:51:10 alucardo kernel:   Error: Medium error -- (Sense key=0x03)
Feb  2 23:51:10 alucardo kernel:   Unrecovered read error -- (asc=0x11, ascq=0x00)
Feb  2 23:51:10 alucardo kernel:   The failed "Read 10" packet command was: 
Feb  2 23:51:10 alucardo kernel:   "28 00 00 20 3b ed 00 00 02 00 00 00 00 00 00 00 "
Feb  2 23:51:10 alucardo kernel: end_request: I/O error, dev hdb, sector 8449972

[scdbackup]

Without wanting to make any excuses: this looks like a media problem.

The analog quality of recording is in the realm of the burner device and its firmware. Programs like wodim or libburner can only request certain settings about speed or burn-proof. Especially DVD are quite free of opportunities for low-level tuning.

It could possibly be about a difference in parameters given to wodim and those chosen automatically by libburner.

Feb  2 23:51:10 alucardo kernel:   "28 00 00 20 3b ed 00 00 40 00 00 00 00 00 00 00 "
Feb  2 23:51:10 alucardo kernel: end_request: I/O error, dev hdb, sector 8449972
Feb  2 23:51:10 alucardo kernel: printk: 118 messages suppressed.
Feb  2 23:51:10 alucardo kernel: Buffer I/O error on device hdb, logical block 2112493

The problem happens quite near the end of a single layer DVD at 4125 MiB, 4.326 merchand's GB. Did wodim have to write a similar amount of data in your test ?

How many wodim success and libbuner failures so far ?

Again: no attempt to make excuses. But my personal experience is that such problems are finally not so much about the underlying program capabilities but about media-drive compatibility.

Could you give me the exact command lines used with wodim and libburner.

How does cdrskin/cdrskin when you use it with the wodim options ?

What do you get if you examine both wodim and libburner media with

test/telltoc --drive /dev/hdb

If you have dvd+rw-tools installed, the outputs of this command could possibly show other decisive differences.

dvd+rw-mediainfo /dev/hdc

[squisher]

wodim burn

Command line options: none

telltoc

Media current: DVD-R sequential recording
Media status : is written , is closed
Media reuse  : is not erasable
Avail. speed : max=16.0  , min=4.0
Speed unit 1x: 1385.0 kB/s  (DVD)
Speed descr. : 22160 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 16620 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 11080 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 5540 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 22160 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 16620 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 11080 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 5540 kB/s, 4198.7 MiB, DVD-R sequential recording
Format status: formatted, with 4198.7 MiB
Media content: session  1  track     1 data   lba:         0    00:02:00
Media content: session  1  leadout            lba:   2149728   477:45:03

dvd+rw-mediainfo

INQUIRY:                [BENQ    ][DVD LS DW1655   ][BCIB]
GET [CURRENT] CONFIGURATION:
 Mounted Media:         11h, DVD-R Sequential
 Current Write Speed:   16.0x1385=22160KB/s
 Write Speed #0:        16.0x1385=22160KB/s
 Write Speed #1:        12.0x1385=16620KB/s
 Write Speed #2:        8.0x1385=11080KB/s
 Write Speed #3:        4.0x1385=5540KB/s
GET [CURRENT] PERFORMANCE:
 Write Performance:     16.0x1385=22160KB/s@[0 -> 2149727]
 Speed Descriptor#0:    00/2149727 R@6.7x1385=9276KB/s W@16.0x1385=22160KB/s
 Speed Descriptor#1:    00/2149727 R@6.7x1385=9276KB/s W@12.0x1385=16620KB/s
 Speed Descriptor#2:    00/2149727 R@6.7x1385=9276KB/s W@8.0x1385=11080KB/s
 Speed Descriptor#3:    00/2149727 R@6.7x1385=9276KB/s W@4.0x1385=5540KB/s
READ DVD STRUCTURE[#10h]:
 Media Book Type:       00h, DVD-ROM book [revision 0]
 Legacy lead-out at:    2298496*2KB=4707319808
READ DVD STRUCTURE[#0h]:
 Media Book Type:       25h, DVD-R book [revision 5]
 Last border-out at:    2045*2KB=4188160
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:           complete
 Track Start Address:   0*2KB
 Free Blocks:           0*2KB
 Track Size:            2149728*2KB
 Last Recorded Address: 2149727*2KB
FABRICATED TOC:
 Track#1  :             14@0
 Track#AA :             17@2149728
 Multi-session Info:    #1@0
READ CAPACITY:          2149728*2048=4402642944

libburn/xfburn

telltoc

Media current: DVD-R sequential recording
Media status : is written , is closed
Media reuse  : is not erasable
Avail. speed : max=16.0  , min=4.0
Speed unit 1x: 1385.0 kB/s  (DVD)
Speed descr. : 22160 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 16620 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 11080 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 5540 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 22160 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 16620 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 11080 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 5540 kB/s, 4199.0 MiB, DVD-R sequential recording
Format status: formatted, with 4199.0 MiB
Media content: session  1  track     1 data   lba:         0    00:02:00
Media content: session  1  leadout            lba:   2149872   477:46:72

dvd+rw-mediainfo

INQUIRY:                [BENQ    ][DVD LS DW1655   ][BCIB]
GET [CURRENT] CONFIGURATION:
 Mounted Media:         11h, DVD-R Sequential
 Current Write Speed:   16.0x1385=22160KB/s
 Write Speed #0:        16.0x1385=22160KB/s
 Write Speed #1:        12.0x1385=16620KB/s
 Write Speed #2:        8.0x1385=11080KB/s
 Write Speed #3:        4.0x1385=5540KB/s
GET [CURRENT] PERFORMANCE:
 Write Performance:     16.0x1385=22160KB/s@[0 -> 2149871]
 Speed Descriptor#0:    00/2149871 R@6.7x1385=9276KB/s W@16.0x1385=22160KB/s
 Speed Descriptor#1:    00/2149871 R@6.7x1385=9276KB/s W@12.0x1385=16620KB/s
 Speed Descriptor#2:    00/2149871 R@6.7x1385=9276KB/s W@8.0x1385=11080KB/s
 Speed Descriptor#3:    00/2149871 R@6.7x1385=9276KB/s W@4.0x1385=5540KB/s
READ DVD STRUCTURE[#10h]:
 Media Book Type:       00h, DVD-ROM book [revision 0]
 Legacy lead-out at:    2298496*2KB=4707319808
READ DVD STRUCTURE[#0h]:
 Media Book Type:       25h, DVD-R book [revision 5]
 Last border-out at:    2045*2KB=4188160
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:           complete
 Track Start Address:   0*2KB
 Free Blocks:           0*2KB
 Track Size:            2149872*2KB
 Last Recorded Address: 2149871*2KB
FABRICATED TOC:
 Track#1  :             14@0
 Track#AA :             17@2149872
 Multi-session Info:    #1@0
READ CAPACITY:          2149872*2048=4402937856

libburn/libburner

This run produced the error messages posted in the bug report.

telltoc

Media current: DVD-R sequential recording
Media status : is written , is closed
Media reuse  : is not erasable
Avail. speed : max=16.0  , min=4.0
Speed unit 1x: 1385.0 kB/s  (DVD)
Speed descr. : 22160 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 16620 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 11080 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 5540 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 22160 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 16620 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 11080 kB/s, 4199.0 MiB, DVD-R sequential recording
Speed descr. : 5540 kB/s, 4199.0 MiB, DVD-R sequential recording
Format status: formatted, with 4199.0 MiB
Media content: session  1  track     1 data   lba:         0    00:02:00
Media content: session  1  leadout            lba:   2149872   477:46:72

dvd+rw-mediainfo

INQUIRY:                [BENQ    ][DVD LS DW1655   ][BCIB]
GET [CURRENT] CONFIGURATION:
 Mounted Media:         11h, DVD-R Sequential
 Current Write Speed:   16.0x1385=22160KB/s
 Write Speed #0:        16.0x1385=22160KB/s
 Write Speed #1:        12.0x1385=16620KB/s
 Write Speed #2:        8.0x1385=11080KB/s
 Write Speed #3:        4.0x1385=5540KB/s
GET [CURRENT] PERFORMANCE:
 Write Performance:     16.0x1385=22160KB/s@[0 -> 2149871]
 Speed Descriptor#0:    00/2149871 R@6.7x1385=9276KB/s W@16.0x1385=22160KB/s
 Speed Descriptor#1:    00/2149871 R@6.7x1385=9276KB/s W@12.0x1385=16620KB/s
 Speed Descriptor#2:    00/2149871 R@6.7x1385=9276KB/s W@8.0x1385=11080KB/s
 Speed Descriptor#3:    00/2149871 R@6.7x1385=9276KB/s W@4.0x1385=5540KB/s
READ DVD STRUCTURE[#10h]:
 Media Book Type:       00h, DVD-ROM book [revision 0]
 Legacy lead-out at:    2298496*2KB=4707319808
READ DVD STRUCTURE[#0h]:
 Media Book Type:       25h, DVD-R book [revision 5]
 Last border-out at:    2045*2KB=4188160
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:           complete
 Track Start Address:   0*2KB
 Free Blocks:           0*2KB
 Track Size:            2149872*2KB
 Last Recorded Address: 2149871*2KB
FABRICATED TOC:
 Track#1  :             14@0
 Track#AA :             17@2149872
 Multi-session Info:    #1@0
READ CAPACITY:          2149872*2048=4402937856

cdrskin

No command line options. The verification speed was good this time, but the corruption is again in the last file of the iso.

dmesg

hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
hdb: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 }
ide: failed opcode was: unknown
ATAPI device hdb:
  Error: Medium error -- (Sense key=0x03)
  Unrecovered read error -- (asc=0x11, ascq=0x00)
  The failed "Read 10" packet command was: 
  "28 00 00 1e 82 2d 00 00 40 00 00 00 00 00 00 00 "
end_request: I/O error, dev hdb, sector 7997620
Buffer I/O error on device hdb, logical block 1999405
Buffer I/O error on device hdb, logical block 1999406
Buffer I/O error on device hdb, logical block 1999407
Buffer I/O error on device hdb, logical block 1999408
Buffer I/O error on device hdb, logical block 1999409
Buffer I/O error on device hdb, logical block 1999410
Buffer I/O error on device hdb, logical block 1999411
Buffer I/O error on device hdb, logical block 1999412
Buffer I/O error on device hdb, logical block 1999413
Buffer I/O error on device hdb, logical block 1999414
hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
hdb: media error (bad sector): error=0x34 { AbortedCommand LastFailedSense=0x03 }
ide: failed opcode was: unknown
ATAPI device hdb:
  Error: Medium error -- (Sense key=0x03)
  Unrecovered read error -- (asc=0x11, ascq=0x00)
  The failed "Read 10" packet command was: 
  "28 00 00 1e 82 2d 00 00 02 00 00 00 00 00 00 00 "
end_request: I/O error, dev hdb, sector 7997620

telltoc

Media current: DVD-R sequential recording
Media status : is written , is closed
Media reuse  : is not erasable
Avail. speed : max=16.0  , min=4.0
Speed unit 1x: 1385.0 kB/s  (DVD)
Speed descr. : 22160 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 16620 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 11080 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 5540 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 22160 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 16620 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 11080 kB/s, 4198.7 MiB, DVD-R sequential recording
Speed descr. : 5540 kB/s, 4198.7 MiB, DVD-R sequential recording
Format status: formatted, with 4198.7 MiB
Media content: session  1  track     1 data   lba:         0    00:02:00
Media content: session  1  leadout            lba:   2149728   477:45:03

dvd+rw-mediainfo

INQUIRY:                [BENQ    ][DVD LS DW1655   ][BCIB]
GET [CURRENT] CONFIGURATION:
 Mounted Media:         11h, DVD-R Sequential
 Current Write Speed:   16.0x1385=22160KB/s
 Write Speed #0:        16.0x1385=22160KB/s
 Write Speed #1:        12.0x1385=16620KB/s
 Write Speed #2:        8.0x1385=11080KB/s
 Write Speed #3:        4.0x1385=5540KB/s
GET [CURRENT] PERFORMANCE:
 Write Performance:     16.0x1385=22160KB/s@[0 -> 2149727]
 Speed Descriptor#0:    00/2149727 R@6.7x1385=9276KB/s W@16.0x1385=22160KB/s
 Speed Descriptor#1:    00/2149727 R@6.7x1385=9276KB/s W@12.0x1385=16620KB/s
 Speed Descriptor#2:    00/2149727 R@6.7x1385=9276KB/s W@8.0x1385=11080KB/s
 Speed Descriptor#3:    00/2149727 R@6.7x1385=9276KB/s W@4.0x1385=5540KB/s
READ DVD STRUCTURE[#10h]:
 Media Book Type:       00h, DVD-ROM book [revision 0]
 Legacy lead-out at:    2298496*2KB=4707319808
READ DVD STRUCTURE[#0h]:
 Media Book Type:       25h, DVD-R book [revision 5]
 Last border-out at:    2045*2KB=4188160
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:           complete
 Track Start Address:   0*2KB
 Free Blocks:           0*2KB
 Track Size:            2149728*2KB
 Last Recorded Address: 2149727*2KB
FABRICATED TOC:
 Track#1  :             14@0
 Track#AA :             17@2149728
 Multi-session Info:    #1@0
READ CAPACITY:          2149728*2048=4402642944

[squisher]

So in summary:

• 3x burns with corruption by xfburn
• 1x burn with no corruption by wodim

The media is Philips DVD-R.

[scdbackup]

The logical structure of the media after burn looks the same in all cases. I cannot spot any trace of negligence in our write results.

The sizes differ slightly: wodim=cdrskin , libburner=xfburn. But the error address from the kernel log is well before both end addresses.

Pity that this is with one-time media. So we are restricted in making wasteful experiments.

"wodim burn Command line options: none"

"cdrskin No command line options."

But you did not just toggle in

wodim
cdrskin

and it burned, i assume. At least not with cdrskin.

There must have been some arguments ... somewhere.

---

I have to confess that i am a bit clueless now.

The read errors point rather to drive media compatibility. But the 3:1 result is not easy to shrug off.

I propose you do your next few regular burns with wodim and check whether they all succeed.

If not: get other media.

If yes: we will have to explore more exactly what wodim and cdrskin get as command arguments.

With cdrskin-0.4.x it should also be possible to foist cdrskin under any wodim frontend as long as it is for DVD. So if wodim works reliably, this might be the next experiment. Just to get exactly the same preconditions.

---

Theory background:

There are two write types for DVD-R: DAO and Incremental. wodim and cdrecord only do DAO. cdrskin does DAO by default if it knows the size of the image in advance and if there is no multi-session aspect involved. (Option -multi or non-closed disc with data in the drive)

I guess your write run with cdrskin was DAO. So there should hardly much difference between wodim and cdrskin results.

[vreixo]

I remember that cdrecord padded iso images, to prevent read errors caused by a bug in linux driver, that attemps to read after the last recorded block. May be a problem related with this? The fact the error happens in last file seems a thing like this...

[scdbackup]

The error addresses are to early for any tail-cut effect.

They are too late for hald interference, btw.

---

The cdrecord-mkisofs end padding is needed for CD TAO tracks which announce their size including two non-data blocks at the end .

These two data blocks confuse the Linux block device driver which tries to read them with the normal SCSI data READ command. One cannot distinguish TAO tracks from others easily, but one can easily retry reading two blocks less after READ failed on the first try. telltoc does so.

Linux is too proud for that. It prefers to deliver truncated data. Since more than 10 years.

The remedy is to write more padding bytes than the Linux block device driver uses as read buffer. So any failure happens in the padding and not in the payload.

This kind of problem cannot occur with DVD because all DVD blocks are data blocks. In general, no burn program has much influence on the low-level parameters of a DVD burn. We are just clients of the drive.

[squisher]

Replying to scdbackup:

The logical structure of the media after burn looks the same in all cases. I cannot spot any trace of negligence in our write results. The sizes differ slightly: wodim=cdrskin , libburner=xfburn. But the error address from the kernel log is well before both end addresses. Pity that this is with one-time media. So we are restricted in making wasteful experiments.

I don't mind wasting a couple more DVDs if we can get to the bottom of this.

"wodim burn Command line options: none" "cdrskin No command line options." But you did not just toggle in {{{ wodim cdrskin }}} and it burned, i assume. At least not with cdrskin. There must have been some arguments ... somewhere.

Of course not... to be explicit, I used wodim /path/to/iso and similarly cdrskin /path/to/iso.

------------------ I have to confess that i am a bit clueless now. The read errors point rather to drive media compatibility. But the 3:1 result is not easy to shrug off. I propose you do your next few regular burns with wodim and check whether they all succeed. If not: get other media. If yes: we will have to explore more exactly what wodim and cdrskin get as command arguments.

Did two more burns, similar size and both verified to be correct.

With cdrskin-0.4.x it should also be possible to foist cdrskin under any wodim frontend as long as it is for DVD. So if wodim works reliably, this might be the next experiment. Just to get exactly the same preconditions.

As I wrote above, I used both wodim and cdrskin with just the iso as an argument. Doesn't that qualify as the same preconditions?

I used gnomebaker for my most two recent burns, and in the options I have wodim select as the backend. But when I burn, I get the following command:

genisoimage -gui -V XXXVolume -A GnomeBaker -iso-level 3 -l -r -hide-rr-moved -J -joliet-long -graft-points --path-list /home/squisher/tmp/GnomeBaker/gnomebaker-ATVU5T | builtin_dd of=/dev/hdb obs=32k seek=0

----------------- Theory background: There are two write types for DVD-R: DAO and Incremental. wodim and cdrecord only do DAO. cdrskin does DAO by default if it knows the size of the image in advance and if there is no multi-session aspect involved. (Option -multi or non-closed disc with data in the drive) I guess your write run with cdrskin was DAO. So there should hardly much difference between wodim and cdrskin results.

Well, one is useable and the other is not ;-). So what to do next?

Btw, trac's quote function sucks, but I was too lazy to reformat, sorry!

[scdbackup]

genisoimage ... | builtin_dd of=/dev/hdb obs=32k seek=0

This does not really look like a run where wodim is involved.

I know "builtin_dd" rather from growisofs where it depicts the MMC writer code (of which i learned a lot).

cdrskin /path/to/iso

This was a DAO run. So on the large scale cdrskin does about the same as wodim does.

The problem must be in the details - or in the pitfalls of the low numbers of the experiments made so far.

Proposals:

Try whether growisofs succeeds in DAO mode:

growisofs -dvd-compat -Z /dev/hdb=/path/to/iso

Try whether cdrskin and growisofs succeed in Incremental mode:

growisofs -Z /dev/hdb=/path/to/iso
cdrskin -vvv dev=/dev/hdb -tao /path/to/iso

The -vvv shall make cdrskin extra verbous. I would be interested in seeing the full output.

Please send it directly to me by mail: scdbackup at gmx dot net

[scdbackup]

Ah well ... as we are in wasteful mood.

Try to get some DVD-R media from a different manufacturer. With DVD-R one can expect a different brand to come from a different factory. Best would be to use media of different nominal speed. Those would be guaranteed to be of different factory type.

[scdbackup]

Another proposal: if you can get to making experiments with the same DVD-R but a different burner drive, then this would give us more insight into the reproducability.

I ponder about detail experiments in libburn's MMC code. But this would be damn risky. Any MMC command in that code has its justification from the specs. Actually the MMC commands for DVD-R are about the same as used by growisofs. I can hardly change them and expect that anything will still work.

Another approach would be an analysis of wodim's DVD code. This is about the worst outcome i can imagine for myself. I will consider if resp. when statistics leave me no excuse that anything else might be decisive.

I would be convinced if cross experiments with different media and drives still reliably point to libburn as culprit.

If so, i am a bit hampered with time right now. We are preparing the first release of two new sub projects and before this is done i will hardly find time and motivation for exploring wodim code.

Probably i will waste a DVD-R and check whether my drives still can burn them. It is a while ago that i had use for one-time media. But last year, cdrskin worked fine for me with DVD-R (and with DVD+R which are operated somewhat differently).

[scdbackup]

One more dimension to explore: the reader drive.

I currently have fun with an old DVD+R DL disc which produces heavy errors in my DVD-ROM drive but is readable fine in my USB attached DVD burner.

So if the error addresses in the kernel log vary from drive to drive or even from try to try, then this would be a strong indication of analog level media problems.

(This is not meant as lame excuse. But this DVD DL behaves about as weird as your DVD-R. It was written with growisofs a while ago. No libburn involved. I just read it via libburn for my xorriso tests.)

[scdbackup]

Own adventures give me a new idea about the reason of the problem.

Did you eject and reload the media before checkreading it ?

It seems that the block device buffer of modern Linux is tainted after write until the media get reloaded and newly assessd by the operating system.

The effect is volatile enough to match what you are experiencing.

[squisher]

I think I had reloaded the media in the first place, but just to make sure I checked it again right now and still got i/o errors.

Also I've finally gotten a hold of a different brand of DVD-R media, which libburn writes correctly it seems. So I guess that confirms the write/media combination strangeness...

So is that it, and it's not worth it to follow up? Or any suggestions?

[scdbackup]

This outcome supports the initial suspicion that it was the usual case of drive-media incompatibility.

This is a standard problem entirely located inside the burner drive. Neither the operating system nor the burn program have means to gain positive influence on this (besides speed reduction which is said to help in some cases).

It needs quite a large number of experiments to get a plausible image of the circumstances of success of failure. The history of this ticket indicates that sometimes it works and sometimes not. I still doubt that wodim or growisofs are the decisive component which makes them work. I rather believe in random coincidence here.

Among my four DVD drives, none is able to write 4x DVD-RW in a reliable way. Sometimes it works, most times it fails. In the beginning, growisofs succeeded and cdrskin failed. So i began to believe in a bug in libburn. But then growisofs failed several times in a row - and cdrskin began to succeed. It appears purely random now ... and i gave up on those media.

There can be single bad media or there can be whole media types or production lots which are unsuitable for a particular drive. I am not aware that two drives of the same type differ with the same media, but in theory this is not impossible either. Burner drives show aging effects after a few years.

I close this ticket now. But feel free to append any new insight if you find some.

[deewang]

Thanks for a resourceful content. this is what i have been looking for so long. I don't get the idea why they start these kind of trial when the criminal are old. Perhaps this more personal form of accountability will deter future actors where the fear of international condemnation has not. Ed Hardy stores are located in many locations internationally including the Americas, Europe and Asia.

---

 Cheap Ed Hardy |  Ed Hardy Shop |  Ed Hardy Sale |  Ed Hardy UK |  Ed Hardy Clothing |  Ed Hardy London |  Ed Hardy Apparel |  Ed Hardy T-Shirts