Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Using TLER enabled WD enterprise harddrives on an Intel onboard raid controller, is that good or bad?

share|improve this question
I think the answer may be different for different RAID levels. Would love to see some good answers on this. – Andrew Mao Sep 5 '14 at 18:02
up vote 4 down vote accepted

Many of the more software based raid styles, like the simple onboard Intel raid, will wait for a long time before freaking out, they can be much more forgiving than a fully hardware based raid Card with onboard processor and onboard ram. Besides you have to Have an error first :-) If my disks were having errors and flaking out the raid to often, in reality I would WANT TO KNOW , even if that means it bails out and I have to reboot , halt the system, and let it complete a hardware task. Then next I am going to be wondering what error it got, and why to took so long to "fix" or hide it.

The noise about the ammount of time set on the TLER is important for many raid systems, so knowlegable raid experts would always say that the time needs to be limited, and "There Is No Other Way". But the same experts will also admit that the more consumer based systems are fully capable of handling the situation of a drive not responding as quick. Because they are more consumer based.

Tidbits from a manufacture: From,279

When an error is found on a desktop edition hard drive, the drive will enter into a deep recovery cycle to attempt to repair the error, recover the data from the problematic area, and then reallocate a dedicated area to replace the problematic area. This process can take up to 2 minutes depending on the severity of the issue. Most RAID controllers allow a very short amount of time for a hard drive to recover from an error. If a hard drive takes too long to complete this process, the drive will be dropped from the RAID array. Most RAID controllers allow from 7 to 15 seconds for error recovery before dropping a hard drive from an array. Western Digital does not recommend installing desktop edition hard drives in an enterprise environment (on a RAID controller).

It would be Good to read the rest there. Notice how a Cavier "black" does not define a "raid drive" for WD. The (RE) designation does. How many times have you seen users say that "blacks" are the ones to use in a raid system?

Myself I have used consumer disks and more consumer based raid systems for ages, i rarely get errors of ANY sort, and have never had a problem with a consumer drive in a consumerish raid system. I am not running a Web Server, I have a fair idea as to how the hardwares are reacting. I think some of the noise about TLER is overrated. Again, VERY important for some raid systems, or even configurations, but is nothing but noise to me, because all my stuff has not skipped a beat.

If you want less problems you get the right stuff, if you are a cheapskate :-) you can get away with more than any expert would say you could. I also treat my hard drives like they are easily damaged, that means my computer should not even be bumped, while it is spun up.

These answers are not supposed to be "opinion" so the Facts are "proper drives should be used in raid systems" Especially important for high end "full" raid cards. The facts also are that thousands of users are running raid systems with consumer and even green drives with long TLER times in the intel onboard and other lightweight raid controllers . both with a relative ammount of troubles from either.

If the TLER time is greater than the preset timeout period for the controller, the controller could mark the drive as defective, even though the drive is just trying to repair bad sectors. <--- that is the key.

share|improve this answer
So you are saying that the only negative effect that could come from using TLER is that the system may 'overreact' when things take a long time? – cc0 Mar 2 '12 at 13:16
@cc0 Yes like marking the disk as bad, unnessisary rebuilds. the windows system is even capable of crashing or locking up when an i/o doesnt complete. I have seen it occur one time on a promice raid system , went back to check after getting it going again, and there were 13 new bad sectors. . . If we Put in some re-built drive, or one of those re-tested returns from the manufacture, or a drive doing bad seeks and all, and again, I as a user (not web server) would rather it fail, then I test the drive and replace if nessisary. – Psycogeek Mar 2 '12 at 13:22
Excellent, thank you. – cc0 Mar 2 '12 at 13:23
Part of it is drives are much faster at repairing and relocating bad sectors these days, and ECC is much much better also. so longer timeouts are rare on consumer drives, there was a time when you better use TLER on older consumer drives with raid controllers or else. Seems to be a moot point on modern drives. – Moab Mar 2 '12 at 16:50

NO TLER is not noise .. I lose 2 wd caviar blue myself were in raid for 1 year and suddenly they dead without any notice. TLER is VERY important for any raid system..

share|improve this answer
Welcome to SU. Can you format your answer in a way to doesn't come across so rude. Include specific (ideally technical) reasons as to why you hold this position rather than a life experience. Makes your answer more useful. Thanks. – Matthew Williams Mar 26 '14 at 15:22
Please try to focus on providing a factual answer and not just commentary which does not help the OP reach a conclusion. – Eric G Mar 26 '14 at 15:42

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.