From: Mark Lord <liml@rtr.ca>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Jody Belka <lists-lkml@pimb.org>,
linux-ide@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: marvell sata status?
Date: Sat, 03 Jan 2009 00:04:21 -0500 [thread overview]
Message-ID: <495EF1D5.1020106@rtr.ca> (raw)
In-Reply-To: <alpine.DEB.1.10.0901021518150.8210@p34.internal.lan>
Justin Piszcz wrote:
>
>
> On Fri, 2 Jan 2009, Mark Lord wrote:
>
>> Justin Piszcz wrote:
>>> On Fri, 2 Jan 2009, Mark Lord wrote:
>>
>>>> I suppose, of all of the vendors, Adaptec probably has the best chance
>>>> of getting that part right, and probably without randomly writing
>>>> metadata
>>>> somewhere on the drive simply for JBOD.
>>>>
>>>> Anyone know for sure ?
>>>>
>>>> Cheers
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>
>>>
>>> The Star Tech seems to work right, you plug in the disks and they're
>>> recognized as regular sata disks, as if on your on-board controller.
>>> No special modifications required.
>> ..
>>
>> Inconclusive. The Highpoint cards behave like that, too,
>> except they silently corrupt a sector (or more) on the drive
>> at every boot, whether or not one ever "configures" the drive
>> through the built-in RAID/JBOD BIOS.
..
Well.. what do *you* think the answer is?
Unless you've zeroed the entire drive beforehand,
and then inserted it into a given controller,
and then scanned for non-zero sectors.. how can you tell?
That's what we ended up having to do with the Highpoint ones,
and the result was rather shocking at the time.
Cheers
next prev parent reply other threads:[~2009-01-03 5:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 5:10 marvell sata status? Jody Belka
2009-01-01 9:54 ` Justin Piszcz
2009-01-01 14:07 ` Mark Lord
2009-01-01 18:44 ` Jody Belka
2009-01-01 19:11 ` Justin Piszcz
2009-01-01 19:43 ` Jody Belka
2009-01-02 16:09 ` Mark Lord
2009-01-02 16:10 ` Mark Lord
2009-01-02 18:03 ` Justin Piszcz
2009-01-02 20:18 ` Mark Lord
2009-01-02 20:18 ` Justin Piszcz
2009-01-03 5:04 ` Mark Lord [this message]
2009-01-03 9:13 ` Justin Piszcz
2009-01-03 14:44 ` Mark Lord
2009-01-03 14:46 ` Mark Lord
2009-01-21 1:33 ` Jody Belka
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=495EF1D5.1020106@rtr.ca \
--to=liml@rtr.ca \
--cc=jgarzik@pobox.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--cc=lists-lkml@pimb.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;
as well as URLs for NNTP newsgroup(s).