From: Stan Hoeppner <stan@hardwarefreak.com>
To: "Jan Kundrát" <jkt@flaska.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: External USB-SATA bridge rewriting logical block sizes
Date: Tue, 04 Mar 2014 00:36:35 -0600 [thread overview]
Message-ID: <53157473.30801@hardwarefreak.com> (raw)
In-Reply-To: <29626b57-c751-4ba7-8774-b45fc090b4b6@flaska.net>
On 3/3/2014 9:18 AM, Jan Kundrát wrote:
> On Monday, 3 March 2014 15:26:24 CEST, Stan Hoeppner wrote:
>> Presumably you have some md raid level with fault tolerance, since you
>> posted this to the linux-raid list. Why not simply kick the drive from
>> the array, install it "direct" inside the chassis, repartition it the
>> same as the other members of the array that are direct connected to the
>> SATA controller, re-add the partition to the array, and rebuild.
>
> Hi Stan, I don't run RAID on these machines. I saw a recent thread
> dealing with 4k drives on this ML which made me hope that this topic
> won't be considered OT here. Sorry if this is not appropriate -- do you
> happen to know a more suitable ML?
Such an issue should be discussed on either of these two lists:
linux-ide@vger.kernel.org
linux-usb@vger.kernel.org
http://vger.kernel.org/vger-lists.html
>> Why you prepped this drive in it with intention of moving it into the
>> PC chassis leaves me scratching my head.
>
> My primary machine is a T420s laptop which has a USB3 port, but no
> eSATA. The throughput I can get from a drive attached there is much
> better than what I can get via network from my other box with plenty of
> SATA ports, but only a VIA C7 CPU (even though it has a gigabit NIC).
> Expected, I guess.
So you simply want to be able to access this 4TB drive on both your
T420s and your VIA C7 based desktop/media PC. The solution to the
current problem is simple: plug the USB enclosure into one of the PC's
USB ports instead of plugging the bare drive into the SATA cage.
Logical sector size problem solved.
Now, if the C7 PC only has USB 2.0 ports and you demand more throughput
than the ~50MB/s this provides, USB 3.0 PCIe, mini PCIe, and PCI cards
are available. If your C7 system doesn't have any slots available, then
you're left with only one solution: acquire an eSATA ExpressCard/34 for
the T420s and an eSATA enclosure for the drive. This will give you 512B
sectors on both platforms and the maximum throughput of the drive.
However, you'll have to blow away the contents of the drive,
repartition, reformat, etc, since it was partitioned with 4096B logical
sector size being reported by the enclosure bridge chip.
...
>> Is this some habit you developed years ago? Prepping a new drive
>> in a USB before permanently installing it in the chassis? If so, I'd
>> recommend using a hot swap SATA chassis that installs in a 5.25" drive
>> bay instead. They're $15-30 USD, cheaper, and more reliable, than a USB
>> dock, by far.
>
> Yes, that's what I use for the direct connection. 100% passive, very
> reliable, appears to be robust, mechanically. However, I cannot connect
> that to the laptop where I do most of my work. I do have a dock, so it's
> very convenient and ergonomic, but the IO options are a bit limited on
> this model.
Sounds like an eSATA ExpressCard and eSATA enclosure are in your future.
Unless of course you have no way to get your data off the drive and
restore it after wiping the drive and starting over, in which case
you're stuck with USB 2.0 speed on the C7 box.
--
Stan
--
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
prev parent reply other threads:[~2014-03-04 6:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 5:02 External USB-SATA bridge rewriting logical block sizes Jan Kundrát
2014-03-03 14:26 ` Stan Hoeppner
2014-03-03 15:18 ` Jan Kundrát
2014-03-04 6:36 ` Stan Hoeppner [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=53157473.30801@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=jkt@flaska.net \
--cc=linux-raid@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).