xfs
[Top] [All Lists]

Re: xfs_repair fails after trying to format log cycle?

To: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
Subject: Re: xfs_repair fails after trying to format log cycle?
From: Andrew Ryder <tireman@xxxxxxx>
Date: Mon, 6 Jun 2016 15:19:51 -0400
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, Brian Foster <bfoster@xxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-raid@xxxxxxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20150330; t=1465240790; bh=1Y241U/AXgmfnJ0+XFZ2eM0nz7hBprOsKBQSxqzwGOA=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=jA73g5JSn3BgIdGbj8HKlrf6jUSa/cAx6V8vdPEtFnDoiXhvRMASxvpNGmtKcjMn+ /+7lzDkaAQ2B+jURHWDBgWHzf2fNKcvqur1Jk9+0WJylbokw+XSybeM3Ry72vg9vTP GiKDkskAk80xMBD6LZ9evJLa6Sxod+jnJ40LNK3qNJpNTXYU7XwZsxY3c/GWnup0wa JkOibO9wb8ZJ8RC8UDW3e93feIv/OBRFzNys229S+lax+CNyvNd+fB6IqovmqkNliY kZ82bEqP9NBPQQZGdQD9LGg9DUx0kV0a9dvZBo+n1Z21r0CDoCi2UUwn3DoyMbRk/t Jj6xJlbjtKG3g==
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20150330; t=1465240790; bh=1Y241U/AXgmfnJ0+XFZ2eM0nz7hBprOsKBQSxqzwGOA=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=jA73g5JSn3BgIdGbj8HKlrf6jUSa/cAx6V8vdPEtFnDoiXhvRMASxvpNGmtKcjMn+ /+7lzDkaAQ2B+jURHWDBgWHzf2fNKcvqur1Jk9+0WJylbokw+XSybeM3Ry72vg9vTP GiKDkskAk80xMBD6LZ9evJLa6Sxod+jnJ40LNK3qNJpNTXYU7XwZsxY3c/GWnup0wa JkOibO9wb8ZJ8RC8UDW3e93feIv/OBRFzNys229S+lax+CNyvNd+fB6IqovmqkNliY kZ82bEqP9NBPQQZGdQD9LGg9DUx0kV0a9dvZBo+n1Z21r0CDoCi2UUwn3DoyMbRk/t Jj6xJlbjtKG3g==
In-reply-to: <20160606173336.027917f5@xxxxxxxxxxxxxxxxxxxx>
References: <56F6DE67.60403@xxxxxxx> <20160328085541.GA27040@xxxxxxxxxxxxxxx> <570C8D4D.3060304@xxxxxxx> <20160412140512.GA59690@xxxxxxxxxxxxxxx> <570D578D.5010706@xxxxxxx> <570DB6CD.1000007@xxxxxxx> <20160413045129.GO567@dastard> <57523CE6.7020906@xxxxxxx> <20160606173336.027917f5@xxxxxxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0


On 06/06/2016 11:33 AM, Emmanuel Florac wrote:
Le Fri, 3 Jun 2016 22:28:54 -0400
Andrew Ryder <tireman@xxxxxxx> Ãcrivait:

Sorry to dig up old stuff here but after replacing hardware and
pulling my hair out to no end, I traced the source of the problem out.

On every drive in the array, the points on the PCB which the contacts
for the drives motors and head/actuators make contact with were
oxidized enough to cause the issue. I ended up pulling the PCB off
each drive and cleaning them as well as cleaning out all other cable
and drive connectors from the HBA outward and everything is happy
again.

http://s33.postimg.org/uhjmvw4dr/Not_Cleaned.jpg
http://s33.postimg.org/xo94ieii7/Partial_Cleaned_1.jpg
http://s33.postimg.org/hoqgyumgf/Partial_Cleaned_2.jpg
http://s33.postimg.org/68k20t8a7/Partial_Cleaned_3.jpg


Good job, that was quite unexpected :) Are you next to the
seashore?



No. I'm up in NW Ontario in Canada actually, far away from any salt water. I'm guessing it was from the combination of air pollutants/humidity and heat given the drives are not in the most hospitable environment esp during the summer ... but after cleaning the board contacts up as well as the esata cable ends/ports, its working great again.

I'm beginning to think when I do replace any drives, after warranty is up on them, pull off the PCB, clean it up and coat the contacts with a good smearing of dielectric grease to keep the issue from happening.

Makes me wonder how many other people out there suffer from the same issue given the amount of unresolved similar hw errors I've found while googling the errors..

Thanks again,
Andrew

<Prev in Thread] Current Thread [Next in Thread>