From owner-freebsd-hackers Sun Feb 4 17:49:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA21670 for hackers-outgoing; Sun, 4 Feb 1996 17:49:46 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA21662 for ; Sun, 4 Feb 1996 17:49:43 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id CAA12912; Mon, 5 Feb 1996 02:49:39 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id CAA05223; Mon, 5 Feb 1996 02:49:39 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id CAA02607; Mon, 5 Feb 1996 02:23:55 +0100 (MET) From: J Wunsch Message-Id: <199602050123.CAA02607@uriah.heep.sax.de> Subject: Re: Problem with new drive (Connor CFP1060S 1.05GD 243F) To: scrappy@ki.net (Marc G. Fournier) Date: Mon, 5 Feb 1996 02:23:55 +0100 (MET) Cc: freebsd-hackers@FreeBSD.ORG Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Marc G. Fournier" at Feb 4, 96 02:08:12 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@FreeBSD.ORG Precedence: bulk As Marc G. Fournier wrote: > > When I tried to install, it newfs'd 3 partitions, then got the above error > on the 4th (you could hear the drive powerdown) and then when it went to > the 5th, you could hear it power up again, and it newfs'd it and the 6th > properly again. > The drive is: > > (aha0:0:0): "CONNER CFP1060S 1.05GB 243F" type 0 fixed SCSI 2 > sd0(aha0:0:0): Direct-Access 1013MB (2074880 512 byte sectors) > > Are there any known problems with this drive? Anything I should > have jumpered that isn't? Settings on the controller that I've missed? The problems you are describing are of some other nature, trust me. I've also got this kind of problems occasionally, and last time, i've been suspicous about the drive, too. It turned out to be a weak power connector, my box is full of Y-cables... <:) Try the drive with a totally different power supply. Maybe your power supply has too many spikes on the DC (possibly even R.F. spikes, use an oscilloscope if you can). Make absolutely sure that your drive does _NOT_ supply term power to the bus. Let the controller do this, not the drive. (Normally, the only problem with this is if a controller supplies +5 V for passive termination, and a drive supplies +2.85 V for active termination, but you never know for sure. Remove the jumper if there is any.) Some drives don't like to be grounded. Try it without connecting the metallic case to ground. Finally, if the drive overheats, it usually also turns down. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)