From: Ludovico Cavedon <ludovico.cavedon@gmail.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: understanding the cause of ATA failures
Date: Thu, 18 Mar 2010 20:38:05 -0700 [thread overview]
Message-ID: <4BA2F19D.1090501@gmail.com> (raw)
In-Reply-To: <4BA2B9BE.5030607@hardwarefreak.com>
Stan Hoeppner wrote:
> 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.
Uhm, yes, you are right, it has a backplane with SES-2 over I2C support.
At first I though that backplanes were used only on external enclosures.
> 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
Unfortunately the I2C connectors on the backplane are not connected to
anything. The motherboard has a "IPMB I2C" connector", but I guess I
cannot connect a generic I2C device... I should probably get a USB-I2C
module...
Btw, once I am able to access the I2C device on the backplane, what tool
is able to query the state? I am having troubles finding documentation
about that. lm-sensors does not seem to mention that... Is the ses
kernel module able to work over i2c?
> 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.
I see.
>>> 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.
Makes sense.
> 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,
That would not be a problem.
Thank you for the information!
Cheers,
Ludovico
next prev parent reply other threads:[~2010-03-19 3:38 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
2010-03-19 3:38 ` Ludovico Cavedon [this message]
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=4BA2F19D.1090501@gmail.com \
--to=ludovico.cavedon@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=stan@hardwarefreak.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