Find the answer to your Linux question:
Results 1 to 5 of 5
Hi all, I have occasional problems with my CD/RW Drive. The problems appear to be documented in my /var/log/messages file, starting back in November 06. Due to the fact that ...
  1. #1
    Just Joined!
    Join Date
    Jan 2007
    Posts
    5

    CD/WR drive error

    Hi all,

    I have occasional problems with my CD/RW Drive.

    The problems appear to be documented in my /var/log/messages file, starting back in November 06. Due to the fact that I 've been having these problems for some time now, I do not remember what I was trying to do on each occasion. I hope that by posting parts of my /var/log/messages file, somebody will be able to tell me what the problem is or suggest where to look for more answers.

    Here are some entries in my /var/log/messages file.
    Day 1:
    Nov 19 22:24:25 myDesktopPC kernel: SCSI cdrom error : host 0 channel 0 id 0 lun 0 return code = 28000000
    Nov 19 22:24:25 myDesktopPC kernel: Info fld=0x120, Current sd0b:00: sense key Hardware Error
    Nov 19 22:24:25 myDesktopPC kernel: Additional sense indicates Focus servo failure
    Nov 19 22:24:25 myDesktopPC kernel: I/O error: dev 0b:00, sector 1152

    Day 2:
    Dec 7 20:07:03 myDesktopPC kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
    Dec 7 20:07:03 myDesktopPC kernel: sr0: scsi3-mmc drive: 52x/52x writer cd/rw xa/form2 cdda tray
    Dec 7 20:07:29 myDesktopPC kernel: SCSI cdrom error : host 0 channel 0 id 0 lun 0 return code = 28000000
    Dec 7 20:07:29 myDesktopPC kernel: Info fld=0x619f, Current sd0b:00: sense key Hardware Error
    Dec 7 20:07:29 myDesktopPC kernel: Additional sense indicates Focus servo failure
    Dec 7 20:07:29 myDesktopPC kernel: I/O error: dev 0b:00, sector 99964

    Some other day:
    Dec 10 11:31:47 myDesktopPC kernel: I/O error: dev 0b:00, sector 64
    Dec 10 11:31:47 myDesktopPC kernel: isofs_read_super: bread failed, dev=0b:00, iso_blknum=16, block=16

    Today:
    I am posting a few lines that have been written to my /var/log/messages file, as I tried to rip an audio CD using grip today. Grip created the directory I expected it to create (i.e. group name) but no encoded files were written. Grip also ejected the CD, thinking that the rip process had finished. Of course, this was the first time I was trying to use grip and this example may relate to problematic grip configuration rather than CDRom failure (although I doubt that!).

    Jan 6 11:46:45 myDesktopPC kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
    Jan 6 11:46:45 myDesktopPC kernel: sr0: scsi3-mmc drive: 52x/52x writer cd/rw xa/form2 cdda tray
    Jan 6 11:47:28 myDesktopPC kernel: cdrom: open failed.
    Jan 6 11:47:30 myDesktopPC kernel: cdrom: open failed.
    Jan 6 11:48:00 myDesktopPC kernel: I/O error: dev 0b:00, sector 64
    Jan 6 11:48:00 myDesktopPC kernel: isofs_read_super: bread failed, dev=0b:00, iso_blknum=16, block=16
    Jan 6 11:48:05 myDesktopPC kernel: I/O error: dev 0b:00, sector 64
    Jan 6 11:48:05 myDesktopPC kernel: isofs_read_super: bread failed, dev=0b:00, iso_blknum=16, block=16

    Also bare in mind that it seems the same task will not necessarily create a problem when repeated again and again. For example, I was trying the other day to play a large avi file reading it directly from the CD/RW Rom. This did not work and Totem crashed after the first minute. However, I tried exactly the same this morning and everything worked fine.

    Some more info about my system:

    Here are the contents of my /proc/scsi/scsi file, which is my CD/RW drive.
    Host: scsi0 Channel: 00 Id: 00 Lun: 00
    Vendor: ARTEC Model: WRR-52Z Rev: 1.23
    Type: CD-ROM ANSI SCSI revision: 02

    And here is the result of “grep hd.: /var/log/kern.log” which tells you a bit more about my disks. My CD/RW drive is an ATAPI one using an ide-scsi driver, which has been working fine since April 06.

    Jan 6 11:04:16 myDesktopPC kernel: ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hdaMA, hdbio
    Jan 6 11:04:16 myDesktopPC kernel: ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdcMA, hddMA
    Jan 6 11:04:16 myDesktopPC kernel: hda: ST3120022A, ATA DISK drive
    Jan 6 11:04:16 myDesktopPC kernel: hdc: ARTEC WRR-52Z 1.23 20030421, ATAPI CD/DVD-ROM drive
    Jan 6 11:04:16 myDesktopPC kernel: hdd: IDE DVD-ROM 16X, ATAPI CD/DVD-ROM drive
    Jan 6 11:04:16 myDesktopPC kernel: hda: attached ide-disk driver.
    Jan 6 11:04:16 myDesktopPC kernel: hda: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=14593/255/63, UDMA(100)
    Jan 6 11:04:16 myDesktopPC kernel: hdd: attached ide-cdrom driver.
    Jan 6 11:04:16 myDesktopPC kernel: hdd: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
    Jan 6 11:04:16 myDesktopPC kernel: hdc: attached ide-scsi driver.

    (by the way, how do I turn the stupid smilies off?)


    Any suggestions will be much appreciated. Thanks.

    Daidalus13
    [P4 2.4GHz - RAM 512Mb -HDD 120Gb - Debian Sarge 2.4]

  2. #2
    Linux User
    Join Date
    Feb 2006
    Posts
    484
    i think is a hardware problem
    1. your cd/rw drive is faild
    2. ide cable is broken
    3. some metal-oxid on the ide connector cause the problems

  3. #3
    Just Joined!
    Join Date
    Jan 2007
    Posts
    5
    Well,
    Considering that my DVD drive which is connected as slave drive on the same controller had been occasionaly behaving abnormal recently (I was not able to play DVDs), I assume that this is probably a cable or a controller issue. If it is a cable issue I am lucky. If it is a controller problem, should I start looking for a new motherboard?
    Any other ideas, much appreciated.
    Daidalus13

  4. #4
    Linux User
    Join Date
    Feb 2006
    Posts
    484
    did the bios detect your dvd rom?
    error messages in dmesg output?

  5. #5
    Just Joined!
    Join Date
    Jan 2007
    Posts
    5
    Sorry for the late reply. That has been a long week for me.

    BIOS seems to detect the DVD drive just fine. I don't have any error messages from dmesg but there is one thing that probably worths mentioning. Look at the following line taken from my startup log (dmesg output):

    ide_setup: hdc=ide-scsi
    Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
    ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
    NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    ide: late registration of driver.
    ICH4: IDE controller at PCI slot 00:1f.1
    ICH4: chipset revision 2
    ICH4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda: DMA, hdb: pio
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc: DMA, hdd: DMA
    hda: ST3120022A, ATA DISK drive
    blk: queue e0820b80, I/O limit 4095Mb (mask 0xffffffff)
    hdc: ARTEC WRR-52Z 1.23 20030421, ATAPI CD/DVD-ROM drive
    hdd: IDE DVD-ROM 16X, ATAPI CD/DVD-ROM drive
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    ide1 at 0x170-0x177,0x376 on irq 15
    hda: attached ide-disk driver.
    hda: 234441648 sectors (120034 MB) w/2048KiB Cache, CHS=14593/255/63, UDMA(100)
    Partition check:
    /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 >
    Journalled Block Device driver loaded
    kjournald starting. Commit interval 5 seconds
    EXT3-fs: mounted filesystem with ordered data mode.
    EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
    Real Time Clock Driver v1.10f
    hdd: attached ide-cdrom driver.
    hdd: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)

    Uniform CD-ROM driver Revision: 3.12
    SCSI subsystem driver Revision: 1.00
    kjournald starting. Commit interval 5 seconds
    EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,6), internal journal
    EXT3-fs: mounted filesystem with ordered data mode.

    Correct me if i am wrong, but I think that the DVD drive is correctly identified as 16x but the driver that is later used is 48x. Could this be a problem? And if yes, why does the DVD drive sometimes play a film perfectly well and some other times just cannot work at all?

    This last log issue with the DVD drive does not explain why my CD drive does not work sometimes. Or does it?
    Any ideas?

    Thanks
    Daidalus13

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •