Thread View: sanet.list.sco
1 messages
1 total messages
Started by apl
Mon, 24 Aug 1992 20:57
SCSI ID Problems resolved
Author: apl
Date: Mon, 24 Aug 1992 20:57
Date: Mon, 24 Aug 1992 20:57
41 lines
1828 bytes
1828 bytes
In article <Bt2xIF.Ep3@world.std.com> I wrote: >New AST 486 eisa, Adaptac 1744, 510 Meg Connor, Archive 2525S. >Installation went fine. Same problem with tape, though. Then, >suddenly, screenfulls of "Can't read block " off of dev 1,40. > >So, I was going to look at replacing the Adaptec, but now I'm not sure. > Boy, did I screw up! First, this wasn't a 1744, it was a 1740. But that was just a typo and not at all the problem. The problem was that diagnostics would see 8 drives attached and the tape did not work at all. As I said in my post, the only time I've ever seen that is when the drive is at ID 7. My post went on to state "This drive assuredly is NOT at ID 7". Well, what's required here is some creative re-definition of "assuredly NOT". Because it was, and I even looked at the jumpers (yep, all 3 of them) and somehow just did not see it. Or somehow figured that all closed MUST mean 0 because who would ship a drive ID'd at 7? (*Conner would-and does) As I had said to the client as I lay on my back, reaching up into the machine to see if cables were loose: "There's something really screwy here, because this drive acts like it's ID 7" Did I listen to myself? No. Am I a total idiot? Maybe. Tony Lawrence & Clark, Inc (617) 762-0707 (206) 323-2864 Xenix/Unix support,etc Boston Seattle
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads