From joe@zircon.seattle.wa.us  Thu Feb 12 23:57:17 2009
Return-Path: <joe@zircon.seattle.wa.us>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id F3AD2106566B
	for <FreeBSD-gnats-submit@freebsd.org>; 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 <FreeBSD-gnats-submit@freebsd.org>; 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 <joe@zircon.seattle.wa.us>
Reply-To: Joe Kelsey <joe@zircon.seattle.wa.us>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: atapicam2: detached
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         131624
>Category:       kern
>Synopsis:       [atapicam] atapicam2: detached
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    mav
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Feb 13 00:00:12 UTC 2009
>Closed-Date:    Fri May 08 02:41:43 UTC 2009
>Last-Modified:  Fri May  8 02:50:01 UTC 2009
>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 <Seagate ST3400620AS 3.AAC> at ata2-master SATA300
ad6: 381554MB <Seagate ST3400620AS 3.AAC> 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:

From: Alexander Motin <mav@FreeBSD.org>
To: bug-followup@FreeBSD.org, joe@zircon.seattle.wa.us
Cc:  
Subject: Re: kern/131624: [atapicam] atapicam2: detached
Date: Thu, 07 May 2009 03:33:53 +0300

 You should give more information about your controller and also 
 reproduce it booting kernel with verbose messages. Disconnect could be 
 initiated by controller, if it lost SATA signals from drive.
 
 `ata reinit` command does not adds new found devices. You have to 
 `detach` and `attach` the whole ATA channel to found lost drive.
 
 -- 
 Alexander Motin
State-Changed-From-To: open->feedback 
State-Changed-By: linimon 
State-Changed-When: Thu May 7 18:11:17 UTC 2009 
State-Changed-Why:  
Note that feedback was requested. 


Responsible-Changed-From-To: freebsd-bugs->mav 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Thu May 7 18:11:17 UTC 2009 
Responsible-Changed-Why:  

http://www.freebsd.org/cgi/query-pr.cgi?pr=131624 

From: Joe Kelsey <joe@zircon.seattle.wa.us>
To: bug-followup@FreeBSD.org, joe@zircon.seattle.wa.us
Cc:  
Subject: Re: kern/131624: [atapicam] atapicam2: detached
Date: Thu, 07 May 2009 16:23:33 -0700

 I finally attributed the problem to a slowly failing disk drive.
 
 I eventually replaced the mirror with a new set of disks.
 
 The basic problem is that the kernel provided absolutely no information 
 about disk drive errors.  The disk drive eventually simply stopped 
 completely and I was forced to replace both drives in the mirror.
 
 The information I provided was the absolute limit to the amount of 
 information available from the kernel messages.
 
 It was a Promise SATA controller.
 
 
State-Changed-From-To: feedback->closed 
State-Changed-By: mav 
State-Changed-When: Fri May 8 02:41:06 UTC 2009 
State-Changed-Why:  
Originator reported that it is hardware problem. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=131624 

From: Alexander Motin <mav@FreeBSD.org>
To: bug-followup@FreeBSD.org, joe@zircon.seattle.wa.us
Cc:  
Subject: Re: kern/131624: [atapicam] atapicam2: detached
Date: Fri, 08 May 2009 05:40:16 +0300

 Ok. Thanks.
 
 Drive can die quite invisibly during a long time. You may use S.M.A.R.T. 
 tools to predict some kinds of drive failures. On the state when drive 
 just disappears is a bit late for OS to do anything about it.
 
 -- 
 Alexander Motin
>Unformatted:
