• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

NAS drive without TLER\CCTL?

B

Bobeggy

n00b
Joined
Oct 5, 2014
Messages
4
I've seen many articles with people wanting to turn CCTL/ERC/TLER on for consumer grade drives so the can be used in a raid.
I'm looking for the exact opposite. I want a raid level drive, for 24\7 use but with deep recovery.
I want the dual actuators, extra vibration control, and higher MTBF that comes with the NAS or enterprise drives but with the extra data recover effort as well.
I will be using a pair of 4TB drives in a server but they won't be in a raid.

Does anyone know if these drives are even capable of deep recovery?

For example, in WD's NASWARE 2.0 and 3.0 firmware, since they built it specifically for NAS environments, they limit recovery efforts to 7 seconds. Did they even bother to include the deep recovery code?
 
I'm not sure there is some special code involved here. Chances are that if the drive cannot read a sector during the first 7 seconds, it won't be able to read it at all.
That said you can turn off TLER on WD RED drives with smartctl. I have been using RED drives as single storage drives for a while now.
 
Thank for the response.

I don't know enough about the error recovery to know if maybe it's done in stages with later stages using "deeper" (but much slower) methods to try to grab unreadable bits. The manufacturers say the process could take over 2 minutes, so not sure what is happening during all that time.
If a NAS drive is built to stop trying after 7 seconds, letting the raid controller perform the recovery, then maybe those deeper stages are simply left out of the firmware?

It is good to know it can be disabled on those WD Reds. Does it stay disabled through power cycles, or do I have to disable every time I power up?
 
Bobeggy said:
Does it stay disabled through power cycles, or do I have to disable every time I power up?
Click to expand...

I'm almost sure that they keep this state over power cycles, although I can't try it as I don't have any spare RED drives around.
 
There were a batch of reds that came out with tler disabled or at least set to a long time, thinking last fall or early this year. They released an updater that let you change the time.
 
So I guess I'm back to asking if anyone knows of a drive, like the older Reds, that can have the TLER shut off?
 
Bobeggy said:
I think WD has answered the question.

http://wdc.custhelp.com/app/answers/detail/a_id/1478/session/L3RpbWUvMTQxMjcwMjU1MC9zaWQvSkx4bXloNG0%3D

I'm not sure how you manage to disable TLER on your drives. Maybe yours are older versions?
Click to expand...

This is about RE series drives and has nothing to do with WD RED series.

Code: 
root@quantum:~# smartctl -l scterc /dev/sdm
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-35-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

root@quantum:~# smartctl -l scterc,0,0 /dev/sdm
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-35-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

SCT Error Recovery Control set to:
           Read: Disabled
          Write: Disabled

root@quantum:~# smartctl -l scterc /dev/sdm
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-35-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

root@quantum:~# smartctl -l scterc,70,70 /dev/sdm
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-35-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

SCT Error Recovery Control set to:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

root@quantum:~# smartctl -l scterc /dev/sdm
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-35-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

SCT Error Recovery Control:
           Read:     70 (7.0 seconds)
          Write:     70 (7.0 seconds)

root@quantum:~# smartctl -i /dev/sdm
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.13.0-35-generic] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Red (AF)
Device Model:     WDC WD30EFRX-68AX9N0
Serial Number:    <snip>
LU WWN Device Id: <snip>
Firmware Version: 80.00A80
User Capacity:    3,000,592,982,016 bytes [3.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 (minor revision not indicated)
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed Oct  8 08:33:01 2014 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

SCT stays at the set value. Drive was purchased August 2013 and is from the newest batch of WD RED drives I currently can test this on.
I'm not going to test whether the value is persistent across reboots.
 
You must log in or register to reply here.
Back
Top