From: Stan Hoeppner <stan@hardwarefreak.com>
To: linux-ide@vger.kernel.org
Subject: Re: understanding the cause of ATA failures
Date: Thu, 18 Mar 2010 18:39:42 -0500 [thread overview]
Message-ID: <4BA2B9BE.5030607@hardwarefreak.com> (raw)
In-Reply-To: <4BA2B15E.6000301@gmail.com>
Ludovico Cavedon put forth on 3/18/2010 6:03 PM:
> Stan Hoeppner wrote:
>> Is there a SATA backplane involved or is each drive cabled directly to the
>> controller? If backplane, is it active or passive? Whose product is it?
>
> no backplance.
> This is the machine
> http://www.supermicro.com/products/system/2U/6026/SYS-6026T-URF.cfm
It most certainly does have a backplane, and an active backplane at that.
Defective or marginal backplanes are known to cause intermittent problems of
the nature you're describing, especially active backplanes. This is why I
asked. "Enclosure Management" below is a feature of only active backplanes.
The difference between active and passive is that active units have one or
more ASICs (chips) on the circuit board to control various functions of the
backplane such as fan control, alarms, drive monitoring circuits to sense
drive failures, etc. Have you configured an I2C module to monitor the
backplane? If so, check those logs. If not, do so now. It's possible that
the backplane controller is erroneously kicking the drives off-line. This
could explain the SATA bus errors. It's also possible there is a problem
with the backplane controller chip itself or other circuitry on the PCB
causing problems.
SAS Backplane
1x 2U SAS backplane w/ Enclosure Management
http://www.supermicro.com/products/chassis/2U/825/SC825TQ-R720U.cfm
>> Is this a relatively new machine or has it been running for some months
>> without problems until recently?
>
> It is new machine, running only for two months.
You need to call SuperMicro support and tell them about your issue.
Backplane boards are relatively cheap. Get them to send you a warranty
advance replacement backplane and see if that fixes the problem. If you're
not a hardware person, replacing it may not be a job for you. In that case,
I'm not sure what to tell you, as last I knew SuperMicro doesn't offer
onsite service. If indeed the backplane is the problem, you may have to
ship the unit back for repair. This is the main reason (lack of onsite
service) than most companies stick with IBM, Dell, HP, etc servers.
--
Stan
next prev parent reply other threads:[~2010-03-18 23:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 21:50 understanding the cause of ATA failures Ludovico Cavedon
2010-03-18 22:00 ` Tim Small
2010-03-18 22:13 ` Ludovico Cavedon
2010-03-18 22:33 ` Stan Hoeppner
2010-03-18 23:03 ` Ludovico Cavedon
2010-03-18 23:39 ` Stan Hoeppner [this message]
2010-03-19 3:38 ` Ludovico Cavedon
2010-03-19 10:26 ` Stan Hoeppner
2010-03-25 0:52 ` Tejun Heo
2010-03-26 2:22 ` Ludovico Cavedon
2010-03-22 3:37 ` Robert Hancock
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=4BA2B9BE.5030607@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-ide@vger.kernel.org \
/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