<?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: My Seagate hard drives are safe now</title>
	<atom:link href="http://stevemaller.com/blog/2009/01/22/my-seagate-hard-drives-are-safe-now/feed/" rel="self" type="application/rss+xml" />
	<link>http://stevemaller.com/blog/2009/01/22/my-seagate-hard-drives-are-safe-now/</link>
	<description>It’s my turn now</description>
	<lastBuildDate>Wed, 13 Jan 2010 00:44:45 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: steve</title>
		<link>http://stevemaller.com/blog/2009/01/22/my-seagate-hard-drives-are-safe-now/comment-page-1/#comment-494</link>
		<dc:creator>steve</dc:creator>
		<pubDate>Wed, 04 Feb 2009 01:00:50 +0000</pubDate>
		<guid isPermaLink="false">http://stevemaller.com/blog/?p=370#comment-494</guid>
		<description>In my experience, you can leave non-affected drives in, and they&#039;re simply skipped over by the updater, as are drives for which the updater doesn&#039;t have the particular firmware that&#039;s required. With respect to the RAID drives, there&#039;s nothing actually written to the drive&#039;s data areas itself, so it shouldn&#039;t matter as long as the drives aren&#039;t connected to a RAID card (meaning they&#039;re directly connected to one of the Mac Pro&#039;s internal SATA ports).</description>
		<content:encoded><![CDATA[<p>In my experience, you can leave non-affected drives in, and they&#8217;re simply skipped over by the updater, as are drives for which the updater doesn&#8217;t have the particular firmware that&#8217;s required. With respect to the RAID drives, there&#8217;s nothing actually written to the drive&#8217;s data areas itself, so it shouldn&#8217;t matter as long as the drives aren&#8217;t connected to a RAID card (meaning they&#8217;re directly connected to one of the Mac Pro&#8217;s internal SATA ports).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray</title>
		<link>http://stevemaller.com/blog/2009/01/22/my-seagate-hard-drives-are-safe-now/comment-page-1/#comment-493</link>
		<dc:creator>Ray</dc:creator>
		<pubDate>Wed, 04 Feb 2009 00:19:29 +0000</pubDate>
		<guid isPermaLink="false">http://stevemaller.com/blog/?p=370#comment-493</guid>
		<description>Thanks for the step-by-step.  Question:  Should I remove my main drive from my Mac before performing the update?  Also, the two Seagate drives in question are configured as a RAID 1 assembly.  Should I do the update on one drive at a time, or leave &#039;em in place and just go for it?</description>
		<content:encoded><![CDATA[<p>Thanks for the step-by-step.  Question:  Should I remove my main drive from my Mac before performing the update?  Also, the two Seagate drives in question are configured as a RAID 1 assembly.  Should I do the update on one drive at a time, or leave &#8216;em in place and just go for it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Brumfield</title>
		<link>http://stevemaller.com/blog/2009/01/22/my-seagate-hard-drives-are-safe-now/comment-page-1/#comment-492</link>
		<dc:creator>Brian Brumfield</dc:creator>
		<pubDate>Mon, 02 Feb 2009 15:03:40 +0000</pubDate>
		<guid isPermaLink="false">http://stevemaller.com/blog/?p=370#comment-492</guid>
		<description>Thanks Steve - a friend sent me a link to this and I had one of these drives in my Pro - I have to check my off-site vault to see if there is another one there. The rest of my 1TB drives are Western Digital&#039;s. One curious thing is that I have a 1.5TB Baracuda 7200.11 drive at firmware level SD17 and Seagate&#039;s serial number validator said that it&#039;s not affected. Here&#039;s to hoping they&#039;re right. The internal drive updated just fine. Thanks again!</description>
		<content:encoded><![CDATA[<p>Thanks Steve &#8211; a friend sent me a link to this and I had one of these drives in my Pro &#8211; I have to check my off-site vault to see if there is another one there. The rest of my 1TB drives are Western Digital&#8217;s. One curious thing is that I have a 1.5TB Baracuda 7200.11 drive at firmware level SD17 and Seagate&#8217;s serial number validator said that it&#8217;s not affected. Here&#8217;s to hoping they&#8217;re right. The internal drive updated just fine. Thanks again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steve</title>
		<link>http://stevemaller.com/blog/2009/01/22/my-seagate-hard-drives-are-safe-now/comment-page-1/#comment-491</link>
		<dc:creator>steve</dc:creator>
		<pubDate>Sun, 01 Feb 2009 21:58:33 +0000</pubDate>
		<guid isPermaLink="false">http://stevemaller.com/blog/?p=370#comment-491</guid>
		<description>Have you checked the Seagate support pages? You can start here: http://www.seagate.com/ww/v/index.jsp?locale=en-US&amp;name=freeagent-downloads&amp;vgnextoid=3723b5b59b7d5110VgnVCM100000f5ee0a0aRCRD</description>
		<content:encoded><![CDATA[<p>Have you checked the Seagate support pages? You can start here: <a href="http://www.seagate.com/ww/v/index.jsp?locale=en-US&#038;name=freeagent-downloads&#038;vgnextoid=3723b5b59b7d5110VgnVCM100000f5ee0a0aRCRD" rel="nofollow">http://www.seagate.com/ww/v/index.jsp?locale=en-US&#038;name=freeagent-downloads&#038;vgnextoid=3723b5b59b7d5110VgnVCM100000f5ee0a0aRCRD</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://stevemaller.com/blog/2009/01/22/my-seagate-hard-drives-are-safe-now/comment-page-1/#comment-490</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Sun, 01 Feb 2009 20:09:23 +0000</pubDate>
		<guid isPermaLink="false">http://stevemaller.com/blog/?p=370#comment-490</guid>
		<description>Can someone point me to some definitive text that confirms or denies whether my Seagate FreeAgent external hard disk is effected by this firmware bug? 

AND, if it IS effected, I&#039;d sure appreciate a pointer to instructions on how I can fix it ... or at least follow along with the efforts to get a fix.</description>
		<content:encoded><![CDATA[<p>Can someone point me to some definitive text that confirms or denies whether my Seagate FreeAgent external hard disk is effected by this firmware bug? </p>
<p>AND, if it IS effected, I&#8217;d sure appreciate a pointer to instructions on how I can fix it &#8230; or at least follow along with the efforts to get a fix.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ExtraBITS for 26-Jan-09 &#124; Web News Directory</title>
		<link>http://stevemaller.com/blog/2009/01/22/my-seagate-hard-drives-are-safe-now/comment-page-1/#comment-488</link>
		<dc:creator>ExtraBITS for 26-Jan-09 &#124; Web News Directory</dc:creator>
		<pubDate>Wed, 28 Jan 2009 00:40:17 +0000</pubDate>
		<guid isPermaLink="false">http://stevemaller.com/blog/?p=370#comment-488</guid>
		<description>[...] Fix for Buggy Seagate Firmware on Intel-based Macs &#8212; Although Seagate has yet to respond to our inquiries about how Mac users can update buggy firmware in a wide selection of buggy Seagate drives, Steve Maller reports that Seagate tech support walked him through building a CD that booted his Mac Pro into FreeDOS, after which he could run the firmware updater. PowerPC-based Macs and drives in external cases are still out in the cold. (Posted 2009-01-26) [...]</description>
		<content:encoded><![CDATA[<p>[...] Fix for Buggy Seagate Firmware on Intel-based Macs &#8212; Although Seagate has yet to respond to our inquiries about how Mac users can update buggy firmware in a wide selection of buggy Seagate drives, Steve Maller reports that Seagate tech support walked him through building a CD that booted his Mac Pro into FreeDOS, after which he could run the firmware updater. PowerPC-based Macs and drives in external cases are still out in the cold. (Posted 2009-01-26) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steve</title>
		<link>http://stevemaller.com/blog/2009/01/22/my-seagate-hard-drives-are-safe-now/comment-page-1/#comment-487</link>
		<dc:creator>steve</dc:creator>
		<pubDate>Tue, 27 Jan 2009 23:09:15 +0000</pubDate>
		<guid isPermaLink="false">http://stevemaller.com/blog/?p=370#comment-487</guid>
		<description>Well done, Mr. Fearless! :-)</description>
		<content:encoded><![CDATA[<p>Well done, Mr. Fearless! <img src='http://stevemaller.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mrfearless47</title>
		<link>http://stevemaller.com/blog/2009/01/22/my-seagate-hard-drives-are-safe-now/comment-page-1/#comment-486</link>
		<dc:creator>mrfearless47</dc:creator>
		<pubDate>Tue, 27 Jan 2009 23:03:32 +0000</pubDate>
		<guid isPermaLink="false">http://stevemaller.com/blog/?p=370#comment-486</guid>
		<description>I had four Seagate 7200.11 1TB drives with the old firmware.  Seagate had already replaced two of them under warranty but sent the same old firmware.  After reading your piece, I was able to build a CD, boot to it and update the firmware on all four drives.  I now feel more secure now that the firmware is upgraded to the later, presumably correct, version.   No problem whatsoever booting into FreeDOS under the current (early 2008, Mac Pro).</description>
		<content:encoded><![CDATA[<p>I had four Seagate 7200.11 1TB drives with the old firmware.  Seagate had already replaced two of them under warranty but sent the same old firmware.  After reading your piece, I was able to build a CD, boot to it and update the firmware on all four drives.  I now feel more secure now that the firmware is upgraded to the later, presumably correct, version.   No problem whatsoever booting into FreeDOS under the current (early 2008, Mac Pro).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CVBruce</title>
		<link>http://stevemaller.com/blog/2009/01/22/my-seagate-hard-drives-are-safe-now/comment-page-1/#comment-485</link>
		<dc:creator>CVBruce</dc:creator>
		<pubDate>Tue, 27 Jan 2009 02:49:49 +0000</pubDate>
		<guid isPermaLink="false">http://stevemaller.com/blog/?p=370#comment-485</guid>
		<description>Steve,

The point that I was trying to make about the Mac Mini, is that I don&#039;t physically have an internal place to mount the drive so that the firmware can be updated.  I don&#039;t see going out and buying a Mac Pro, or a Windows box, just so I can update the firmware as a practical solution to the problem.  

As far as I&#039;m concerned Seagate needs to step up and figure out a solution that will allow the drive to be updated in an external enclosure.  Or they can ship me a new drive.

CVBruce</description>
		<content:encoded><![CDATA[<p>Steve,</p>
<p>The point that I was trying to make about the Mac Mini, is that I don&#8217;t physically have an internal place to mount the drive so that the firmware can be updated.  I don&#8217;t see going out and buying a Mac Pro, or a Windows box, just so I can update the firmware as a practical solution to the problem.  </p>
<p>As far as I&#8217;m concerned Seagate needs to step up and figure out a solution that will allow the drive to be updated in an external enclosure.  Or they can ship me a new drive.</p>
<p>CVBruce</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://stevemaller.com/blog/2009/01/22/my-seagate-hard-drives-are-safe-now/comment-page-1/#comment-484</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Tue, 27 Jan 2009 02:15:57 +0000</pubDate>
		<guid isPermaLink="false">http://stevemaller.com/blog/?p=370#comment-484</guid>
		<description>After reading a success story from a reader on Macintouch who successfully updated an affected drive using a MacBook Pro with external eSata enclosure, I did the same today. We have different enclosures and ExpressCard adapter brands (Vantec/Griffin vs. Seritek/Seritek).

You can read his account there now and my followup should appear tomorrow:

http://www.macintouch.com/readerreports/harddrives/index.html#d26jan2009</description>
		<content:encoded><![CDATA[<p>After reading a success story from a reader on Macintouch who successfully updated an affected drive using a MacBook Pro with external eSata enclosure, I did the same today. We have different enclosures and ExpressCard adapter brands (Vantec/Griffin vs. Seritek/Seritek).</p>
<p>You can read his account there now and my followup should appear tomorrow:</p>
<p><a href="http://www.macintouch.com/readerreports/harddrives/index.html#d26jan2009" rel="nofollow">http://www.macintouch.com/readerreports/harddrives/index.html#d26jan2009</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
