On Mon, Jul 07, 2003 at 11:28:51AM +0100, Matthew Seaman wrote:
> On Mon, Jul 07, 2003 at 06:18:12AM -0400, Jud wrote:
> > On 06 Jul 2003 15:18:51 -0400, "Adam" <[EMAIL PROTECTED]> said:
> > > On Sun, 2003-07-06 at 14:10, Bill Moran wrote:
> > > > Sounds like a HDD going ... I had a similar sceneri
On Mon, Jul 07, 2003 at 06:18:12AM -0400, Jud wrote:
> On 06 Jul 2003 15:18:51 -0400, "Adam" <[EMAIL PROTECTED]> said:
> > On Sun, 2003-07-06 at 14:10, Bill Moran wrote:
> > > Sounds like a HDD going ... I had a similar sceneria a few months ago
> > > and it was the HDD.
> > > You could get a FreeS
On 06 Jul 2003 15:18:51 -0400, "Adam" <[EMAIL PROTECTED]> said:
> On Sun, 2003-07-06 at 14:10, Bill Moran wrote:
> > Sounds like a HDD going ... I had a similar sceneria a few months ago
> > and it was the HDD.
> > You could get a FreeSBIE CD, boot it and run cpuburn to test the CPU.
>
> Good idea
On Sun, 2003-07-06 at 14:10, Bill Moran wrote:
> Sounds like a HDD going ... I had a similar sceneria a few months ago
> and it was the HDD.
> You could get a FreeSBIE CD, boot it and run cpuburn to test the CPU.
Good idea about FreeSBIE. I'll take a look at that in more detail
tomorrow. Thanks.
Adam wrote:
My main FreeBSD (4.8) box has died on me again, and I'm 99% certain it's
due to hardware failure. However, I'm having a very hard time
determining what hardware is going bad, due to the nature of the crash.
Let me describe the scenario.
I was working on the machine, not doing anything
My main FreeBSD (4.8) box has died on me again, and I'm 99% certain it's
due to hardware failure. However, I'm having a very hard time
determining what hardware is going bad, due to the nature of the crash.
Let me describe the scenario.
I was working on the machine, not doing anything out of the
