<?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: ssacli zero disk for media errors in HPE ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/ssacli-zero-disk-for-media-errors/m-p/7227827#M189606</link>
    <description>&lt;P&gt;I think I found my solution&lt;BR /&gt;&lt;A href="https://support.hpe.com/resource3/docDisplay/pdfjs/web/viewer.html?file=%2Fhpesc%2Fpublic%2Fapi%2Fdocument%2Fdp00002635en_us%3Fv%3D1724321506000&amp;amp;locale=en-US&amp;amp;rangeChunkSize=256000&amp;amp;disableAutoFetch=false&amp;amp;disableCache=true&amp;amp;version=20241003140944#_OPENTOPIC_TOC_PROCESSING_d1561e4214" target="_blank"&gt;https://support.hpe.com/resource3/docDisplay/pdfjs/web/viewer.html?file=%2Fhpesc%2Fpublic%2Fapi%2Fdocument%2Fdp00002635en_us%3Fv%3D1724321506000&amp;amp;locale=en-US&amp;amp;rangeChunkSize=256000&amp;amp;disableAutoFetch=false&amp;amp;disableCache=true&amp;amp;version=20241003140944#_OPENTOPIC_TOC_PROCESSING_d1561e4214&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Erasing a Physical Drive&lt;/U&gt;&lt;/STRONG&gt;&lt;BR /&gt;This section provides syntax to begin and stop the drive erase process.&lt;BR /&gt;Syntax:&lt;BR /&gt;To begin the drive erase process:&lt;BR /&gt;&lt;EM&gt;&amp;lt;target&amp;gt; modify [erasepattern= zero|random_zero|random_random_zero|crypto|block|&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;overwrite][unrestricted=on|off]&lt;/EM&gt;&lt;BR /&gt;Where&lt;BR /&gt;• the &amp;lt;target&amp;gt; can be any valid physical drive&lt;BR /&gt;• block is for SSDs only&lt;BR /&gt;• overwrite is for HDDs only&lt;BR /&gt;• crypto, if implemented, is for both SSDs and HDDs&lt;BR /&gt;To stop the drive erase process:&lt;BR /&gt;&amp;lt;target&amp;gt; modify [stoperase]&lt;BR /&gt;Where&lt;BR /&gt;• the &amp;lt;target&amp;gt; can be any valid physical drive&lt;BR /&gt;• stoperase applies to zero, random_zero, and random_random_zero erase patterns only&lt;BR /&gt;• crypto, block, or overwrite drive erase processes cannot be stopped.&lt;BR /&gt;Example Commands:&lt;BR /&gt;&lt;EM&gt;=&amp;gt; ctrl slot=3 physicaldrive 1e:1:1 modify enableerasedrive&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;=&amp;gt; ctrl slot=3 physicaldrive 1e:1:1 modify erase erasepattern=zero&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;=&amp;gt; ctrl slot=3 pd 1e:1:1 modify stoperase&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;=&amp;gt; ctrl slot=3 physicaldrive 1e:1:1 modify erase erasepattern=crypto unrestricted=on&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 23 Oct 2024 18:26:22 GMT</pubDate>
    <dc:creator>mr_vaughn</dc:creator>
    <dc:date>2024-10-23T18:26:22Z</dc:date>
    <item>
      <title>ssacli zero disk for media errors</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/ssacli-zero-disk-for-media-errors/m-p/7227824#M189605</link>
      <description>&lt;P&gt;Got the following message on a DL380 Gen10 P408i RAID10 Array running ESXi 6.7u3&lt;/P&gt;&lt;P&gt;I updated the firmware's the system everything, disks, conroller bios etc.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;I&gt;1915 Slot # Smart Array - Drive media errors could not be recovered by RAID protection.Action: Backup and restore the data on the drive. Overwriting the affected blocks should resolve the media errors.&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&lt;I&gt;I did find the HPE Advisory &lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&amp;amp;docId=a00104843en_us" target="_blank" rel="noopener"&gt;"1716" or "1915" POST Error&lt;/A&gt;&amp;nbsp;&lt;/I&gt;&lt;/P&gt;&lt;P&gt;But issue is there are Zero command examples on how to "Erase all disks in the array using SSA/SSCLI with One-pass: Write all zeroes."&lt;/P&gt;&lt;P&gt;This has been my base for structuring and learning SSACLi commands.&lt;BR /&gt;&lt;A href="https://kallesplayground.wordpress.com/useful-stuff/hp-smart-array-cli-commands-under-esxi/" target="_blank"&gt;https://kallesplayground.wordpress.com/useful-stuff/hp-smart-array-cli-commands-under-esxi/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This talks about the secure erase &lt;A href="https://www.cloudhosting.lv/eng/faq/How-To-Secure-Erase-ESXi-Disks-HPE-or-Generic-Hardware" target="_blank"&gt;https://www.cloudhosting.lv/eng/faq/How-To-Secure-Erase-ESXi-Disks-HPE-or-Generic-Hardware&lt;/A&gt; , which is not the same and one-pass write all zero's correct?&lt;/P&gt;&lt;P&gt;If so I do see all disks support the Santize Erase but have concerns since some disks say 52min to erase and other over 3hours.&lt;/P&gt;&lt;P&gt;All disks are the same 15K 900Gb SAS HPE disks&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Sanitize Erase Supported: True&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Estimated Max Erase Time: 3 hour(s), 14 minute(s)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Unrestricted Sanitize Supported: True&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;1. Is it the correct method to use the Sanitise erase to have it write all Zero's&lt;/P&gt;&lt;P&gt;2. Do i have to do this on each disk in the array?&lt;/P&gt;&lt;P&gt;3. Why the large time differences?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 18:01:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/ssacli-zero-disk-for-media-errors/m-p/7227824#M189605</guid>
      <dc:creator>mr_vaughn</dc:creator>
      <dc:date>2024-10-23T18:01:33Z</dc:date>
    </item>
    <item>
      <title>Re: ssacli zero disk for media errors</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/ssacli-zero-disk-for-media-errors/m-p/7227827#M189606</link>
      <description>&lt;P&gt;I think I found my solution&lt;BR /&gt;&lt;A href="https://support.hpe.com/resource3/docDisplay/pdfjs/web/viewer.html?file=%2Fhpesc%2Fpublic%2Fapi%2Fdocument%2Fdp00002635en_us%3Fv%3D1724321506000&amp;amp;locale=en-US&amp;amp;rangeChunkSize=256000&amp;amp;disableAutoFetch=false&amp;amp;disableCache=true&amp;amp;version=20241003140944#_OPENTOPIC_TOC_PROCESSING_d1561e4214" target="_blank"&gt;https://support.hpe.com/resource3/docDisplay/pdfjs/web/viewer.html?file=%2Fhpesc%2Fpublic%2Fapi%2Fdocument%2Fdp00002635en_us%3Fv%3D1724321506000&amp;amp;locale=en-US&amp;amp;rangeChunkSize=256000&amp;amp;disableAutoFetch=false&amp;amp;disableCache=true&amp;amp;version=20241003140944#_OPENTOPIC_TOC_PROCESSING_d1561e4214&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Erasing a Physical Drive&lt;/U&gt;&lt;/STRONG&gt;&lt;BR /&gt;This section provides syntax to begin and stop the drive erase process.&lt;BR /&gt;Syntax:&lt;BR /&gt;To begin the drive erase process:&lt;BR /&gt;&lt;EM&gt;&amp;lt;target&amp;gt; modify [erasepattern= zero|random_zero|random_random_zero|crypto|block|&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;overwrite][unrestricted=on|off]&lt;/EM&gt;&lt;BR /&gt;Where&lt;BR /&gt;• the &amp;lt;target&amp;gt; can be any valid physical drive&lt;BR /&gt;• block is for SSDs only&lt;BR /&gt;• overwrite is for HDDs only&lt;BR /&gt;• crypto, if implemented, is for both SSDs and HDDs&lt;BR /&gt;To stop the drive erase process:&lt;BR /&gt;&amp;lt;target&amp;gt; modify [stoperase]&lt;BR /&gt;Where&lt;BR /&gt;• the &amp;lt;target&amp;gt; can be any valid physical drive&lt;BR /&gt;• stoperase applies to zero, random_zero, and random_random_zero erase patterns only&lt;BR /&gt;• crypto, block, or overwrite drive erase processes cannot be stopped.&lt;BR /&gt;Example Commands:&lt;BR /&gt;&lt;EM&gt;=&amp;gt; ctrl slot=3 physicaldrive 1e:1:1 modify enableerasedrive&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;=&amp;gt; ctrl slot=3 physicaldrive 1e:1:1 modify erase erasepattern=zero&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;=&amp;gt; ctrl slot=3 pd 1e:1:1 modify stoperase&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;=&amp;gt; ctrl slot=3 physicaldrive 1e:1:1 modify erase erasepattern=crypto unrestricted=on&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 18:26:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/ssacli-zero-disk-for-media-errors/m-p/7227827#M189606</guid>
      <dc:creator>mr_vaughn</dc:creator>
      <dc:date>2024-10-23T18:26:22Z</dc:date>
    </item>
    <item>
      <title>Re: ssacli zero disk for media errors</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/ssacli-zero-disk-for-media-errors/m-p/7227848#M189608</link>
      <description>&lt;P&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/97508"&gt;@mr_vaughn&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Excellent! Glad to know that you have found the solution. Thank you for sharing the steps.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2024 03:40:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/ssacli-zero-disk-for-media-errors/m-p/7227848#M189608</guid>
      <dc:creator>Parvez_Admin</dc:creator>
      <dc:date>2024-10-24T03:40:20Z</dc:date>
    </item>
    <item>
      <title>Re: ssacli zero disk for media errors</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/ssacli-zero-disk-for-media-errors/m-p/7228042#M189634</link>
      <description>&lt;P&gt;Here is the command for ESXi for all disks on controller in slot 3&lt;/P&gt;&lt;P&gt;&lt;EM&gt;/opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=3 pd all modify erase erasepattern=zero&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;but erase times are massive difference between models of the same HPE part number Drive for 15K 600Gb SAS drives&lt;/P&gt;&lt;P&gt;&lt;U&gt;&lt;STRONG&gt;52min vs 3 hours14min. Why?&lt;/STRONG&gt;&lt;/U&gt;&lt;/P&gt;&lt;P&gt;Firmware cannot be updated in ESXi 6.7 I cannot reboot Host to apply SPP offline either.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;[root@ESXHOST:~] /opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=3 pd all show detail |grep Erase&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Status: Erase In Progress&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Pattern: zero&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Percent Complete: 3%&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Erase Supported: True&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Estimated Max Erase Time: 0 hour(s), 52 minute(s)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Status: Erase In Progress&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Pattern: zero&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Percent Complete: 3%&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Erase Supported: True&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Estimated Max Erase Time: 0 hour(s), 52 minute(s)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Status: Erase In Progress&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Pattern: zero&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Percent Complete: 3%&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Erase Supported: True&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Estimated Max Erase Time: 0 hour(s), 52 minute(s)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Status: Erase In Progress&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Pattern: zero&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Percent Complete: 0%&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Erase Supported: True&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Estimated Max Erase Time: 3 hour(s), 14 minute(s)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Status: Erase In Progress&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Pattern: zero&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Percent Complete: 3%&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Erase Supported: True&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Estimated Max Erase Time: 0 hour(s), 52 minute(s)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Status: Erase In Progress&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Pattern: zero&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Percent Complete: 0%&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Erase Supported: True&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Estimated Max Erase Time: 3 hour(s), 14 minute(s)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Status: Erase In Progress&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Pattern: zero&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Percent Complete: 0%&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Erase Supported: True&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Estimated Max Erase Time: 3 hour(s), 14 minute(s)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Status: Erase In Progress&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Pattern: zero&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Erase Percent Complete: 0%&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Erase Supported: True&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Sanitize Estimated Max Erase Time: 3 hour(s), 14 minute(s)&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;[root@ESXHOST:~] /opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=3 pd all show detail |grep Model&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Model: HPE EH000600JWCPL&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Model: HPE EH000600JWCPL&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Model: HPE EH000600JWCPL&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Model: HPE EH000600JWHPN&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Model: HPE EH000600JXLVT&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Model: HPE EH000600JWHPN&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Model: HPE EH000600JWHPN&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Model: HPE EH000600JWHPN&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;[root@ESXHOST:~] /opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=3 pd all show detail |grep Firmware&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Firmware Revision: HPD8&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Firmware Revision: HPD8&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Firmware Revision: HPD8&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Firmware Revision: HPD7&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Firmware Revision: HPD9&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Firmware Revision: HPD7&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Firmware Revision: HPD7&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Firmware Revision: HPD7&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;[root@ESXHOST:~]&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 26 Oct 2024 02:06:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/ssacli-zero-disk-for-media-errors/m-p/7228042#M189634</guid>
      <dc:creator>mr_vaughn</dc:creator>
      <dc:date>2024-10-26T02:06:54Z</dc:date>
    </item>
    <item>
      <title>Re: ssacli zero disk for media errors</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/ssacli-zero-disk-for-media-errors/m-p/7228047#M189637</link>
      <description>&lt;P&gt;Further this command worked on the drive that got stuck at 0% for zero write.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;/opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=3 pd 1I:2:4 modify erase erasepattern=overwrite unrestricted=off forced&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 26 Oct 2024 05:46:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/ssacli-zero-disk-for-media-errors/m-p/7228047#M189637</guid>
      <dc:creator>mr_vaughn</dc:creator>
      <dc:date>2024-10-26T05:46:20Z</dc:date>
    </item>
  </channel>
</rss>

