From owner-freebsd-questions@FreeBSD.ORG Mon Jan 18 14:50:51 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 39265106566B for ; Mon, 18 Jan 2010 14:50:51 +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 E86F58FC15 for ; Mon, 18 Jan 2010 14:50:50 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NWswK-0000pR-4o for freebsd-questions@freebsd.org; Mon, 18 Jan 2010 15:50:48 +0100 Received: from 93-138-35-57.adsl.net.t-com.hr ([93.138.35.57]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 18 Jan 2010 15:50:48 +0100 Received: from ivoras by 93-138-35-57.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 18 Jan 2010 15:50:48 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Ivan Voras Date: Mon, 18 Jan 2010 15:50:25 +0100 Lines: 26 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 93-138-35-57.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.21 (X11/20090612) In-Reply-To: Sender: news Subject: Re: gmirror+gjournal: spontaneous reboots on "excessive" disk access 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, 18 Jan 2010 14:50:51 -0000 Michael Grimm wrote: > Hi -- > > I'm running a gmirror raid1 plus gjournal for a year now. This is a > 7.2-RELEASE-p6 right now. Both disks are regular ATA and healthy > according smartctl. > > Sometimes, not always though, I do experience spontaneous reboots > without leaving any hints in logfiles whenver I "beat" my disks > "excessively". This might be something like: > > dd if=/dev/null of=/some/file bs=1M count=4k > plus > parallel disk accesses by mail and news server. > > If I omit all parallel disk access those dd's will run to completion > without reboots, always. What you have is a common symptom of hardware problems - either a weak power supply or a broken disk controller. In the first case because two drives try to suck power where only one was doing it before and in the second reason because the disk controller is too broken to correctly handle simultaneous access to two drives. Unfortunately, if you don't get any console error messages it is hard to tell which. The power supply is usually easier to replace.