From owner-freebsd-questions@FreeBSD.ORG Fri Jan 6 05:12:40 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F221E1065672 for ; Fri, 6 Jan 2012 05:12:40 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id D06808FC16 for ; Fri, 6 Jan 2012 05:12:40 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id q065CeIv068696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 5 Jan 2012 21:12:40 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id q065CeLU068695; Thu, 5 Jan 2012 21:12:40 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA05125; Thu, 5 Jan 12 21:09:50 PST Date: Fri, 06 Jan 2012 04:09:35 -0800 From: perryh@pluto.rain.com To: btillman99@yahoo.com Message-Id: <4f06e47f.QF6Gxpsj/Dl6yEXA%perryh@pluto.rain.com> References: <4F0517BA.1050405@mykitchentable.net> <1325819792.82542.YahooMailNeo@web36502.mail.mud.yahoo.com> In-Reply-To: <1325819792.82542.YahooMailNeo@web36502.mail.mud.yahoo.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: 9.0-RELEASE amd64 Bricked My Hard Drive X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2012 05:12:41 -0000 Bill Tillman wrote: > ... no matter which computer I chose, and no matter how I setup > the Slave/Master drive, as long as this drive which I had > installed FreeBSD-9.0-amd64 was in the loop, the computer would > lockup at the bios screen. I could not get anything to boot if > this drive was in the loop. If you have an oldish machine with a spare PCI slot, you could try plugging in a PCI-IDE controller card and connect the drive to that. Many of the older BIOS won't look for drives on add-in controllers.