From owner-freebsd-questions@FreeBSD.ORG Wed Jul 29 09:36:18 2009 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 CCB68106564A for ; Wed, 29 Jul 2009 09:36:18 +0000 (UTC) (envelope-from mirror176@cox.net) Received: from fed1rmmtao102.cox.net (fed1rmmtao102.cox.net [68.230.241.44]) by mx1.freebsd.org (Postfix) with ESMTP id 8EF8D8FC12 for ; Wed, 29 Jul 2009 09:36:18 +0000 (UTC) (envelope-from mirror176@cox.net) Received: from fed1rmimpo02.cox.net ([70.169.32.72]) by fed1rmmtao102.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090729093619.TOVS20976.fed1rmmtao102.cox.net@fed1rmimpo02.cox.net> for ; Wed, 29 Jul 2009 05:36:19 -0400 Received: from darkstar.l.net ([98.165.138.223]) by fed1rmimpo02.cox.net with bizsmtp id MlcJ1c0014pNzHu04lcJCW; Wed, 29 Jul 2009 05:36:18 -0400 X-VR-Score: -10.00 X-Authority-Analysis: v=1.0 c=1 a=6I5d2MoRAAAA:8 a=IP17e_1XAAAA:8 a=pFyrSAfZfGu3VVamdZsA:9 a=CGFg5Hm8Y0c8xecLZxgA:7 a=lUdIwbW-6UFQrZpQkfA8xV_wpwMA:4 X-CM-Score: 0.00 Received: from localhost (localhost [127.0.0.1]) (uid 1001) by darkstar.l.net with local; Wed, 29 Jul 2009 02:36:17 -0700 id 00017A5F.4A701811.0000FA0D From: "Edward Sanford Sutton, III" To: freebsd-questions@freebsd.org Date: Wed, 29 Jul 2009 02:36:17 -0700 User-Agent: KMail/1.9.10 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907290236.17385.mirror176@cox.net> Subject: kernel panic on SATA 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: Wed, 29 Jul 2009 09:36:19 -0000 The FreeBSD Developers' Handbook describes how to get panic information (and dig out further details). http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#KERNELDEBUG-OBTAIN Was there any output before "ad7: FAILURE - device detached"? Losing the drive in the bios makes me think hardware, but I'd check for any firmware problems/updates if they exist. I have not tried yet, but FreeBSD8 is supposed to finally handle the anxiety of losing a drive. http://freebsdfoundation.org/press/2008Dec-newsletter.shtml#Project1 I would try smartctl from ports; run a long scan and read the full output to see if it passes or if you get a response like: # 1 Extended offline Completed: read failure 20% 32490 308342849 Also look above that output to see if there any metioned 'Error ## occured at disk power-on lifetime' type of messages. to scan, run: smartctl -t long /dev/ad7 after the scan, read output with: smartctl -a long /dev/ad7 What motherboard is it? "GeForce 8200" sounds like a graphics chipset to me. For hardware analysis, try to isolate it to a particular drive (sounds like it is only the seagate), cable (data or power), motherboard sata port. When the drive is not recognized, does a coldboot redetect it? Does the drive start any audible clicking? What model of drive is it? Make sure the drive is dusted off, increase the cooling, and try again; I have a drive that flakes out if the three speed antec fan in front of it is only on low but stabilizes when kept cooler; its a great hint to me that the drive is near life's end.