NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ayodeji13
Apr 21, 2016Aspirant
RN202 Web Interface not starting!
I just uninstalled transmission app and now I can't get into the interface. I'm getting 'Err_connection_refused' in chrome. Help!
JennC
Apr 21, 2016NETGEAR Employee Retired
Hello ayodeji13,
Can you still get to the shares of the NAS? Have you tried rebooting the NAS?
Welcome to the community!
Regards,
ayodeji13
Apr 22, 2016Aspirant
Progress!
I rebooted and got into readyNAS (yay!). But I still can't access the shares in windows anymore. :(
I have these messages in my logs
| Fri Apr 22 2016 11:58:33 | Disk: Detected high command timeouts: [60] on disk 2 (Internal) [ST6000DM001-1XY17Z, Z4D2QXDG]. This condition often indicates an impending failure. Be prepared to replace this disk to maintain data redundancy. | |
| Fri Apr 22 2016 11:57:07 | System: ReadyNASOS background service started. | |
| Fri Apr 22 2016 11:56:52 | Volume: System volume root's usage is 100%. This condition should not occur in normal conditions. Contact technical support. |
- StephenBApr 22, 2016Guru - Experienced User
Of course both are concerning, but the full root volume is why you can't access the NAS.
Do you have ssh enabled? Did you install transmission manually, or did you use super_poussin's app?
- ayodeji13Apr 22, 2016Aspirant
I installed transmission via the UI (Apps -> Available apps). BTW, its still showing transmission under my installed apps. I had clicked 'remove' before this whole thing started, so I guess it didn't uninstall.
In system--services, SSH is NOT enabled.
Hope that helps
- StephenBApr 22, 2016Guru - Experienced User
The OS partition needs to be cleaned out.
Options are
(a) contact support, and have them do it remotely. Alternatively, someone from Netgear who posts here might reach out to you and offer.
(b) Enable ssh, and troubleshoot it yourself.
(c) delete all logs (system and backup) from the admin ui, and see if that helps.
(d) do a factory reset, and restore all the data.
If you aren't familiar with linux commands, then you probably shouldn't attempt (b).
The risk with (c) is that it might not address the real root cause.
You should probably also power down the NAS and test disk 2 in a PC with Seatools.
Related Content
- Mar 26, 2017Retired_Member
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!