<?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 Lone &amp;quot;bad block&amp;quot; on new unformatted Intel X25-E Extreme 32GB in Archive</title>
    <link>https://community.solidigm.com/t5/archive/lone-quot-bad-block-quot-on-new-unformatted-intel-x25-e-extreme/m-p/669#M531</link>
    <description>&lt;P&gt;Purchased 2 Intel X25-E Extreme 32GB from &lt;A href="http://amazon.com" rel="nofollow noopener noreferrer"&gt;amazon.com&lt;/A&gt;.&lt;/P&gt;Get both with same "PACK DATE", "PACKED BY", "BATCH # ", very similar "SN".I started with updating firmware on both.One of them had "bad block" when I checked it with HD Tune (Read benchmark). It was, like, at 97% pos, near the end of disk.Write benchmark got rid of that "bad block".I got following ideas about this issue:1) Firmware update caused rare block encoding incompatibility.2) One bit of SLC memory lost its charge over last 4.5 month.3) While performing write test on factory unit was unplugged unexpectedly, so during its writing block got damaged.&lt;P&gt;Any suggestions?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;S.M.A.R.T. following:&lt;/P&gt;&lt;P&gt;Event log record following (sorry, in russian):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Data" for this even log record following:&lt;/P&gt;&lt;P&gt;0000: 03 00 68 00 01 00 b6 00   ..h...╢.&lt;/P&gt;0008: 00 00 00 00 07 00 04 c0   .......└0010: 00 01 00 00 9c 00 00 c0   ....?..└0018: 00 00 00 00 00 00 00 00   ........0020: 00 4a e5 72 07 00 00 00   .Jσr....0028: 1a 88 01 00 00 00 00 00   .?......0030: ff ff ff ff 00 00 00 00       ....0038: 40 00 00 84 02 00 00 00   @..?....0040: 00 20 0a 12 40 03 20 00   . ..@. .0048: 00 00 00 00 0a 00 00 00   ........0050: 48 00 7e 01 50 36 a8 87   H.~.P6¿?0058: 00 00 00 00 80 96 68 87   ....??h?0060: 02 00 00 00 a5 72 b9 03   ....Ñr╣.0068: 28 00 03 b9 72 a5 00 00   (..╣rÑ..0070: 80 00 00 00 00 00 00 00   ?.......0078: f0 00 03 00 00 00 00 0b   ≡.......0080: 00 00 00 00 00 00 00 00   ........0088: 00 00 00 00 00 00 00 00   ........</description>
    <pubDate>Tue, 15 Sep 2009 21:04:39 GMT</pubDate>
    <dc:creator>idata</dc:creator>
    <dc:date>2009-09-15T21:04:39Z</dc:date>
    <item>
      <title>Lone "bad block" on new unformatted Intel X25-E Extreme 32GB</title>
      <link>https://community.solidigm.com/t5/archive/lone-quot-bad-block-quot-on-new-unformatted-intel-x25-e-extreme/m-p/669#M531</link>
      <description>&lt;P&gt;Purchased 2 Intel X25-E Extreme 32GB from &lt;A href="http://amazon.com" rel="nofollow noopener noreferrer"&gt;amazon.com&lt;/A&gt;.&lt;/P&gt;Get both with same "PACK DATE", "PACKED BY", "BATCH # ", very similar "SN".I started with updating firmware on both.One of them had "bad block" when I checked it with HD Tune (Read benchmark). It was, like, at 97% pos, near the end of disk.Write benchmark got rid of that "bad block".I got following ideas about this issue:1) Firmware update caused rare block encoding incompatibility.2) One bit of SLC memory lost its charge over last 4.5 month.3) While performing write test on factory unit was unplugged unexpectedly, so during its writing block got damaged.&lt;P&gt;Any suggestions?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;S.M.A.R.T. following:&lt;/P&gt;&lt;P&gt;Event log record following (sorry, in russian):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Data" for this even log record following:&lt;/P&gt;&lt;P&gt;0000: 03 00 68 00 01 00 b6 00   ..h...╢.&lt;/P&gt;0008: 00 00 00 00 07 00 04 c0   .......└0010: 00 01 00 00 9c 00 00 c0   ....?..└0018: 00 00 00 00 00 00 00 00   ........0020: 00 4a e5 72 07 00 00 00   .Jσr....0028: 1a 88 01 00 00 00 00 00   .?......0030: ff ff ff ff 00 00 00 00       ....0038: 40 00 00 84 02 00 00 00   @..?....0040: 00 20 0a 12 40 03 20 00   . ..@. .0048: 00 00 00 00 0a 00 00 00   ........0050: 48 00 7e 01 50 36 a8 87   H.~.P6¿?0058: 00 00 00 00 80 96 68 87   ....??h?0060: 02 00 00 00 a5 72 b9 03   ....Ñr╣.0068: 28 00 03 b9 72 a5 00 00   (..╣rÑ..0070: 80 00 00 00 00 00 00 00   ?.......0078: f0 00 03 00 00 00 00 0b   ≡.......0080: 00 00 00 00 00 00 00 00   ........0088: 00 00 00 00 00 00 00 00   ........</description>
      <pubDate>Tue, 15 Sep 2009 21:04:39 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/lone-quot-bad-block-quot-on-new-unformatted-intel-x25-e-extreme/m-p/669#M531</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2009-09-15T21:04:39Z</dc:date>
    </item>
  </channel>
</rss>

