<?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: Creating a namespace in Solid State Drives (NAND)</title>
    <link>https://community.solidigm.com/t5/solid-state-drives-nand/creating-a-namespace/m-p/24536#M12282</link>
    <description>&lt;P&gt;Hello rainer_d,&lt;/P&gt;
&lt;P&gt;Thank you for your contacting Solidigm! It sounds like you’re close, but there are a few key considerations when creating namespaces on Solidigm SSDs that might help clarify the process.&lt;/P&gt;
&lt;P&gt;First, when creating a namespace, ensure that the parameters for size (&lt;CODE&gt;-s&lt;/CODE&gt;) and capacity (&lt;CODE&gt;-c&lt;/CODE&gt;) align correctly with the drive’s specifications and intended usage. Here’s a step-by-step guide that might be helpful:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Confirm Size and Capacity Values&lt;/STRONG&gt;: Double-check that the values provided for the &lt;CODE&gt;-s&lt;/CODE&gt; (size) and &lt;CODE&gt;-c&lt;/CODE&gt; (capacity) flags are suitable for the storage available on your SSD. You might want to try smaller values initially to test if a smaller namespace can be successfully created.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Use the Correct Controller ID&lt;/STRONG&gt;: For the &lt;CODE&gt;nvme attach-ns&lt;/CODE&gt; command, ensure that &lt;CODE&gt;--controllers=0&lt;/CODE&gt; is actually the correct controller ID for your setup. If your SSD is connected through a specific controller, replace &lt;CODE&gt;0&lt;/CODE&gt; with the correct ID.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Specify the Namespace UUID&lt;/STRONG&gt;: Sometimes, explicitly setting a UUID when creating the namespace can help. You can try adding the &lt;CODE&gt;-u&lt;/CODE&gt; parameter with a UUID, for example:&lt;/P&gt;
&lt;DIV class="contain-inline-size rounded-md border-[0.5px] border-token-border-medium relative bg-token-sidebar-surface-primary dark:bg-gray-950"&gt;
&lt;DIV class="flex items-center text-token-text-secondary px-4 py-2 text-xs font-sans justify-between rounded-t-md h-9 bg-token-sidebar-surface-primary dark:bg-token-main-surface-secondary select-none"&gt;bash&lt;/DIV&gt;
&lt;DIV class="sticky top-9 md:top-[5.75rem]"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="overflow-y-auto p-4" dir="ltr"&gt;&lt;CODE class="!whitespace-pre hljs language-bash"&gt;/usr/local/sbin/nvme create-ns /dev/nvme0 -s 150031139328 -c 200041519104 -d 0 -m 0 -f 0 -u &amp;lt;uuid&amp;gt;
&lt;/CODE&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Check for Existing Namespaces&lt;/STRONG&gt;: Run the following command to confirm that there aren’t any pre-existing namespaces that might interfere:&lt;/P&gt;
&lt;DIV class="contain-inline-size rounded-md border-[0.5px] border-token-border-medium relative bg-token-sidebar-surface-primary dark:bg-gray-950"&gt;
&lt;DIV class="flex items-center text-token-text-secondary px-4 py-2 text-xs font-sans justify-between rounded-t-md h-9 bg-token-sidebar-surface-primary dark:bg-token-main-surface-secondary select-none"&gt;bash&lt;/DIV&gt;
&lt;DIV class="sticky top-9 md:top-[5.75rem]"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="overflow-y-auto p-4" dir="ltr"&gt;&lt;CODE class="!whitespace-pre hljs language-bash"&gt;nvme list-ns /dev/nvme0
&lt;/CODE&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Verify Namespace List After Creation&lt;/STRONG&gt;: After executing the &lt;CODE&gt;nvme create-ns&lt;/CODE&gt; and &lt;CODE&gt;nvme attach-ns&lt;/CODE&gt; commands, verify that the namespace is recognized by running:&lt;/P&gt;
&lt;DIV class="contain-inline-size rounded-md border-[0.5px] border-token-border-medium relative bg-token-sidebar-surface-primary dark:bg-gray-950"&gt;
&lt;DIV class="flex items-center text-token-text-secondary px-4 py-2 text-xs font-sans justify-between rounded-t-md h-9 bg-token-sidebar-surface-primary dark:bg-token-main-surface-secondary select-none"&gt;bash&lt;/DIV&gt;
&lt;DIV class="sticky top-9 md:top-[5.75rem]"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="overflow-y-auto p-4" dir="ltr"&gt;&lt;CODE class="!whitespace-pre hljs language-bash"&gt;nvme list /dev/nvme0
&lt;/CODE&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Consider Rebooting&lt;/STRONG&gt;: Occasionally, namespaces might not show up immediately. A system reboot can sometimes refresh the NVMe subsystem and display newly created namespaces.&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;If the namespace still doesn’t appear, it could also be helpful to &lt;A href="https://www.solidigm.com/support-page/product-doc-cert/ka-00099.html" target="_self"&gt;check&lt;/A&gt; for the latest firmware. (You can use our &lt;A href="https://www.solidigm.com/support-page/drivers-downloads/ka-00085.html" target="_self"&gt;tool&lt;/A&gt; for updating)&amp;nbsp; Feel free to share any error messages or further details if you’re still facing issues, and we’ll do our best to help.&lt;/P&gt;
&lt;P&gt;Kind regards,&lt;BR /&gt;Gleb&lt;BR /&gt;Solidigm Customer Support&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SolidigmGleb_0-1731064163101.png" style="width: 400px;"&gt;&lt;img src="https://community.solidigm.com/t5/image/serverpage/image-id/483iB15F4534A48344F3/image-size/medium?v=v2&amp;amp;px=400" role="button" title="SolidigmGleb_0-1731064163101.png" alt="SolidigmGleb_0-1731064163101.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 08 Nov 2024 11:11:10 GMT</pubDate>
    <dc:creator>SolidigmGleb</dc:creator>
    <dc:date>2024-11-08T11:11:10Z</dc:date>
    <item>
      <title>Creating a namespace</title>
      <link>https://community.solidigm.com/t5/solid-state-drives-nand/creating-a-namespace/m-p/24533#M12280</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a pair of Solidigm SSDs:&lt;/P&gt;&lt;P&gt;SOLIDIGM SSDPF2SQ800GZ&lt;/P&gt;&lt;P&gt;(actually two pairs)&lt;/P&gt;&lt;P&gt;I am trying to create namespaces on that SSD, but I am struggling with the right parameters.&lt;/P&gt;&lt;P&gt;/usr/local/sbin/nvme create-ns /dev/nvme0 -s 150031139328 -c 200041519104 -d 0 -m 0 -f 0&lt;/P&gt;&lt;P&gt;nvme attach-ns /dev/nvme0 --namespace-id=1 -controllers=0&lt;/P&gt;&lt;P&gt;However, while these commands succeed on the surface, there's no namespace created&lt;/P&gt;&lt;P&gt;nvme list /dev/nvme0&lt;/P&gt;&lt;P&gt;is empty.&lt;/P&gt;&lt;P&gt;Can someone steer me to the correct parameters for the create command?&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Nov 2024 11:22:51 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/solid-state-drives-nand/creating-a-namespace/m-p/24533#M12280</guid>
      <dc:creator>rainer_d</dc:creator>
      <dc:date>2024-11-06T11:22:51Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a namespace</title>
      <link>https://community.solidigm.com/t5/solid-state-drives-nand/creating-a-namespace/m-p/24536#M12282</link>
      <description>&lt;P&gt;Hello rainer_d,&lt;/P&gt;
&lt;P&gt;Thank you for your contacting Solidigm! It sounds like you’re close, but there are a few key considerations when creating namespaces on Solidigm SSDs that might help clarify the process.&lt;/P&gt;
&lt;P&gt;First, when creating a namespace, ensure that the parameters for size (&lt;CODE&gt;-s&lt;/CODE&gt;) and capacity (&lt;CODE&gt;-c&lt;/CODE&gt;) align correctly with the drive’s specifications and intended usage. Here’s a step-by-step guide that might be helpful:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Confirm Size and Capacity Values&lt;/STRONG&gt;: Double-check that the values provided for the &lt;CODE&gt;-s&lt;/CODE&gt; (size) and &lt;CODE&gt;-c&lt;/CODE&gt; (capacity) flags are suitable for the storage available on your SSD. You might want to try smaller values initially to test if a smaller namespace can be successfully created.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Use the Correct Controller ID&lt;/STRONG&gt;: For the &lt;CODE&gt;nvme attach-ns&lt;/CODE&gt; command, ensure that &lt;CODE&gt;--controllers=0&lt;/CODE&gt; is actually the correct controller ID for your setup. If your SSD is connected through a specific controller, replace &lt;CODE&gt;0&lt;/CODE&gt; with the correct ID.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Specify the Namespace UUID&lt;/STRONG&gt;: Sometimes, explicitly setting a UUID when creating the namespace can help. You can try adding the &lt;CODE&gt;-u&lt;/CODE&gt; parameter with a UUID, for example:&lt;/P&gt;
&lt;DIV class="contain-inline-size rounded-md border-[0.5px] border-token-border-medium relative bg-token-sidebar-surface-primary dark:bg-gray-950"&gt;
&lt;DIV class="flex items-center text-token-text-secondary px-4 py-2 text-xs font-sans justify-between rounded-t-md h-9 bg-token-sidebar-surface-primary dark:bg-token-main-surface-secondary select-none"&gt;bash&lt;/DIV&gt;
&lt;DIV class="sticky top-9 md:top-[5.75rem]"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="overflow-y-auto p-4" dir="ltr"&gt;&lt;CODE class="!whitespace-pre hljs language-bash"&gt;/usr/local/sbin/nvme create-ns /dev/nvme0 -s 150031139328 -c 200041519104 -d 0 -m 0 -f 0 -u &amp;lt;uuid&amp;gt;
&lt;/CODE&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Check for Existing Namespaces&lt;/STRONG&gt;: Run the following command to confirm that there aren’t any pre-existing namespaces that might interfere:&lt;/P&gt;
&lt;DIV class="contain-inline-size rounded-md border-[0.5px] border-token-border-medium relative bg-token-sidebar-surface-primary dark:bg-gray-950"&gt;
&lt;DIV class="flex items-center text-token-text-secondary px-4 py-2 text-xs font-sans justify-between rounded-t-md h-9 bg-token-sidebar-surface-primary dark:bg-token-main-surface-secondary select-none"&gt;bash&lt;/DIV&gt;
&lt;DIV class="sticky top-9 md:top-[5.75rem]"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="overflow-y-auto p-4" dir="ltr"&gt;&lt;CODE class="!whitespace-pre hljs language-bash"&gt;nvme list-ns /dev/nvme0
&lt;/CODE&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Verify Namespace List After Creation&lt;/STRONG&gt;: After executing the &lt;CODE&gt;nvme create-ns&lt;/CODE&gt; and &lt;CODE&gt;nvme attach-ns&lt;/CODE&gt; commands, verify that the namespace is recognized by running:&lt;/P&gt;
&lt;DIV class="contain-inline-size rounded-md border-[0.5px] border-token-border-medium relative bg-token-sidebar-surface-primary dark:bg-gray-950"&gt;
&lt;DIV class="flex items-center text-token-text-secondary px-4 py-2 text-xs font-sans justify-between rounded-t-md h-9 bg-token-sidebar-surface-primary dark:bg-token-main-surface-secondary select-none"&gt;bash&lt;/DIV&gt;
&lt;DIV class="sticky top-9 md:top-[5.75rem]"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="overflow-y-auto p-4" dir="ltr"&gt;&lt;CODE class="!whitespace-pre hljs language-bash"&gt;nvme list /dev/nvme0
&lt;/CODE&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/LI&gt;
&lt;LI&gt;
&lt;P&gt;&lt;STRONG&gt;Consider Rebooting&lt;/STRONG&gt;: Occasionally, namespaces might not show up immediately. A system reboot can sometimes refresh the NVMe subsystem and display newly created namespaces.&lt;/P&gt;
&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;If the namespace still doesn’t appear, it could also be helpful to &lt;A href="https://www.solidigm.com/support-page/product-doc-cert/ka-00099.html" target="_self"&gt;check&lt;/A&gt; for the latest firmware. (You can use our &lt;A href="https://www.solidigm.com/support-page/drivers-downloads/ka-00085.html" target="_self"&gt;tool&lt;/A&gt; for updating)&amp;nbsp; Feel free to share any error messages or further details if you’re still facing issues, and we’ll do our best to help.&lt;/P&gt;
&lt;P&gt;Kind regards,&lt;BR /&gt;Gleb&lt;BR /&gt;Solidigm Customer Support&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="SolidigmGleb_0-1731064163101.png" style="width: 400px;"&gt;&lt;img src="https://community.solidigm.com/t5/image/serverpage/image-id/483iB15F4534A48344F3/image-size/medium?v=v2&amp;amp;px=400" role="button" title="SolidigmGleb_0-1731064163101.png" alt="SolidigmGleb_0-1731064163101.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Nov 2024 11:11:10 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/solid-state-drives-nand/creating-a-namespace/m-p/24536#M12282</guid>
      <dc:creator>SolidigmGleb</dc:creator>
      <dc:date>2024-11-08T11:11:10Z</dc:date>
    </item>
    <item>
      <title>Re: Creating a namespace</title>
      <link>https://community.solidigm.com/t5/solid-state-drives-nand/creating-a-namespace/m-p/24539#M12284</link>
      <description>&lt;P&gt;Hi Gleb,&lt;/P&gt;&lt;P&gt;th&lt;/P&gt;&lt;P&gt;thanks for getting back to me.&lt;/P&gt;&lt;P&gt;In the meantime (and because there was a certain pressure to get this working), I downloaded the "sst" tool from your website and installed it in a life-cd of GRML (the server doesn't run any of the supported OSs).&lt;/P&gt;&lt;P&gt;With that tool, I was able to create a new namespace that is acceptable for the OS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;Rainer&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Nov 2024 11:47:09 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/solid-state-drives-nand/creating-a-namespace/m-p/24539#M12284</guid>
      <dc:creator>rainer_d</dc:creator>
      <dc:date>2024-11-08T11:47:09Z</dc:date>
    </item>
  </channel>
</rss>

