From owner-freebsd-fs@FreeBSD.ORG Sun Apr 14 10:35:48 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 286D66AA for ; Sun, 14 Apr 2013 10:35:48 +0000 (UTC) (envelope-from radiomlodychbandytow@o2.pl) Received: from moh3-ve1.go2.pl (moh3-ve1.go2.pl [193.17.41.30]) by mx1.freebsd.org (Postfix) with ESMTP id DF97BA09 for ; Sun, 14 Apr 2013 10:35:47 +0000 (UTC) Received: from moh3-ve1.go2.pl (unknown [10.0.0.117]) by moh3-ve1.go2.pl (Postfix) with ESMTP id 8C83CA6A029 for ; Sun, 14 Apr 2013 12:35:46 +0200 (CEST) Received: from unknown (unknown [10.0.0.108]) by moh3-ve1.go2.pl (Postfix) with SMTP for ; Sun, 14 Apr 2013 12:35:46 +0200 (CEST) Received: from unknown [93.175.66.185] by poczta.o2.pl with ESMTP id QtpKGS; Sun, 14 Apr 2013 12:35:44 +0200 Message-ID: <516A8680.2020107@o2.pl> Date: Sun, 14 Apr 2013 12:35:44 +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: Charles Sprickman Subject: Re: A failed drive causes system to hang References: <51672164.1090908@o2.pl> <20130411212408.GA60159@icarus.home.lan> <5168821F.5020502@o2.pl> <51691524.4050009@sneakertech.com> <4617BC69-842C-422E-9616-3BCDC11C0048@bway.net> In-Reply-To: <4617BC69-842C-422E-9616-3BCDC11C0048@bway.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-O2-Trust: 1, 31 X-O2-SPF: neutral 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 10:35:48 -0000 On 13/04/2013 20:14, Charles Sprickman wrote: > On Apr 13, 2013, at 4:19 AM, Quartz wrote: > >> >>> As to dmesg, tough luck. I have 2 photos on my phone and their >>> transcripts are all I can give until the problem reappears >> >> I think there's a communication gap here. >> >> While a messages and logs from the time the incident happens are ideal, Jeremy *also* just needs to see the generic info about your hardware, which can be found in any dmesg taken at any time. > > More specifically, I think the OP did supply the full output of the 'dmesg' *command*, but what I think is wanted is the contents of /var/run/dmesg.boot. > > Charles > >> >> ______________________________________ >> it has a certain smooth-brained appeal >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > Yeah. Thanks, I didn't even know about /var/run/dmesg.boot existence. -- Twoje radio