From: Andrew Ryder <tireman@shaw.ca>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: linux-raid@vger.kernel.org, Brian Foster <bfoster@redhat.com>,
xfs@oss.sgi.com
Subject: Re: xfs_repair fails after trying to format log cycle?
Date: Mon, 6 Jun 2016 15:19:51 -0400 [thread overview]
Message-ID: <5755CCD7.1000104@shaw.ca> (raw)
In-Reply-To: <20160606173336.027917f5@harpe.intellique.com>
On 06/06/2016 11:33 AM, Emmanuel Florac wrote:
> Le Fri, 3 Jun 2016 22:28:54 -0400
> Andrew Ryder <tireman@shaw.ca> é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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-06-06 19:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 19:09 xfs_repair fails after trying to format log cycle? Andrew Ryder
2016-03-28 8:55 ` Brian Foster
2016-04-12 5:53 ` Andrew Ryder
2016-04-12 14:05 ` Brian Foster
2016-04-12 20:16 ` Andrew Ryder
2016-04-13 3:02 ` Andrew Ryder
2016-04-13 4:51 ` Dave Chinner
2016-06-04 2:28 ` Andrew Ryder
2016-06-06 15:33 ` Emmanuel Florac
2016-06-06 19:19 ` Andrew Ryder [this message]
2016-06-06 19:37 ` Andrew Ryder
2016-04-13 12:12 ` Brian Foster
2016-04-13 22:34 ` Andrew Ryder
2016-04-14 4:32 ` Andrew Ryder
2016-04-15 4:24 ` Andrew Ryder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5755CCD7.1000104@shaw.ca \
--to=tireman@shaw.ca \
--cc=bfoster@redhat.com \
--cc=eflorac@intellique.com \
--cc=linux-raid@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox