<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:admin="http://webns.net/mvcb/"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<channel> 

	<title>Comments on: Diagnosing a faulty hard drive</title>
	<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive/</link>
	<description>Comments on Ask MetaFilter post Diagnosing a faulty hard drive</description>
	<pubDate>Wed, 25 Feb 2009 03:05:54 -0800</pubDate>
	<lastBuildDate>Wed, 25 Feb 2009 03:05:54 -0800</lastBuildDate>
	<language>en-us</language>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>60</ttl>

	<item>
		<title>Question: Diagnosing a faulty hard drive</title>
		<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive</link>	
		<description>My PC is no longer recognising one of my SATA hard drives. &lt;br /&gt;&lt;br /&gt; This morning when I turned on my PC it did not recognise any of the SATA devices - OS HD (200gb Seagate), storage HD (500gb Seagate), and DVD writer (a cheapo Samsung job).  After a bit of messing about I discovered that I can boot fine with just the OS HD and the DVD plugged in, but plugging in the storage HD - whether it&apos;s the only SATA device plugged in or in any combination with the others - causes the system to stop seeing any SATA devices (and once caused it to power off as soon as it powered on).&lt;br&gt;
&lt;br&gt;
I have nothing on the PATA port.  My motherboard is a Gigabyte P31-DS3L, my PSU is a Corsair VX450, and I run Windows XP SP2.  The 200gb (working) drive is about three years old, the 500gb (broken) one is a little less than a year old.  The PC has not been moved recently.  I&apos;ve tried them all on different SATA cables and off different sockets (although the mobo only has four) and with different power cables off the PSU.  I&apos;ve reset the bios to &quot;failsafe defaults&quot;.  Running Windows on the working drive seems as stable as usual.&lt;br&gt;
&lt;br&gt;
Last night I left the PC downloading, set to hibernate when it had finished getting the file.&lt;br&gt;
&lt;br&gt;
I&apos;m assuming the drive has just flat-out died at this point, but before I RMA I&apos;d love some ideas to get it working again, even just for long enough to rescue some data (the data on the drive isn&apos;t important enough to actually spend money on a retrieval service, but there are some photos and documents and things it would be nice to rescue; and yes, I&apos;ve learned my lesson about backing files up now!).</description>
		<guid isPermaLink="false">post:ask.metafilter.com,2009:site.115107</guid>
		<pubDate>Wed, 25 Feb 2009 01:34:25 -0800</pubDate>
		<dc:creator>ArmyOfKittens</dc:creator>
		
			<category>harddrive</category>
		
			<category>sata</category>
		
			<category>seagate</category>
		
			<category>serialata</category>
		
			<category>pc</category>
		
	</item> <item>
		<title>By: Blazecock Pileon</title>
		<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive#1652241</link>	
		<description>&lt;a href=&quot;http://www.trisweb.com/archives/2005/06/15/hard-disk-recovery-the-freezer-trick/&quot;&gt;Hard drive freezer trick&lt;/a&gt;</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2009:site.115107-1652241</guid>
		<pubDate>Wed, 25 Feb 2009 03:05:54 -0800</pubDate>
		<dc:creator>Blazecock Pileon</dc:creator>
	</item><item>
		<title>By: gjc</title>
		<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive#1652307</link>	
		<description>I doubt the freezer trick would work in this case, that&apos;s usually for mechanical failures.  This is an electronic failure.  Probably shot.  You could try getting an identical drive and swapping the circuit boards, that has worked for me a few times when I had a hard drive that&apos;s mechanically sound but electronically shot.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2009:site.115107-1652307</guid>
		<pubDate>Wed, 25 Feb 2009 05:51:42 -0800</pubDate>
		<dc:creator>gjc</dc:creator>
	</item><item>
		<title>By: kdar</title>
		<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive#1652321</link>	
		<description>I think you&apos;ve pretty much exhausted all of your options for diagnostics, unless you&apos;re interested in trying the affected drive in another machine.  Looks like it&apos;s time to RMA + swap.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2009:site.115107-1652321</guid>
		<pubDate>Wed, 25 Feb 2009 06:18:20 -0800</pubDate>
		<dc:creator>kdar</dc:creator>
	</item><item>
		<title>By: Simon Barclay</title>
		<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive#1652359</link>	
		<description>Your 500 GB Seagate is probably part of a batch with a &lt;a href=&quot;http://www.theinquirer.net/inquirer/news/374/1050374/seagate-barracudas-7200-11-failing&quot;&gt;known&lt;/a&gt; firmware &lt;a href=&quot;http://www.articledashboard.com/Article/Seagate-7200-11--ES2-and-DiamondMax-22-Firmware-Failures---The-so-called--Bricked--drives/736771&quot;&gt;problem&lt;/a&gt;. If that&apos;s the case, your data is still there, but you need to flash your firmware. See &lt;a href=&quot;http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931&amp;NewLang=en&quot;&gt;here&lt;/a&gt; to determine if your drive is potentially affected, and how to act. &lt;br&gt;
&lt;br&gt;
I&apos;ve heard that Seagate is worried about their image, so they may pay to retrieve your data - don&apos;t just send it in as any normal RMA without calling them first and complaining. Push to get them to retrieve your data.&lt;br&gt;
&lt;br&gt;
Also, do some Google searching (&lt;a href=&quot;http://www.google.com/search?q=flash+firmware+bricked+seagate+7200.11&quot;&gt;for example&lt;/a&gt;), as some people have had success flashing their drive even after it bricked. Normally, you would have downloaded an ISO file to burn onto CD, boot from the CD, and flash your drive. Maybe you can still do that, even with the bricked drive?</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2009:site.115107-1652359</guid>
		<pubDate>Wed, 25 Feb 2009 06:57:09 -0800</pubDate>
		<dc:creator>Simon Barclay</dc:creator>
	</item><item>
		<title>By: ArmyOfKittens</title>
		<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive#1652446</link>	
		<description>Simon, that looks right on the money.  Pootling around the forum indicates that my drive has the classic symptoms of brickitude caused by that firmware fault.  I&apos;ll look into flashing the thing before I succumb to the whole &quot;please don&apos;t look at my photos and embarrassing archived diary entries from when I was seventeen&quot; data retrieval service.&lt;br&gt;
&lt;br&gt;
Thanks :)</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2009:site.115107-1652446</guid>
		<pubDate>Wed, 25 Feb 2009 08:11:57 -0800</pubDate>
		<dc:creator>ArmyOfKittens</dc:creator>
	</item><item>
		<title>By: Simon Barclay</title>
		<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive#1652899</link>	
		<description>Please let me know how it works out.</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2009:site.115107-1652899</guid>
		<pubDate>Wed, 25 Feb 2009 13:51:24 -0800</pubDate>
		<dc:creator>Simon Barclay</dc:creator>
	</item><item>
		<title>By: ArmyOfKittens</title>
		<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive#1653699</link>	
		<description>Flashing didn&apos;t work, unfortunately, but it seemed like a long shot anyway.  I have a ticket raised with Seagate right now, to start the whole repair and recovery process.  So it&apos;s looking good for me and all my embarrassing old photographs :)</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2009:site.115107-1653699</guid>
		<pubDate>Thu, 26 Feb 2009 04:04:19 -0800</pubDate>
		<dc:creator>ArmyOfKittens</dc:creator>
	</item><item>
		<title>By: ArmyOfKittens</title>
		<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive#1657885</link>	
		<description>Further update: Seagate have confirmed to me that *if* the drive died because of this formware issue, they can force-flash it with the new firmware and ship it back to me, good as new.  If it&apos;s another issue, they&apos;ll replace the drive; in which case I&apos;ll lose my data, but I can&apos;t afford hundreds of pounds for a data recovery service right now.  Or ever, really.&lt;br&gt;
&lt;br&gt;
So it seems to be working out as well as could be hoped :)</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2009:site.115107-1657885</guid>
		<pubDate>Mon, 02 Mar 2009 02:42:37 -0800</pubDate>
		<dc:creator>ArmyOfKittens</dc:creator>
	</item><item>
		<title>By: Simon Barclay</title>
		<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive#1659317</link>	
		<description>Good luck with your data!</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2009:site.115107-1659317</guid>
		<pubDate>Tue, 03 Mar 2009 06:21:58 -0800</pubDate>
		<dc:creator>Simon Barclay</dc:creator>
	</item><item>
		<title>By: ArmyOfKittens</title>
		<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive#1689136</link>	
		<description>The automail reminded me to come back to this thread, so here I am, confirming that I got the hard drive back from Seagate, data intact, firmware upgraded, and working perfectly. :)</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2009:site.115107-1689136</guid>
		<pubDate>Fri, 27 Mar 2009 12:13:10 -0800</pubDate>
		<dc:creator>ArmyOfKittens</dc:creator>
	</item><item>
		<title>By: Simon Barclay</title>
		<link>http://ask.metafilter.com/115107/Diagnosing-a-faulty-hard-drive#1689416</link>	
		<description>Wow, that was pretty fast. Congratulations!</description>
		<guid isPermaLink="false">comment:ask.metafilter.com,2009:site.115107-1689416</guid>
		<pubDate>Fri, 27 Mar 2009 16:43:35 -0800</pubDate>
		<dc:creator>Simon Barclay</dc:creator>
	</item>
	</channel>
</rss>
