Date: Sat, 13 Apr 2013 14:14:42 -0400 From: Charles Sprickman <spork@bway.net> To: Quartz <quartz@sneakertech.com> Cc: freebsd-fs@freebsd.org, =?utf-8?Q?Radio_m=C5=82odych_bandyt=C3=B3w?= <radiomlodychbandytow@o2.pl> Subject: Re: A failed drive causes system to hang Message-ID: <4617BC69-842C-422E-9616-3BCDC11C0048@bway.net> In-Reply-To: <51691524.4050009@sneakertech.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 13, 2013, at 4:19 AM, Quartz wrote: >=20 >> As to dmesg, tough luck. I have 2 photos on my phone and their >> transcripts are all I can give until the problem reappears >=20 > I think there's a communication gap here. >=20 > 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 >=20 > ______________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4617BC69-842C-422E-9616-3BCDC11C0048>