From: "Stefan /*St0fF*/ Hübner" <stefan.huebner@stud.tu-ilmenau.de>
To: Ian Dall <ian@beware.dropbear.id.au>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Device kicked from raid too easilly
Date: Tue, 08 Jun 2010 07:56:07 +0200 [thread overview]
Message-ID: <4C0DDB77.1070907@stud.tu-ilmenau.de> (raw)
In-Reply-To: <1275974154.4313.72.camel@sibyl.beware.dropbear.id.au>
Am 08.06.2010 07:15, schrieb Ian Dall:
> On Sat, 2010-06-05 at 09:22 +0200, Stefan /*St0fF*/ Hübner wrote:
> [...]
>
> Puzzlingly, swapping the disks around in the backplane works so long as
> it is brand "A" in the first slot and not brand "B"! My current theory
> is that there are transmission line effects (or maybe RFI) which make
> some slots fall outside the range of the brand "B" disks to compensate!
>
> One might think that sata would be better, but I am simultaneously
> looking for a problem in another raid array which gives me sata CRC
> errors which I assume to be cable related. Interestingly the sata
> transport layer treats these CRC errors as soft (at least, there is no
> corresponding action from md).
Weird, but on some Synology RackStations (RS407 and RS408) brand NAS
devices I had similar problems and what you wrote is exactly what I told
the customers what I think the problem might be.
The devices of mentioned make which failed, always failed slot #1.
Those that made problems, always kicked drive #1 sporadically. But on
those problem-kids I could never find a real error. Swapping another
disk into slot #1 made the problems disappear surprinsingly. So I guess
you thoughts are right, some disks may be able to compensate
transmission-noise better than others.
But I wouldn't want to subject it to the cabling, because (well, I'm not
100% sure if that's right) slot #1's cable is the shortest. I'd rather
think it might be not-so-well placed electronics on the board or
backplane. Maybe a capacitor or a resistor (of which there should be
some for each port) are placed for port #1 that way, that they get a lot
warmer than the others ports' passive elements. Resistors increase
resistance if they're hotter, capacitors loose capacity when they're
hotter. So this might change the signal levels to some noticeable extent.
>
>> P.S.: maybe you should check for firmware updates of the disks?
>
> No such luck. These (brand "B") are "Worldisk" (which I believe to be
> re-manufactured Fujitsu). The less troublesome disks (brand "A") are
> Hitachi.
That's too bad. But actually, if our shared thoughts above are right, a
firmware update wouldn't help much...
>
> Thanks for your thoughts.
>
> Regards,
> Ian
>
Stefan
> [...]
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-08 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 1:51 Device kicked from raid too easilly Ian Dall
2010-06-05 7:22 ` Stefan /*St0fF*/ Hübner
2010-06-08 5:15 ` Ian Dall
2010-06-08 5:56 ` Stefan /*St0fF*/ Hübner [this message]
2010-06-08 6:59 ` Tim Small
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=4C0DDB77.1070907@stud.tu-ilmenau.de \
--to=stefan.huebner@stud.tu-ilmenau.de \
--cc=ian@beware.dropbear.id.au \
--cc=linux-raid@vger.kernel.org \
--cc=st0ff@npl.de \
/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;
as well as URLs for NNTP newsgroup(s).