<?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: RAID gets Revisited (TLER and the WDTLER utility)</title>
	<atom:link href="http://blog.agdunn.net/?feed=rss2&#038;p=208" rel="self" type="application/rss+xml" />
	<link>http://blog.agdunn.net/?p=208</link>
	<description>return { true }</description>
	<lastBuildDate>Tue, 13 Jul 2010 07:11:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1-alpha</generator>
	<item>
		<title>By: Storrgie</title>
		<link>http://blog.agdunn.net/?p=208&#038;cpage=1#comment-962</link>
		<dc:creator>Storrgie</dc:creator>
		<pubDate>Thu, 04 Mar 2010 21:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agdunn.net/?p=208#comment-962</guid>
		<description>I am not sure, but WD never responded to my emails from my personal or professional addresses. I will no longer be purchasing their drives. This is an example of closing up functionality, forcing users to pay more for something that exists in their lower level functioning drives.</description>
		<content:encoded><![CDATA[<p>I am not sure, but WD never responded to my emails from my personal or professional addresses. I will no longer be purchasing their drives. This is an example of closing up functionality, forcing users to pay more for something that exists in their lower level functioning drives.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pk442</title>
		<link>http://blog.agdunn.net/?p=208&#038;cpage=1#comment-954</link>
		<dc:creator>pk442</dc:creator>
		<pubDate>Wed, 10 Feb 2010 06:06:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agdunn.net/?p=208#comment-954</guid>
		<description>I purchase several of these at Microcenter 3 weeks ago - still in the box.  I was planning on using them in a new build that I&#039;m about to start.  Is there any way to tell via serial number/model number on the box  if I have the ones with or without the TLER lockout on them?
Mine are the 1TB WD Caviar Black drives model #WD10000LSRTL.
Thanks - PK</description>
		<content:encoded><![CDATA[<p>I purchase several of these at Microcenter 3 weeks ago &#8211; still in the box.  I was planning on using them in a new build that I&#8217;m about to start.  Is there any way to tell via serial number/model number on the box  if I have the ones with or without the TLER lockout on them?<br />
Mine are the 1TB WD Caviar Black drives model #WD10000LSRTL.<br />
Thanks &#8211; PK</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles</title>
		<link>http://blog.agdunn.net/?p=208&#038;cpage=1#comment-953</link>
		<dc:creator>Charles</dc:creator>
		<pubDate>Sun, 07 Feb 2010 00:34:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agdunn.net/?p=208#comment-953</guid>
		<description>It is unacceotable that WD has decides to remove TDLER as a feature on these drives--RAID is raoidly becoming common on systems due to the low drive prices, and thus it would make it far more useful if manufacturers provided firmware support for TDLER or otherwise made their drives configurable for use in RAID.

It is becoming common for people to start with a single drive with the intention of later converting to RAID--this is now made more difficult scince it will require builders to determine if this is going to happen before building each system--and removes the ability for the owner to change their mind later and change to RAID.

Worse, by removing an existing feature from a current model, WD has opened a rats nest of trouble for technicians who want to go to RAID, as they must now check the existing drive.

Given that WD warranties the drives for 5 years (and many will exceed that lifetime, WD has created a problem needlessly which will be with us for at least a decade.

Perhaps if enough people complain they will reverse this annoying decision?</description>
		<content:encoded><![CDATA[<p>It is unacceotable that WD has decides to remove TDLER as a feature on these drives&#8211;RAID is raoidly becoming common on systems due to the low drive prices, and thus it would make it far more useful if manufacturers provided firmware support for TDLER or otherwise made their drives configurable for use in RAID.</p>
<p>It is becoming common for people to start with a single drive with the intention of later converting to RAID&#8211;this is now made more difficult scince it will require builders to determine if this is going to happen before building each system&#8211;and removes the ability for the owner to change their mind later and change to RAID.</p>
<p>Worse, by removing an existing feature from a current model, WD has opened a rats nest of trouble for technicians who want to go to RAID, as they must now check the existing drive.</p>
<p>Given that WD warranties the drives for 5 years (and many will exceed that lifetime, WD has created a problem needlessly which will be with us for at least a decade.</p>
<p>Perhaps if enough people complain they will reverse this annoying decision?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrique</title>
		<link>http://blog.agdunn.net/?p=208&#038;cpage=1#comment-950</link>
		<dc:creator>Henrique</dc:creator>
		<pubDate>Sun, 24 Jan 2010 02:40:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agdunn.net/?p=208#comment-950</guid>
		<description>Warning: the newer versions of the WD1001FALS have TLER permanently locked to the disabled state.

If the extended device timeout doesn&#039;t solve the issue, this makes these devices completely useless for RAID.  Also, you would get one of the TLER-less devices if one of your older ones with TLER support ever need a replacement under warranty...

So, the real golden question is: does increasing the device timeout fix these drivers absurd command timeout delays?</description>
		<content:encoded><![CDATA[<p>Warning: the newer versions of the WD1001FALS have TLER permanently locked to the disabled state.</p>
<p>If the extended device timeout doesn&#8217;t solve the issue, this makes these devices completely useless for RAID.  Also, you would get one of the TLER-less devices if one of your older ones with TLER support ever need a replacement under warranty&#8230;</p>
<p>So, the real golden question is: does increasing the device timeout fix these drivers absurd command timeout delays?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Caviar Blacks RAID issues? - Page 2 - Overclock.net - Overclocking.net</title>
		<link>http://blog.agdunn.net/?p=208&#038;cpage=1#comment-933</link>
		<dc:creator>Caviar Blacks RAID issues? - Page 2 - Overclock.net - Overclocking.net</dc:creator>
		<pubDate>Mon, 21 Dec 2009 15:44:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agdunn.net/?p=208#comment-933</guid>
		<description>[...] other things to be able to use RAID properly.   Check out my friend&#039;s blog where he talks about it. http://blog.agdunn.net/?p=208    Make sure to look at the Wikipedia TLER link......  [...]</description>
		<content:encoded><![CDATA[<p>[...] other things to be able to use RAID properly.   Check out my friend&#39;s blog where he talks about it. <a href="http://blog.agdunn.net/?p=208" rel="nofollow">http://blog.agdunn.net/?p=208</a>    Make sure to look at the Wikipedia TLER link&#8230;&#8230;  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Storrgie</title>
		<link>http://blog.agdunn.net/?p=208&#038;cpage=1#comment-931</link>
		<dc:creator>Storrgie</dc:creator>
		<pubDate>Mon, 21 Dec 2009 13:31:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agdunn.net/?p=208#comment-931</guid>
		<description>It isnt a patch that will effect you at the OS Level. It is a setting in the firmware to my knowledge. This will make the devices wait for the controller to resolve an issue instead of trying to resolve it themselves. 

When the drives try to resolve an i/o issue, frequently the controller will mark them as unresponsive/failed. TLER is a setting to make the drives wait for controller resolution.</description>
		<content:encoded><![CDATA[<p>It isnt a patch that will effect you at the OS Level. It is a setting in the firmware to my knowledge. This will make the devices wait for the controller to resolve an issue instead of trying to resolve it themselves. </p>
<p>When the drives try to resolve an i/o issue, frequently the controller will mark them as unresponsive/failed. TLER is a setting to make the drives wait for controller resolution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: QReality</title>
		<link>http://blog.agdunn.net/?p=208&#038;cpage=1#comment-925</link>
		<dc:creator>QReality</dc:creator>
		<pubDate>Sun, 20 Dec 2009 22:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agdunn.net/?p=208#comment-925</guid>
		<description>Hi,

I&#039;m wondering how to apply this TLER patch to drives already in a RAID configuration using ICH10R. Would I have to basically destroy and rebuild the RAID to do this? (Urk...!)</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I&#8217;m wondering how to apply this TLER patch to drives already in a RAID configuration using ICH10R. Would I have to basically destroy and rebuild the RAID to do this? (Urk&#8230;!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Storrgie</title>
		<link>http://blog.agdunn.net/?p=208&#038;cpage=1#comment-820</link>
		<dc:creator>Storrgie</dc:creator>
		<pubDate>Mon, 07 Dec 2009 12:15:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agdunn.net/?p=208#comment-820</guid>
		<description>I have never played with the timeout settings. I also never experienced drive failures like you describe. 

The drives are not truely failing right? Just dropping from the array?</description>
		<content:encoded><![CDATA[<p>I have never played with the timeout settings. I also never experienced drive failures like you describe. </p>
<p>The drives are not truely failing right? Just dropping from the array?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kevin</title>
		<link>http://blog.agdunn.net/?p=208&#038;cpage=1#comment-748</link>
		<dc:creator>kevin</dc:creator>
		<pubDate>Tue, 01 Dec 2009 12:06:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agdunn.net/?p=208#comment-748</guid>
		<description>Just wondering if you had played around with /sys/block/sd?/device/timeout as a mechanism to delay the timeouts that the raid is experiencing for the device - i.e. is an alternative to setting the TLER low setting the disk timeout higher. I&#039;m just not sure if the about setting will affect this.

I&#039;m experiencing a disk failure of this king every 4 weeks or so and it takes about 24 hrs to resync the array - I&#039;d be more than happy for the devices to wait a couple of minutes once a month if it meant I didn&#039;t have to resync the array again.</description>
		<content:encoded><![CDATA[<p>Just wondering if you had played around with /sys/block/sd?/device/timeout as a mechanism to delay the timeouts that the raid is experiencing for the device &#8211; i.e. is an alternative to setting the TLER low setting the disk timeout higher. I&#8217;m just not sure if the about setting will affect this.</p>
<p>I&#8217;m experiencing a disk failure of this king every 4 weeks or so and it takes about 24 hrs to resync the array &#8211; I&#8217;d be more than happy for the devices to wait a couple of minutes once a month if it meant I didn&#8217;t have to resync the array again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RAID0 on WD 1TB &#34;Blacks&#34; - Page 2 - Overclock.net - Overclocking.net</title>
		<link>http://blog.agdunn.net/?p=208&#038;cpage=1#comment-326</link>
		<dc:creator>RAID0 on WD 1TB &#34;Blacks&#34; - Page 2 - Overclock.net - Overclocking.net</dc:creator>
		<pubDate>Mon, 29 Jun 2009 18:40:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.agdunn.net/?p=208#comment-326</guid>
		<description>[...] http://blog.agdunn.net/?p=208  Here is a link to my friend&#039;s blog where he shows how he did this in Linux.   __________________ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://blog.agdunn.net/?p=208" rel="nofollow">http://blog.agdunn.net/?p=208</a>  Here is a link to my friend&#39;s blog where he shows how he did this in Linux.   __________________ [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
