<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Super Parked &#187; Craig Simms</title>
	<atom:link href="http://www.superparked.com/author/craig-simms/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.superparked.com</link>
	<description>The latest new from around the world!</description>
	<lastBuildDate>Sat, 17 Apr 2010 11:56:48 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Seagate fixes 7200.11 drives&#8211;except when it doesn&#8217;t</title>
		<link>http://www.superparked.com/2009/01/21/seagate-fixes-720011-drives-except-when-it-doesnt/</link>
		<comments>http://www.superparked.com/2009/01/21/seagate-fixes-720011-drives-except-when-it-doesnt/#comments</comments>
		<pubDate>Wed, 21 Jan 2009 17:39:00 +0000</pubDate>
		<dc:creator>Craig Simms</dc:creator>
				<category><![CDATA[Tech]]></category>

		<guid isPermaLink="false">http://news.cnet.com/8301-17938_105-10146909-1.html</guid>
		<description><![CDATA[
                    
                            <p>Seagate on Tuesday released a fix to a bug in its current generation of drives that caused them to become undetectable by a computer. Users have found, however, that the fix breaks 500GB drives--the fix has since been retracted.</p><p> 
A member of Seagate's community forums <a href="http://forums.seagate.com/stx/board/message?board.id=ata_drives&#38;thread.id=3283&#38;view=by_date_ascending&#38;page=1">raised the issue</a> in November, with Seagate taking close to two months to offer a fix.
</p>

<div class="cnet-image-div image-medium float-right" style="200px;"><img class="cnet-image" src="http://i.i.com.com/cnwk.1d/i/bto/20090121/seagate_1.jpg" alt="Seagate logo" width="200" height="150" /></div>

<p> 
The bug affects a significant portion of not only Seagate's <a title="Seagate ups ante to 1.5TB with new Barracuda hard drive -- Thursday, Jul 10, 2008" href="http://news.cnet.com/8301-17938_105-9987407-1.html">Barracuda 7200.11 drives</a>, but Barracuda ES.2 SATA and Maxtor DiamondMax 22 drives. Forums across the Internet have been filled with warnings not to buy drives that feature the SD15 revision of firmware; however, Seagate's own documentation shows that SD16, SD17, SD18, and SD19 are also affected within certain model numbers.
</p><p> 
This is not the first time Seagate has had a firmware issue with the 7200.11 series of drives. The SD04 and SD14 firmware revisions were found to be under-performing because they <a href="http://www.seagate.com/www/en-us/support/downloads/other_downloads/cuda-fw">weren't accessing the full cache of the drives</a>, and were replaced with version AD14 to fix this.
</p><p> 
The new <a href="http://forums.seagate.com/stx/board/message?board.id=ata_drives&#38;thread.id=3283&#38;view=by_date_ascending&#38;page=1">SD1A firmware</a> was meant to be preventative only, but some users have found success updating and reviving already dead drives, according to Seagate's forums.
</p><p> 
Users of Seagate's Barracuda 7200.11 500GB product, however, have found that the update "bricks" their drives--terminology used in the tech industry to mean the unit is dead.
</p><p> 
Seagate has since removed the firmware update, claiming it is "in validation."
</p><p> 
U.S. customers have been offered free data recovery should the firmware bug have resulted in data loss. 
</p><p> 
The affected drives are listed below.
</p>

...
                        
                ]]></description>
		<wfw:commentRss>http://www.superparked.com/2009/01/21/seagate-fixes-720011-drives-except-when-it-doesnt/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

