Seagate Constellation ES.3 in non-RAID/error recovery time limit?

GCabot

Honorable
Aug 21, 2013
10
0
10,510
I'm looking at getting a Seagate Constellation ES.3 hard drive, but plan on using it as a stand-alone drive rather than in RAID. My understanding is that enterprise drives tend to limit the error recovery time by default since they are designed to run in RAID, and this would need to be turned off to run properly as a stand-alone drive. Seagate calls this Error Recovery Control (ERC).

I haven't been able to figure out if this model has ERC. Seagate's website states that the previous ES and ES.2 iterations included it, but doesn't mention anything about the ES.3. Nothing in the documentation mentions anything about error recovery time limits either.

Does anyone happen to know if the Constellation ES.3 has an error recovery time limit by default that I would need to turn off to use it as a stand-alone drive? If so, is this even possible? (I understand that this is no longer possible on WD enterprise drives.) If it is possible, how difficult would it be? I'm reasonably tech-savvy, but I'm not any kind of computer expert at modifying internal settings.


Update:
The response I got from Seagate is as follows:
"You will need to disable any features on the Constellation drive. Error correction should be left as is."

Completely vague and seems contradictory to me...
 
Solution
I dont believe seagate lets you set this. I know they didnt used to but I dont know if thats still their policy. A quick google did not reveal anything on this particular drive. You could always run the drive in raid mode as a single drive raid 0/1 (depending on what your raid controller needs) and avoid the issue.

popatim

Titan
Moderator
I dont believe seagate lets you set this. I know they didnt used to but I dont know if thats still their policy. A quick google did not reveal anything on this particular drive. You could always run the drive in raid mode as a single drive raid 0/1 (depending on what your raid controller needs) and avoid the issue.
 
Solution