From owner-freebsd-hubs@FreeBSD.ORG Sun Jan 23 12:36:03 2011 Return-Path: Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B351D106564A for ; Sun, 23 Jan 2011 12:36:03 +0000 (UTC) (envelope-from fabian@wenks.ch) Received: from batman.home4u.ch (batman.home4u.ch [IPv6:2001:8a8:1005:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 49B548FC08 for ; Sun, 23 Jan 2011 12:36:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at home4u.ch Received: from tatsu.wenks.ch (fabian@superman.wenks.ch [62.12.173.3]) (authenticated bits=0) by batman.home4u.ch (8.14.4/8.14.4) with ESMTP id p0NCa0jS088578 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sun, 23 Jan 2011 13:36:01 +0100 (CET) (envelope-from fabian@wenks.ch) Message-ID: <4D3C20B0.10205@wenks.ch> Date: Sun, 23 Jan 2011 13:36:00 +0100 From: Fabian Wenk User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-hubs@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: bg.freebsd.org down X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD Distributions Hubs: mail sup ftp" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2011 12:36:03 -0000 Hello Dimitar On 23.01.11 12:31, Dimitar Vassilev wrote: > Situation is that the ARC1120 we got behaves flaky and marks whenever > it wants some of the disks as bad. A few years ago I had the same problem with an ARC-1220 and Western Digital RE2 WD5000YS disks. The Areca marked the disks as bad, but after removing and reinserting it back, it was working fine again. It was a bug in the firmware of the disks, sometimes they took too long to respond to S.M.A.R.T requests from the RAID controller and then the Areca decided that this disk was broken. A firmware upgrade from WD fixed the problem, but for doing the upgrade the SATA disks needed to be attached to a regular SATA controller (not the Areca RAID controller). The flash utility needed to be started from a DOS disk. bye Fabian