WD Green Drives no good for QNAP's??

[jasoncun]

Does that mean the Western Digital Caviar Green 2TB HDD WD20EADS is no good then for the QNAP ?

I was originally intending to get 2 of them to put into a 2bay QNAP 239 to be used as backup for my QNAP 509 Pro, but now i am not sure anymore

I installed 2 2TB WD20EADS (RAID 1) on my 239 . No problem yet. It's very fast and trouble free. I just transferred 500 Gbs worth of data on it.

[xavierh]

i do not believe that they are not good, but mine decided to show those errors way before what I would expect. Therefore i'm getting a new drive that should arrive on friday to replace it...

[johannlo]

If I had to do it all over again, ** NO would I trust WD green drives. I've always preferred WD drives until this debacle. 'we don't support linux' my a$$

But having said that, after using the wdidle3 utility the LCC issue is gone for me.

Performance isn't so hot (TS409 so old model with pitiful CPU), with RADI5 I'm only getting around 9Mb/sec write speeds compared to closer to 11-12Mb/sec before (using WD Server Edition drives) and it noticeably chokes when you have more than 2 transfers at the same time, but I'm just glad I've got no stuttering issues or otherwise. I do suspect that if it was a newer, more powerful model I may have run into the other issues described in this forum.

Never buying cheap drives for a NAS again thats for sure (funny how when its your home environment, and your $$$ the rules you rigidly enforce at work go out the window)

[Parax]

I have to say its funny that everyone says its the WD drives that are 'broken' where as to my eyes it looks like its Linux that is preventing the drives being Green! surely linux does not need to keep checking the drive every 30 seconds?? or am I missing something...

Anyway WD advised that LLC was likly to be much higher on GP drives - but they decided not to update the minimum lifetime figures, carelessness/lazy/overcautious/something to hide you decide.

The drives do not say NOT SUITABLE FOR LINUX on them so im not too worried about WD sticking to their warrantee!

as for my experience:
Power_On_Hours 12648
Load_Cycle_Count 1340304
2 Drives and no failures...

well its only a 'smidge' over.......

[xavierh]

I bought a green drive earlier in the year and it developed bad sectors. I do not know if this is due to the LLC count but I sent it to Western Digital for replacement. In the meantime I bought a black drive (same size for my nas).

[birillobo]

I have a TS-210 with two new WD20EADS (2TB).
During the configuration of the raid1, one of them became "Abnormal" and the fan start very fast.
In the hdd smart information the only red voice is "Raw read error Rate" with this values:

Value 001
Worst Value 001
Threshold 051
Raw Value 4818

After two hour i'm stil waiting the end of the process...

Is the disk faulty or there is an explanation for this?

Thank you for your help.

[sonicmainliner]

I got something to add to all this, I bought 2 WD10EADS-00P8B0 these have a high LCC, currently ~5000 for 88hours of use, then I bought another 2, this time they are WD10EADS-00L5B1 and these two have an LCC of 24 for 39 hours of use.

What do you make of this? Also note that smart reports the same firmware for both.

[schumaku]

I have a TS-210 with two new WD20EADS (2TB). During the configuration of the raid1, one of them became "Abnormal" and the fan start very fast. In the hdd smart information the only red voice is "Raw read error Rate" ...

Print out these details, remove the disk and then back for warranty exchange. Building the RAID is very intensive, hard to say if the fan went to fast due the normal load, or due to the broken disk.

Have you followed the advice and
a) Checked WD support if it is possible to enale TLER on your units?
b) Had you enabled TLER to seven seconds for read and write before installing in the TS and attempting to build the RAID?
c) Precautionously set the IDLE3 timer to avoid the high LCC seen in neighboring posts?

Be happy - better now than with your precious data on it. Please seriously consider swapping these desktop drives with your seller to WD REx RAID-capable units.

After two hour i'm stil waiting the end of the process...

...you will very likely never see.

Is the disk faulty or there is an explanation for this?

Well, obviously a broken disk - beyond WD desktop drives which are not supported for RAID usage by WDC.

Sorry for the troubles - complaints to WDC please.

-Kurt.

[schumaku]

I got something to add to all this, I bought 2 WD10EADS-00P8B0 these have a high LCC, currently ~5000 for 88hours of use, then I bought another 2, this time they are WD10EADS-00L5B1 and these two have an LCC of 24 for 39 hours of use.

Even if the same firmware is on the units, the unit configuration parameters might be very different.

What do you make of this?

I would adjust the IDLE3 timer to 30 seconds by using the WDIDLE3.EXE on all disks, or at least on the new ones.

Beyond, I would consider swapping the two new units to e.g. WD REx enterprise and RAID-capable drives.

-Kurt.

[schumaku]

I have to say its funny that everyone says its the WD drives that are 'broken' where as to my eyes it looks like its Linux that is preventing the drives being Green! surely linux does not need to keep checking the drive every 30 seconds?? or am I missing something...

The IDLE3 timer is only one part of the issues - interesting enough, newer production drives don't show the high LLC anymore.

The drives do not say NOT SUITABLE FOR LINUX on them so im not too worried about WD sticking to their warrantee!

This is not the point: WD says clear, their desktop drives are not feasible for RAID usage, and new manufactured drives can't have TLER enabled - a soon as these disks start doing so called deep error corrections, this takes two minutes or longer - but after maximum eight seconds, the disk will be ejected from the RAID.

While the IDLE3 part does mainly lead to some performance impacts and ridiculous counter numbers for LLC, the error correction is bringing your data into risk - but not mine.

-Kurt.

[birillobo]

Have you followed the advice and
a) Checked WD support if it is possible to enale TLER on your units?
b) Had you enabled TLER to seven seconds for read and write before installing in the TS and attempting to build the RAID?
c) Precautionously set the IDLE3 timer to avoid the high LCC seen in neighboring posts?

I downloaded WDTLER.exe and WIDDLE3.exe to enable tler and set the idle timer but i now i don't know how to make this!
I launched the software but nothing happened. I must link the nas directly to the pc?

[sonicmainliner]

I tried to run these programs, but in Vista they crash, even in compatibility mode.

[schumaku]

XP, Vista, or Windows 7 don't allow "physical" low-level access to the drives while running, e.g. from cmd/command.

You need to create a bootable MS-DOS device (e.g. a CD-ROM), add the programs, and launch from there.

-Kurt.

[sonicmainliner]

Any boot cd(that run dos programs) suggestions? I have come across many boot loaders and other bits and bobs, but nothing to burn and use immediately.

[Dawgneck]

I suggest you create a boot usb thumbdrive as Jollster suggested earlier in this thread. The directions and files are found here: http://www.bay-wolf.com/usbmemstick.htm

Make sure you set your motherboard to boot from your usb/external connector (the wording differs from manufacturer).

Any boot cd(that run dos programs) suggestions? I have come across many boot loaders and other bits and bobs, but nothing to burn and use immediately.