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: YAMAHAModel: 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= 1785 [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-AccessANSI 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 = 2504 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 = 2504 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 3sr0: 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 6cdrom: 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 = 2504 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 = 2504 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 [EMAIL PROTECTED] /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,
Re: Basic SCSI question
John Pearson wrote: . 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-AccessANSI SCSI revision: 02 I join you an answer of the SCSI maintainer in addition to the excellents advices John P. gave. Hope it will help. JY -- Jean-Yves BARBIER [EMAIL PROTECTED] Les choses ne sont pas toujours ce que l'on voudrait qu'elles soient qu'elles fussent... P. DAC Boycott Intel, watch: http://www.bigbrotherinside.com If you need N components to build your board, you'll ALWAYS have N-1 in stock Murphy's law - FORWARDED MAIL == I've got a TEKRAM DC390 scsi card (simple fast-scsi), and here is my problem: Debian distribution, ABIT BH6 w/PII400, SCSI chain: CTRLR=Id7, CD-ROM PIONEER DR-U16S=Id4, CD-R YAMAHA CDR-4416S=Id5 ^ This device is very well known to me. It caused trouble to more people than to you. That's a Yamaha bug: It needs too much time to recover from a SCSI bus reset. 1- Weird thing: If I let the speed setting of the DC390 @ 10.0 MHz transfer speed, at boot the YAMAHA says its working @ 8.0 MHz; If I put 8.0 MHz in the DC390, at next boot, it says its working @ .. 6.6 MHz (don't know why?) Me neither. Almost certainly some Yamaha firmware misfunction. * Started (a month ago) w/kernel 2.0.36 from debian's CD: YAMAHA causes troubles, zapped from system (I was obliged to cut-off the main power supply to recover it in the system!): The DC390 was recognized as AM53C974, Then you used the AM53C974 driver. Well it's buggy, if you allow disconnection, so I'd prefer not to use it. Unfortunately, it's also unmaintained. * Recompiled the kernel w/only the DC390: DC390 was recognized as DC390, YAMAHA CR was not recognized, * Upgrade to 2.2.1: always no recognition of the CDR (not seen by the driver) * Upgrade to 2.2.7: still the same! It's the same driver in those kernel, so the behaviour must be the same. Here's the band aid: Become root and type echo scsi add-single-device 0 0 5 0 /proc/scsi/scsi cat /proc/scsi/scsi Your CD-R will be detected. Please read the web page http://www.garloff.de/kurt/linux/dc390/problems.html for more information. Hope this helps. -- Kurt Garloff [EMAIL PROTECTED] SuSE GmbH, Nürnberg, FRG Linux kernel development;SCSI driver: DC390 (tmscsim/AM53C974)
Re: Basic SCSI question
:- Randy == Randy Edwards [EMAIL PROTECTED] writes: 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: Did you add also SCSI DISK support, didn't you? Detected scsi disk sda at scsi0, channel 0, id 6, lun 0 detected, ok, but what about support ? Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: IBM Model: DDRS-39130D Rev: DC1B Type: Direct-AccessANSI SCSI revision: 02 is this the correct hardware you ahve in your machine ? brw-rw 1 root disk 8, 0 May 18 22:59 sda brw-rw 1 root disk 11, 0 May 18 22:59 scd0 you shoud have some /dev/sda1 /dev/sda2 etc for the partitions, too 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 = 2504 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 = 2504 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 3sr0: 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 6cdrom: 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 = 2504 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 = 2504 May 19 06:16:09 spartacus kernel: ^ISense class 0, sense error 0, extended sense 0 I see that you have the cdrom as id 2 and the disk as id 6. If you intend to boot from that hard disk you should set it's id to 0 (unless your scsi adapter has a configurable boot device, which on cheaper cards it couldn't be the case...). Also check that: 1) the hard disk is on the first connector next to the adapter card. (this really is not required but eliminates some error possibilities because that's the way it works for me :-) 2) the cdrom is on the last connector on the strip. This is important. If your strip has more than 2 connectors, the LAST ONE must be occupied, possibly leaving some empty ones in the middle. The empty ones in the middle don't hurt. 3) The hard disk MUST NOT be terminated (there's a little series of jumpers on the hd, check for the one that has a mark as TE or TERM - better yet, check on the instruction manual that I hope your dealer gave you) 4) THe cdrom MUST BE terminated (again, a small jumper on the back of the device, better if you check the manual because usually there are 6 or 7 jumpers all together and it may be confusing figuring out the right one) 5) Check that both devices support parity check (there are jumpers for this too), and that parity is set up to be used in the adapter's set-up 6) Set adapter's speed to auto-sense so that you don't have to mess with 20 MB/s or fast buses or the like :-) 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. Hope this is enough :-) Pf -- --- Pierfrancesco Caci | mailto:[EMAIL PROTECTED] - http://gusp.infogroup.it ik5pvx| http://www.geocities.com/SoHo/Lofts/8999 Firenze - Italia | Office for the Complication of Otherwise Simple Affairs Linux penny 2.2.9 #1 Sat May 15 10:10:38 CEST 1999 i586 unknown
Basic SCSI question
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: YAMAHAModel: 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= 1785 [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-AccessANSI 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 = 2504 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 = 2504 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 3sr0: 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 6cdrom: 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 = 2504 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 = 2504 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
