Re: SCSI I/O errors galore, PART II
> Several people responded to my previous note with good suggestions for
> providing more complete information on my problem. Here's a recap of my
> situation, with what I hope will be more helpful info from dmesg and
Thanks, this should help narrowing down your problem.
> here are the details from that file:
> Jun 16 15:29:13 lumper kernel: SCSI disk error : host 0 channel 0 id 1 lun 0
> return code = 8000000
> Jun 16 15:29:13 lumper kernel: [valid=0] Info fld=0x0, Current sd08:08:
> sense key Illegal Request
> Jun 16 15:29:13 lumper kernel: Additional sense indicates Invalid field in
Your last post said return code = 6000000, now it's 8000000. Plus the
"Current sd08:08" is a bit confusing. Are you accessing /dev/sda8 there?
The 'invalid field in cdb' hints at a SCSI driver problem. I don't get
that on MESH; does this only happen with lots of collisions on the net, or
even with just copying huge files around on disk?
> scsi0 : MESH
> scsi1 : 53C94
> scsi : 2 hosts.
> mesh: target 1 synchronous at 10.0 MB/s
> Vendor: IBM Model: DDRS-39130 Rev: S97B
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 1, lun 0
> Vendor: MATSHITA Model: CD-ROM CR-8005A Rev: 4.0i
> Type: CD-ROM ANSI SCSI revision: 02
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0
> scsi : detected 2 SCSI generics 1 SCSI cdrom 1 SCSI disk total.
> Uniform CD-ROM driver Revision: 3.11
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 17850000 [8715 MB] [8.7
Well, at least the drive info and partition table can be read :-)