Date: Sun, 14 Apr 2013 12:35:44 +0200 From: =?UTF-8?B?UmFkaW8gbcWCb2R5Y2ggYmFuZHl0w7N3?= <radiomlodychbandytow@o2.pl> To: Charles Sprickman <spork@bway.net> Cc: freebsd-fs@freebsd.org Subject: Re: A failed drive causes system to hang Message-ID: <516A8680.2020107@o2.pl> In-Reply-To: <4617BC69-842C-422E-9616-3BCDC11C0048@bway.net> References: <mailman.11.1365681601.78138.freebsd-fs@freebsd.org> <51672164.1090908@o2.pl> <20130411212408.GA60159@icarus.home.lan> <5168821F.5020502@o2.pl> <51691524.4050009@sneakertech.com> <4617BC69-842C-422E-9616-3BCDC11C0048@bway.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?516A8680.2020107>