<?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: Using generic drives in a Netapp FAS250</title>
	<atom:link href="http://ramblings.narrabilis.com/wp/using-generic-drives-in-a-netapp-fas250/feed/" rel="self" type="application/rss+xml" />
	<link>http://ramblings.narrabilis.com/wp/using-generic-drives-in-a-netapp-fas250/</link>
	<description>Scripts, settings, and fixes...</description>
	<lastBuildDate>Fri, 23 Jul 2010 17:37:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: vardomskiy</title>
		<link>http://ramblings.narrabilis.com/wp/using-generic-drives-in-a-netapp-fas250/comment-page-1/#comment-31236</link>
		<dc:creator>vardomskiy</dc:creator>
		<pubDate>Tue, 25 May 2010 19:05:34 +0000</pubDate>
		<guid isPermaLink="false">http://ramblings.narrabilis.com/wp/?p=141#comment-31236</guid>
		<description>I had my post on flashing NetApp firmware onto Seagate disks suspended on livejournal.com alledgedly due to a DMCA takedown notice.  So just a heads up.</description>
		<content:encoded><![CDATA[<p>I had my post on flashing NetApp firmware onto Seagate disks suspended on livejournal.com alledgedly due to a DMCA takedown notice.  So just a heads up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gasve</title>
		<link>http://ramblings.narrabilis.com/wp/using-generic-drives-in-a-netapp-fas250/comment-page-1/#comment-31057</link>
		<dc:creator>Gasve</dc:creator>
		<pubDate>Thu, 20 May 2010 14:52:14 +0000</pubDate>
		<guid isPermaLink="false">http://ramblings.narrabilis.com/wp/?p=141#comment-31057</guid>
		<description>Hi:
       I already have ST31000340NS drives with SN16 Fw and the ISO images don&#039;t work for me, I have tried using the ISO for SN16 making all the changes recommended but with no luck it tell me something about the model of the disk is not the the right.
      Some has used smartmon-ux to do the fw download?

Thanks in Advance 

Gasve</description>
		<content:encoded><![CDATA[<p>Hi:<br />
       I already have ST31000340NS drives with SN16 Fw and the ISO images don&#8217;t work for me, I have tried using the ISO for SN16 making all the changes recommended but with no luck it tell me something about the model of the disk is not the the right.<br />
      Some has used smartmon-ux to do the fw download?</p>
<p>Thanks in Advance </p>
<p>Gasve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Old Moose</title>
		<link>http://ramblings.narrabilis.com/wp/using-generic-drives-in-a-netapp-fas250/comment-page-1/#comment-22587</link>
		<dc:creator>Old Moose</dc:creator>
		<pubDate>Wed, 02 Sep 2009 08:12:05 +0000</pubDate>
		<guid isPermaLink="false">http://ramblings.narrabilis.com/wp/?p=141#comment-22587</guid>
		<description>Get a ST31000340NS 1TB Barracuda. This drive had a Firmware-Bug so Seagate and NetApp had to release an Firmware-Update. X269_SMOOS01TSSX.NA01.LOD is the NetApp-Version for this drive. Now goto http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?&amp;DocId=207963&amp;NewLang=en and get SN06 ISO-Image. From this image extract the eltorito-Bootpart (Linux: geteltorito). In this Diskimage is a zip-file. Extract it, copy the NetApp-Firmware into it and modify the batchfile flash.bat. Remove the old firmware and the .txs-File to save some space.
.
.
.
set options=-s -x -b -v -a 20
.
.
:SEAFLASH2
rem set model=ST31000340NS
%exe% -m %family% -f X269_SMOOS01TSSX.NA01.LOD -i %model2% %options%
if errorlevel 2 goto WRONGMODEL2
if errorlevel 1 goto ERROR
goto DONE
.
.
.

zip it again, put it into the diskimage and create a bootfloppy from it (dd). Attach the harddisk to a SATA-Controller, boot the PC from the floppy and flash the disk. After that you have a NetApp-Disk with Bad label...how to solve this is mentioned in the text above.</description>
		<content:encoded><![CDATA[<p>Get a ST31000340NS 1TB Barracuda. This drive had a Firmware-Bug so Seagate and NetApp had to release an Firmware-Update. X269_SMOOS01TSSX.NA01.LOD is the NetApp-Version for this drive. Now goto <a href="http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?&amp;DocId=207963&amp;NewLang=en" rel="nofollow">http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?&amp;DocId=207963&amp;NewLang=en</a> and get SN06 ISO-Image. From this image extract the eltorito-Bootpart (Linux: geteltorito). In this Diskimage is a zip-file. Extract it, copy the NetApp-Firmware into it and modify the batchfile flash.bat. Remove the old firmware and the .txs-File to save some space.<br />
.<br />
.<br />
.<br />
set options=-s -x -b -v -a 20<br />
.<br />
.<br />
:SEAFLASH2<br />
rem set model=ST31000340NS<br />
%exe% -m %family% -f X269_SMOOS01TSSX.NA01.LOD -i %model2% %options%<br />
if errorlevel 2 goto WRONGMODEL2<br />
if errorlevel 1 goto ERROR<br />
goto DONE<br />
.<br />
.<br />
.</p>
<p>zip it again, put it into the diskimage and create a bootfloppy from it (dd). Attach the harddisk to a SATA-Controller, boot the PC from the floppy and flash the disk. After that you have a NetApp-Disk with Bad label&#8230;how to solve this is mentioned in the text above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Old Moose</title>
		<link>http://ramblings.narrabilis.com/wp/using-generic-drives-in-a-netapp-fas250/comment-page-1/#comment-22586</link>
		<dc:creator>Old Moose</dc:creator>
		<pubDate>Wed, 02 Sep 2009 08:07:53 +0000</pubDate>
		<guid isPermaLink="false">http://ramblings.narrabilis.com/wp/?p=141#comment-22586</guid>
		<description>Get a ST31000340NS 1TB Barracuda. This drive had a Firmware-Bug so Seagate and NetApp had to release an Firmware-Update. X269_SMOOS01TSSX.NA01.LOD is the NetApp-Version for this drive. Now goto http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?&amp;DocId=207963&amp;NewLang=en and get SN06 ISO-Image. From this image extract the eltorito-Bootpart (Linux: geteltorito). In this Diskimage is a zip-file. Extract it, copy the NetApp-Firmware into it and modify the batchfile flash.bat. Remove the old firmware and the .txs-File to save some space.
.
.
.
:SEAFLASH2
rem set model=ST31000340NS
%exe% -m %family% -f X269_SMOOS01TSSX.NA01.LOD -i %model2% %options%
if errorlevel 2 goto WRONGMODEL2
if errorlevel 1 goto ERROR
goto DONE
.
.
.

zip it again, put it into the diskimage and create a bootfloppy from it (dd). Attach the harddisk to a SATA-Controller, boot the PC from the floppy and flash the disk. After that you have a NetApp-Disk with Bad label...how to solve this is mentioned in the text above.</description>
		<content:encoded><![CDATA[<p>Get a ST31000340NS 1TB Barracuda. This drive had a Firmware-Bug so Seagate and NetApp had to release an Firmware-Update. X269_SMOOS01TSSX.NA01.LOD is the NetApp-Version for this drive. Now goto <a href="http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?&amp;DocId=207963&amp;NewLang=en" rel="nofollow">http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?&amp;DocId=207963&amp;NewLang=en</a> and get SN06 ISO-Image. From this image extract the eltorito-Bootpart (Linux: geteltorito). In this Diskimage is a zip-file. Extract it, copy the NetApp-Firmware into it and modify the batchfile flash.bat. Remove the old firmware and the .txs-File to save some space.<br />
.<br />
.<br />
.<br />
:SEAFLASH2<br />
rem set model=ST31000340NS<br />
%exe% -m %family% -f X269_SMOOS01TSSX.NA01.LOD -i %model2% %options%<br />
if errorlevel 2 goto WRONGMODEL2<br />
if errorlevel 1 goto ERROR<br />
goto DONE<br />
.<br />
.<br />
.</p>
<p>zip it again, put it into the diskimage and create a bootfloppy from it (dd). Attach the harddisk to a SATA-Controller, boot the PC from the floppy and flash the disk. After that you have a NetApp-Disk with Bad label&#8230;how to solve this is mentioned in the text above.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dana Mandell</title>
		<link>http://ramblings.narrabilis.com/wp/using-generic-drives-in-a-netapp-fas250/comment-page-1/#comment-20543</link>
		<dc:creator>Dana Mandell</dc:creator>
		<pubDate>Thu, 25 Jun 2009 20:45:09 +0000</pubDate>
		<guid isPermaLink="false">http://ramblings.narrabilis.com/wp/?p=141#comment-20543</guid>
		<description>Nice work!
This all looks good, and I have been successful at &quot;flashing&quot; IDE and FC drive for use in NetApp, but has anyone tried SATA drives? Something must be very different since the blocks size is fixed at 512 bytes on SATA drives and cannot be reformatted to 520. (I noticed that even the NetApp SATA drives show up as having 512 byte blocks.)</description>
		<content:encoded><![CDATA[<p>Nice work!<br />
This all looks good, and I have been successful at &#8220;flashing&#8221; IDE and FC drive for use in NetApp, but has anyone tried SATA drives? Something must be very different since the blocks size is fixed at 512 bytes on SATA drives and cannot be reformatted to 520. (I noticed that even the NetApp SATA drives show up as having 512 byte blocks.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uphill</title>
		<link>http://ramblings.narrabilis.com/wp/using-generic-drives-in-a-netapp-fas250/comment-page-1/#comment-18993</link>
		<dc:creator>uphill</dc:creator>
		<pubDate>Tue, 26 May 2009 15:19:03 +0000</pubDate>
		<guid isPermaLink="false">http://ramblings.narrabilis.com/wp/?p=141#comment-18993</guid>
		<description>I spent more than half a day :-)  Thanks, your work was indeed very useful.</description>
		<content:encoded><![CDATA[<p>I spent more than half a day :-)  Thanks, your work was indeed very useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vardomskiy</title>
		<link>http://ramblings.narrabilis.com/wp/using-generic-drives-in-a-netapp-fas250/comment-page-1/#comment-18992</link>
		<dc:creator>vardomskiy</dc:creator>
		<pubDate>Tue, 26 May 2009 15:02:18 +0000</pubDate>
		<guid isPermaLink="false">http://ramblings.narrabilis.com/wp/?p=141#comment-18992</guid>
		<description>Hey, cool. 

Since I was basically working on a shelf full of new drives, I didn&#039;t think of copying the disk over in maintenance mode.  I guess that&#039;s the best option if you only work on a single drive. 

After re-reading my instructions, I realized that I forgot to mention that I had a spare ESH2 that I was able to pop into the DS14mk2 instead of FAS250 module.   So in essence I was turning an FAS250 into a dumb FC shelf for the time.  But if you have some other means of attaching FC disk to a Linux system and uploading firmware/formatting the disk  a 3rd party disk enclosure), you of course could use it for the Linux stage. 

I also downplay the importance of seatools during the Linux stage, since the system I use was IDE only, and dmesg was making very clear what the device ids of the drives were.  st is very nice in terms of information it provides, but I was very frustrated about the fact that it was segfaulting for me during the firmware update step. 

Lastly, it might make sense to issue &#039;disk zero spares&#039; command if you plan to use that disk as a spare.  

Any way, glad that half a day of my research was useful to someone.</description>
		<content:encoded><![CDATA[<p>Hey, cool. </p>
<p>Since I was basically working on a shelf full of new drives, I didn&#8217;t think of copying the disk over in maintenance mode.  I guess that&#8217;s the best option if you only work on a single drive. </p>
<p>After re-reading my instructions, I realized that I forgot to mention that I had a spare ESH2 that I was able to pop into the DS14mk2 instead of FAS250 module.   So in essence I was turning an FAS250 into a dumb FC shelf for the time.  But if you have some other means of attaching FC disk to a Linux system and uploading firmware/formatting the disk  a 3rd party disk enclosure), you of course could use it for the Linux stage. </p>
<p>I also downplay the importance of seatools during the Linux stage, since the system I use was IDE only, and dmesg was making very clear what the device ids of the drives were.  st is very nice in terms of information it provides, but I was very frustrated about the fact that it was segfaulting for me during the firmware update step. </p>
<p>Lastly, it might make sense to issue &#8216;disk zero spares&#8217; command if you plan to use that disk as a spare.  </p>
<p>Any way, glad that half a day of my research was useful to someone.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
