jrd@cc.usu.edu (04/17/91)
This seems to be the time and place to ask a couple of questions of the folks who have been through the exercise. AT&T Unix SVR4.02. Dell 310 386-20 w/4MB. Here is the problem: bringing up the system with a WD 7000 FASST2 controller. I have no troubles with a ST-506 drive. With the AT&T SCSI 4.0 Boot Floppy v2.0, however, and no other disk controller except the WD 7000 the system says something like can inappropriate system for HD 0 at address 0x0...0350, and then can't init HD 0. The jumpers are right. I checked the works under DOS with CDP's diagnostics and all went swimmingly. The hard disk is a CDC (aka Seagate) ST4766N (766 MB raw). So, I said if it has trouble with the official 0x350 port address then try another nearby. No go, can't energize the floppy, as we would expect if the controller were not matched to the software. No obvious conflicts in the system (having removed essentially all other boards). The AT&T SCSI Diagnostics disk, v2.1, also shows problems. Any test leaves the system hanging forever with the disk's red light on. Red switch to recover. So, what might be going on here. The WD 7000 is brand new, with v3.36 ROM. The drive is brand new (albeit of an older design) and checks out fine with non-Unix tests. I even reformatted it under DOS and found no extra bad blocks. The machine is well worn and trustworthy. My fall back is to find an extra day, build an ST506 kernel, go through the fun of replacing the hd driver with Columbia Data Product's material, make a new boot floppy and reconstuct the machine (remove extra boards and such). My hope is that it's all my fat fingers rather than a "no way" kind of thing. [Yes, the WD board was set for DMA 6, IRQ 15h, port 350h, with the floppy controller activated, with the Bios set to CE00h, basically straight out the box condition matching what my AT&T manuals say to do. LUN 0 on the drive.] Puzzled, Joe D.
kentkar@shambala.uucp (Kent Karrer) (04/21/91)
In article <1991Apr16.201741.47441@cc.usu.edu> jrd@cc.usu.edu writes: > ||lots of stuff deleted|| > So, what might be going on here. The WD 7000 is brand new, with v3.36 >ROM. The drive is brand new (albeit of an older design) and checks out fine >with non-Unix tests. I even reformatted it under DOS and found no extra bad >blocks. The machine is well worn and trustworthy. My fall back is to find >an extra day, build an ST506 kernel, go through the fun of replacing the >hd driver with Columbia Data Product's material, make a new boot floppy and >reconstuct the machine (remove extra boards and such). My hope is that it's >all my fat fingers rather than a "no way" kind of thing. [Yes, the WD board >was set for DMA 6, IRQ 15h, port 350h, with the floppy controller activated, >with the Bios set to CE00h, basically straight out the box condition matching >what my AT&T manuals say to do. LUN 0 on the drive.] > Puzzled, > Joe D. I just tried the same thing with a WD7000FASST2 and Maxtor 8380. My first problem was that I could not get the floppy to read correctly. A call to Columbia Tech Support indicated that the jumpers for ANSI floppy were wrong in the documentation. That corrected, the floppies worked for about an hour and then died completely. I think the floppy controller portion of the board went around the bend. I substituted in my old controller, strapped it to be the primary floppy controller and was off again until I tried to create file systems on the hard drive. I got a read block error or something to that effect, the install aborted and nothing I did in the last two and a half days has gottenaround that. At this point, my only alternative is to try and get my money back and see what happens with an Adaptec 1540B controller. -- [~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~] [ A GREAT DEAL OF CHAOS IN THE WORLD occurs because people don't appreciate ] [ themselves. -- Chogyam Trungpa ] [ "SHAMBHALA - The Sacred Path of the Warrior" ] [___________________uunet!seaeast.wa.com!shambala!kentkar___________________]