can anyone give me a hint? I woke up to the red light under first HDD. The HDD is cca one month old after old one has reported failure (come to think of it, I did not checked it too much, seen the red light, bought new one). After month of usage, the new one reports as bad in dasboard. I found it weird, so I pulled the smart data from smartctl, run quick test (passed), waiting to complete long test.
Thing is, I cannot find anything wrong in the smart data in the “failing” drive. Anyone can spot something?
smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.22] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: WDC WD40EFPX-68C6CN0
Serial Number: WD-WX52D43CU71U
LU WWN Device Id: 5 0014ee 215c8ae26
Firmware Version: 81.00A81
User Capacity: 4,000,787,030,016 bytes [4.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 3.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Fri Aug 11 09:02:29 2023 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 249) Self-test routine in progress...
90% of test remaining.
Total time to complete Offline
data collection: (40980) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 427) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x3039) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 1
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 594
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 0
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1
194 Temperature_Celsius 0x0022 111 105 000 Old_age Always - 36
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 593 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Had « SMART » failure reported for the first drive. Then bought a WD RED Pro to replace it.
The new new drive was reported as being in « bad » state and has consequently been already RMAed.
And now the replacement disk is also said to be in bad state, each time with red light on drive 1.
I am in touch with support since.
I am running tests as required. System test and quick test has been said to be OK. Complete test is undergoing…
Full test done, no errors. Raised a ticket too, added smart data + logs. Let’s see what they come back with. Seems that I bought a new drive for no reason whatsoever.
On my side too.
All tests (system, quick, full) passed successfully.
Waiting for t’support to update me on this.
But that raises the question of who is to be trusted, why would my My Cloud EX2 Ultra reports that the disk is in bad state… twice in this case.
I’ve had the same red LED on the first drive, a couple times (PR4100).
I found that rebooting the PR4100 clears the red LED. To me, this likely indicates a software problem rather than a hardware failure.
Additionally, on one occasion, I copied all the S.M.A.R.T. data (red LED indicated), then rebooted, and again copied the S.M.A.R.T. data (blue LED indicated), and compared the two. No differences.
I am having similar issues with drive bay 3 in my PR4100.
Are you removing the drive in placing it within a separate drive dock to obtain the SMART data? It seems that my PR4100 reads valid data for a while but, after 10 minutes the red light is lit on bay 3.
Very weird.
This is a second PR4100 that I have had. I have sent a different one back because drive bay 4 kept failing.
smartctl -a /dev/sdc;
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-4.14.22] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Short INQUIRY response, skip product id
A mandatory SMART command failed: exiting. To continue, add one or more ‘-T permissive’ options.
root@Temple-datasafe ~ # smartctl -a /dev/sdc -T permissive;
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-4.14.22] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Short INQUIRY response, skip product id
=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature: 0 C
Drive Trip Temperature: 0 C
Read defect list: asked for grown list but didn’t get it
Error Counter logging not supported
Device does not support Self Test logging
The other two drives look normal.
By the way, I have went through this before on this NAS. I used Active @KillDisk utility to erase the drives and rotate the four drives that I have but, the issue returned.
I will reach out to WD support tomorrow to see what they can suggest.
I am only using 3 drives right now as the 4th would have been the spare.
Here is drive 1
smartctl -a /dev/sda;
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-4.14.22] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD60EFZX-68B3FN0
Serial Number: WD-CA11UAJK
LU WWN Device Id: 5 0014ee 26a48a607
Firmware Version: 81.00A81
User Capacity: 6,001,175,126,016 bytes [6.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5640 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Nov 8 21:34:19 2023 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (62760) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 664) minutes.
SCT capabilities: (0x303d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA _of_first_error
1 Short offline Completed without error 00% 5916 -
2 Short offline Completed without error 00% 5913 -
3 Short offline Completed without error 00% 5882 -
4 Short offline Completed without error 00% 5880 -
5 Short offline Completed without error 00% 5867 -
6 Short offline Completed without error 00% 5697 -
7 Short offline Completed without error 00% 5632 -
8 Short offline Completed without error 00% 5094 -
9 Extended offline Completed without error 00% 4941 -
#10 Short offline Completed without error 00% 4931 - #11 Short offline Completed without error 00% 3963 - #12 Short offline Completed without error 00% 3918 - #13 Short offline Completed without error 00% 0 -
Oh, the first 3 drives have the same drive type installed WD Red Plus 6TB drives. If I reboot the drive shows up for a while - SMART data is assessable from the web dashboard but, eventually, it flags the drive as bad.
The S.M.A.R.T. data displayed by the dashboard is a crock of BS because it intentionally omits the RAW_VALUE attribute. Otherwise, without including results from the problematic drive, what’s the point?
After I reboot the NAS, there is a few minutes before it times out where SSH allows me to obtain the SMART data. Here is what I have for Drive 3.
smartctl -a /dev/sdc;
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-4.14.22] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD60EFZX-68B3FN0
Serial Number: WD-CA12SLUK
LU WWN Device Id: 5 0014ee 214f3ade0
Firmware Version: 81.00A81
User Capacity: 6,001,175,126,016 bytes [6.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5640 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Nov 8 22:20:14 2023 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (64560) seconds.
Offline data collection
capabilities: (0x11) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 683) minutes.
SCT capabilities: (0x303d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
1 Short offline Completed without error 00% 5918 -
2 Short offline Completed without error 00% 5916 -
3 Short offline Completed without error 00% 5880 -
4 Short offline Completed without error 00% 5878 -
5 Short offline Completed without error 00% 5867 -
6 Short offline Completed without error 00% 5697 -
7 Short offline Completed without error 00% 5632 -
8 Short offline Completed without error 00% 5094 -
9 Extended offline Completed without error 00% 4941 -
#10 Short offline Completed without error 00% 4931 - #11 Short offline Completed without error 00% 3964 - #12 Short offline Completed without error 00% 3918 - #13 Short offline Completed without error 00% 0 -
The drive looks ok, except for a number of UDMA_CRC_Error_Count errors, which generally indicates an issue with the SATA connection, but the errors could also be caused by the drive itself.
My guess would be that there’s an issue with the SATA backplane within the NAS itself, and swapping out the drive would likely have zero effect.
Personally, I doubt that the problem is gone for good. SATA problems are often caused by dirty connectors, either on the backplane, the drive, or both. Perhaps a few well placed shots of canned air might do the trick?
It could also be a hardware problem, but without extensive testing, and perhaps a bit of trial and error, there’s no way to know for sure.
Well, while I was setting up a new PR4100, the infamous “Drive Bay 3” error appears shortly after powering up the unit. Moving the NAS hardware to a location that was unobstructed for good air flow didn’t help.
Adding an external fan (old desk fan with fabric fins) that would direct airflow continuously into the back of the unit has kept the unit temperature from 50+ degrees centigrade down to 38 degrees. Thus far, the drive failure error hasn’t occurred.
I am running the latest firmware therefore, I am planning to make a modification to the hardware to override the fan control. Some type of external switch to drive the fan (with a PWM value) of my choice should permanently fix the issue. I am sure there is some type of desktop PC fan driver circuit that I can add to the hardware to make an elegant solution.
Long story short, the PR4100 has a thermal management problem with the latest firmware (hardware cantation.)
