Re: dd bug or cdrom driver bug???
Hi,
Spent some time trying to figure out what is going with my cdrom
drives with alpha.
Used stock 2.2.15 kernel from debian
Here are the dmesg information about the cdrom drives.
hda: TOSHIBA CD-ROM XM-6302B, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: ATAPI 32X CD-ROM drive, 256kB Cache
Uniform CDROM driver Revision: 2.56
ncr53c8xx: 53c810 detected
ncr53c810-0: rev=0x02, base=0x109100000, io_port=0x10000b000, irq=24
ncr53c810-0: ID 7, Fast-10, Parity Checking
ncr53c810-0: restart (scsi reset).
scsi0 : QLogic ISP1020 SCSI on PCI bus 01 device 30 irq 47 I/O base 0x100009800
scsi1 : ncr53c8xx - version 3.2a-2
scsi : 2 hosts.
Vendor: DEC Model: RZ2DD-KS (C) DEC Rev: 0306
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: Model: CRW620 Rev: 1.00
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi1, channel 0, id 5, lun 0
scsi : detected 1 SCSI cdrom 1 SCSI disk total.
ncr53c810-0-<5,*>: device did not report SYNC.
sr0: scsi3-mmc drive: 6x/6x writer cd/rw xa/form2 cdda tray
First thing that I found out is that the i/o input error was correct.
The CDROM disk being used was damaged and the i/o input error was real.
I then got a good cdrom disk and found that the scsi cdrom worked
like a charm with all the following commands:
dd if=/dev/scd0 of=cdrom.iso bs=8192
dd if=/dev/scd0 of=cdrom.iso bs=2048
dd if=/dev/scd0 of=cdrom.iso
I then tried the same cdrom disk in the eide drive with the same
commands (of course I changed /dev/scd0 to /dev/hda).
The eide cdrom produced an i/o input error and the following errors
were in the /var/log/massages file.
** Start error **
Jul 27 19:04:35 alpha kernel: ATAPI device hda:
Jul 27 19:04:35 alpha kernel: Error: Illegal request -- (Sense key=0x05)
Jul 27 19:04:35 alpha kernel: Logical block address out of range -- (asc=0x21,
ascq=0x00)
Jul 27 19:04:35 alpha kernel: hda: command error: status=0x51 { DriveReady SeekC
omplete Error }
Jul 27 19:04:35 alpha kernel: hda: command error: error=0x52
Jul 27 19:04:35 alpha kernel: end_request: I/O error, dev 03:00 (hda), sector 17
3870
Jul 27 19:04:35 alpha kernel: ATAPI device hda:
Jul 27 19:04:35 alpha kernel: Error: Illegal request -- (Sense key=0x05)
Jul 27 19:04:35 alpha kernel: Logical block address out of range -- (asc=0x21,
ascq=0x00)
Jul 27 19:13:27 alpha kernel: set_program_attributes(12000000 d8c000 14000000 45
d1d0)
Jul 27 19:13:29 alpha kernel: <sc 0(84,1f4,11ffff940)><sc 53(8,1f4,11ffff940)><s
c 0(17,1f4,11ffff940)><sc 53(8,1f4,11ffff940)>set_program_attributes(12000000 d8
c000 14000000 45d1d0)
Jul 27 19:27:36 alpha kernel: <sc 0(84,1f4,11ffff960)><sc 53(8,1f4,11ffff960)><s
c 0(17,1f4,11ffff960)><sc 53(8,1f4,11ffff960)>set_program_attributes(120000000 2
3e000 140000000 56b50)
** End error **
Now the interesting thing even with all the errors "dd" worked fine
and when I compared all the images produced with "cmp" all the images
were identical. The scsi iso images were identical to the eide cdrom
images. I guess these errors really don't mean much. To be very frank
I don't have a clue what these errors mean. Interesting enough even
with a different cdrom disk (that is known good) I get the exact same
errors. Note this is the same eide drive that would not work with
cdparanoia.
So I guess one should make sure that the cdrom disk is good in the
first place. Especially before posting. :-)
So why did the i386 machine read the bad cdrom disk correctly? I
suspect the reason is the i386 machine has a brand new scsi cdrom
reader/writer that was able to read the damaged disk. That is of
course a guess. If I have some time I may change cdrom drives and see.
Does anyone know what these hda cdrom errors mean?
Thanks!!!
Alan
Reply to: