Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!medsys!wendell From: wendell@medsys.uucp (Wendell Dingus) Newsgroups: comp.sys.amiga.hardware Subject: Re: Hardrives and the A3000 Message-ID: <1991Mar26.231915.19560@medsys.uucp> Date: 26 Mar 91 23:19:15 GMT References: <1991Mar19.222827.16244@en.ecn.purdue.edu> <17727@crdgw1.crd.ge.com> <1991Mar20.220547.4677@en.ecn.purdue.edu> <20023@cbmvax.commodore.com> <18de57f0.ARN0f78@cbmami.UUCP> Organization: Med-Systems, Kingsport, Tennessee Lines: 38 This thread has been running for some time now, but I haven't been keeping up with it very closely. Now though, I'm having a problem with a new hard drive on my A3000. System is an A3000/16 with 6MB Ram, stock Quantum 50 Meg drive, and a new Quantum 105 Meg drive. Because of drive size, I moved the (thinner) 50 megger over to the front (floppy) bay, and put the 100 meg in the back. The stock drive was jumpered as SCSI ID 6, and I put the new drive as ID 5. Left all three partitions intact on the 50 Meg, and just added two new partitions on the 100 Meg. Reselection is off on both drives (Don't remember what the problem is here, but I remember reading to do this). Anyway, things work fine at first. After a cold boot though, "Volume System2.0: has a read/write error" and it won't read in the Kickstart image. Oh well, maybe I shook it around too much or some such... re low-level formatted it, partitioned it, and installed system software. Works fine for a day, things must be fixed. Next day, after being powered off, "read/write error". This time I take Quarterback tools to it, and am informed that WB_2.x: has 72 hard errors on it. Oh brother, I go ahead and mark them as bad, and re-format. Works fine..... now it's the next day.. read/write error again. What is the deal here????? Here's how things are: SCSI on MB Quantum 105 Quantum 52 (appeared unterminated) (unterminated) (terminated) (SCSI ID 7???) (SCSI ID 5) (SCSI ID 6) (no bootable partitions) (WB_2.x: boot part.) O-----SCSI-Cable--------------O------------------------O PS. I took the stock cable out and used it in a Xenix system I needed a SCSI cable for at work, and made a new one for this system. Put all the connectors on a length of cable with a vise, and I'm fairly confident all have solid connections. Any ideas on how I can clean this up will be GREATLY appreciated!!! ----- Wendell Dingus UseNet: ...uunet!medsys!wendell