From owner-freebsd-bugs@FreeBSD.ORG Fri Feb 13 00:00:12 2009 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E97761065677 for ; Fri, 13 Feb 2009 00:00:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B081B8FC0A for ; Fri, 13 Feb 2009 00:00:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n1D00Cat060173 for ; Fri, 13 Feb 2009 00:00:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n1D00CQU060172; Fri, 13 Feb 2009 00:00:12 GMT (envelope-from gnats) Resent-Date: Fri, 13 Feb 2009 00:00:12 GMT Resent-Message-Id: <200902130000.n1D00CQU060172@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Joe Kelsey Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3AD2106566B for ; Thu, 12 Feb 2009 23:57:16 +0000 (UTC) (envelope-from joe@zircon.seattle.wa.us) Received: from zircon.seattle.wa.us (zircon.seattle.wa.us [71.164.28.3]) by mx1.freebsd.org (Postfix) with ESMTP id D0B508FC16 for ; Thu, 12 Feb 2009 23:57:16 +0000 (UTC) (envelope-from joe@zircon.seattle.wa.us) Received: (qmail 11965 invoked by uid 1001); 12 Feb 2009 23:57:16 -0000 Message-Id: <20090212235716.11964.qmail@zircon.seattle.wa.us> Date: 12 Feb 2009 23:57:16 -0000 From: Joe Kelsey To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: kern/131624: atapicam2: detached X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joe Kelsey List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2009 00:00:13 -0000 >Number: 131624 >Category: kern >Synopsis: atapicam2: detached >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Feb 13 00:00:12 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Joe Kelsey >Release: FreeBSD 7.1-STABLE amd64 >Organization: Joseph M. Kelsey >Environment: System: FreeBSD zircon.zircon.seattle.wa.us 7.1-STABLE FreeBSD 7.1-STABLE #32: Wed Feb 11 18:06:03 PST 2009 root@:/usr/obj/usr/src/sys/ZIRCON amd64 >Description: One of my disk drives just started "detach"ing. There is apparantly no way to "reattach" this drive once it "detaches". I am completely at a loss for what to do. From dmesg: ad4: 381554MB at ata2-master SATA300 ad6: 381554MB at ata3-master SATA300 subdisk4: detached ad4: detached atapicam2: detached So, basically, ad4 just disappears from the system. I have tried to puzzle out the mysterious documentation around atacontrol to no avail. There doesn't seem to be any relationship between "ata channels" and the system except for random printouts during booting. There is no place to ask for a list of channels that I can find. If I try to "reinit" the channel, it reports no masters or slaves found. The disk is simply missing. $ atacontrol reinit ata2 Master: no device present Slave: no device present >How-To-Repeat: Hardware problems on ad4. How do I get more information about things that may or may not be happening? >Fix: >Release-Note: >Audit-Trail: >Unformatted: