From owner-freebsd-questions@FreeBSD.ORG Fri Jan 6 18:21:33 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 14B5A1065672 for ; Fri, 6 Jan 2012 18:21:33 +0000 (UTC) (envelope-from illoai@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 9A9D88FC14 for ; Fri, 6 Jan 2012 18:21:32 +0000 (UTC) Received: by wgbdr11 with SMTP id dr11so1988767wgb.31 for ; Fri, 06 Jan 2012 10:21:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=6Mdz1jAAO4zUFIS2+dClT60cbiS6w3if36CeE0/mSRY=; b=XuN6YBfAupMWfKTqumvMPtwuYvaBd0ohwGNzdyX+x0uvO6OJJt3235D31BgvnQuMlg 6quw80NoPjlzkkIIB98BcAJMpK3tsSuTgnUYG5jfZ1MrixmoULKICXseOPlCaJIao7aO 2beMXSouI5svBEQ30ZtZUgUeD5ChaDGZLL72E= MIME-Version: 1.0 Received: by 10.180.96.72 with SMTP id dq8mr13057131wib.10.1325874091544; Fri, 06 Jan 2012 10:21:31 -0800 (PST) Received: by 10.216.71.68 with HTTP; Fri, 6 Jan 2012 10:21:31 -0800 (PST) In-Reply-To: <1325819792.82542.YahooMailNeo@web36502.mail.mud.yahoo.com> References: <4F0517BA.1050405@mykitchentable.net> <1325819792.82542.YahooMailNeo@web36502.mail.mud.yahoo.com> Date: Fri, 6 Jan 2012 13:21:31 -0500 Message-ID: From: "illoai@gmail.com" To: Bill Tillman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Questions 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 18:21:33 -0000 On 5 January 2012 22:16, Bill Tillman wrote: ... > then I attempted to reboot the system but nothing happened. And by that I > mean the computer's flash screen would come up and give me the choice > to enter the Bios Setup or Boot Menu and that's all. I could not enter th= e > bios setup or the Boot menu. The keyboard was still responding as I > could press the CapLock key and toggle the light on and off, but outside > of that the computer would not boot. On the advice of some of the techs > in #FreeBSD channel I=A0moved the drive over to another computer which > was working fine, and the same thing happened. The computer would > start up, show me the flash screen to do the Bios setup and then nothing. > I put the other drive back in and it worked fine. I tried another compute= r > and the results were the same. Now it gets really wierd. I thought that I > could just make this IDE drive a slave and boot with another drive and > cleanup the mess. But 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 I removed it everything was fine. So basically, > FreeBSD-9.0-RELEASE bricked an otherwise good 80GB hard drive > and I can't seem to recover it. > > Any suggestions would be appreciated. I have an old IDE->USB adapter that I think I picked up for $15 a few years ago. (amazon has them for that right now http://amzn.to/xfyeOW Your local Beast Buy or MicroSinter may have such as well the newer once seem to all have eSATA ports too) Silly things like that come in handy once in a great while. Though you may have that rare case when your HDD's board cooked itself for some reason. --=20 --