Also I tried installing RAIDar on another machine on the same network to access the NAS from there and I got this message:
Your connection is not private Attackers might be trying to steal your information from 192.168.1.XXX (for example, passwords, messages, or credit cards). Learn more NET::ERR_CERT_AUTHORITY_INVALID This server could not prove that it is 192.168.1.XXX; its security certificate is not trusted by your computer's operating system. This may be caused by a misconfiguration or an attacker intercepting your connection.
Proceed to 192.168.1.XXX (unsafe)
I feel that this has something to do with the issue.
Also I tried installing RAIDar on another machine on the same network to access the NAS from there and I got this message:
Your connection is not private Attackers might be trying to steal your information from 192.168.1.XXX (for example, passwords, messages, or credit cards). Learn more NET::ERR_CERT_AUTHORITY_INVALID This server could not prove that it is 192.168.1.XXX; its security certificate is not trusted by your computer's operating system. This may be caused by a misconfiguration or an attacker intercepting your connection.
Proceed to 192.168.1.XXX (unsafe)
I feel that this has something to do with the issue.
This is completely normal, and is because the NAS uses a self-signed certificate. You must have either trusted the certificate on the other machine, or you set a security exception (possible with firefox).
Right now it says (PLEASE DON'T TELL ME I'VE LOST MY DATA)
Shares on RAID Volumes No shares exist. Shares on USB Storage Devices No USB shares exist. Plug in a USB storage device and click Refresh to display a USB share.
The log for the LeafP2P service used by the discontinued ReadyNAS Remote and ReadyNAS Replicate had grown to over 3GB in size.
As the root volume was full when the system went to change configuration files there was no space to write them so they were overwritten with empty files.
I would suggest anyone still running RAIDiator firmware uninstall ReadyNAS Remote and Replicate if you haven't already and then if comfortable with SSH, login and check for LeafP2P.log under /var/log and remove it.
Another issue unrelated with the problems not being able to connect is that disk 1 has over 4000 reallocated sectors and failed the SMART self-assessment test. The disk needs replacing.
