kern/131624: atapicam2: detached

[Joe Kelsey]

>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 <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:
>Unformatted: