Unrecoverable read errors and RAID5

  • Thread starter Thread starter joema
  • Start date Start date
  • Tags Tags
    Errors Hdd
Click For Summary
SUMMARY

The discussion centers on the reliability of RAID5 configurations in light of unrecoverable read errors (URE) during rebuilds. It challenges the prevailing notion that RAID5 becomes impractical with larger data volumes due to URE rates, specifically the claim that a 16TB 8-drive RAID5 array faces a near 100% chance of a second HDD failure during rebuild. The author argues that the URE rate of 1 in 10^14 reads translates to a much lower risk when considering modern HDD operations and error correction mechanisms. Empirical studies indicate that actual failure rates are significantly lower than manufacturer specifications, suggesting RAID5 remains a viable option for data storage.

PREREQUISITES
  • Understanding of RAID configurations, particularly RAID5
  • Familiarity with hard drive unrecoverable read error (URE) rates
  • Knowledge of error correction codes (ECC) in RAID systems
  • Basic comprehension of data transfer volumes and HDD read operations
NEXT STEPS
  • Research the impact of error correction codes (ECC) on RAID5 reliability
  • Examine empirical studies on HDD failure rates and URE occurrences
  • Learn about the differences between theoretical and observed HDD performance metrics
  • Explore RAID alternatives and their comparative reliability in large data environments
USEFUL FOR

Data storage professionals, system architects, and IT administrators seeking to optimize RAID configurations and understand HDD reliability metrics in large-scale environments.

joema
Messages
106
Reaction score
3
A number of popular-level articles have been published saying that RAID5 is increasingly impractical at larger data volumes due to the chance of an individual HDD having an unrecoverable read error (URE) during the rebuild phase. I think the underlying math which produced this conclusion may be in error, and I'd like someone to check it.

Published reasoning: typical HDDs have a URE rate of 1 in 10^14 reads (interpreted as bytes). If a 16TB 8-drive RAID5 array has a single URE, that HDD must be replaced and data rebuilt on the spare. During the rebuild no further errors can be tolerated else the entire array is bad. Apparent mathematical reasoning: 1 URE per 10^14 bytes / 8 HDD per array = 1 URE per 12.5 TB read from the 8-drive array. Conclusion: given that URE rate there is a nearly 100% chance of a 2nd HDD failing while rebuilding the 16TB array. Example article: http://www.zdnet.com/article/has-raid5-stopped-working/

I think this is incorrect for several reasons:

(1) Common sense: if the chance of a URE is 1 per 12.5 TB read, large RAID0 and RAID5 arrays would be failing at an incredible rate.

(2) The specified URE rate is 1 per 10^14 *reads*, not bytes. Modern drives do reads in 4k-byte sectors, not bytes or 512-byte sectors. So translated to bytes, the URE rate is 1 per 10^14 * 4096 bytes per sector, or 1 URE per 409,600 terabytes read.

(3) While number of drives in the array increases chance of an individual failure per unit of *operating time*, they do not increase failure chance per data transfer volume vs a single HDD of equal capacity. E.g, if reading the *same* data volume from a single HDD vs an n-drive RAID array, each drive in the array will only do 1/nth the reads, hence have 1/nth the failure chance per aggregate volume of data. Therefore for a given number of reads, the URE probability is about the same between a single drive and a multi-drive RAID array.
 
Computer science news on Phys.org
Link to an article that may help explain this:

raid 5 and ure

Also if a URE is encountered, it would seem that a smart raid controller would attempt to correct the error by using ECC to caculate the data needed for the failed sector and rewrite it, giving the hard drive some chance to recover from the error (the hard drive might remap the bad sector to a spare sector which will get updated by the write).
 
I'm still investigating this. I think my above numbers and reasoning are incorrect, because the HDD non-recoverable error spec is failed reads per total bits read, not sectors read. However the fact remains, hard drives and RAID5 are much more reliable than indicated by the manufacturer's "non-recoverable error rate". That was the key point in the article you mentioned -- thanks!

If the spec is 1 failure per 10^14 bits read, 10^14 bits = 12.5 terabytes. So by that spec you'd expect a failure on average every 12.5TB -- that's where Robin Harris who wrote all the "doom and gloom" ZDNet articles got his number. However -- we know from observation that HDDs and RAID systems do not fail anywhere near that often.

One answer is the spec is simply a "worst case" spec -- IOW a guarantee the HDD will be no *worse* than that. It is not an average failure rate, nor a predicted failure rate. It's more like an uptime or availability guarantee. If a vendor promises 90% availability, that doesn't mean the system is unavailable 10% of the time. It may well achieve 99% availability -- it's just a worst case guarantee.

If the HDD is really more reliable than, say, 1 error per 10^14 bits read, why don't they say that? We could just as well ask if the average engine in a Honda car will last 180,000 miles, why is the engine warranty only 60,000 miles? There are many reasons for that.
 
A key study (while several years old) covers this exact area: namely the disparity between the "non-recoverable error rate" spec published by HDD manufacturers and empirically-observed results. A spec of one non-recoverable error per 10^14 bits read would equate to one error every 12.5 terabytes read. This study found four non-recoverable errors per two petabytes read, which equates to one error per 4E15 bits read, or about 40 times more reliable than the HDD manufacturer spec. Empirical Measurements of Disk Failure Rates and Error Rates (2005, Jim Gray, et al):
: http://research.microsoft.com/apps/pubs/default.aspx?id=64599
 
  • Like
Likes   Reactions: jim mcnamara

Similar threads

  • · Replies 30 ·
2
Replies
30
Views
6K
  • · Replies 14 ·
Replies
14
Views
5K
Replies
2
Views
6K
Replies
3
Views
10K
  • · Replies 1 ·
Replies
1
Views
9K
  • · Replies 1 ·
Replies
1
Views
3K
Replies
5
Views
2K
  • · Replies 1 ·
Replies
1
Views
3K
  • · Replies 0 ·
Replies
0
Views
2K
  • · Replies 7 ·
Replies
7
Views
3K