Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 77968 - errors reading CDRW (ide-scsi)
Summary: errors reading CDRW (ide-scsi)
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 8.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2002-11-15 23:07 UTC by robert
Modified: 2008-08-01 16:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2004-09-30 15:40:12 UTC

Attachments (Terms of Use)

Description robert 2002-11-15 23:07:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98)

Description of problem:
A brand new CDRW drive burns disks using cdrecord just fine. On attempt to read 
the freshly recorded disk it reads most of it, but just as the disk spins down, 
gets "read error".
The same CDRW disk can be read fine without ide-scsi emulation on the same 
The same CDRW disk can be read fine on a different machine with 2.4.9 kernel.
It appears to be a bug in ide-scsi module in kernel 2.4.18.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Write about 300M to a CDRW disk using cdrecord
2.dd if=/dev/scd0 of=/dev/null

Actual Results:  dd: reading `/dev/scd0': Input/output error
705808+0 records in
705808+0 records out
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
scsi0: ERROR on channel 0, id 0, lun 0, CDB: Request Sense 00 00 00 40 00
Info fld=0x2b170 (nonstd), Current sd0b:00: sense key Medium Error
Additional sense indicates Unrecovered read error
 I/O error: dev 0b:00, sector 705812

Expected Results:  no read errors

Additional info:

[root@marten /]# cdrecord -scanbus
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 JC7rg Schilling
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.5'
        0,0,0     0) 'LITE-ON ' 'LTR-40125S      ' 'ZS05' Removable CD-ROM
[root@marten /]# cdrecord -checkdrive dev=0,0,0
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 JC7rg Schilling
scsidev: '0,0,0'
scsibus: 0 target: 0 lun: 0
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.5'
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   :
Vendor_info    : 'LITE-ON '
Identifikation : 'LTR-40125S      '
Revision       : 'ZS05'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags   : SWABAUDIO

Comment 1 Jim Cornette 2003-02-22 02:34:03 UTC
When burning a CDR, everything seems fine. But after the CDR is burned, you
cannot mount it on the burner. /dev/cdrom1

I get the following message, when trying to mount the drive with the disk
management tool.

mount: wrong fs type, bad option, bad superblock on /dev/cdrom1,
       or too many mounted file systems
       (could this be the IDE device where you in fact use
       ide-scsi so that sr0 or sda or so is needed?)

The entries for SCSI devices is this.

/dev/cdrom            /mnt/cdrom            iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0              /mnt/floppy              auto    noauto,owner,kudzu 0 0
/dev/cdrom1           /mnt/cdrom1       udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/sda1             /mnt/flash               auto    noauto,owner,kudzu 0 0

The symlink for my /dev/cdrom1 points to /dev/hdd for the device driver.

phoebe2 and phoebe3 have the same problem.

Comment 2 Bugzilla owner 2004-09-30 15:40:12 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

Note You need to log in before you can comment on or make changes to this bug.