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

Re: trouble with DVD+R



On Wednesday 05 November 2003 04:00 am, you wrote:
> > I'm having trouble getting DVD+R disks to burn correctly.  I am using a
> > NEC ND-1100A DVD+RW drive, and everything seems to work correctly when I
> > am burning the disk with growisofs.  However when I go to read the data
> > off the disk I get IO error trying to read any files past the first 2Gig.
>
> How do you tell that it's just the files past the first 2G? Submit
> relevant snippet from /var/log/messages? How did you perform your
> recording? If with -Z /dev/dvd=image.iso, how did you prepare image.iso?
> Submit dvd+rw-mediainfo output for media you have the problem with. A.

Ok.  To start with I burn the disk using the following command:

[legowik@tahiti reg]# growisofs -Z /dev/scd0 -R -J conv.1
Executing 'mkisofs -R -J conv.1 | builtin_dd of=/dev/scd0 obs=32k seek=0'
Using CONV_000.100 for  /conv.0425.1008 (conv.0425.1001)
  0.24% done, estimate finish Wed Nov  5 12:35:44 2003
  0.47% done, estimate finish Wed Nov  5 11:07:27 2003
  0.70% done, estimate finish Wed Nov  5 10:37:48 2003
  0.94% done, estimate finish Wed Nov  5 10:23:02 2003
  1.17% done, estimate finish Wed Nov  5 10:14:08 2003
... 
99.47% done, estimate finish Wed Nov  5 09:39:00 2003
 99.70% done, estimate finish Wed Nov  5 09:39:00 2003
 99.94% done, estimate finish Wed Nov  5 09:39:00 2003
Total translation table size: 0
Total rockridge attributes bytes: 42361
Total directory bytes: 90112
Path table size(bytes): 450
Max brk space used 3e404
2131360 extents written (4162 Mb)
/dev/scd0: flushing cache
/dev/scd0: closing track
/dev/scd0: closing session
/dev/scd0: reloading tray

No errors show up in the log file during this process.  To see how the write 
progressed I mount the disk and get an idea of the amount of data added by 
each additional directory: 

[legowik@tahiti reg]# mount /mnt/cdrom1
[legowik@tahiti reg]# cd /mnt/cdrom1
[legowik@tahiti cdrom1]# ls
conv.0424.1234      conv.0424.1732  conv.0425.1047  conv.0425.1201  
conv.0425.1412
conv.0424.1241      conv.0425.0933  conv.0425.1112  conv.0425.1215  
conv.0425.1422
conv.0424.1251      conv.0425.0943  conv.0425.1122  conv.0425.1222
conv.0424.1724      conv.0425.1001  conv.0425.1132  conv.0425.1330
conv.0424.1724.old  conv.0425.1008  conv.0425.1146  conv.0425.1352
[legowik@tahiti cdrom1]# du -s * | awk -- '{sum = sum + $1; print(sum, $2);}'
33214 conv.0424.1234
65204 conv.0424.1241
91781 conv.0424.1251
296146 conv.0424.1724
323011 conv.0424.1724.old
558780 conv.0424.1732
984542 conv.0425.0933
1403824 conv.0425.0943
1635789 conv.0425.1001
1784417 conv.0425.1008
1925276 conv.0425.1047
2077431 conv.0425.1112
2215263 conv.0425.1122
2452205 conv.0425.1132
2767059 conv.0425.1146
2988174 conv.0425.1201
3274886 conv.0425.1215
3566345 conv.0425.1222
3748537 conv.0425.1330
3921618 conv.0425.1352
4082526 conv.0425.1412
4262254 conv.0425.1422

Picking a representative file (which appears in each of the data directories) 
we try to access the file in each directory in turn, and we get:

[legowik@tahiti cdrom1]# foreach dir ( * )
foreach? echo $dir
foreach? cat $dir/obst.pgm > /dev/null
foreach? end
conv.0424.1234
conv.0424.1241
conv.0424.1251
conv.0424.1724
conv.0424.1724.old
conv.0424.1732
conv.0425.0933
conv.0425.0943
cat: conv.0425.0943/obst.pgm: Input/output error
conv.0425.1001
cat: conv.0425.1001/obst.pgm: Input/output error
conv.0425.1008
cat: conv.0425.1008/obst.pgm: Input/output error
conv.0425.1047
cat: conv.0425.1047/obst.pgm: Input/output error
conv.0425.1112
cat: conv.0425.1112/obst.pgm: Input/output error
conv.0425.1122
cat: conv.0425.1122/obst.pgm: Input/output error
conv.0425.1132
cat: conv.0425.1132/obst.pgm: Input/output error
conv.0425.1146
cat: conv.0425.1146/obst.pgm: Input/output error
conv.0425.1201
cat: conv.0425.1201/obst.pgm: Input/output error
conv.0425.1215
cat: conv.0425.1215/obst.pgm: Input/output error
conv.0425.1222
cat: conv.0425.1222/obst.pgm: Input/output error
conv.0425.1330
cat: conv.0425.1330/obst.pgm: Input/output error
conv.0425.1352
cat: conv.0425.1352/obst.pgm: Input/output error
conv.0425.1412
cat: conv.0425.1412/obst.pgm: Input/output error
conv.0425.1422
cat: conv.0425.1422/obst.pgm: Input/output error

And with the IO errors we get a flood of log messages like these:

Nov  5 10:06:17 localhost kernel: Additional sense indicates No seek complete
Nov  5 10:06:17 localhost kernel:  I/O error: dev 0b:00, sector 8502588
Nov  5 10:06:21 localhost kernel: scsi1: ERROR on channel 0, id 0, lun 0, CDB: 
Read (10) 00 00 20 6f 50 00 00 02 00
Nov  5 10:06:21 localhost kernel: Info fld=0x206f50, Current sd0b:00: sense 
key Medium Error
Nov  5 10:06:21 localhost kernel: Additional sense indicates No seek complete
Nov  5 10:06:21 localhost kernel:  I/O error: dev 0b:00, sector 8502592
Nov  5 10:06:26 localhost kernel: scsi1: ERROR on channel 0, id 0, lun 0, CDB: 
Read (10) 00 00 20 6f 51 00 00 01 00
Nov  5 10:06:26 localhost kernel: Info fld=0x206f51, Current sd0b:00: sense 
key Medium Error
Nov  5 10:06:26 localhost kernel: Additional sense indicates Unrecovered read 
error
Nov  5 10:06:26 localhost kernel:  I/O error: dev 0b:00, sector 8502596

Lastly, here is the output of dvd_rw-mediainfo:

[legowik@tahiti cdrom1]# dvd+rw-mediainfo /dev/scd0
GET [CURRENT] CONFIGURATION:
 Mounted Media:         1Bh, DVD+R
READ DVD STRUCTURE[#0h]:
 Media Book Type:       01h, DVD-ROM book [revision 1]
 Legacy lead-out at:    2295103*2KB=4700370944
READ DISC INFORMATION:
 Disc status:           appendable
 Number of Sessions:    2
 State of Last Session: empty
 "Next" Track:          2
 Number of Tracks:      2
READ TRACK INFORMATION[#1]:
 Track State:           partial
 Track Start Address:   0*2KB
 Free Blocks:           0*2KB
 Track Size:            2131360*2KB
READ TRACK INFORMATION[#2]:
 Track State:           blank
 Track Start Address:   2133408*2KB
 Next Writable Address: 2133408*2KB
 Free Blocks:           161696*2KB
 Track Size:            161696*2KB

The files are not uniformly bad after a certain point, but the IO errors 
become much more frequent after about 2Gig into the disk.

Any insite into the problem, or additional tests I can make would be welcome.

-steve



Reply to: