<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Intel 545s Stuck in Read-Only Mode (100% Health) - MAS Tool Failure &amp;quot;Drive no longer suppor in Solid State Drives (NAND)</title>
    <link>https://community.solidigm.com/t5/solid-state-drives-nand/intel-545s-stuck-in-read-only-mode-100-health-mas-tool-failure/m-p/24783#M12437</link>
    <description>&lt;P&gt;Dear Mango,&lt;BR /&gt;&lt;BR /&gt;Thank you for the detailed description. Before we proceed with escalated analysis, please follow the steps below to isolate whether the write‑protection is caused by the current Windows environment or by the SSD firmware itself.&lt;/P&gt;
&lt;HR /&gt;
&lt;H3&gt;&lt;STRONG&gt;1. Diskpart clear read-only (Windows Only)&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;Run these commands &lt;STRONG&gt;in this exact sequence&lt;/STRONG&gt; on a separate Windows host if possible:&lt;/P&gt;
&lt;P&gt;diskpart&lt;BR /&gt;list disk&lt;BR /&gt;select disk X&lt;BR /&gt;attributes disk clear readonly&lt;BR /&gt;exit&lt;BR /&gt;format X: /fs=ntfs /p:1 (This will wipe all the SSD info / Backup if necessary)&lt;/P&gt;
&lt;P&gt;&lt;I&gt;(Replace X with the drive number/letter.)&lt;/I&gt;&lt;BR /&gt;If any of these commands fail with &lt;I&gt;“media is write‑protected”&lt;/I&gt;, the protection is not OS‑level.&lt;/P&gt;
&lt;HR /&gt;
&lt;H3&gt;&lt;STRONG&gt;2. Test the Drive on a Different System / OS&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;To eliminate any OS‑level or controller‑driver interaction in the current server:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Connect the Intel SSD 545s to &lt;STRONG&gt;another PC&lt;/STRONG&gt;. If possible, also test it on &lt;STRONG&gt;any Linux system &lt;/STRONG&gt;(Ubuntu, Debian, etc.).
&lt;UL&gt;
&lt;LI&gt;In Linux, attempt a write test or run a simple format command (e.g., &lt;CODE&gt;sudo mkfs.ext4 /dev/sdX&lt;/CODE&gt;) to confirm whether the device remains read‑only outside the customer’s current environment.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;If the drive is read‑only on multiple systems, the condition is controller‑level, not OS‑level.&lt;/P&gt;
&lt;HR /&gt;
&lt;H3&gt;&lt;STRONG&gt;Summary&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;Test to isolate whether the write‑protection is caused by the current Windows environment or by the SSD firmware itself. If further analysis is required, please let us know.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 07 Mar 2026 00:24:30 GMT</pubDate>
    <dc:creator>SolidigmJose</dc:creator>
    <dc:date>2026-03-07T00:24:30Z</dc:date>
    <item>
      <title>Intel 545s Stuck in Read-Only Mode (100% Health) - MAS Tool Failure "Drive no longer supported"</title>
      <link>https://community.solidigm.com/t5/solid-state-drives-nand/intel-545s-stuck-in-read-only-mode-100-health-mas-tool-failure/m-p/24781#M12435</link>
      <description>&lt;P&gt;Intel 545s Stuck in Read-Only Mode (100% Health) - MAS Tool Failure "Drive no longer supported"&lt;/P&gt;
&lt;P&gt;Dear Solidigm Support Team,&lt;/P&gt;
&lt;P&gt;I am reaching out because Intel has transitioned its SSD support to Solidigm, and I am facing a critical firmware-level issue with my Intel 545s 512GB SSD.&lt;/P&gt;
&lt;P&gt;Drive Identification:&lt;/P&gt;
&lt;P&gt;Model: Intel SSD 545s Series 512GB (SSDSC2KW512G8)&lt;/P&gt;
&lt;P&gt;Firmware: LHF004C&lt;/P&gt;
&lt;P&gt;The Problem:&lt;BR /&gt;My drive has entered a "Write-Protected" or "Firmware Lock" state. However, the Solidigm Storage Tool (and Intel MAS) shows that the drive is in perfect physical condition:&lt;/P&gt;
&lt;P&gt;Estimated Life Remaining: 100%&lt;/P&gt;
&lt;P&gt;SMART Status: Good&lt;/P&gt;
&lt;P&gt;The Conflict:&lt;BR /&gt;When I attempt to recover the drive using the official Secure Erase or Sanitize commands via the CLI/GUI tool, the software terminates the process with the following error:&lt;/P&gt;
&lt;P&gt;"Error: This drive is no longer supported."&lt;/P&gt;
&lt;P&gt;My Question to Solidigm:&lt;BR /&gt;If the hardware is 100% healthy and the controller is responsive, why is the official software blocking maintenance commands? By preventing a simple Secure Erase or Sanitize on a healthy drive, the software is effectively creating unnecessary E-waste.&lt;/P&gt;
&lt;P&gt;What I need:&lt;/P&gt;
&lt;P&gt;A version of the Solidigm Storage Tool that actually supports the 545s series for recovery.&lt;/P&gt;
&lt;P&gt;A specific command-line override to force a Secure Erase on this drive regardless of its EOL status.&lt;/P&gt;
&lt;P&gt;Or any internal tool that can reset the SM2259G controller mapping table to unlock the write protection.&lt;/P&gt;
&lt;P&gt;Please do not provide generic troubleshooting steps like "check your SATA cable." The drive is detected; the software is simply refusing to work. I expect a technical solution for this "supported" hardware that still has 100% life left.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;[nimadebi/mango]&lt;/P&gt;</description>
      <pubDate>Sat, 07 Mar 2026 00:28:17 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/solid-state-drives-nand/intel-545s-stuck-in-read-only-mode-100-health-mas-tool-failure/m-p/24781#M12435</guid>
      <dc:creator>mango</dc:creator>
      <dc:date>2026-03-07T00:28:17Z</dc:date>
    </item>
    <item>
      <title>Re: Intel 545s Stuck in Read-Only Mode (100% Health) - MAS Tool Failure "Drive no longer suppor</title>
      <link>https://community.solidigm.com/t5/solid-state-drives-nand/intel-545s-stuck-in-read-only-mode-100-health-mas-tool-failure/m-p/24783#M12437</link>
      <description>&lt;P&gt;Dear Mango,&lt;BR /&gt;&lt;BR /&gt;Thank you for the detailed description. Before we proceed with escalated analysis, please follow the steps below to isolate whether the write‑protection is caused by the current Windows environment or by the SSD firmware itself.&lt;/P&gt;
&lt;HR /&gt;
&lt;H3&gt;&lt;STRONG&gt;1. Diskpart clear read-only (Windows Only)&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;Run these commands &lt;STRONG&gt;in this exact sequence&lt;/STRONG&gt; on a separate Windows host if possible:&lt;/P&gt;
&lt;P&gt;diskpart&lt;BR /&gt;list disk&lt;BR /&gt;select disk X&lt;BR /&gt;attributes disk clear readonly&lt;BR /&gt;exit&lt;BR /&gt;format X: /fs=ntfs /p:1 (This will wipe all the SSD info / Backup if necessary)&lt;/P&gt;
&lt;P&gt;&lt;I&gt;(Replace X with the drive number/letter.)&lt;/I&gt;&lt;BR /&gt;If any of these commands fail with &lt;I&gt;“media is write‑protected”&lt;/I&gt;, the protection is not OS‑level.&lt;/P&gt;
&lt;HR /&gt;
&lt;H3&gt;&lt;STRONG&gt;2. Test the Drive on a Different System / OS&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;To eliminate any OS‑level or controller‑driver interaction in the current server:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Connect the Intel SSD 545s to &lt;STRONG&gt;another PC&lt;/STRONG&gt;. If possible, also test it on &lt;STRONG&gt;any Linux system &lt;/STRONG&gt;(Ubuntu, Debian, etc.).
&lt;UL&gt;
&lt;LI&gt;In Linux, attempt a write test or run a simple format command (e.g., &lt;CODE&gt;sudo mkfs.ext4 /dev/sdX&lt;/CODE&gt;) to confirm whether the device remains read‑only outside the customer’s current environment.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;If the drive is read‑only on multiple systems, the condition is controller‑level, not OS‑level.&lt;/P&gt;
&lt;HR /&gt;
&lt;H3&gt;&lt;STRONG&gt;Summary&lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;Test to isolate whether the write‑protection is caused by the current Windows environment or by the SSD firmware itself. If further analysis is required, please let us know.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;/P&gt;
&lt;P&gt;&lt;LI-WRAPPER&gt;&lt;/LI-WRAPPER&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 07 Mar 2026 00:24:30 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/solid-state-drives-nand/intel-545s-stuck-in-read-only-mode-100-health-mas-tool-failure/m-p/24783#M12437</guid>
      <dc:creator>SolidigmJose</dc:creator>
      <dc:date>2026-03-07T00:24:30Z</dc:date>
    </item>
  </channel>
</rss>

