<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Upgrading the Seagate Barracuda 7200.11 to firmware SD1A</title>
	<atom:link href="http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/</link>
	<description>source control for my (useless) knowledge</description>
	<lastBuildDate>Fri, 06 Jan 2012 16:44:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: yiming</title>
		<link>http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/comment-page-1/#comment-18149</link>
		<dc:creator>yiming</dc:creator>
		<pubDate>Wed, 28 Dec 2011 17:26:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.yimingliu.com/?p=564#comment-18149</guid>
		<description>Wow, I&#039;m amazed that this is still a problem.  I actually made a complaint to their support personnel about the issue just after writing this post, more than two years ago.  I suggested that their documentation was incomplete, and that they did not cover this very confusing problem about SATA modes causing firmware update failures.  Lots of other people have had this issue, and are wasting hours because of Seagate&#039;s incomprehensible error messages.  Apparently they didn&#039;t do anything with this information.</description>
		<content:encoded><![CDATA[<p>Wow, I&#8217;m amazed that this is still a problem.  I actually made a complaint to their support personnel about the issue just after writing this post, more than two years ago.  I suggested that their documentation was incomplete, and that they did not cover this very confusing problem about SATA modes causing firmware update failures.  Lots of other people have had this issue, and are wasting hours because of Seagate&#8217;s incomprehensible error messages.  Apparently they didn&#8217;t do anything with this information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sandra</title>
		<link>http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/comment-page-1/#comment-18147</link>
		<dc:creator>sandra</dc:creator>
		<pubDate>Wed, 28 Dec 2011 17:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.yimingliu.com/?p=564#comment-18147</guid>
		<description>One would have hoped that seagate could have given a hint about this on their support site by now (late 2011!!)</description>
		<content:encoded><![CDATA[<p>One would have hoped that seagate could have given a hint about this on their support site by now (late 2011!!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sandra</title>
		<link>http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/comment-page-1/#comment-18145</link>
		<dc:creator>sandra</dc:creator>
		<pubDate>Wed, 28 Dec 2011 16:57:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.yimingliu.com/?p=564#comment-18145</guid>
		<description>Thank you for the tip. Temporary switching sata from ahci to ide in bios solved the problem I was having getting the updater running for me.</description>
		<content:encoded><![CDATA[<p>Thank you for the tip. Temporary switching sata from ahci to ide in bios solved the problem I was having getting the updater running for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nona Mills</title>
		<link>http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/comment-page-1/#comment-7408</link>
		<dc:creator>Nona Mills</dc:creator>
		<pubDate>Wed, 22 Dec 2010 17:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.yimingliu.com/?p=564#comment-7408</guid>
		<description>I fully agree with autor of this post. I used Seagate for more than 15 years, many drives (small on $86DX PC 40 Mg up to 1TB drive), many of my friends used it too. And it&#039;s one conclusion for this: 8/10 drives were broken due to different reasons over time (overheat, freezing, electronic problem, etc). In the same time we use also a WD HDD, and it&#039;s still working. I&#039;m not prefering a single firm of hdd, but due to lot of year using different drives I can say one: Seagate hdd it&#039;s not good choice for stability. Only WD will last long.</description>
		<content:encoded><![CDATA[<p>I fully agree with autor of this post. I used Seagate for more than 15 years, many drives (small on $86DX PC 40 Mg up to 1TB drive), many of my friends used it too. And it&#8217;s one conclusion for this: 8/10 drives were broken due to different reasons over time (overheat, freezing, electronic problem, etc). In the same time we use also a WD HDD, and it&#8217;s still working. I&#8217;m not prefering a single firm of hdd, but due to lot of year using different drives I can say one: Seagate hdd it&#8217;s not good choice for stability. Only WD will last long.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Briz</title>
		<link>http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/comment-page-1/#comment-6472</link>
		<dc:creator>Briz</dc:creator>
		<pubDate>Thu, 18 Nov 2010 06:25:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.yimingliu.com/?p=564#comment-6472</guid>
		<description>Thanks for posting your problem and solution. I was actually trying to run the Active@ KillDisk from a Boot CD and had the same getFATblock error. The machine I&#039;m wiping the hard drive on is a Dell as well. I went into the BIOS, changed the SATA mode and presto, it worked! I&#039;m now happily on my way to wiping the hard drive! Thanks again for taking the time to share your experience so thoroughly, you saved me a lot of hassle and heartache. Not only that, I also learned to avoid Seagate in the future, you rock man, thanks!</description>
		<content:encoded><![CDATA[<p>Thanks for posting your problem and solution. I was actually trying to run the Active@ KillDisk from a Boot CD and had the same getFATblock error. The machine I&#8217;m wiping the hard drive on is a Dell as well. I went into the BIOS, changed the SATA mode and presto, it worked! I&#8217;m now happily on my way to wiping the hard drive! Thanks again for taking the time to share your experience so thoroughly, you saved me a lot of hassle and heartache. Not only that, I also learned to avoid Seagate in the future, you rock man, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: xippon</title>
		<link>http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/comment-page-1/#comment-4596</link>
		<dc:creator>xippon</dc:creator>
		<pubDate>Sun, 13 Jun 2010 11:07:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.yimingliu.com/?p=564#comment-4596</guid>
		<description>I fully agree with autor of this post. I used Seagate for more than 15 years, many drives (small on $86DX PC 40 Mg up to 1TB drive), many of my friends used it too. And it&#039;s one conclusion for this: 8/10 drives were broken due to different reasons over time (overheat, freezing, electronic problem, etc). In the same time we use also a WD HDD, and it&#039;s still working.

I&#039;m not prefering a single firm of hdd, but due to lot of year using different drives I can say one: Seagate hdd it&#039;s not good choice for stability. Only WD will last long.</description>
		<content:encoded><![CDATA[<p>I fully agree with autor of this post. I used Seagate for more than 15 years, many drives (small on $86DX PC 40 Mg up to 1TB drive), many of my friends used it too. And it&#8217;s one conclusion for this: 8/10 drives were broken due to different reasons over time (overheat, freezing, electronic problem, etc). In the same time we use also a WD HDD, and it&#8217;s still working.</p>
<p>I&#8217;m not prefering a single firm of hdd, but due to lot of year using different drives I can say one: Seagate hdd it&#8217;s not good choice for stability. Only WD will last long.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Askii</title>
		<link>http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/comment-page-1/#comment-3724</link>
		<dc:creator>Askii</dc:creator>
		<pubDate>Tue, 16 Mar 2010 06:44:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.yimingliu.com/?p=564#comment-3724</guid>
		<description>ditto - 820AS firmware upgrade would freeze on loading freeDos, after switching to legacy ata the firmware update went without a hitch. Many thanks!!!</description>
		<content:encoded><![CDATA[<p>ditto &#8211; 820AS firmware upgrade would freeze on loading freeDos, after switching to legacy ata the firmware update went without a hitch. Many thanks!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yiming</title>
		<link>http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/comment-page-1/#comment-3717</link>
		<dc:creator>yiming</dc:creator>
		<pubDate>Sun, 14 Mar 2010 16:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.yimingliu.com/?p=564#comment-3717</guid>
		<description>happy to be of help :)  we&#039;re definitely agreed here.  this kind of guidance should have been part of the install instructions, and Seagate should have been more proactive in repairing the broken hardware/firmware they shipped.</description>
		<content:encoded><![CDATA[<p>happy to be of help <img src='http://blog.yimingliu.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   we&#8217;re definitely agreed here.  this kind of guidance should have been part of the install instructions, and Seagate should have been more proactive in repairing the broken hardware/firmware they shipped.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hubert</title>
		<link>http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/comment-page-1/#comment-3715</link>
		<dc:creator>Hubert</dc:creator>
		<pubDate>Sun, 14 Mar 2010 12:48:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.yimingliu.com/?p=564#comment-3715</guid>
		<description>Many, many thanks !!!
Your AHCI tip solved my problem. Why shouldn&#039;t we find this information on Seagate&#039;s website? They even have the guts to charge you more than $1000 to unbrick their own crap. Seagate? Never again!</description>
		<content:encoded><![CDATA[<p>Many, many thanks !!!<br />
Your AHCI tip solved my problem. Why shouldn&#8217;t we find this information on Seagate&#8217;s website? They even have the guts to charge you more than $1000 to unbrick their own crap. Seagate? Never again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ramadoodan</title>
		<link>http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/comment-page-1/#comment-2051</link>
		<dc:creator>ramadoodan</dc:creator>
		<pubDate>Mon, 09 Nov 2009 12:33:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.yimingliu.com/?p=564#comment-2051</guid>
		<description>I SUFFERED DIFFERETWAY WITH SEAGATE I ONCE SUFFERED IN1990 WITH UNDETUCTED IN BIOS.THE SECOND NOW WITH FIRMWARE PROBLEM OF ST3500620AS BARRACUDA 7200.11. I WILL NO LONGER BUY SEAGATE. ITS A NON STSANDARD THAILAND JUNK.I LOST ALL MY PRECIOUS DATA WHICH IS NOT RETRIEVABLE
RAMADOODAN</description>
		<content:encoded><![CDATA[<p>I SUFFERED DIFFERETWAY WITH SEAGATE I ONCE SUFFERED IN1990 WITH UNDETUCTED IN BIOS.THE SECOND NOW WITH FIRMWARE PROBLEM OF ST3500620AS BARRACUDA 7200.11. I WILL NO LONGER BUY SEAGATE. ITS A NON STSANDARD THAILAND JUNK.I LOST ALL MY PRECIOUS DATA WHICH IS NOT RETRIEVABLE<br />
RAMADOODAN</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Red Leatherman</title>
		<link>http://blog.yimingliu.com/2009/07/08/upgrading-the-seagate-barracuda-720011-to-firmware-sd1a/comment-page-1/#comment-1134</link>
		<dc:creator>Red Leatherman</dc:creator>
		<pubDate>Sun, 30 Aug 2009 16:25:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.yimingliu.com/?p=564#comment-1134</guid>
		<description>About a week ago I had to send my ST31000340AS in for replacement due to total failure. In the past I seem to recall having to describe the failure.
This time the question of what kind of failure I had wasn&#039;t ask in the online form.</description>
		<content:encoded><![CDATA[<p>About a week ago I had to send my ST31000340AS in for replacement due to total failure. In the past I seem to recall having to describe the failure.<br />
This time the question of what kind of failure I had wasn&#8217;t ask in the online form.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

