RAID 0 :WD Caviar Black 1TB mi Samsung spinpoint F4 mü ?

quote:

Orijinalden alıntı: apollonx

Tabiiki de 2x F4. Yüksek kapasite raidde o kadarda iyi olmuyor. Mesela benim raidin C'si 100gb D'si 900gb ve D'deki performans C'den düşük. Extradan da şunu söyliyim, 2 tb'lık heran uçabilecek ve üzülmüyeceğin ne yükleyebilirsin ki, durumu öyle düşün. Ben oyunları harici hdd'den D'ye kuruyorum, geçen sata kablolarından biri gevşekti oynamış, açılışda tıkk raid çöktü failed verdi haliyle sonra önce windowsn sonra hariciden tekrar oyunları kurdum güncelleştirmeler driverlar falan baya uğraştırdı. Ben 500x2 F3 yaptım mecburen çünkü vatanda o gün F4 yoktu, sende F4 yap en güzeli 320x2 her türlü yeter. Bu arada raidi kesinlikle yap çok farkediyor, 5 dk da windows7 kurmak, pc açılırken masaüstünü gördüğün gibi iconlara tıklamak falan çok keyifli.

quote:

How to convert a Western Digital “Black” drive into a “Raid Edition” drive.

It’s all in the firmware. Here’s why you should care:

The Western Digital Black one terabyte drive is an outstanding value with a street price of $99, but the manufacturer advises you against using them in RAID arrays. It turns out that they have good reason. Modern high storage density drives are designed to fail regularly but safely. With all those electrical charges so close to each other, even perpendicular recording technology won’t keep the magnetic records from influencing one another in naughty ways. The modern consumer drives monitor the health of each sector of data, and if the signal to noise ratio becomes too weak, the drive packs up the data and moves it to a fresher portion of the disk platter. This happens far more often than you might expect, and is the principle reason that lower density drives are used in enterprise settings. This means two things to the user:

* High density drives become less reliable the closer they are to being full.
* High density drives will sometimes stop to perform routine data recovery – for up to two minutes, while your disk controller waits.

It is the second behavior that is of real concern in a RAID setting. Most RAID controllers will only wait a short time for a drive to respond. Usually this period is as short as 10-20 seconds. If the drive hits this time limit, the controller will mark the entire drive as failed. This is not something you want to happen routinely, as your entire array is at jeopardy of going offline. The preferred behavior in RAID environments is for the drive to quickly time-out and report the sector as bad, so that the raid controller can reconstruct the missing data from the parity information stored on the other drives in the array. RAID parity strategies combined with high density drives synergize extremely well with the fault-tolerant approach adopted in most modern high-availability infrastructure. The philosophy is to use cheap hardware, add redunancy, and then fail and recovery quickly and transparently.

So what’s the real difference between the consumer models and the “RAID Edition” drives from Western Digital? They have the same vital specs. They are even rumored to come off the same assembly line as the “Black” edition consumer grade drives. The chief difference, apart from a 60%-80% difference in price, comes down to a firmware setting. (source) The setting prevents the drive from spending too much time attempting to recover data from a sector on disk. This feature is called Time Limited Error Recover (TLER.) It’s turned off by default on the WD Black, and it’s turned on by default on the RE3. And guess what? You can change the defaults with a simple command line utility, WDTLER.EXE. Wikipedia has an article on how to make the change.

http://en.wikipedia.org/wiki/TLER