<?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 X25-M G2 80GB Damaged Blocks - Should I RMA? in Archive</title>
    <link>https://community.solidigm.com/t5/archive/x25-m-g2-80gb-damaged-blocks-should-i-rma/m-p/1333#M1195</link>
    <description>&lt;P&gt;I was one of the unlucky whose drive died after updating the firmware but afterwards I was able to re-install Win7 anyway and it has been working well for the last two days.  I was curious if the update caused any problems with speed, so I ran HDTune 2.55's benchmark, which didn't complete because of a read error.  So then I ran HDTune's error scan and it detected 0.4% damaged blocks (see the screenshot below).  Are damaged blocks to be expected or should I RMA for a new, clean/perfect drive?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 31 Oct 2009 04:16:23 GMT</pubDate>
    <dc:creator>idata</dc:creator>
    <dc:date>2009-10-31T04:16:23Z</dc:date>
    <item>
      <title>X25-M G2 80GB Damaged Blocks - Should I RMA?</title>
      <link>https://community.solidigm.com/t5/archive/x25-m-g2-80gb-damaged-blocks-should-i-rma/m-p/1333#M1195</link>
      <description>&lt;P&gt;I was one of the unlucky whose drive died after updating the firmware but afterwards I was able to re-install Win7 anyway and it has been working well for the last two days.  I was curious if the update caused any problems with speed, so I ran HDTune 2.55's benchmark, which didn't complete because of a read error.  So then I ran HDTune's error scan and it detected 0.4% damaged blocks (see the screenshot below).  Are damaged blocks to be expected or should I RMA for a new, clean/perfect drive?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 31 Oct 2009 04:16:23 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/x25-m-g2-80gb-damaged-blocks-should-i-rma/m-p/1333#M1195</guid>
      <dc:creator>idata</dc:creator>
      <dc:date>2009-10-31T04:16:23Z</dc:date>
    </item>
    <item>
      <title>Re: X25-M G2 80GB Damaged Blocks - Should I RMA?</title>
      <link>https://community.solidigm.com/t5/archive/x25-m-g2-80gb-damaged-blocks-should-i-rma/m-p/1334#M1196</link>
      <description>&lt;P&gt;Hi calbearz,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My G1 80 GB drive initially had 0 defective sectors, but after a rough use (several HDDerase's, W7 installations and BSOD's), it developed 7 bad sectors, as detected by HD Tune - Health.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems that SSD's are very sensitives to hard use (fond of Velociraptors) and prone to get bad blocks or damaged areas.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After that, i was unable to to run HD Tune benchmark, like you, but to my surprise, after a new clean W7 install, HD Tune ran OK without any errors, even though the bad blocks still were detected by HD Tune.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also with the Intel Toolbox we can see the number of damaged sectors under SMART Re-allocated Sector Count but in the User Guide there is no a clear statement of how many damaged/re-allocated sectors are allowed before the drive "dies".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I suppose this thing is analogous to "dead pixels" on LCD screens, where a new screen may have a few bad pixels, and this is considered normal by the manufacturer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, i suppose that you should contact Intel about the issue, after this FW update tsunami is over.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck.&lt;/P&gt;</description>
      <pubDate>Sat, 31 Oct 2009 21:16:59 GMT</pubDate>
      <guid>https://community.solidigm.com/t5/archive/x25-m-g2-80gb-damaged-blocks-should-i-rma/m-p/1334#M1196</guid>
      <dc:creator>VPent</dc:creator>
      <dc:date>2009-10-31T21:16:59Z</dc:date>
    </item>
  </channel>
</rss>

