From owner-freebsd-questions@FreeBSD.ORG Mon Aug 30 13:26:03 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 B16921065695 for ; Mon, 30 Aug 2010 13:26:03 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6BA108FC29 for ; Mon, 30 Aug 2010 13:26:03 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Oq4N6-00075N-8F for freebsd-questions@freebsd.org; Mon, 30 Aug 2010 15:26:00 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Aug 2010 15:26:00 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Aug 2010 15:26:00 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Ivan Voras Date: Mon, 30 Aug 2010 15:25:53 +0200 Lines: 23 Message-ID: References: <20100830131822.529B3106564A@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.9) Gecko/20100518 Thunderbird/3.0.4 In-Reply-To: <20100830131822.529B3106564A@hub.freebsd.org> X-Enigmail-Version: 1.0.1 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: Mon, 30 Aug 2010 13:26:03 -0000 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.