Posting as I didn’t find this exact same symptom combination herein, though several posts gave me hope that the “alert” algorithm was the real problem. If you encounter this same combination, something to try.
MyCloud Mirror 2 Bay, Gen 2, 4TB, RAID 1, circa Oct, 2017
First issue I’ve had with this unit in just short of 6 years.
Drive 1 LED showed solid red. Dashboard indicated RAID was Healthy, Raid 1 was Good, and Drive 1 was Bad. Seemed odd that Raid could be Healthy/Good with a Bad Drive. S.M.A.R.T results for both drives were identical. Quick Test on both drives came back Good.
Rebooted MyCloud from dashboard and all issues resolved. Possible(?) that running the Quick Test reset some internal register.
'Twas my lucky day. Hope it holds but I still obtained a new (spare) drive as insurance.
Have you opened a Support Case? If not opened, for more information, please contact the WD Technical Support team for the best assistance and troubleshooting: https://support-en.wd.com/app/ask
Yes, Incident: 230908-000172
The response I received was prompt but I had continued to search the WD Community in the meantime and got enough clues that I tried something on my own. That actually resolved the issue with less effort than the response suggested. The response was as follows:
I would suggest you to please turn off the device and remove the drive one by one, then insert them back in the same bay you removed from (Left drive on the Left side and Right drive on the right side.) and then check if issue get resolved or not.
if issue still persist you can perform drive test using the link below and share screenshot of test result with us
This fixed my issue. The same condition recently returned and my “solution” worked again. I should add that although I’ve alerts ON, I received nothing. I just happened to notice the drive 1 light was red. So I’m thinking this is actually a false positive for the drive.
I’ve had the exact same thing happen to me 4 times between March 2023 and October 2023 (~20 months). The Red LED comes on in the front indicating a BAD disk, and it has always been Disk 1. RAID Health is Healthy, even with a BAD Drive 1.
When following the procedure described by WdMc.48 I was able to reset the status to GOOD.
Settings>Utilities>System Diagnostics> QUICK TEST
Settings>Utilities>Device Maintenance> REBOOT
I wish I read this post earlier, because I’ve spent over $400 replacing the 4TB WD Red Pro Drives 3 times.
I will detail my history below with some more specifics. I’ve gotten a solid 8.5 years out of Drive2, original with the unit, and it keeps going. There was a major update to MyCloud OS 5 and a variety of firmware updates when my problem crept up, maybe this is causing this source of this behavior…
2016-04-06: Purchased WD 8TB My Cloud Mirror Gen 2 (running in RAID1, i.e. 4TB of mirrored storage) 2016-04-10: Upgraded to Firmware Version 2.11.140.0321.2016
.
.
. 2020-10-25: Upgraded to Firmware Version 2.40.157.1015.2020 2020-12-08: Upgraded to Firmware Version 2.41.116.1117.2020 2021-12-07: Upgraded to Firmware Version 2.41.121.1115.2021 2022-01-01: Upgraded to Firmware Version 5.18.117.1022.2021 2022-01-06: Started getting noticed to Upgrade to My Cloud OS 5 to maintain remote access 2023-03-01: Received an email to update to firmware version 5.25.132 and above to address critical vulnerabilities, and remote access will be lost starting 2023-03-15. 2023-03-21: Drive 1 was indicated as BAD. Date of replacement with 4TB WD Red Pro. 2023-03-31: Upgraded to Firmware Version 5.26.119.1229.2022 2024-06-11: Drive 1 was indicated as BAD. Date of replacement with 4TB WD Red Pro. 2023-07-07: Upgraded to Firmware Version 5.26.300.0523.2023 2024-09-08: Drive 1 was indicated as BAD. Date of replacement with 4TB WD Red Pro. 2023-09-17: Upgraded to Firmware Version 5.28.105.0409.2024 2024-10-11: Drive 1 was indicated as BAD. Followed steps #1 and #2 and everything reset to GOOD. Device uptime was about 30 days. (Currently running Firmware 5.28.105)
If issue reappears, I will update.
Other than this one issue, I really love this product. It has served me solidly for a while and acts as a great NAS for my family network.
Sadly when I contacted WD regarding getting replacements for the drives they insisted on me sending the “BAD” drive back to WD to inspect. I understand from a technical/engineering perspective why they would want this (not to mention to “trust” they are not getting scammed), but I don’t think it is prudent for me to release all my information. They would not accept my request to be exempt for returning them because I did not have a corporate letterhead (i.e., the small customers do not matter).
Carlton,
Saw your comment a couple months ago but got busy with other things and it slipped my mind. Glad it worked for you too. Having my NAS do it again recently reminded me. And, as before, I just happened to notice the red light on the NAS. I’d gotten no alerts. Happily, the fix I found before worked once again.
I did buy a replacement drive but hadn’t taken it out of the box when I stumbled upon the “fix”. However I decided to keep it on hand just in case a drive does ■■■■ out.
My biggest disappointment is that WD apparently refuses to acknowledge there’s an obvious glitch in their product, be it hardware or software, and let folks know. My guess is they haven’t because they don’t know what’s actually happening, and they don’t want to promote a fix when they neither know what’s happening nor how the fix is correcting it. I just hope that anyone who has this issue manages to find this post.
