> Hi,
> I have a problem with my new FIREBALL SE6.4S scsi disk.
> The controller is an ncr83c810 as you can see from the boot messages
> using the ncr53c8xx driver.
The boot messages says that sdb fails the READ CAPACITY with
"extended sense code = 2"
This code seems to be the Sense Key (byte 2 of sense data).
|--------+--------------------------------------------------------------------|
| 2h | NOT READY. Indicates that the logical unit addressed cannot be |
| | accessed. Operator intervention may be required to correct this |
| | condition. |
|--------+--------------------------------------------------------------------|
Here is what I've seen from the boot messages:
> scsi0 : ncr53c8xx - revision 2.5f
> scsi : 1 host.
> ncr53c810-0-<0,0>: using tagged command queueing, up to 4 cmds/lun
> Vendor: QUANTUM Model: FIREBALL SE6.4S Rev: PJ0A
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
> Vendor: FUJITSU Model: M2512A Rev: 1507
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi removable disk sdb at scsi0, channel 0, id 4, lun 0
> scsi : detected 2 SCSI disks total.
> ncr53c810-0-<0,0>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 8)
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 12594960 [6149 MB] [6.1 GB]
> ncr53c810-0-<4,0>: FAST-5 SCSI 5.0 MB/s (200 ns, offset 8)
> sdb : READ CAPACITY failed.
> sdb : status = 1, message = 00, host = 0, driver = 28
> sdb : extended sense code = 2
sdb: Sense Key = NOT READY
> sdb : block size assumed to be 512 bytes, disk size 1GB.
> Partition check:
> sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
> sdb:scsidisk I/O error: dev 08:10, sector 0
sdb has problem reading sector 0.
> SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 2505007f
> scsidisk I/O error: dev 08:05, sector 1753136
> EXT2-fs error (device 08:05): ext2_read_inode: unable to read inode block - inode=220127, block=876568
sda (sda5) has problems now.
> Remounting filesystem read-only
> scsi : aborting command due to timeout : pid 90555, scsi0, channel 0, id 0, lun 0 Write (6) 09 40 62 02 00
> ncr53c8xx_abort: pid=90555 serial_number=90561 serial_number_at_timeout=90561
> ncr53c810-0: abort ccb=c038d020 (skip)
> scsi : aborting command due to timeout : pid 90556, scsi0, channel 0, id 0, lun 0 Write (6) 1d 41 06 02 00
> ncr53c8xx_abort: pid=90556 serial_number=90562 serial_number_at_timeout=90562
> ncr53c810-0: abort ccb=c038d820 (skip)
> scsi : aborting command due to timeout : pid 90557, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 68 83 b0 00 00 02 00
> ncr53c8xx_abort: pid=90557 serial_number=90563 serial_number_at_timeout=90563
> ncr53c810-0: abort ccb=c038e820 (skip)
The SCSI system seems locked up.
Seems the FUJITSU (removable) have problems with the medium and messes up
the SCSI BUS is such a situation.
Gerard.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html