Date: Sun, 14 Apr 2013 11:51:17 -0700 From: Jeremy Chadwick <jdc@koitsu.org> To: Radio =?unknown-8bit?B?bcU/b2R5Y2ggYmFuZHl0w7N3?= <radiomlodychbandytow@o2.pl> Cc: freebsd-fs@freebsd.org, support@lists.pcbsd.org Subject: Re: A failed drive causes system to hang Message-ID: <20130414185117.GA38259@icarus.home.lan> In-Reply-To: <516AF61B.7060204@o2.pl> References: <516A8092.2080002@o2.pl> <9C59759CB64B4BE282C1D1345DD0C78E@multiplay.co.uk> <516AF61B.7060204@o2.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
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" > ><radiomlodychbandytow@o2.pl> > >To: <support@lists.pcbsd.org> > >Cc: <freebsd-fs@freebsd.org> > >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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130414185117.GA38259>