From: Roman Mamedov <rm@romanrm.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: Why 4k native drives haven't arrived
Date: Mon, 13 Jan 2014 02:25:51 +0600 [thread overview]
Message-ID: <20140113022551.656b95e1@natsu> (raw)
In-Reply-To: <B202E185-81A8-4F10-A311-521F2E7086BA@colorremedies.com>
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]
On Sun, 12 Jan 2014 12:04:53 -0700
Chris Murphy <lists@colorremedies.com> wrote:
>
> On Jan 12, 2014, at 11:32 AM, "Martin K. Petersen" <martin.petersen@oracle.com> wrote:
>
> >>>>>> "Chris" == Chris Murphy <lists@colorremedies.com> writes:
> >
> > Chris> I think this is a pretty craptastic thing for a vendor to do to
> > Chris> users. It doesn't matter that the overwhelming majority will buy
> > Chris> the product as a unit, and never remove it. It means some users
> > Chris> will need esoteric knowledge to recover their own data, a
> > Chris> recovery from data loss that's induced by ill conceived product
> > Chris> behavior.
> >
> > Removing the physical drive from the USB enclosure is getting pretty far
> > away from "intended purpose".
>
> It's common enough that it's predictable that a significant minority users will get into trouble with a product of this type. That even Mac users are pulling drives out of enclosures, for reasons other than troubleshooting, further demonstrates that it's not at all uncommon practice.
From what I remember reading about these drives, some of the newer ones are
just USB-only. There is no "enclosure" to speak of, that you could remove and
then simply plug the drive into SATA. It may be still possible, but certainly
not easy:
http://www.datarecoverytools.co.uk/2010/05/05/how-to-connect-and-recover-usb-only-western-digital-drives-with-hd-doctor-suite/
It does make sense for the manufacturers to roll-out these lesser-compatible
features on such USB-only drives first. Another instance where that was the
case, is the first 3 TB drives. They can manufacture and sell those with
confidence, knowing that no one will try to use the drive plugged directly into
their Windows XP PC with a 10-year-old BIOS.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-01-12 20:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 21:49 Why 4k native drives haven't arrived Chris Murphy
2014-01-12 4:01 ` Chris Murphy
2014-01-12 13:55 ` Martin K. Petersen
[not found] ` <F92ECEC1-D375-498B-8C6A-C88C815C325F@colorremedies.com>
2014-01-12 18:32 ` Martin K. Petersen
2014-01-12 19:04 ` Chris Murphy
2014-01-12 19:27 ` Chris Murphy
2014-01-12 20:25 ` Roman Mamedov [this message]
2014-01-12 18:41 ` Stan Hoeppner
-- strict thread matches above, loose matches on Subject: below --
2014-01-03 1:53 Stan Hoeppner
2014-01-03 11:23 ` Mikael Abrahamsson
2014-01-03 11:27 ` Dimitri John Ledkov
2014-01-23 2:19 ` Phillip Susi
2014-01-03 21:04 ` Martin K. Petersen
2014-01-04 18:40 ` Stan Hoeppner
2014-01-06 23:35 ` Martin K. Petersen
2014-01-05 18:48 ` Peter Grandi
2014-01-06 23:50 ` Martin K. Petersen
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=20140113022551.656b95e1@natsu \
--to=rm@romanrm.net \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).