From owner-freebsd-hackers Mon Feb 5 05:22:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA26047 for hackers-outgoing; Mon, 5 Feb 1996 05:22:06 -0800 (PST) Received: from sivka.carrier.kiev.ua (root@sivka.carrier.kiev.ua [193.125.68.130]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA25977 for ; Mon, 5 Feb 1996 05:19:49 -0800 (PST) Received: from elvisti.kiev.ua (uucp@localhost) by sivka.carrier.kiev.ua (Sendmail 8.who.cares/5) with UUCP id PAA18711 for hackers@freebsd.org; Mon, 5 Feb 1996 15:19:13 +0200 Received: from office.elvisti.kiev.ua (office.elvisti.kiev.ua [193.125.28.33]) by spider2.elvisti.kiev.ua (8.6.12/8.ElVisti) with ESMTP id OAA24222 for ; Mon, 5 Feb 1996 14:52:11 +0200 Received: (from stesin@localhost) by office.elvisti.kiev.ua (8.6.12/8.ElVisti) id OAA05742 for hackers@freebsd.org; Mon, 5 Feb 1996 14:52:10 +0200 Date: Mon, 5 Feb 1996 14:52:10 +0200 From: "Andrew V. Stesin" Message-Id: <199602051252.OAA05742@office.elvisti.kiev.ua> To: hackers@freebsd.org Subject: Re: Problem with new drive (Connor CFP1060S 1.05GD 243F) Organization: Electronni Visti InformAgency (ElVisti) X-Newsreader: TIN [version 1.2 PL2+] Sender: owner-hackers@freebsd.org Precedence: bulk Michael Smith wrote: : Marc G. Fournier stands accused of saying: : > : > 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. : Aiee! Unless you have a faulty power connector, _send_it_back_ right now. : If it's spinning down the drive is sure it has a _serious_ problem. I STRONGLY second this. We had this same drive model died recently. Two last days before final death it was stinking with the messages "not ready" to the console... : > (aha0:0:0): "CONNER CFP1060S 1.05GB 243F" type 0 fixed SCSI 2 : > sd0(aha0:0:0): Direct-Access 1013MB (2074880 512 byte sectors) : Some firmware revisions of this drive have problems with large read/write : operations. I'd suggest searching the list archives... That's not the issue. Faulty drives were _before_ 203C firmware revision, this one is 243F; and two older drives which were upgraded to 203C are still Ok here. -- With best regards -- Andrew Stesin. +380 (44) 2760188 +380 (44) 2713457 +380 (44) 2713560 "You may delegate authority, but not responsibility." Frank's Management Rule #1.