From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stan Hoeppner Subject: Re: Mdadm server eating drives Date: Tue, 02 Jul 2013 15:23:42 -0500 Message-ID: <51D336CE.7080800@hardwarefreak.com> References: <51BA7B28.9030808@turmel.org> <51BB8A67.5000605@turmel.org> <51BB8B86.9050803@turmel.org> <51CC72A4.4040508@jungers.net> <51D233A5.504@hardwarefreak.com> <51D32DBB.8030401@hardwarefreak.com> Reply-To: stan@hardwarefreak.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Jon Nelson Cc: Barrett Lewis , "linux-raid@vger.kernel.org" List-Id: linux-raid.ids On 7/2/2013 3:07 PM, Jon Nelson wrote: > On Tue, Jul 2, 2013 at 2:44 PM, Stan Hoeppner wrote: >> On 7/2/2013 10:48 AM, Barrett Lewis wrote: >>> After sending the last email I went out and bought 2 new WD reds, and >>> a new motherboard. I came back and in those 2 hours all but 1 of my >>> drives failed to the point of being unable to read the superblock so >>> it really seems like my array is ended >> >> The drive may be ok. They all may be. > > Indeed. A number of years back, I had an MD RAID array that kept > throwing drives, one after the other, after years of rock-solid > stability. Nothing had changed, the machine hadn't been touched (or > even rebooted!) in months, etc... It turns out that the motherboard > had gone. It "worked" perfectly, except under any drive load at all it > would start throwing I/O errors. I replaced only the motherboard (same > PSU, memory, CPU, etc....) and that machine - built at least 4 years > ago - is still humming along quite nicely. Were the drives were attached to the onboard SATA controller or an HBA? -- Stan