From owner-freebsd-questions@FreeBSD.ORG Sun Nov 21 11:23:59 2004 Return-Path: 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 447DC16A4CE for ; Sun, 21 Nov 2004 11:23:59 +0000 (GMT) Received: from smtp17.wxs.nl (smtp17.wxs.nl [195.121.6.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD79543D53 for ; Sun, 21 Nov 2004 11:23:58 +0000 (GMT) (envelope-from marco@beishuizen.info) Received: from tsunami.bsd (ipd50a233c.speed.planet.nl [213.10.35.60]) by smtp17.wxs.nl (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0I7J00ADR0ZXBX@smtp17.wxs.nl> for questions@freebsd.org; Sun, 21 Nov 2004 12:23:57 +0100 (CET) Date: Sun, 21 Nov 2004 12:23:57 +0100 (CET) From: Marco Beishuizen In-reply-to: Sender: marco@tsunami.bsd To: Panagiotis Christias Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII; format=flowed Content-transfer-encoding: 7BIT FreeBSD: Homepage: References: <20041120145845.O686@yokozuna.lan> cc: FreeBSD questions mailing list 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: Marco Beishuizen List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 11:23:59 -0000 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? Thanks, Marco -- If Patrick Henry thought that taxation without representation was bad, he should see how bad it is with representation.