From owner-freebsd-fs@FreeBSD.ORG Sun Apr 14 18:31:59 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 03A45B40 for ; Sun, 14 Apr 2013 18:31:59 +0000 (UTC) (envelope-from radiomlodychbandytow@o2.pl) Received: from moh3-ve1.go2.pl (moh3-ve2.go2.pl [193.17.41.86]) by mx1.freebsd.org (Postfix) with ESMTP id B7DE9CE2 for ; Sun, 14 Apr 2013 18:31:58 +0000 (UTC) Received: from moh3-ve1.go2.pl (unknown [10.0.0.157]) by moh3-ve1.go2.pl (Postfix) with ESMTP id 30AF7AF696C for ; Sun, 14 Apr 2013 20:31:57 +0200 (CEST) Received: from unknown (unknown [10.0.0.108]) by moh3-ve1.go2.pl (Postfix) with SMTP for ; Sun, 14 Apr 2013 20:31:57 +0200 (CEST) Received: from unknown [93.175.66.185] by poczta.o2.pl with ESMTP id zSKbSz; Sun, 14 Apr 2013 20:31:55 +0200 Message-ID: <516AF61B.7060204@o2.pl> Date: Sun, 14 Apr 2013 20:31:55 +0200 From: =?UTF-8?B?UmFkaW8gbcWCb2R5Y2ggYmFuZHl0w7N3?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130407 Thunderbird/17.0.5 MIME-Version: 1.0 To: Steven Hartland Subject: Re: A failed drive causes system to hang References: <516A8092.2080002@o2.pl> <9C59759CB64B4BE282C1D1345DD0C78E@multiplay.co.uk> In-Reply-To: <9C59759CB64B4BE282C1D1345DD0C78E@multiplay.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-O2-Trust: 1, 34 X-O2-SPF: neutral 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:31:59 -0000 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. > > Regards > Steve > > ================================================ > This e.mail is private and confidential between Multiplay (UK) Ltd. and > the person or entity to whom it is addressed. In the event of > misdirection, the recipient is prohibited from using, copying, printing > or otherwise disseminating it or any information contained in it. > In the event of misdirection, illegible or incomplete transmission > please telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk. > > No errors on any of these drives. -- Twoje radio