I few weeks ago I had a Drive Fault notice. It may have been there for a while (perhaps since the last update - I’m now on 5.26.300 OS) but I haven’t logged into my drive for a quite a while. I did a Scan Disk scan and then a full system scan and no problems were found. I rebooted and then my drive status was Healthy.
Yesterday I had the notice again and repeated the procedure and my drive status is now Healthy again.
How do I determine if this is a real problem with the drive or a bug in the diagnostics software?
I’ve enabled SSH, where do I enter the command?
Thanks, I’ll put a post in that thread to maintain continuity.
Feel free.
I have no clue whether it’s a widespread issue, but @WDStaff does not seem ready to recognise it either as a software or hardware issue. I had support explaining me that despite there was a red light and a warning in the admin panel, it did not mean that there was an issue…
The very point of my comment was to let know that it seems widespread.
1 Like
=== START OF READ SMART DATA SECTION ===
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 188 166 021 Pre-fail Always - 3591
4 Start_Stop_Count 0x0032 035 035 000 Old_age Always - 65378
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 028 028 000 Old_age Always - 53036
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 177
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 129
193 Load_Cycle_Count 0x0032 179 179 000 Old_age Always - 65964
194 Temperature_Celsius 0x0022 111 093 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 200 200 000 Old_age Offline - 0
Since my drive is out of warranty I suspect that WD would tell me that my drive has failed and I need to buy a new WD My Cloud.
Wonder if WD has rolled in some form of WDDA into OS5 firmware like they did with Synology DSM 7.x where it trips after the drive reaches its expected life time and indicates the drive should be replaced even though the drive otherwise reports fine.
Instructions to Suppress or Disable WDDA Warning Messages in Synology DiskStation Manager
Understanding WDDA Warning On WD Drives: Should You Replace Your NAS Drives?
I thought I’d post a follow-up. I have not had the problem since I updated to 5.27.157 firmware.
I’ve been doing a bit of digging, and believe I may be close to discovering the true source of many mysterious drive fault notices with a red drive LED that returns to normal after a reboot.
Out of curiouisity, what drives do you have? To find out the exact drive model and family, the following commands can be executed via an SSH connection. Some commands may not be needed, depending on the number [a,b,c,d] of drives installed.
smartctl -i /dev/sda;smartctl -i /dev/sdb;smartctl -i /dev/sdc;smartctl -i /dev/sdd;
Look for “Model Family” and “Device Model”.
Like @RKCRLR I did not have any problem since updating my My Cloud EX2 Ultra to 5.27… (although I had to reboot once due to power failure a few days ago) until today…
Back to weird business: no notice, but the status is now “mauvais” (or “fault”) and the light of drive 1 is red. That’s the less than one year old WD RED Pro I bought directly from WD to change an alleged faulty drive (and that was already RMAed)…
So what’s your clue?
@Cerberus, here are the infos you ware asking @RKCRLR for:
smartctl -i /dev/sda
Model Family: Western Digital Red Pro
Device Model: WDC WD8003FFBX-68B9AN0smartctl -i /dev/sdb
Model Family: Western Digital Red
Device Model: WDC WD80EFAX-68KNBN0
This drive (FFBX) uses CMR technology, and is suitable to use with RAID, but the S.M.A.R.T. status should be checked for errors.
This drive (EFAX) uses SMR technology, and is NOT suitable to use with RAID, and the S.M.A.R.T. status should definitely be checked because they tend to fail rather quickly.
CORRECTION: 8TB and up EFAX hard drives use CMR technology.
To verify the hard drive type and S.M.A.R.T. status, use either of the following options. The app I created also updates the smartctl database and reports the drive self-test status.
Option 1:
Enable SSH, then run the following commands, one at a time. The results can be easily copied and posted to the forums for further analysis if desired.
smartctl -a /dev/sda;smartctl -a /dev/sdb;
How to Access WD My Cloud Using SSH (Secure Shell)
Option 2:
Install the “Get S.M.A.R.T.” app for My Cloud OS5 NAS devices, available from the list below. The preformatted results can be easily copied and posted to the forums for further analysis if desired.
1 Like
Hi thanks for looking into this.
The “EFAX” drive came with my MCEX2U, I have a 2x 8TB and I remember reading that the EFAX series was CMR starting with 8TB and over.
Nevertheless, that’s the FFBX drive that is said to be faulty.
I ran the test you were referring to, see below.
They seem both to be passed.
And quick test said everything was OK, so I don’t understand what is faulty… it seems random to me. You said you had a educated guess about what was causing it?
Best,
root@MyCloudEX2Ultra ~ # smartctl -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [armv7l-linux-4.14.22-armada-18.09.3] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red Pro
Device Model: WDC WD8003FFBX-68B9AN0
Serial Number:
LU WWN Device Id: 5 000cca 0c6d5533e
Firmware Version: 83.00A83
User Capacity: 8,001,563,222,016 bytes [8.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon Dec 4 00:42:45 2023 CET
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: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
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: ( 87) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: ( 817) minutes.
SCT capabilities: (0x003d) 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 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0004 133 133 054 Old_age Offline - 92
3 Spin_Up_Time 0x0007 225 225 024 Pre-fail Always - 431 (Average 292)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 12
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000a 100 100 067 Old_age Always - 0
8 Seek_Time_Performance 0x0004 128 128 020 Old_age Offline - 18
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 3914
10 Spin_Retry_Count 0x0012 100 100 060 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 171
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 171
194 Temperature_Celsius 0x0002 105 105 000 Old_age Always - 57 (Min/Max 23/64)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 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% 3912 -
# 2 Extended offline Completed without error 00% 2974 -
# 3 Short offline Completed without error 00% 2958 -
# 4 Extended offline Completed without error 00% 1192 -
# 5 Short offline Completed without error 00% 1172 -
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.
root@MyCloudEX2Ultra ~ # smartctl -a /dev/sdb
smartctl 7.2 2020-12-30 r5155 [armv7l-linux-4.14.22-armada-18.09.3] (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 WD80EFAX-68KNBN0
Serial Number:
LU WWN Device Id: 5 000cca 099eb9e81
Firmware Version: 81.00A81
User Capacity: 8,001,563,222,016 bytes [8.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5400 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon Dec 4 00:47:23 2023 CET
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: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
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: ( 87) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: ( 868) minutes.
SCT capabilities: (0x003d) 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 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0004 127 127 054 Old_age Offline - 112
3 Spin_Up_Time 0x0007 177 177 024 Pre-fail Always - 452 (Average 466)
4 Start_Stop_Count 0x0012 099 099 000 Old_age Always - 7818
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000a 100 100 067 Old_age Always - 0
8 Seek_Time_Performance 0x0004 128 128 020 Old_age Offline - 18
9 Power_On_Hours 0x0012 097 097 000 Old_age Always - 25282
10 Spin_Retry_Count 0x0012 100 100 060 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 112
192 Power-Off_Retract_Count 0x0032 093 093 000 Old_age Always - 8530
193 Load_Cycle_Count 0x0012 093 093 000 Old_age Always - 8530
194 Temperature_Celsius 0x0002 116 116 000 Old_age Always - 56 (Min/Max 12/63)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 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% 25280 -
# 2 Extended offline Completed without error 00% 24343 -
# 3 Short offline Completed without error 00% 24326 -
# 4 Extended offline Completed without error 00% 22559 -
# 5 Short offline Completed without error 00% 22540 -
# 6 Short offline Completed without error 00% 17737 -
# 7 Short offline Completed without error 00% 17735 -
# 8 Short offline Completed without error 00% 17480 -
# 9 Extended offline Completed without error 00% 17013 -
#10 Short offline Completed without error 00% 16999 -
#11 Short offline Completed without error 00% 15046 -
#12 Extended offline Aborted by host 80% 15044 -
#13 Short offline Completed without error 00% 15042 -
#14 Short offline Aborted by host 90% 15042 -
#15 Extended offline Completed without error 00% 13694 -
#16 Short offline Completed without error 00% 13681 -
#17 Extended offline Aborted by host 90% 13679 -
#18 Short offline Completed without error 00% 13652 -
#19 Short offline Completed without error 00% 13124 -
#20 Short offline Completed without error 00% 11884 -
#21 Extended offline Completed without error 00% 10004 -
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.```The WD8003FFBX hard drive appears to be fine, per the S.M.A.R.T. results. Post the results of the following command, which will output kernel log warnings and errors.
dmesg -t -l warn,emerg,alert,crit,err;
You’re right, the WD80EFAX hard drive is CMR. I was distracted at the time and could have sworn it was a 6TB drive. Instinctively, when I see EFAX I think “trouble”. Regardless, the EFAX drive appears to be fine, per the S.M.A.R.T. results.
1 Like
Here you are.
Does not look very helpful though.
dmesg -t -l warn,emerg,alert,crit,err;
mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling
mvebu-pmsu: CPU idle is currently broken on Armada 38x: disabling
marvell-nfc f10d0000.flash: Timeout on CMDD (NDSR: 0x00000080)
marvell-nfc f10d0000.flash: Timeout on CMDD (NDSR: 0x00000280)
(NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
ahci-mvebu f10a8000.sata: masking port_map 0x3 -> 0x3
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
jnl: loading out-of-tree module taints kernel.
ufsd: module license 'Commercial product' taints kernel.
Disabling lock debugging due to kernel taint
restart sysinfod...
scandisk for power failure now.
volume_stop.sh /mnt/HD/HD_a2...
kill_process.sh /mnt/HD/HD_a2...
kill_process.sh done.
volume_stop.sh done.
Unfortunately you’re correct, but the kernel log likely won’t have any related errors if the NAS has been rebooted since the problem occurred. It was a long shot.
Since the hard drives are not a matched pair, it’s possible that may contribute to the problem, but I can’t say for certain.
It’s more of a hunch than a guess, and I’m still investigating the problem, so I can’t really draw any conclusions just yet because more information is needed. Honestly, this problem has been a tough nut to crack, but that’s the kind I like best.
1 Like
Thanks again.
It’s been back since the last reboot. It did not occur before after updating to 5.27.
It’s possible indeed, but supporte assured me it should go fine before I bought the Pro. I wanted a 5y warranty.
Let me know if I can help.
Part of my hunch is that the outdated My Cloud OS5 Linux kernel is somehow related to the problem. It’s difficult to explain, but with each base Debian packages update (Buster to Bullseye), WD increases the likelyhood of very subtle incompatibilities creeping into the mix.
If it happens again, run the kernel log command and save the output, which is where most errors are likely to be located. The following command may also reveal useful information, but type it very carefully, because mdadm can really mess things up if used improperly.
mdadm --detail /dev/md1;
Well, it’s currently happening so here it is:
root@MyCloudEX2Ultra ~ # mdadm --detail /dev/md1;
/dev/md1:
Version : 1.0
Creation Time : Sun Jan 22 15:44:08 2023
Raid Level : raid1
Array Size : 7809830720 (7448.03 GiB 7997.27 GB)
Used Dev Size : 7809830720 (7448.03 GiB 7997.27 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Mon Dec 4 02:04:55 2023
State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Consistency Policy : bitmap
Name : MyCloudEX2Ultra:1 (local to host MyCloudEX2Ultra)
UUID :
Events : 39009
Number Major Minor RaidDevice State
2 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
Nothing stands out as being unusual, just a typical RAID1 array. Does the kernel log have anything new?
Another possibility is that there may be filesystem errors. You can run a full “Scan Disk” via the dashboard, or do it manually using the following procedure.
Execute the following commands to kill running processes and unmount the /dev/md1 device.
/usr/sbin/kill_process.sh /dev/md1;umount /dev/md1;
Next, as quickly as possible after running the first two commands, run the following command to start the e2fsck filesystem repair process. It will probably take a long time (hours to days) to run, and it may generate error messages, etc.
Type the command EXACTLY as shown below, and DO NOT close the SSH window until it’s finished.
e2fsck -p -f -C 0 /dev/md1;
