linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Chua <jeff.chua.linux@gmail.com>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Ming Lei <tom.leiming@gmail.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: How to secure erase PCI-E NVME SSD connected via USB3?
Date: Thu, 2 Aug 2018 20:56:15 +0800	[thread overview]
Message-ID: <CAAJw_ZsAUstFKrMQCy5AguyXb9=oQVecN2+b5G8ubQqLUp1YTQ@mail.gmail.com> (raw)
In-Reply-To: <20180802132956.6b7110ed@alans-desktop>

On Thu, Aug 2, 2018 at 8:29 PM, Alan Cox <gnomes@lxorguk.ukuu.org.uk> wrote:
>> # hdparm --user-master u --security-erase p /dev/sda
>> (returns immediately and does nothing).
>>
>> I've tried hdparm on an SSD connected via USB3 and it secure-erased ok.
>>
>> Anyone working on this?
>
> Sounds to me like you need to contact the vendor of the interface in
> question. If it accepted a security erase command and didn't do it then
> it's broken. It's at liberty to refuse it, or report it doesn't know what
> you are talking about, but if it just returned and after re-plugging the
> device its still using the old keys then it or the device is busted and
> it's not something the OS can do much about.

Alan,

You're right. I wrote to JMicron, and they are kind to reply that
"hdparm not support secure-erase feature with USB to NVMe device", and
told me to plug the card into a PCI slot to perform the
security-erase.

I'm asking JMicron again if the JMS583 even support security-erase.

Thanks,
Jeff

      reply	other threads:[~2018-08-02 12:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-29  9:09 How to secure erase PCI-E NVME SSD connected via USB3? Jeff Chua
2018-07-31 11:07 ` Ming Lei
2018-08-01  5:02   ` Jeff Chua
2018-08-01 14:52     ` Jeff Chua
2018-08-02 12:29       ` Alan Cox
2018-08-02 12:56         ` Jeff Chua [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='CAAJw_ZsAUstFKrMQCy5AguyXb9=oQVecN2+b5G8ubQqLUp1YTQ@mail.gmail.com' \
    --to=jeff.chua.linux@gmail.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tom.leiming@gmail.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).