From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phil Turmel Subject: Re: Mdadm server eating drives Date: Wed, 03 Jul 2013 10:36:32 -0400 Message-ID: <51D436F0.7050503@turmel.org> References: <51BB8A67.5000605@turmel.org> <51BB8B86.9050803@turmel.org> <51CC72A4.4040508@jungers.net> <51D233A5.504@hardwarefreak.com> <51D32DBB.8030401@hardwarefreak.com> <51D38354.6090001@har dwarefreak.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Jon Nelson Cc: Barrett Lewis , Stan Hoeppner , "linux-raid@vger.kernel.org" List-Id: linux-raid.ids On 07/03/2013 10:03 AM, Jon Nelson wrote: > On Wed, Jul 3, 2013 at 12:26 AM, Barrett Lewis > wrote: >> >> didn't sound like a single source at all. But I guess could have been >> mistaken. I have been really curious about this "beeping" issue since >> it is so bizarre. Anyway like I said only 2 of those original 6 (they >> were seagate ST2000DM001) remain. > > > A quick google search shows the ST2000DM001 (which I have 2 of) *do* > make "chirping" or "beeping" noises. Additionally, it seems there are > firmware updates available. Sadly, I bought two of these drives some > months ago (current firmware: CC26) and so far so good. However, > should I be worried about these drives? They don't support ERC. You *must* use a 2-3 minute driver timeout for these if you use them in a raid array. Phil