<?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: ReadyNAS NV+, Seagate Firmware Update Take 1</title>
	<atom:link href="http://whalespine.org/2009/02/15/readynas-nv-seagate-firmware-update-take-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://whalespine.org/2009/02/15/readynas-nv-seagate-firmware-update-take-1/</link>
	<description>what now?</description>
	<lastBuildDate>Sun, 13 Jun 2010 19:55:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tim</title>
		<link>http://whalespine.org/2009/02/15/readynas-nv-seagate-firmware-update-take-1/comment-page-1/#comment-1108</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Fri, 24 Apr 2009 03:34:26 +0000</pubDate>
		<guid isPermaLink="false">http://whalespine.org/?p=460#comment-1108</guid>
		<description>Thanks for the update.  As I posted &lt;a href=&quot;http://whalespine.org/2009/03/25/readynas-nv-seagate-firmware&quot; rel=&quot;nofollow&quot;&gt;last month&lt;/a&gt;, I bought the adapter you suggested in your original comment and the drives were successfully updated.</description>
		<content:encoded><![CDATA[<p>Thanks for the update.  As I posted <a href="http://whalespine.org/2009/03/25/readynas-nv-seagate-firmware" rel="nofollow">last month</a>, I bought the adapter you suggested in your original comment and the drives were successfully updated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scostall</title>
		<link>http://whalespine.org/2009/02/15/readynas-nv-seagate-firmware-update-take-1/comment-page-1/#comment-1107</link>
		<dc:creator>scostall</dc:creator>
		<pubDate>Fri, 24 Apr 2009 03:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://whalespine.org/?p=460#comment-1107</guid>
		<description>An update - mostly because I hate people who don&#039;t post updates.  ;-)

I successfully upgraded my RAID6 array without any difficulties.  With the ST31000340AS drives, and the 3ware 9650SE-16ML RAID controller card, the drive firmware update did *not* cause the drive to &quot;forget&quot; it was part of the array.  I could theoretically have upgraded all the drives at once and it would have been OK.

I did not do this, however, because I didn&#039;t have to.  What I did do was install four upgraded drives as hot spares first.  I then removed the live drives one at a time for upgrade.  I also verified the array after every drive upgrade, just to be sure.

Still, the process did work well - if a little time-consuming, at one drive per day.

Oddly enough, however, one of my upgraded drives failed shortly afterwards - and not due to a power cycle, either.  Strange, as this array was running for over 450 days straight without any problems, and power cycling the array to R&amp;R drives did not cause any problems at the time.  Perhaps the problem drive was simply due to give out?  

I will probably be testing the Seagate warranty program as a result of this, as none of these drives are anywhere near 5 years old yet.  One of my hot spares stepped in, and the array was rebuilt before I even knew there was a problem, so no worries on that point.

Hope this helps someone.</description>
		<content:encoded><![CDATA[<p>An update &#8211; mostly because I hate people who don&#8217;t post updates.  <img src='http://whalespine.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p>I successfully upgraded my RAID6 array without any difficulties.  With the ST31000340AS drives, and the 3ware 9650SE-16ML RAID controller card, the drive firmware update did *not* cause the drive to &#8220;forget&#8221; it was part of the array.  I could theoretically have upgraded all the drives at once and it would have been OK.</p>
<p>I did not do this, however, because I didn&#8217;t have to.  What I did do was install four upgraded drives as hot spares first.  I then removed the live drives one at a time for upgrade.  I also verified the array after every drive upgrade, just to be sure.</p>
<p>Still, the process did work well &#8211; if a little time-consuming, at one drive per day.</p>
<p>Oddly enough, however, one of my upgraded drives failed shortly afterwards &#8211; and not due to a power cycle, either.  Strange, as this array was running for over 450 days straight without any problems, and power cycling the array to R&amp;R drives did not cause any problems at the time.  Perhaps the problem drive was simply due to give out?  </p>
<p>I will probably be testing the Seagate warranty program as a result of this, as none of these drives are anywhere near 5 years old yet.  One of my hot spares stepped in, and the array was rebuilt before I even knew there was a problem, so no worries on that point.</p>
<p>Hope this helps someone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://whalespine.org/2009/02/15/readynas-nv-seagate-firmware-update-take-1/comment-page-1/#comment-411</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Fri, 27 Mar 2009 07:07:57 +0000</pubDate>
		<guid isPermaLink="false">http://whalespine.org/?p=460#comment-411</guid>
		<description>Contact Seagate support.  http://www.seagate.com/www/en-us/support/   If this is due to the firmware issue they should help you recover your data.</description>
		<content:encoded><![CDATA[<p>Contact Seagate support.  <a href="http://www.seagate.com/www/en-us/support/" rel="nofollow">http://www.seagate.com/www/en-us/support/</a>   If this is due to the firmware issue they should help you recover your data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dvid Stevenson</title>
		<link>http://whalespine.org/2009/02/15/readynas-nv-seagate-firmware-update-take-1/comment-page-1/#comment-408</link>
		<dc:creator>Dvid Stevenson</dc:creator>
		<pubDate>Fri, 27 Mar 2009 02:56:19 +0000</pubDate>
		<guid isPermaLink="false">http://whalespine.org/?p=460#comment-408</guid>
		<description>My seagate external drive will not work after short time. All my photos were stored the re now what do I do?</description>
		<content:encoded><![CDATA[<p>My seagate external drive will not work after short time. All my photos were stored the re now what do I do?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://whalespine.org/2009/02/15/readynas-nv-seagate-firmware-update-take-1/comment-page-1/#comment-290</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Sun, 08 Mar 2009 01:05:34 +0000</pubDate>
		<guid isPermaLink="false">http://whalespine.org/?p=460#comment-290</guid>
		<description>Nope, not too late to help me.  I haven&#039;t had time to research a new solution, but this sounds like a good option.  &lt;a href=&quot;http://memoryexpress.com&quot; rel=&quot;nofollow&quot;&gt;Memory Express&lt;/a&gt; carries this item (&lt;a href=&quot;http://www.memoryexpress.com/Products/PID-MX21483(ME).aspx&quot; rel=&quot;nofollow&quot;&gt;link&lt;/a&gt;) for those of you in Winnipeg, Calgary or Edmonton.  

Good advice re: flashing RAID drives one at a time.  I was planning on doing it like that for sure.

Thanks for the help.</description>
		<content:encoded><![CDATA[<p>Nope, not too late to help me.  I haven&#8217;t had time to research a new solution, but this sounds like a good option.  <a href="http://memoryexpress.com" rel="nofollow">Memory Express</a> carries this item (<a href="http://www.memoryexpress.com/Products/PID-MX21483(ME).aspx" rel="nofollow">link</a>) for those of you in Winnipeg, Calgary or Edmonton.  </p>
<p>Good advice re: flashing RAID drives one at a time.  I was planning on doing it like that for sure.</p>
<p>Thanks for the help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scostall</title>
		<link>http://whalespine.org/2009/02/15/readynas-nv-seagate-firmware-update-take-1/comment-page-1/#comment-289</link>
		<dc:creator>scostall</dc:creator>
		<pubDate>Sun, 08 Mar 2009 00:38:38 +0000</pubDate>
		<guid isPermaLink="false">http://whalespine.org/?p=460#comment-289</guid>
		<description>This may be too late to help you, although it may help someone else out there.

I had similar problems to you, in that I had no PC with a SATA controller available.  I have lots of PCs, but most are in use.  The one spare unit I had didn&#039;t have SATA, and the Seagate firmware update utility refused to recognize my ST31000340AS drive using the PCI SATA adapter I had available.

After some debate, I went to the local computer shop and bought a &quot;generic&quot; plug-in SATA to IDE adapter.  It&#039;s a small circuit board the plugs directly into the SATA drive and provides an IDE header, which allowed me to plug the SATA drive into the mainboard IDE controller.

Believe it or not, it actually worked.  The firmware utility recognized the drive and (as far as I can tell) the firmware update worked fine.

This is good news for me, as I have no less than ten of these drives - six running inside a RAID 6 server, and four loose drives that were due to be installed into that same server (for a total of 8 Tb).  Now, at least, I can upgrade the drives, even though I may have to wait 24 hours or so for each rebuild of the array.

Just a word of warning: if you are running these drives in a RAID array, do not re-flash them all at once!  There is a good chance that reflashing the drive will &quot;disconnect&quot; it (so to speak) from the array.  If you do them all at once, you may have just destroyed your RAID array logical organization - and, consequently, all the data on it.  If your array is virgin, this is OK, but if not you are best advised to upgrade the drives one at a time, and let the array re-build with the new unit before upgrading the next unit.

Specifications for the adapter I used can be found at:

http://www.startech.com/item/IDE2SAT-IDE-to-SATA-Drive-Mounted-Adapter.aspx

Hope this helps,
S.</description>
		<content:encoded><![CDATA[<p>This may be too late to help you, although it may help someone else out there.</p>
<p>I had similar problems to you, in that I had no PC with a SATA controller available.  I have lots of PCs, but most are in use.  The one spare unit I had didn&#8217;t have SATA, and the Seagate firmware update utility refused to recognize my ST31000340AS drive using the PCI SATA adapter I had available.</p>
<p>After some debate, I went to the local computer shop and bought a &#8220;generic&#8221; plug-in SATA to IDE adapter.  It&#8217;s a small circuit board the plugs directly into the SATA drive and provides an IDE header, which allowed me to plug the SATA drive into the mainboard IDE controller.</p>
<p>Believe it or not, it actually worked.  The firmware utility recognized the drive and (as far as I can tell) the firmware update worked fine.</p>
<p>This is good news for me, as I have no less than ten of these drives &#8211; six running inside a RAID 6 server, and four loose drives that were due to be installed into that same server (for a total of 8 Tb).  Now, at least, I can upgrade the drives, even though I may have to wait 24 hours or so for each rebuild of the array.</p>
<p>Just a word of warning: if you are running these drives in a RAID array, do not re-flash them all at once!  There is a good chance that reflashing the drive will &#8220;disconnect&#8221; it (so to speak) from the array.  If you do them all at once, you may have just destroyed your RAID array logical organization &#8211; and, consequently, all the data on it.  If your array is virgin, this is OK, but if not you are best advised to upgrade the drives one at a time, and let the array re-build with the new unit before upgrading the next unit.</p>
<p>Specifications for the adapter I used can be found at:</p>
<p><a href="http://www.startech.com/item/IDE2SAT-IDE-to-SATA-Drive-Mounted-Adapter.aspx" rel="nofollow">http://www.startech.com/item/IDE2SAT-IDE-to-SATA-Drive-Mounted-Adapter.aspx</a></p>
<p>Hope this helps,<br />
S.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

