From owner-freebsd-questions@FreeBSD.ORG Fri Sep 3 21:19:54 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B071010656A9 for ; Fri, 3 Sep 2010 21:19:54 +0000 (UTC) (envelope-from peter@vfemail.net) Received: from vfemail.net (dotsevenfive.vfemail.net [69.11.239.75]) by mx1.freebsd.org (Postfix) with ESMTP id EFB908FC1B for ; Fri, 3 Sep 2010 21:19:53 +0000 (UTC) Received: (qmail 579 invoked by uid 89); 3 Sep 2010 21:17:50 -0000 Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1) by localhost with SMTP; 3 Sep 2010 21:17:49 -0000 Received: (qmail 562 invoked by uid 89); 3 Sep 2010 21:17:32 -0000 Received: from unknown (HELO www-51-2.vfemail.net) (vfemail@172.16.100.51) by FreeQueue with SMTP; 3 Sep 2010 21:17:32 -0000 Received: (qmail 69869 invoked by uid 89); 3 Sep 2010 21:19:36 -0000 Received: by simscan 1.4.0 ppid: 69861, pid: 69864, t: 0.1939s scanners:none Received: from unknown (HELO Bacchus.vfemail.net) (cGV0ZXJAdmZlbWFpbC5uZXQ=@67.101.12.44) by 172.16.100.51 with ESMTPA; 3 Sep 2010 21:19:36 -0000 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 03 Sep 2010 17:19:02 -0400 To: freebsd-questions@freebsd.org From: peter@vfemail.net In-Reply-To: References: <20100830131822.529B3106564A@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <20100903211954.B071010656A9@hub.freebsd.org> Subject: Re: What made my FreeBSD server freeze? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Sep 2010 21:19:54 -0000 Thanks. I cloned the hard drive and replaced the old drive with the new drive this afternoon. ------- At 09:25 AM 8/30/2010, Ivan Voras wrote: >On 08/30/10 13:24, peter@vfemail.net wrote: >> >>When I awoke this morning my FreeBSD box was frozen -- completely unresponsive at the console -- and displayed these messages on the console: >> >> ad0: READ command timeout tag=0 serv=0 -resetting >> ata0: resetting devices >> ad0: removed from configuration >> done >> Aug 30 03:09:25 abc sm-mta 88427 xyz SYSERR(root): collect: Cannot write: ./xyz (fsync uid=o, gid=25): Device not configured >> >>The box has been in continuous operation for years, and I've never seen this behavior before. >> >>I rebooted the machine this morning and, thank God, it came back to life. >> >>Is this an early warning that the hard drive is failing and should be replaced this week? > >Very probably! > >>Is there anything else I should explore or do at this time? > >If not the drive, check drive cables, the power supply and motherboard/CPU overheating. > > >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" ------------------------------------------------- This message sent via VFEmail.net http://www.vfemail.net $14.95 Lifetime accounts - 1GB disk, No bandwidth quotas!