First post, by dionb
- Rank
- l33t++
Two weeks back I was able to pick up a Seagate Cheetah ST39103LC 9.1GB 10k RPM U2W SCA SCSI drive for free. Yippee... but the only SCSI hardware I had was a Dawicontrol narrow SCSI card and an external Sun 5.25" enclosure with Plextor CDRW (and no cable...). Apart from the performance thing, I didn't have any narrow->wide adapters (or even any 50p flat cables for that matter). So if I was going to have to acquire something else anyway I might as well do it properly. So I located an Adapter AHA-2940U2W, and a nicely terminated 68p cable. This afternoon the AHA-2940U2W arrived, so I could get started. Only I got stuck pretty much immediately.
HW:
--- known good ---
Tekram P5MVP-A4 rev 1.01 motherboard
K6-3+ 450 (not currently overclocked, just plain 4.5x100@2.0V)
64MB PC100 SDR-SDRAM
Diamond Viper V770 TNT2-Ultra AGP
FSP-350-6PN (PF) PSU (ATX, 350W)
SCA-80 to HD-68 + Molex adapter cards (two different ones, simple passive things - behaviour is identical with both)
--- not known good yet ---
Adapter AHA-2940UW
50cm, 3 connector HD-68 SCSI cable with Amphenol terminator, rated for LVD and U320
Seagate Cheetah ST39103LC (set to SCSI ID 0)
SW:
Adapter SCSISelect V.2.20.0 GE
(yes, in German 😒 - my German is fine, but figuring out how technical terms were translated isn't my favourite activity in any language)
Issue:
The drive isn't being detected, regardless of what I do. What *does* happen differs depending on which connector on the AHA-2940U2W I connect the drive to:
- If I connect the drive to the Ultra2-LVD/SE connector, the drive doesn't spin up. The LED on the drive does go on and stays on. The SCSI Disk Utilities drive scan completes normally, but no drives found.
- If I connect the drive to the secondary (SE only) connector, the drive does spin up. The LED on the drive flashes a bit afterwards, the goes off. The SCSI Disk Utilities drive scan hangs on SCSI-ID 0 : LUN 0
Now, the problem is I have three unknowns (adapter, cable and disk) and don't have any other hardware to exchange to identify which is causing the issue.
Things I've tried:
- Resetting SCSI BIOS to defaults.
- Setting the HDD to a different ID, either through jumper on the drive itself or on the SCA-HD68 adapter.
- Using the other connector on the SCSI cable.
- Trying this set of tips from the Adaptec knowledge base from 1999 - basically altering SCSI host adapter settings to their most simple, compatible.
- Swapping round the two SCA-HD68 adaptors.
- Turning it all off, sitting down to a nice local craft beer and thinking nice positive thoughts. Then turning it all on again.
Nothing changes behaviour. I'm pretty sure something's dead, but if anyone has a better suggestion than "find some more SCSI cables, drives, or adapters and rule them out one by one" I'd be most grateful.