以前我几年是幸运的，足有购买二手硬件RAID机会 5 卡 (一个槟榔 1220) 一个非常低的价格. 从那时起，我拥有多套驱动器所使用的卡一起 (原本300gig, 然后750gig目前1Tb的) 在一个专用的服务器PC作为一个大的网络文件的存储，为家庭的音乐, 照片, 视频和后备.
Before I obtained the hardware card I tried using software raid, but found the results very disappointing. The server has a low power, single core cpu which isn’t really up to the task of acting as a raid‑5 engine. 虽然我听说过很多次，那 RAID 不是备份, this is a case where only a cheap solution will do. RAID-5 offers protection from single drive failure, which is good enough for my purposes. The dedicated card offers an enormous performance advantage, but in practice this isn’t very important. The features it adds however are! 槟榔卡提供 操作系统 independent raid solution which counts for a lot. It also offers online capacity expansion and raid-level migration (所以, 例如, I could upgrade to raid‑6). Both of these features are much less simple with cheaper solutions.
所以, 你可能认为, what’s the problem. 答案: the lack of options from Hard Disk manufacturers…
Ever since using the Areca card I have suffered from occasional drive “failures”. Upon powering off and on the drive reappears as fully functional. I then have to spend many hours rebuilding the array from degraded back to normal. After much searching I have diagnosed the problem, but am unable to properly solve it.
Hard Drive manufacturers provide a range of drives for different purposes. The typical drives most of us buy are consumer level drives. The manufacturers also offer enterprise-class drives designed for servers which have intensive use patterns and 24.7 运行时间. These drives are often physically identical, but have undergone additional testing and are supplied with slightly different firmware, optimised for server workloads.
One of these features is Error Recovery Control (ERC). This feature is also called CCTL (Command Completion Time Limit) by Samsung and Hitachi and TLER (Time-Limited Error Recovery) by Western Digital. All drives suffer the occasional error at a physical level, which could be caused by things like stray cosmic rays. These errors are handled by redundancy built into the way the drive stores data, but occasionally one can be severe enough to cause problems reading data. Normal consumer drives will spend a prolonged period attempting to read the damaged data to recover it. They then map it to a new part of the drive and everything continues as normal. 然而, this delay can cause severe problems in enterprise environments, so enterprise drives will time-out their self-repair attempts after a short period (usually 7 秒左右) and report the error to the raid controller. The raid controller then handles the error by recalculating the data using the other drives in the array. This prevents large delays in sending data, but requires the presence of other drives and a raid controller.
所以, I have a proper hardware raid card. It expects to hear back from drives within no more than 7–8 seconds regardless of an error. I also have consumer hard drives, which attempt to repair their own errors for a long period. 因此，当出现错误的驱动器会尝试修复它, doesn’t respond within 7–8 seconds, and the raid controller than assumes the drive has failed and kicks it out of the array.
所以, the obvious solutions would be either to tell the raid controller to wait longer without kicking a drive out, 或者告诉驱动器后放弃 7 seconds like an enterprise drive… Infuriatingly, neither is possible!
I have searched extensively, but I can’t find any proper raid‑5 cards which allow the user to change how long they will wait for a drive. In the past there were some WD drives which could have the TLER feature enabled with a utility released by WD called WD-TLER, but recently WD have disabled this option, presumably to “protect” the huge markup on their enterprise drives (which are double the price for the same hardware)
For users like myself that need a large capacity storage, and the features offered by a hardware raid‑5 solution, 但是，这并不需要 24.7 运行时间, long warranties or drives designed for heavy duty usage there is currently NO appropriate solution. Its about time either a drive manufacturer addressed this market (by releasing a consumer drive with ERC enabled for a small, e.g. 15%, premium) or a raid-card manufacturer addressed the market by offering a card with the option to increase the time before drives are timed out. Creating either of these solutions is trivial, a simple firmware tweak would do the job.
直到那时, I advise others to avoid using hardware raid cards with consumer drives, and given the price premium of enterprise drives I recommending avoiding hardware raid altogether.
认为我们已经错过了什么? 让我们通过下面的评论知道. 如果您想订阅，请使用菜单上的订阅链接右上方. 您还可以通过使用下面的链接社会分享这与你的朋友. 干杯.