Date: Fri, 14 Aug 2009 06:02:52 +0200 From: Polytropon <freebsd@edvax.de> To: Ian Smith <smithi@nimnet.asn.au> Cc: Steve Bertrand <steve@ibctech.ca>, PJ <af.gourmet@videotron.ca>, wmoran@potentialtech.com, Roland Smith <rsmith@xs4all.nl>, Polytropon <freebsd@edvax.de>, freebsd-questions@freebsd.org Subject: Re: boot sector f*ed Message-ID: <20090814060252.97030a97.freebsd@edvax.de> In-Reply-To: <20090814012551.H19821@sola.nimnet.asn.au> References: <20090811173211.6FE4D106567B@hub.freebsd.org> <20090812193008.F19821@sola.nimnet.asn.au> <4A82A8D9.30406@videotron.ca> <20090812172704.GA27066@slackbox.xs4all.nl> <4A831DF7.9090506@videotron.ca> <20090812232810.GA37833@slackbox.xs4all.nl> <4A841AC2.1050809@videotron.ca> <20090814012551.H19821@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Aug 2009 13:41:48 +1000 (EST), Ian Smith <smithi@nimnet.asn.au> wrote: > Smells like flakey hardware .. intermittent, inexplicable glitches. It > might survive hours on one workload, minutes on another, no sense to it? I could guess defective RAM here... I suggest running memtest for some hours, just to be sure. It's really a bad situation when you're searching for a software problem when there's none, instead it is explainable by a hardware problem. > Sometimes, quite often in fact, I've found just disassembling, thorough > cleaning, fresh heatsink paste maybe, and reassembly solves many issues, > without ever knowing what exactly did the trick. Life's like that .. This is called "doing nothing." :-) From my own experience, if sometimes really works. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090814060252.97030a97.freebsd>