From owner-freebsd-questions@freebsd.org Wed Jun 24 18:00:44 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BE3791617E for ; Wed, 24 Jun 2015 18:00:44 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 334D915F4 for ; Wed, 24 Jun 2015 18:00:44 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: by igblr2 with SMTP id lr2so80876429igb.0 for ; Wed, 24 Jun 2015 11:00:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=XNLfUNTHZNKq/LYvKth8Z9yiZyiP0TJiFyStDhuY1/s=; b=ZD8ltQC2nmN19pK1g1egUmEJtVGENN0Kjqt7MCV8X5If8z981c9+uoC97YnkWbBKn/ tS3CKwAx0wp/y9vhQle99RgBv7zl33ig9aH+v9ZUucQ5+OpjiJPo3CMmmo9/TPoxb+Am GdpaC1DDv01tb0FwwYGhpw/OZX+nt1XM2U+vW01m/PbY0AqgJAck8dQ+KOCahgmwuyrJ oOgCKV2Wq0964XVgPELSgjNWnN4F718sGAdm4PsyfKgzYmLQl1f7FgCk90397cyUzeNp DlqDROoJdOCQOwJFEl8wo9pRkIejj05dfNwNHb1RrNTxhNoCKH0BLCEQMAYXekhBl/Yz G0cw== X-Received: by 10.42.119.76 with SMTP id a12mr19422636icr.83.1435168843588; Wed, 24 Jun 2015 11:00:43 -0700 (PDT) Received: from localhost.localdomain ([50.243.6.59]) by mx.google.com with ESMTPSA id a82sm17772635ioe.22.2015.06.24.11.00.42 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Jun 2015 11:00:42 -0700 (PDT) Message-ID: <558AF04A.8090206@gmail.com> Date: Wed, 24 Jun 2015 12:00:42 -0600 From: jd1008 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: hard drive problem References: <5589E2F9.3070604@gmail.com> <861th1tdj3.fsf@WorkBox.Home> <20150624153643.GB43640@neutralgood.org> <46363.128.135.70.2.1435160477.squirrel@cosmo.uchicago.edu> In-Reply-To: <46363.128.135.70.2.1435160477.squirrel@cosmo.uchicago.edu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jun 2015 18:00:44 -0000 On 06/24/2015 09:41 AM, Valeri Galtsev wrote: > On Wed, June 24, 2015 10:36 am, kpneal@pobox.com wrote: >> On Wed, Jun 24, 2015 at 08:57:20AM -0500, Brandon J. Wandersee wrote: >>> jd1008 writes: >>> >>>> does anyone have a way to unlock the master pword in >>>> a recent WD 2TB 2.5" drive? >>> "Master pword?" Is this a firmware-level encrypted drive? If so, no. A >>> "reset" feature would defeat the purpose of having encryption in the >>> first place. If the drive is self-encrypting you don't know the >>> password, the drive's a brick. >> My guess is that you can tell the drive to use a new password, but the >> contents of the drive are lost. That's assuming a firmware-level >> encryption. >> >> BTW, are there really 2TB _2.5"_ drives on the market? > It may be an enclosure with two 1TB 2.5" drives either concatenated, or > RAID0 thus presenting itself as 2 TB. Just a wild guess. > > Valeri This one is actually a 4 platter drive, thus rather thick (15mm). Goodby to 7.5mm 2.5" drives. Areal density has not reached the quantum level yet :) But from the technologists I know who are and have worked at HD companies, I hear that mechanical drives are totally on the way out as the the RAM and FLASH electronics get every tinier and faster, and much more reliable and long lasting.