Re: DVD+RW kernel patch - scsi error (help!)
Thanks for the response, Andy. I erred on the side of being too terse,
just to make sure this wasn't something known or obvious. The drive
that I have is an 'Optorite DD0203', based on a Sanyo engine, with the
latest firmware 2.16. I am running 2.4.18, but have tried with 2.4.21 and
2.4.22, as well, with similar results
I have tried two types of media with the unit: KHypermedia DVD+RW and
now HP DVD+RW media.
With both, my experience runs like this:
1 - dvd+rw-format /dev/scd0
this generally works without error, returning the following in the logs:
Sep 2 15:48:50 www kernel: Attached scsi CD-ROM sr0 at scsi0, channel
0, id 0, lun 0
Sep 2 15:48:50 www kernel: sr0: scsi3-mmc drive: 40x/40x writer cd/rw
xa/form2 cdda tray Sep 2 15:48:50 www kernel: sr0: mmc-3 profile
capable, current profile: 0h Sep 2 15:48:50 www kernel: Uniform CD-ROM
driver Revision: 3.12
Sep 2 15:49:15 www kernel: sr0: mmc-3 profile: 1Ah
2 - mkudffs --spartable=2 --media-type=cdrw /dev/scd0
this generally works fine, returning something in the logs like:
Sep 2 15:49:15 www kernel: sr0: mmc-3 profile: 1Ah
Sep 2 15:50:22 www last message repeated 2 times
Sep 2 15:50:47 www kernel: sr0: dirty DVD+RW media, "finalizing"
3 - mount -o rw,noatime /dev/scd0 /mnt/cdrom
this generally is where the error occurs -- but this is only visible in
the logs (the command line returns without error). Note that at this
stage, it is very often it is this particular sector -- 9180032 -- with
both types of media (KHypermedia and HP).
Sep 2 15:51:32 www kernel: sr0: mmc-3 profile: 1Ah
Sep 2 15:51:33 www kernel: udf: registering filesystem
Sep 2 15:51:42 www kernel: scsi0: ERROR on channel 0, id 0, lun 0, CDB:
Request Sense 00 00 00 40 00
Sep 2 15:51:42 www kernel: Current sd0b:00: sense key Medium Error
Sep 2 15:51:42 www kernel: Additional sense indicates No seek complete
Sep 2 15:51:42 www kernel: I/O error:
dev 0b:00, sector 9180032
Sep 2 15:51:42 www kernel: UDF-fs INFO UDF 0.9.7 (2003/01/05) Mounting
volume 'LinuxUDF', timestamp 2003/09/02 15:50 (1ed4)
4 - Any subsequent attempt to copy to this media is futile, eventually
leading to a 'No space left on device' error on the command line and
something like the following in the logs:
Sep 2 16:11:28 www kernel: sr0: injecting "SYNCHRONIZE CACHE"
Sep 2 16:12:40 www last message repeated 2 times
Sep 2 16:13:10 www kernel: scsi : aborting command due to timeout : pid
1608, scsi0, channel 0, id 0, lun 0 Synchronize Cache 00 00 00 00 00 00
00 00 00 Sep 2 16:13:10 www kernel: scsi : aborting command due to
timeout : pid 1609, scsi0, channel 0, id 0, lun 0 Read (10) 00 00 00 05
85 00 00 01 00 Sep 2 16:13:10 www kernel: hdc: irq timeout:
status=0xd0 { Busy } Sep 2 16:13:10 www kernel: hdc: DMA disabled Sep
2 16:13:10 www kernel: hdc: ATAPI reset complete
Sep 2 16:13:10 www kernel: sr0: unable to "SYNCHRONIZE CACHE"
[02/04/07]? Suspending I/O... Sep 2 16:13:10 www kernel: Device 0b:00
not ready.
Sep 2 16:13:10 www kernel: I/O error: dev 0b:00, sector 5652
Sep 2 16:13:10 www last message repeated 3 times
Sep 2 16:13:30 www kernel: I/O error: dev 0b:00, sector 5648
Sep 2 16:13:30 www kernel: I/O error: dev 0b:00, sector 6548
* the above repeated with a whole bunch of different sectors *
When it DID work (with the KHypermedia DVD+RWs), it was to a live UDF
system and it took 60-90 minutes to back up ~3.8 GB (~8 large files).
And none of these errors occurred. :-)
For a test, I did a 'growisofs -Z /dev/scd0=/dev/zero' (/dev/dvd doesn't
exist on my system!) This proceeded normally until:
. . . (beyond 100%? interesting). . .
4873519104/4700372992 (103.7%) @2.4x, remaining 0:-52
4884660224/4700372992 (103.9%) @2.4x, remaining 0:-55
:-[ LBA=247530h, SENSE KEY=4h/ASC=09h/ASCQ=01h ]
:-( write failed: Input/output error
/dev/scd0: flushing cache
/dev/scd0: stopping de-icing
/dev/scd0: writing lead-out
with the logs capturing:
sr0: CDROM (ioctl) error, command: Write (10) 00 00 24 75 30 00 00 10 00
Current sr00:00: sense key Hardware Error
Additional sense indicates Tracking servo failure
This is followed by an hdc DMA diabled/ATAPI reset/SCSI reset.
Any suggestions? This has me going bonkers!
-Frank
P. S. -
> "Medium Error" is not sufficient explanation?
Oh. :-> I thought a "medium error" was, perhaps, a recoverable,
less-serious error than a "severe error" (a kernel panic, perhaps?).
*blush*
Reply to: