From owner-freebsd-questions@FreeBSD.ORG Mon Aug 30 13:18:22 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 529B3106564A for ; Mon, 30 Aug 2010 13:18:22 +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 49B028FC08 for ; Mon, 30 Aug 2010 13:18:21 +0000 (UTC) Received: (qmail 98077 invoked by uid 89); 30 Aug 2010 13:17:24 -0000 Received: from localhost (HELO freequeue.vfemail.net) (127.0.0.1) by localhost with SMTP; 30 Aug 2010 13:17:23 -0000 Received: (qmail 76741 invoked by uid 89); 30 Aug 2010 11:24:40 -0000 Received: from unknown (HELO www-52-2.vfemail.net) (vfemail@172.16.100.52) by FreeQueue with SMTP; 30 Aug 2010 11:24:40 -0000 Received: (qmail 58242 invoked by uid 89); 30 Aug 2010 11:25:18 -0000 Received: by simscan 1.4.0 ppid: 58194, pid: 58235, t: 0.2750s scanners:none Received: from unknown (HELO Bacchus.vfemail.net) (cGV0ZXJAdmZlbWFpbC5uZXQ=@67.101.12.44) by 172.16.100.52 with ESMTPA; 30 Aug 2010 11:25:18 -0000 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 30 Aug 2010 07:24:55 -0400 To: freebsd-questions@freebsd.org From: peter@vfemail.net Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-Id: <20100830131822.529B3106564A@hub.freebsd.org> Subject: 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: Mon, 30 Aug 2010 13:18:22 -0000 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? Is there anything else I should explore or do at this time? ------------------------------------------------- This message sent via VFEmail.net http://www.vfemail.net $14.95 Lifetime accounts - 1GB disk, No bandwidth quotas!