From owner-freebsd-fs@FreeBSD.ORG Sun Apr 14 18:51:22 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 177C4E4A for ; Sun, 14 Apr 2013 18:51:22 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:228]) by mx1.freebsd.org (Postfix) with ESMTP id EF033D6D for ; Sun, 14 Apr 2013 18:51:21 +0000 (UTC) Received: from omta21.emeryville.ca.mail.comcast.net ([76.96.30.88]) by qmta15.emeryville.ca.mail.comcast.net with comcast id PuQK1l0021u4NiLAFurM08; Sun, 14 Apr 2013 18:51:21 +0000 Received: from koitsu.strangled.net ([67.180.84.87]) by omta21.emeryville.ca.mail.comcast.net with comcast id PurH1l00y1t3BNj8hurJoF; Sun, 14 Apr 2013 18:51:20 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id B640973A33; Sun, 14 Apr 2013 11:51:17 -0700 (PDT) Date: Sun, 14 Apr 2013 11:51:17 -0700 From: Jeremy Chadwick To: Radio =?unknown-8bit?B?bcU/b2R5Y2ggYmFuZHl0w7N3?= Subject: Re: A failed drive causes system to hang Message-ID: <20130414185117.GA38259@icarus.home.lan> References: <516A8092.2080002@o2.pl> <9C59759CB64B4BE282C1D1345DD0C78E@multiplay.co.uk> <516AF61B.7060204@o2.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <516AF61B.7060204@o2.pl> User-Agent: Mutt/1.5.21 (2010-09-15) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1365965481; bh=aFlhudGBuSyEIQpvUvzPrBEU0hp/uBYCAjeLPdB7KSw=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=ChOvudQdeeWdlUIUmjtao4JIR2ZUjo8pMBS2wfxzjt7tYdVdiSH6VeYl5IKhIAtS5 I8EypUwTxezsw+KJNIH7JE8NGBTA9OP7g8SSQKov88NDMAcFu78G8l5jhGTkY5rhmG GsphLoYvSWzfW3JVr+9bE+v9klkFwKm/53MFt0aH1D7ngWQvBo1uECzmAeXF8ePJOg uJrj16JMeXykR7RoBAUcVygfj0jNfW5z7domD0Fk6rrx4AqVmTEQsVSI8dsmjIauaT ljh3JWbRtQe/wRJrVFZTP/K/DGQUUK8+sgtP0niekkQK5+4V1yTonoapv0o6BtSo/C VGpPXj+L6aIMA== Cc: freebsd-fs@freebsd.org, support@lists.pcbsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Apr 2013 18:51:22 -0000 On Sun, Apr 14, 2013 at 08:31:55PM +0200, Radio m?odych bandytw wrote: > On 14/04/2013 16:09, Steven Hartland wrote: > > > >----- Original Message ----- From: "Radio mlodych bandytów" > > > >To: > >Cc: > >Sent: Sunday, April 14, 2013 11:10 AM > >Subject: A failed drive causes system to hang > > > > > >>Cross-post from freebsd-fs: > >>http://docs.freebsd.org/cgi/getmsg.cgi?fetch=333977+0+archive/2013/freebsd-fs/20130414.freebsd-fs > >> > >> > >>I have a failing drive in my array. I need to RMA it, but don't have > >>time and it fails rarely enough to be a yet another annoyance. > >>The failure is simple: it fails to respond. > >>When it happens, the only thing I found I can do is switch consoles. > >>Any command hangs, login on different consoles hangs, apps hang. > >>I run PC-BSD 9.1. > >> > >>On the 1st console I see a series of messages like: > >> > >>(ada0:ahcich0:0:0:0): CAM status: Command timeout > >>(ada0:ahcich0:0:0:0): Error 5, Periph was invalidated > >>(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED > >> > >>I've seen it happening even when running an installer from a different > >>drive, while preparing installation (don't remember which step). > >> > >>I have partial dmesg screenshots from an older failure (21st of > >>December 2012), transcript below: > >> > >>Screen1: > >>(ada0:ahcich0:0:0:0): FLUSHCACHE40. ACB: (ea?) 00 00 00 00 (cut?) > >>(ada0:ahcich0:0:0:0): CAM status: Unconditionally Re-qu (cut) > >>(ada0:ahcich0:0:0:0): Error 5, Periph was invalidated > >>(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 05 d3(cut) > >>00 > > > >smartctl has the ability to print out the queued log file if > >the drive supports it. This may give you some more information > >on what the problem may be with your drive. > > No errors on any of these drives. Please provide full output from the following command, and please retain the formatting (pastebin, etc.): smartctl -x /dev/ada0 I would also appreciate seeing the same output for the other drives on the system (specifically /dev/ada1 and /dev/ada2), now that I've seen the dmesg output. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |