From owner-freebsd-current Wed Jul 24 10:00:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA00597 for current-outgoing; Wed, 24 Jul 1996 10:00:07 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA00592 for ; Wed, 24 Jul 1996 10:00:06 -0700 (PDT) Received: from sun ([165.254.119.3]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id KAA03549 for ; Wed, 24 Jul 1996 10:00:04 -0700 Received: (from amir@localhost) by sun (8.6.13/8.6.12) id MAA01886; Wed, 24 Jul 1996 12:58:07 -0400 Date: Wed, 24 Jul 1996 12:58:06 -0400 (EDT) From: Amir Rosenblatt To: "Michael L. VanLoon -- HeadCandy.com" cc: "Amir Y. Rosenblatt" , freebsd-current@freebsd.org Subject: Re: A new twist on the reboot problems In-Reply-To: <199607241641.JAA00407@MindBender.HeadCandy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Jul 1996, Michael L. VanLoon -- HeadCandy.com wrote: > I would definitely say that it's either a dying power supply, or a > dying hard drive (having trouble spinning up). Yeah, I'm about 95% sure it's the hard drive. I shuffled things around this morning a bit to give that drive more breathing room (glad I got a full tower case :) It's been behaving since then -- if it doesn't crash in the next 12 hours or so, then I'm going to run under the assumption that it was a heat problem. Otherwise I'll swap it out for a fresh drive. I'll be calling Seagate this afternoon anyway to see what they can tell me about this sorta stuff. > Either way, I'm pretty positive you're seeing bad hardware somewhere > if you're getting this many crashes. Yeah, it's looking that way. Thanks for your time, -Amir