From owner-freebsd-scsi@FreeBSD.ORG Fri May 9 13:41:42 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C23E37B401 for ; Fri, 9 May 2003 13:41:42 -0700 (PDT) Received: from eowyn.nextra.cz (eowyn.nextra.cz [213.210.153.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id E21CA43FA3 for ; Fri, 9 May 2003 13:41:39 -0700 (PDT) (envelope-from benkovsk@eowyn.nextra.cz) Received: from eowyn.nextra.cz (localhost [127.0.0.1]) by eowyn.nextra.cz (8.12.6/8.12.6) with ESMTP id h49Kf2xf078356 for ; Fri, 9 May 2003 22:41:02 +0200 (CEST) (envelope-from benkovsk@eowyn.nextra.cz) Received: (from benkovsk@localhost) by eowyn.nextra.cz (8.12.6/8.12.6/Submit) id h49Kf2gZ078355 for freebsd-scsi@freebsd.org; Fri, 9 May 2003 22:41:02 +0200 (CEST) Date: Fri, 9 May 2003 22:41:02 +0200 From: benkovsky@nextra.cz To: freebsd-scsi@freebsd.org Message-ID: <20030509204102.GF70376@nextra.cz> References: <0E3FA95632D6D047BA649F95DAB60E57023AE184@EXA-ATLANTA.se.lsil.com> <20030509181835.E09B143FBF@mx1.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030509181835.E09B143FBF@mx1.FreeBSD.org> X-NCC-RegID: cz.terminal User-Agent: Mutt/1.5.4i Subject: Re: RAID status on PowerEdge 2600 with Perc 4/DI X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2003 20:41:42 -0000 On Fri, May 09, 2003 at 02:18:33PM -0400, lists@mediumgreen.com wrote: > > So, I created the amr0 device, started it up: > > RAID Monitor Service Free BSD Version 1.02 Feb 18, 2003 started > tail > Initial CheckConsistency Schedule :- > EnableFlag: 1 > Date: 05/09/2003 > DayOfWeek: 0 > HourOfDay: 0 > Week(s): 1 > ReportChkonProgInterval: 0 seconds(0 means report in-frequently) > > > And my machine hung - I had to call someone to go and press it's reset > button. Similar for me. First time it caused /bin/sh to coredump immediately when run, second time it rebooted the machine -- Jaroslav Benkovsky