Similar story: details as follows:
Drive connected to Apple Airport Extreme with shielded Cat 5e cable.
Front panel LED solid green. IP address fixed at 192.168.0.24; returns pings from Mac and Linux shells. Drive worked for a month or so after last firmware update. (2.43… I think, but admin panel reported firmware up-to-date.)
The drive now does not respond to HTTP calls to its IP address. Mac Finder windows display correct network name (Ted), report “connecting…” then “The drive may not exist or is unavailable at this time.” WD My Cloud.app displays “Ted” and IP address, but reports (a) invalid SSL certificate then (b) “failed to connect to device”.
The problem has survived multiple hard shutdowns, and resets using the recessed button in the rear panel.
Tentative diagnosis: networking hardware and connection OK; firmware corrupted.
A similar problem report in this forum drew from WD a suggestion that the drive is suffering “unit fatigue”. Hardware of course has a finite working life. But this RAID drive is designed and sold for securing valuable files. In duplicate. It is therefore reasonable to expect either that the device degrades gracefully, with timely warnings to replace it, or that there is a safe recovery path for the data if the drive is allowed to fail catastrophically.
WD needs to take a view on this. It seems to have a choice of two:
- There is a robust way to recover the contents to a new drive; or
- The drive does not warn when it needs replacing before catastrophic failure from “unit fatigue”, and was thus sold unfit for purpose.
The user manual describes how to recover from failure of one of the 3Tb disks: replace it and allow the drive some hours to restore the mirroring. If WD asserts (1) then a description of how to recover from drive failure is needed.