WD RED Drives (WD10EFRX WD20EFRX WD30EFRX)

[Toxic17]

Pretty sure it is 5400 rpm for the NASWare 3.0 drives

[P3R]

Pretty sure it is 5400 rpm for the NASWare 3.0 drives

And here is technical proof that it is at least very close to 5400: "The two Red drives produced a slight tone at ~90 Hz, confirming that their motors spin at about 5,400 RPM.".

WD IntelliPower and HGST CoolSpin is of course marketing nonsense but I do have some understanding for not disclosing the actual rpm as most customers looking at the data sheet are not qualified to really understand it, many probably overrate the importance of the rpm. 5400 rpm is not always slower and 7200 rpm is not always using more power. There are other variables in effect as well.

[P3R]

Despite normally being reluctant to be an early adopter regarding disks I actually installed a pair of 3 TB WD Reds in RAID 1 only a month after their introduction in the summer of 2012.

Now 2.5 years later and with around 19500 power_on_hours one of them started to report read errors during SMART testing and the current_pending_sector number climbed steadily. I removed the disk and tested it with the WD Data Lifeguard Diagnostic software and it immediately failed already on the short test. Two hours after having cleared the data from the disk, I installed the warranty replacement and a little more than 10 hours later the volume was again synchronized. No drama at all.

Since this is only one of my backup NASes I didn't bother to immediately rebuild on my cold spare disk (another manufacturer and model) but rather to wait for the warranty replacement. I prefer to have the extremely quiet and low power WD Reds in this unit and there was no risk for any data loss to run a day or two on only one disk.

So yes, WD Reds also fail but at least this time it was a "nice" failure and lucky for me, within warranty. Now probably my other early sample of WD Red will fail a month after the warranty period ends this fall. Being prepared for the worst minimizes disappointment...

Tip: always, always enable scheduled rapid SMART tests daily and complete SMART tests weekly (Control Panel, Storage Manager, HDD SMART, Settings) on all disks and make sure you get alerted of any errors by the NAS (Control Panel, Notifications, SMTP Server).

[Briain]

...Tip: always, always enable scheduled rapid SMART tests daily and complete SMART tests weekly (Control Panel, Storage Manager, HDD SMART, Settings) on all disks and make sure you get alerted of any errors by the NAS (Control Panel, Notifications, SMTP Server).

Hi

Indeed that is a great tip; I've always had the full SMART tests scheduled to happen weekly, but I've never bothered with the daily rapid ones. My thinking - which could be seriously flawed; I've never looked at what the rapid tests actually do - is that as these rapid tests don't perform a full surface scan, I'm not entirely sure what real value they'd bring to the party; does anyone have any thoughts on how flawed (or not) my thinking might be? To be clear, I'm not proposing that I believe my strategy to be correct (so I'm definitely not suggesting that anyone else adopts it); I'm just asking the question as I'm genuinely interested to read any comments anyone might wish to make.

Bri

[P3R]

I don't know what the rapid test actually do (is any SMART test documented in detail by any manufacturer?). I do however know that also the rapid test caught the issues my disk had this time and since the test finishes in 1 or 2 minutes, I see no reason not to take advantage of the feature every night. When a disk is deteriorating, I don't want to wait almost a week (worst case) until I'm alerted about it. By that time it can be too late.

I have my daily rapid tests scheduled after 3 a.m. when the disks are always spun up anyway (on this NAS that is almost exclusively used for backups, I do have disk spin down enabled). I have the weekly complete tests scheduled 10 minutes after the daily rapid tests, to make absolutely sure the rapid tests have finished.

[Briain]

Hi

Interesting that the rapid test caught and alerted you to the problem! As you say, there's no harm in having them set, but it would be interesting to know what they achieve. I can only assume they perform a test read/write (or a scan of a tiny area) as they're way too brief to capture any deteriorating sectors.

Thanks for the info and as I say, very interesting to hear that they worked in your case; I'll go set mine to augment my weekly ones.

All the best
Bri

[axrst]

Hi,

Please help me with this:

I have TS-659-pro+ with QTS 4.1.3 and a RAID 5 volume with 6 x WDC WD30EFRX-68EUZN082.0 (3TB) disks.

After 6 months of normal operation, the disk 4, after a complete SMART test, gave me an error:

It says that the operation of disk is Abnormal and the warning e-mail that send me was:

Code: Select all

Level:  Warning
[Harddisk 4] I/O error, sense_key=0xb, asc=0x0, ascq=0x0, CDB=88 00 00 00 00 01 5d 4d 1e 48 00 00 00 08 00 00 .

After that I send it to the service for replacement. There, they checked the disk with the official WD tool and they send it back to me, because no errors found. I checked the disk myself then and I found no errors also.

When I put the disk to my NAS, the complete test shows no errors, the SMART info shows Good, BUT, in the summary (HDD smart) shows the condition still Abnormal, and I cannot use the disk to my RAID volume again. (Raid volume works in degrated mode).



Please tell me what should I do?

[pwilson]

Hi,

Please help me with this:

I have TS-659-pro+ with QTS 4.1.3 and a RAID 5 volume with 6 x WDC WD30EFRX-68EUZN082.0 (3TB) disks.

After 6 months of normal operation, the disk 4, after a complete SMART test, gave me an error:

It says that the operation of disk is Abnormal and the warning e-mail that send me was:

Code: Select all

Level:  Warning
[Harddisk 4] I/O error, sense_key=0xb, asc=0x0, ascq=0x0, CDB=88 00 00 00 00 01 5d 4d 1e 48 00 00 00 08 00 00 .

After that I send it to the service for replacement. There, they checked the disk with the official WD tool and they send it back to me, because no errors found. I checked the disk myself then and I found no errors also.

When I put the disk to my NAS, the complete test shows no errors, the SMART info shows Good, BUT, in the summary (HDD smart) shows the condition still Abnormal, and I cannot use the disk to my RAID volume again. (Raid volume works in degrated mode).



Please tell me what should I do?

That stupid "Abnormal" screen is useless for troubleshooting purposes. Please post the actual S.M.A.R.T. output itself instead. You can generate a nice "textual" version of the output by accessing your NAS via SSH, (login as "admin"), and running:

Code: Select all

hdparm -i /dev/sdd | grep -i model ; /sbin/get_hd_smartinfo -d 4

Textual output is preferable to a screenshot, as we can "quote" from textual output.

To resolve this issue, simply hot-swap HDD4 with a suitable replacement drive (hopefully another WD30EFRX) by following QNAP Tutorial: Hot-swapping the hard drives when the RAID crashes

It takes less than 2 minutes to hot-swap a drive.

[axrst]

Thank you Patrick for your answer.

Before trying what you suggested, I was lucky trying something else:

After a reminder for upgrading the NAS firmware, I re-booted the NAS. And that's was it! After the reboot, the system saw the disk as "Good" and started immediately to rebuilding the RAID volume. I don't know if you understood that the drive was not faulty. It was good, but the NAS saw it as "Abnormal". So to replace the drive with another one was not I wanted...

[pwilson]

Thank you Patrick for your answer.

Before trying what you suggested, I was lucky trying something else:

After a reminder for upgrading the NAS firmware, I re-booted the NAS. And that's was it! After the reboot, the system saw the disk as "Good" and started immediately to rebuilding the RAID volume. I don't know if you understood that the drive was not faulty. It was good, but the NAS saw it as "Abnormal". So to replace the drive with another one was not I wanted...

If the drive failed. It failed. Re-using a failed drive is a temporary solution at best. You should have replaced it, claiming warranty to do so, so that you aren't out-of-pocket financially. S.M.A.R.T. data is generated by the Drive itself, so this is not a NAS issue.

Replace the drive.

I asked you to provide the S.M.A.R.T. data which you still have not done. It's your drive, your NAS, and your data, so the choice is yours. Why didn't you replace it? Why didn't you provide the S.M.A.R.T. data as requested?

[axrst]

Thank you again for your answer.

Here is the S.M.A.R.T data:

Code: Select all

Model=WDC WD30EFRX-68EUZN0                    , FwRev=82.00A82, SerialNo=     WD-WCC*********
001 Raw_Read_Error_Rate          17       200 200 051 OK
003 Spin_Up_Time                 6050     179 177 021 OK
004 Start_Stop_Count             42       100 100 000 OK
005 Reallocated_Sector_Ct        0        200 200 140 OK
007 Seek_Error_Rate              0        200 200 000 OK
009 Power_On_Hours               4117     095 095 000 OK
010 Spin_Retry_Count             0        100 253 000 OK
011 Calibration_Retry_Count      0        100 253 000 OK
012 Power_Cycle_Count            21       100 100 000 OK
192 Power-Off_Retract_Count      14       200 200 000 OK
193 Load_Cycle_Count             103      200 200 000 OK
194 Temperature_Celsius          32       118 112 000 OK
196 Reallocated_Event_Count      0        200 200 000 OK
197 Current_Pending_Sector       0        200 200 000 OK
198 Offline_Uncorrectable        0        100 253 000 OK
199 UDMA_CRC_Error_Count         0        200 200 000 OK
200 Multi_Zone_Error_Rate        0        200 200 000 OK

I thought that the issue is solved before your second answer. Because the tech support of the drive seller, (and myself later) checked the drive with the "Data Lifeguard Diagnostic" by WD and found no errors. And because the NAS also NOW shows the drive OK. So, how can I prove that the drive is faulty, claiming warranty to replace it? Of course I'd like to replace it but I don't want to pay for a new one...

[schumaku]

If the drive in question was not wiped during the distributor or your testing, the "abnormal" mark is still in place.

[axrst]

Yes, but, how can I prove that the disk is faulty? (Is it? Or it was a false allarm?)

[MrVideo]

Too little. Too late.

WDC has already demonstrated contempt for their customers. Especially in regards to their Caviar "Blue"/"Black"/"Green" drives.
Western Digital Corporation will never see another penny from me. Ever! (The contempt is now mutual).

'Nuff said...

So, Patrick, when did you change your tune? I was snooping around the forum and ran across this thread and saw this posting from you.

[Ron1963]

Too little. Too late.

WDC has already demonstrated contempt for their customers. Especially in regards to their Caviar "Blue"/"Black"/"Green" drives.
Western Digital Corporation will never see another penny from me. Ever! (The contempt is now mutual).

'Nuff said...

So, Patrick, when did you change your tune? I was snooping around the forum and ran across this thread and saw this posting from you.

This was coming from the biggest endorser of RED HDD's I have ever come across? I guess Patrick was just pragmatic and out of only two chose the manufacturer he hates the least .