[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Basic SCSI question



On %M 0, Randy Edwards wrote
>    I don't have any experience with Linux and SCSI drives and was wondering if
> someone could give me some basic-level/newbie pointers on SCSI setup.
> 
>    The computer has an AdvanSys card in it and I've recompiled the kernel with
> advansys, generic SCSI, and SCSI CD-ROM support.  This seems okay as dmesg
> reports:
> scsi0 : AdvanSys SCSI 3.1E: PCI Ultra-Wide: BIOS C8000/7FFF, IO E800/3F, IRQ
> 10
> scsi : 1 host.
>   Vendor: YAMAHA    Model: CRW4416S          Rev: 1.0f
>   Type:   CD-ROM                             ANSI SCSI revision: 02
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 2, lun 0
>   Vendor: IBM       Model: DDRS-39130D       Rev: DC1B
>   Type:   Direct-Access                      ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 6, lun 0
> scsi : detected 1 SCSI cdrom 1 SCSI disk total.
> sr0: scsi3-mmc drive: 16x/16x writer cd/rw xa/form2 cdda tray
> Uniform CDROM driver Revision: 2.54
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 17850000 [8715 MB] [8.7 GB]
> 
>    Similarly, a cat of /proc/scsi/scsi reports:
> Attached devices:
> Host: scsi0 Channel: 00 Id: 02 Lun: 00
>   Vendor: YAMAHA   Model: CRW4416S         Rev: 1.0f
>   Type:   CD-ROM                           ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 06 Lun: 00
>   Vendor: IBM      Model: DDRS-39130D      Rev: DC1B
>   Type:   Direct-Access                    ANSI SCSI revision: 02
> 
>    An output of "cat /proc/devices" reveals:
> Block devices:
>   2 fd
>   3 ide0
>   8 sd
>  11 sr
>  22 ide1
> 
>    That all looks okay (I guess) but I cannot access the devices.  I did a
> /dev/MAKEDEV update and I have these devices in /dev:
> brw-rw----   1 root     disk       8,   0 May 18 22:59 sda
> brw-rw----   1 root     disk      11,   0 May 18 22:59 scd0
> 
>    If I try to do an "fdisk /dev/sda" I get a message of "Unable to read
> /dev/sda" along with:
> May 19 06:13:21 spartacus kernel: SCSI disk error : host 0 channel 0 id 6 lun
> 0 return code = 25040000
> May 19 06:13:21 spartacus kernel: scsidisk I/O error: dev 08:00, sector 0 
> 
>   Similarly, a command of "mount /dev/scd0 /mnt" gives this info in
> /var/log/messages:
> May 19 06:13:21 spartacus kernel: SCSI disk error : host 0 channel 0 id 6 lun
> 0 return code = 25040000
> May 19 06:13:21 spartacus kernel: scsidisk I/O error: dev 08:00, sector 0
> May 19 06:15:35 spartacus kernel: sr00:00: old sense key None
> May 19 06:15:49 spartacus kernel: Non-extended sense class 0 code 0x0 <3>sr0:
> CDROM (ioctl) error, command: Start/Stop Unit 00 00 00 03 00
> May 19 06:15:49 spartacus kernel: sr00:00: old sense key None
> May 19 06:15:49 spartacus kernel: Non-extended sense class 0 code 0x0
> <6>cdrom: open failed.
> May 19 06:15:59 spartacus kernel: scsi : aborting command due to timeout : pid
> 55, scsi0, channel 0, id 2, lun 0 Prevent/Allow Medium Removal 00 00 00 00 00
> May 19 06:15:59 spartacus kernel: SCSI error: host 0 id 2 lun 0 return code =
> 25040000
> May 19 06:15:59 spartacus kernel: ^ISense class 0, sense error 0, extended
> sense 0
> May 19 06:16:09 spartacus kernel: scsi : aborting command due to timeout : pid
> 56, scsi0, channel 0, id 2, lun 0 Test Unit Ready 00 00 00 00 00
> May 19 06:16:09 spartacus kernel: SCSI error: host 0 id 2 lun 0 return code =
> 25040000
> May 19 06:16:09 spartacus kernel: ^ISense class 0, sense error 0, extended
> sense 0 
> 
>    Any advice, RTFM pointers, or tips would be appreciated.  I'm guessing I
> don't have the devices set up properly, but perusing docs and howtos didn't
> turn up anything.  Thanks in advance.
> 
> -- 
>  Regards, | "A contribution by Microsoft Corporation to South Carolina's
>  .        | Republican Party during the 1998 campaign preceded a decision
>  Randy    | by the state's GOP attorney general to withdraw from an
>           | antitrust suit against the computer software giant."
>           | Source: API, 24 December 1998
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
> 

It looks like the problem is with the SCSI chain itself, from the error
messages (not that I am an expert, but I've used an Advansys card
successfully).

There are a few things you can check/try:
  - SCSI disk support & SCSI CDROM support are separate options to SCSI
    support in recent kernels;  double-check that you have them selected 
    in your kernel config.
  - Make sure that termination is enabled on the devices at the two ends of
    the cable (e.g., the card & the CDROM), but not on other devices; set the termination manually,
    rather than using 'auto' termination, if possible;
  - Make sure that the last device on each end of the SCSI cable is at the
    end of the cable (i.e., no empty sockets at either 'end');
  - Use the Advansys BIOS to set the SCSI buss speed low, in case one of both
    devices can't keep up; 
  - Try replacing the SCSI cable;
  - Make sure you are using a proper SCSI cable:  SCSI has rules about how
    far apart devices should be (there is a minimum required cable length
    between devices, for instance); if you break these rules bad things will
    happen.
  - Try connecting each device individually, in case (e.g.) a dodgy CDROM is
    making trouble for everyone; 
  - If you get the CDROM working but not the disk, try a low-level format on
    the disk.
  - Find a goat and some black candles.

Good luck,


John P.
-- 
huiac@camtech.net.au
john@huiac.apana.org.au
"Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark


Reply to: