From owner-freebsd-fs@FreeBSD.ORG Sun Apr 14 14:09:31 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 09964A97 for ; Sun, 14 Apr 2013 14:09:31 +0000 (UTC) (envelope-from prvs=1816034565=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id A3D72D9 for ; Sun, 14 Apr 2013 14:09:30 +0000 (UTC) Received: from r2d2 ([46.65.172.4]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50003265740.msg for ; Sun, 14 Apr 2013 15:09:23 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 14 Apr 2013 15:09:23 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 46.65.172.4 X-Return-Path: prvs=1816034565=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@freebsd.org Message-ID: <9C59759CB64B4BE282C1D1345DD0C78E@multiplay.co.uk> From: "Steven Hartland" To: =?iso-8859-1?Q?Radio_mlodych_bandyt=F3w?= , References: <516A8092.2080002@o2.pl> Subject: Re: A failed drive causes system to hang Date: Sun, 14 Apr 2013 15:09:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-fs@freebsd.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 14:09:31 -0000 ----- 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.