I had this for more than 3 years and it has never given me problems till now. I realised I had an old firmware so upgraded (very painfully) to the latest version. that didn’t help till i read this post (which is unfortunately closed) it mentions to turn off mionet and twonkyserver and
also mentions
The fix, suggested by magugu, is to edit /usr/mionet/monitorCVM.sh and just below the comment lines at the top (prefixed by ‘#’) add the following:
Start of hack to make Mionet obey startup flag
if [! -f “/etc/.mionet_on_startup”];
then exit 1 fi
End of hack to make Mionet obey startup flag -------------------------------------
My Qs 1. Does one disable NAS from going into standby?
-
How do you edit this file? Can you please provide some detailed command lines and explanation like the one for the disabling mionet and twonkyserver? http://community.wd.com/t5/Other-Network-Drives/Drive-Becomes-Un-Accessible-After-short-use-II/td-p/38659
-
Why does WD staff not providing a fix for this? I see so many people having problems with this issue and with more data being stored-people may be coming closer to optimum storage with issues like these!! i still have 220G space and I am having trouble someone please keep this link open till it is resolved!
I have reset the NAS by pressing the button off and on again (number of times now)
Had static IP but now after reset has become dynamic and yet connection is not regained
Connection comes on briefly but is lost again
Light is on (white long light)
Can ping the IP address but not by name
WD discovery tool will not find it
Windows explorer mapped drive doesn’t find it (win 8) -it was working relatively well till about 1 week ago, after which I did an upgrade to new firmware and it has gone worse
managed to get into SSH and followed the instructions as per the link above
but after reboot cannot connect now
