NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNas 2120 v2 RAIDar Status Management Service offline
I have ReadyNas 2120 v2 with firmware 6.10.8 I am able to browse files but admin page wont load and backups not working When i checked via RAIDar it shows as Status Management Service offline Whe...
Dhalz3m wrote:
Volume root is 100% full
This is the reason you can't access the web ui. If you don't address it, you will end up with configuration issues, since the config files are all in the volume root.
Begin by backing up your data.
After that is complete you have two options:
- Do a factory default, rebuild the NAS, and reload the data.
- Repair the full root problem with ssh (removing the files that have filled it).
If ssh is not enabled already, then the alternative for (2) is to reboot in tech support mode, and connect with telnet. From there you'd need to mount the OS partition manually.
If you aren't already familiar with the linux command line, then the first option is best.
Thank you for quick response.
Can this we fixed without losing data.
Dhalz3m wrote:Can this be fixed without losing data.
That is the second option I outlined. Are you familiar with the linux command line?
No matter what option, the data is at risk, so I am strongly recommending that you back it up before proceeding.
Its ok if incase i lose data as it is a backup device.
Yes i am ok with linux commands.
I am at RAIDar i tried to enable Remote Support and now its shows Status as Remote support.
However i can see a Debug Code 60106.
What you need to do is boot the NAS in tech support mode. Possibly you are already in that - hard to day, as there is also a "Secure diagnostic mode". In any event, instructions are on pages 17-18 here: https://www.downloads.netgear.com/files/GDC/RN2120/ReadyNAS_OS6_Rackmount_HWM_EN.pdf
From there, you access the NAS with telnet. Personally I use the putty client (on windows) to do that. The username is root, the password is infr8ntdebug
Once in, enter
rnutil chrootwhich will both start raid, and chroot.
I don't recall if you also need to enter this afterwards:
mount /dev/md0 /sysrootOnce in, you can look for large files in the OS partition, as usually there is just one or two that are causing the problem.
Normally the OS partition is 20-25% full.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
