From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stan Hoeppner Subject: Re: Mdadm server eating drives Date: Mon, 01 Jul 2013 20:57:57 -0500 Message-ID: <51D233A5.504@hardwarefreak.com> References: <51B896A2.9090105@websitemanagers.com.au> <51BA7B28.9030808@turmel.org> <51BB8A67.5000605@turmel.org> <51BB8B86.9050803@turmel.org> <51CC72A4.4040508@jungers.net> 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: Barrett Lewis Cc: "linux-raid@vger.kernel.org" List-Id: linux-raid.ids On 7/1/2013 7:17 PM, Barrett Lewis wrote: > I am very sorry to keep bugging this list, but I am really lost. I apologize as I just noticed this thread. If I'd jumped in sooner you might already have it fixed. I pulled your previous posts from my archive folder and read with interest. > I noticed one drive was going up and down and determined that > the drive had actual physical damage to the power connecter and > was losing and regaining power through vibration. This intermittent contact could have damaged the PSU. You've continued to have drive and lockup problems since replacing this drive with bad connector. The pink elephant in the room is thermal failure due to insufficient airflow. The symptoms you describe sound like drives overheating. What chassis is this? Make/model please. If you've installed individual drive hot swap cages, etc, it would be helpful if you snapped a photo or two and made those available. I've seen many instances of this type of failure over the years and, in order of prevalence, they are: 1. Failed cheap backplane 2. Insufficient airflow 3. Failed or cheap PSU 4. Failed HBA (or Southbridge) -- Stan