From owner-freebsd-questions@FreeBSD.ORG  Mon Nov 22 19:22:08 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8241D16A4CE
	for <questions@freebsd.org>; Mon, 22 Nov 2004 19:22:08 +0000 (GMT)
Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1A7BC43D31
	for <questions@freebsd.org>; Mon, 22 Nov 2004 19:22:08 +0000 (GMT)
	(envelope-from christias@gmail.com)
Received: by rproxy.gmail.com with SMTP id b11so272890rne
        for <questions@freebsd.org>; Mon, 22 Nov 2004 11:22:07 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=atM8+uhIwdIyPjHU95LZoDoL6bZaN5AUny6o6VT6Z2SaeOEUpfon1jnNzSbwJ5bGdKPjBuYqTB6jwexi+KvVQANIMLHSCtNWO59w6V9M9TvaF51GOmF4j6F10szK43im3cb+1cHq0s946Wvp5BRLa539NCCWC5Pvmjh2IpNdMj4=
Received: by 10.38.22.76 with SMTP id 76mr981980rnv;
        Mon, 22 Nov 2004 11:22:06 -0800 (PST)
Received: by 10.38.165.46 with HTTP; Mon, 22 Nov 2004 11:22:06 -0800 (PST)
Message-ID: <e4b0ecef04112211223d3b8961@mail.gmail.com>
Date: Mon, 22 Nov 2004 21:22:06 +0200
From: Panagiotis Christias <christias@gmail.com>
To: Marco Beishuizen <marco@beishuizen.info>
In-Reply-To: <Pine.BSF.4.61.0411221941440.77769@tsunami.bsd>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <20041120145845.O686@yokozuna.lan>
	 <e4b0ecef04112102477fe2aedf@mail.gmail.com>
	 <Pine.BSF.4.61.0411211158190.77660@tsunami.bsd>
	 <Pine.BSF.4.61.0411221941440.77769@tsunami.bsd>
cc: FreeBSD questions mailing list <questions@freebsd.org>
Subject: Re: "amr0: bad slot x completed" and fsck_ufs hanging
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Panagiotis Christias <christias@gmail.com>
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Nov 2004 19:22:08 -0000

On Mon, 22 Nov 2004 19:49:36 +0100 (CET), Marco Beishuizen
<marco@beishuizen.info> wrote:
> On stardate Sun, 21 Nov 2004, the wise Marco Beishuizen entered:
> 
> 
> 
> > On stardate Sun, 21 Nov 2004, the wise Panagiotis Christias entered:
> >
> >> the only hint I could find is from the amr(4) man page:
> >>
> >>  amr%d: bad slot %d completed
> >>
> >>  The controller reported completion of a command that the driver did not
> >>  issue.  This may result in data corruption, and suggests a hardware or
> >>  firmware problem with the system or controller.
> >>
> >> Do you have a second controller available to test? We have the same
> >> controllers in several of our servers and I would interested to find
> >> out what is the problem just in case..
> >
> > Unfortunately it's the only controller I have so I can't test it with an
> > other controller.
> >
> > It looks a bit strange that it could be a hardware or firmware problem
> > because the system is brand new. But does this mean I should update my
> > firmware to a newer version?
> >
> > Since you don't seem to have any problems with FreeBSD on this controller I'm
> > also interested in your configuration. Did you do anything special in the
> > BIOS of the controller or something?
> 
> Looks like I've found the problem.
> 
> I reinstalled everything, including the RAID arrays on the SCSI controller.
> The first time I changed the read and write policies in the BIOS console
> and it seems that wasn't a very good idea. Now I didn't change them, and
> all seems to run fine now.
> 
> So I'm glad that the hardware is ok and I don't have to upgrade the
> firmware.
> 
> Marco

use defaults, use defaults, use defaults, use defaults....