linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jody Belka <lists-lkml@pimb.org>
To: Mark Lord <liml@rtr.ca>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
	linux-ide@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: marvell sata status?
Date: Wed, 21 Jan 2009 01:33:35 +0000	[thread overview]
Message-ID: <20090121013335.GL8281@pimb.org> (raw)
In-Reply-To: <495E3C92.2070304@rtr.ca>

On Fri, Jan 02, 2009 at 11:10:58AM -0500, Mark Lord wrote:
> Jody Belka wrote:
> >On Thu, Jan 01, 2009 at 02:11:37PM -0500, Justin Piszcz wrote:
> >>On Thu, 1 Jan 2009, Jody Belka wrote:
> >>>Cool, I think I'll go for that card then (Adaptec 1430SA). They're
> >>>x4, so good bandwidth, and i'll use the x16 slots on my board for
> >>>them. Only need one for now, but two eventually. And they're a good
> >>>price, at only £77 each.
> >>Does the card 'recognize' disks as SATA or do you have to export them as 
> >>JBOD? The star tech card allows you to see the sata drives directly.
> >
> >Well, it's just fake-raid, so surely you can always see the individual 
> >drives?
> >Are there actually cards out there that don't? *boggle*
> >
> >Hmm.... ok, checking the Adaptec knowledgebase:
> >
> >Q: Can drives be used on an Adaptec RAID controller but not be used as
> >   part of a RAID array?
> >
> >A: Hard drives attached to an Adaptec RAID controller do not have to be
> >   configured as an array member to work properly. The RAID controller
> >   will recognize and access single disks. Please refer to your controller
> >   documentation for instructions on accessing drives that are not a member
> >   of any RAID array. 
> ..
> 
> 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 ?

To follow up on this, I've now picked up one of these cards, and just did
a quick test. Plugged a drive into an on-board socket, booted, made a copy
of about the first 2MB. Blanked that 2MB out, swapped onto the new card,
booted, made a new copy, swapped back to on-board, booted, and made another
copy. Both copies, and a blank 2MB file, md5sum'ed identically, so it looks
like it's safe.

      parent reply	other threads:[~2009-01-21  1:33 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
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 [this message]

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=20090121013335.GL8281@pimb.org \
    --to=lists-lkml@pimb.org \
    --cc=jgarzik@pobox.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=liml@rtr.ca \
    --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;
as well as URLs for NNTP newsgroup(s).