From owner-freebsd-questions@FreeBSD.ORG Mon Dec 20 20:03:06 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 E903816A4F4 for ; Mon, 20 Dec 2004 20:03:04 +0000 (GMT) Received: from allrounder.lame.at (mail.lame.at [195.58.166.252]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85BCA43D46 for ; Mon, 20 Dec 2004 20:03:04 +0000 (GMT) (envelope-from haimat@lame.at) Received: from itchy.lame.at (home.lame.at [80.78.254.138]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by allrounder.lame.at (Postfix) with ESMTP id 3BA0830151 for ; Mon, 20 Dec 2004 21:03:02 +0100 (CET) From: "Matthias F. Brandstetter" To: freebsd-questions@freebsd.org Date: Mon, 20 Dec 2004 21:03:00 +0100 User-Agent: KMail/1.7 References: <41C2CF1A.8090207@cartoon-film.de> In-Reply-To: <41C2CF1A.8090207@cartoon-film.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412202103.01069.haimat@lame.at> Subject: Re: RAID0 problem array broken X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 20:03:06 -0000 ---------- quoting Karsten Fuhrmann ---------- > But now my ar0 stripe will not be recognised anymore. > /var/log/messages showed this : > Dec 17 03:24:44 darkstar kernel: ad6: FAILURE - ATA_IDENTIFY timed out > Dec 17 03:24:49 darkstar kernel: ad6: FAILURE - ATA_IDENTIFY timed out > Dec 17 03:24:49 darkstar kernel: ad6: deleted from ar0 disk1 > Dec 17 03:24:49 darkstar kernel: ar0: ERROR - array broken > Dec 17 03:24:49 darkstar kernel: ad6: WARNING - removed from > configuration Dec 17 03:24:49 darkstar kernel: ar0: ERROR - array broken I had a very similar problem with a RAID1 on a raid hardware controller. I managed to re-build the broken array from within the controller's BIOS during bootup. It seems this error comes from the broken DMA support on 5.3, so I disabled DMA for my disks on this server via sysctl. Hey guys, what's the status of this DMA issue? Greetings, Matthias -- As I got up in front of them, I felt an intoxication that had nothing to do with alcohol. It was the intoxication of being a public spectacle. -- Homer Simpson Dancin' Homer