<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=6893&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / [SOLVED] How to remove security lock from a password protected SSD]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=6893</link>
		<description><![CDATA[The most recent posts in [SOLVED] How to remove security lock from a password protected SSD.]]></description>
		<lastBuildDate>Fri, 18 Oct 2024 16:25:18 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: [SOLVED] How to remove security lock from a password protected SSD]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=52690#p52690</link>
			<description><![CDATA[<p>have had the same experience several times over the years.</p><p>this webpost has helpful:<br /><a href="https://serverfault.com/questions/712849/how-to-unlock-an-ssd-disk-with-hdparm" rel="nofollow"> https://serverfault.com/questions/712849/how-to-unlock-an-ssd-disk-with-hdparm</a></p><p>also see these for faq and tools:<br /><a href="https://www.hdat2.com/hdat2_faq.html" rel="nofollow"> https://www.hdat2.com/hdat2_faq.html</a><br /><a href="https://www.hdat2.com/download.html" rel="nofollow"> https://www.hdat2.com/download.html</a></p><p>direct download link to pdf on creating a dos usb boot thumbdrive:<br /><a href="https://www.hdat2.com/files/Create_DOS_USB.pdf" rel="nofollow"> https://www.hdat2.com/files/Create_DOS_USB.pdf</a></p>]]></description>
			<author><![CDATA[dummy@example.com (stargate-sg1-cheyenne-mtn)]]></author>
			<pubDate>Fri, 18 Oct 2024 16:25:18 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=52690#p52690</guid>
		</item>
		<item>
			<title><![CDATA[[SOLVED] How to remove security lock from a password protected SSD]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=52684#p52684</link>
			<description><![CDATA[<p>I am writing this because I&#039;ve spent a lot of hours trying to figure out how to remove the password from security-locked SATA SSD. It&#039;s very useful to have information at hand when you need it.</p><p>What happened:<br />I was preparing a spare SSD to be installed in another PC. Wanted to wipe everything in 10 seconds using ATA command - Enhanced Secure Erase. Somehow, hdparm enhanced-secure-erase did not finish on my Crucial SSD, and left the drive in password-locked state. This is not unheard of, I read a lot of messages on internet forums with people facing the same problem like me, sometimes because of different reasons, but same problem to solve.<br />So, on every boot, the computer would ask to enter a password to unlock the drive. Password was empty, I just needed to press enter. The security section in my motherboard BIOS (which could apply or remove a password lock) could not get to this drive, saying that my empty password is incorrect. Crucial Storage Executive program for Windows also could do nothing about it. As I don&#039;t use Microsoft Windows at all, I wasted a lot of time at this point, trying to install Windows on another PC, tried different laptops which were incompatible with security-locked SATA drive, even tried VMs, which were incompatible with Crucial Storage Executive program, what a mess it was.</p><p><span style="color: red"><strong>Warning: solution below will wipe all your data from the drive.</strong></span></p><p>Solution (change <strong>/dev/sdc</strong> drive letter as appropriate)<br />Install <strong>hdparm</strong> package in your Linux. Then:</p><div class="codebox"><pre><code>sudo hdparm -I /dev/sdc
(...)
Security: 
        Master password revision code = 65534
                supported
                enabled
                locked
                frozen
        not     expired: security count
                supported: enhanced erase</code></pre></div><p>It should say on the bottom: security <strong>enabled</strong>, <strong>locked</strong> and <strong>frozen</strong>. Meaning, password is enabled, and you can&#039;t take it off, because changing of security settings is not permitted. First thing, you need to remove the <strong>frozen</strong> state. To do that, you must suspend your machine and leave it suspended for a couple of minutes. <strong>Less than one minute doesn&#039;t work, I&#039;ve tried.</strong></p><p>After you wake up the PC, check status again:</p><div class="codebox"><pre><code>sudo hdparm -I /dev/sdc
Security: 
        Master password revision code = 65534
                supported
                enabled
                locked
        not     frozen
        not     expired: security count
                supported: enhanced erase</code></pre></div><p>It should say <strong>not frozen</strong> this time.</p><p>Now you can remove the locked status:</p><div class="codebox"><pre><code>sudo hdparm --user-master u --security-unlock &quot;&quot; /dev/sdc</code></pre></div><p>And perform secure erase to wipe the drive completely and remove the empty password lock:</p><div class="codebox"><pre><code>sudo hdparm --user-master u --security-erase &quot;&quot; /dev/sdc</code></pre></div><p>When this is done, the drive will be completely blank, and all password and security settings will reset. No more password!</p><p>If you did something wrong, for example attempted security-unlock when drive is still <strong>frozen</strong> state, or security-erase when drive is still in <strong>locked</strong> and/or <strong>frozen</strong> state, you will get error like this:</p><div class="codebox"><pre><code>sudo hdparm --user-master u --security-erase &quot;&quot; /dev/sdc
security_password: &quot;&quot;

/dev/sdc:
 Issuing SECURITY_ERASE command, password=&quot;&quot;, user=user
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 00 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]:  70 00 05 00 00 00 00 0a 04 51 40 01 21 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00</code></pre></div><p>You need to sort it out before you try again, as it will not work.</p><p>Hope this helps!</p>]]></description>
			<author><![CDATA[dummy@example.com (VPigEePMUn7X)]]></author>
			<pubDate>Fri, 18 Oct 2024 12:58:29 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=52684#p52684</guid>
		</item>
	</channel>
</rss>
