From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 17:22:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF7AC1065697 for ; Wed, 4 Nov 2009 17:22:04 +0000 (UTC) (envelope-from nwf@cs.jhu.edu) Received: from blaze.cs.jhu.edu (blaze.cs.jhu.edu [128.220.13.50]) by mx1.freebsd.org (Postfix) with ESMTP id 95C668FC24 for ; Wed, 4 Nov 2009 17:22:04 +0000 (UTC) Received: from gradx.cs.jhu.edu (gradx.cs.jhu.edu [128.220.13.52]) by blaze.cs.jhu.edu (8.14.3/8.14.3) with ESMTP id nA4HM37G018424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 4 Nov 2009 12:22:03 -0500 (EST) Received: from gradx.cs.jhu.edu (localhost.localdomain [127.0.0.1]) by gradx.cs.jhu.edu (8.14.2/8.13.1) with ESMTP id nA4HM37n011176 for ; Wed, 4 Nov 2009 12:22:03 -0500 Received: (from nwf@localhost) by gradx.cs.jhu.edu (8.14.2/8.13.8/Submit) id nA4HM3is011175 for freebsd-current@freebsd.org; Wed, 4 Nov 2009 12:22:03 -0500 Date: Wed, 4 Nov 2009 12:22:03 -0500 From: Nathaniel W Filardo To: freebsd-current@freebsd.org Message-ID: <20091104172203.GJ19125@gradx.cs.jhu.edu> References: <20091029213929.GD19125@gradx.cs.jhu.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i57Ucs80xkCVE1Ce" Content-Disposition: inline In-Reply-To: <20091029213929.GD19125@gradx.cs.jhu.edu> User-Agent: Mutt/1.5.18 (2008-05-17) X-Mailman-Approved-At: Wed, 04 Nov 2009 17:28:09 +0000 Subject: Re: SATA disk error and hang until "atacontrol reinit" ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 17:22:05 -0000 --i57Ucs80xkCVE1Ce Content-Type: text/plain; charset=us-ascii Content-Disposition: inline As a follow up, I had this happen again, without rebooting after running "atacontrol reinit ata4". That worked a few times, but the interval between failed requests was very small... At some point, reiniting the channel simply said "no devices attached" and I went and bought a new disk, fearing the worst. Placing that on the channel, I attempted "atacontrol reinit" again and it still refused to see the new disk. I tested both the new and old disks with a different controller and they worked fine. On the suggestion of ##freebsd, I ran "atacontrol detach ata4" and "atacontrol attach ata4"; the former completed, the latter produced this (via serial console): hydra# atacontrol attach ata4 ata4: [ITHREAD] 60201-4533^[[2;2~Master: no device present Slave: no device present ast data access mmu miss t ra p: f cpuid = 0 which I assume really meant to be "trap: fast data access mmu miss". I amn't sure what that means, but I have this lovely multi-gig core file now... which is potentially of little utility since I get told "GDB can't read core files on this machine." but if somebody wants something out of it, just ask. In any case, I powered the machine off, put the old disk back, and rebooted and am now scrubbing the RAIDZ, but it sees the old disk just fine. Suggestions? --nwf; --i57Ucs80xkCVE1Ce Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkrxuDsACgkQTeQabvr9Tc+SZgCaAzh1t0lK7kmij1nR+yIQY/3N o10An3d6hptb9u5p4mcbmGdww720oxIn =I1qj -----END PGP SIGNATURE----- --i57Ucs80xkCVE1Ce--