Re: ReadyNAS Pro 6 not working, booting, but not working

jasongrimme · ‎2015-10-20

I have an RNP6000 that shutdown on me. When I boot it up, everything looks fine, it detects all the desk, the status on the admin page is OK, etc. However, all the file protocols are turned off, if I try to make change changes n the admin page they do not persist. When I go to the status/logs page, no logs exists. I tried a firware reset but no luck. I then took all the drives out and put in 3 different drives, and was able to initialize the unit sucessfully.

So I have a friend at work letting me borrow his readynas pro6 tomorrow, but I'm fearing the worst. I also have an ultra6 I could move the drives into, but i'm wondering if I'm screwed. Is it worth booting into tech support mode and asking/paying Netgear to take a look? I'd hope they'd at least take a look for me, I'm a pretty loyal readynas customer, and willing to buy a 316 or 516 if I can move my drives to it, but I'm afraid it's not a hardware problem 😞

StephenB · ‎2015-10-20

Is SSH enabled?

Do you have crashplan installed?

It could be a full OS partition - which Netgear can fix fairly easily.

View solution in original post

StephenB · ‎2015-10-20

Is SSH enabled?

Do you have crashplan installed?

It could be a full OS partition - which Netgear can fix fairly easily.

jasongrimme · ‎2015-10-21

It was crashplan and a full OS partition, thank goodness someone else on here had it happen to them first (but I do feel bad for the grief it must have caused them :().

jasongrimme · ‎2015-10-21

just to be complete, in case someone else stumbles onto this thread, here's the issue and how to remedy it. (putting all steps I used, with detail, so somethings are probably obvious to a lot of ReadyNas uses, but figured having all the steps in one place can't hurt)

https://community.netgear.com/t5/Using-your-ReadyNAS/ReadyNAS-Pro-6-web-admin-and-data-inaccessible/...

Boot into 'Tech Support' mode

* power off the NAS

* push and hold down the reset button (pinhole button on the back)

* while still holding down the reset button, power on the NAS - after about 15-30 seconds, the screen will display "Boot Menu"

* release the reset button once the "Boot Menu" is displayed

* press the backup button on the front of the NAS to scroll through the options until you get to "Tech Support"

( NOTE: Be sure to NOT leave this menu on Factory Defaults or choose Factory Defaults, this will erase all your data!)

* with the menu on 'Tech Support', push the reset button in the back, the NAS will now boot into tech support mode

Telnet to the NAS

* telnet to the IP address of the NAS

* logon with user=root, pw=infr8ntdebug

(if this PW get's removed, try this link - netgear.nas-central.org/wiki/TechSupportMode)

Mount the OS partition

* start_raid.sh

* mount /dev/md0 /sysroot

Delete the CrashPlan upgrade files

* go to the /usr/local/crashplan/upgrade

- 'cd /usr/local/crashplan/upgrade'

* remove all the 1*.* files and folders

- 'rm -rf 1*.*'

all this info was gleemed from other posts, manuals, etc online, I guess putting it all here so when this happens again to me I can find it 🙂

StephenB · ‎2015-10-21

@jasongrimme wrote:

It was crashplan and a full OS partition, thank goodness someone else on here had it happen to them first (but I do feel bad for the grief it must have caused them :().

I noticed it early - just happened to be using ssh, and noticed that the OS partition was completely full. The NAS hadn't locked up yet, and I was able to delete the upgrade files before that happened. A few minutes of panic, but no grief...

Now that you are running, you do need to upgrade java, so the crashplan upgrade will complete.

jasongrimme · ‎2015-10-21

Thanks StephenB, I actually did do all of that last night, too. I didn't note all the 1*.* files/folders in my crashplan/upgrade directory, I just deleted them. Was that from it trying to auto-upgrade to 4.4.1? Will the files stop downloading there now that I'm on 4.4.1?

StephenB · ‎2015-10-21

@jasongrimme wrote:

Thanks StephenB, I actually did do all of that last night, too. I didn't note all the 1*.* files/folders in my crashplan/upgrade directory, I just deleted them. Was that from it trying to auto-upgrade to 4.4.1? Will the files stop downloading there now that I'm on 4.4.1?

I saw a 1*.* folder (and perhaps a jar) left behind on 4.4.1 also. However, since it worked there was no repeating download problem.

I'm not sure if future crashplan releases will also fail to clean up their install properly - if they make this mistake the next time around, I'll probably create a symlink for /crashplan/upgrade on the C volume.

I also suggest moving the crashplan cache (there are instructions here: http://support.code42.com/CrashPlan/Latest/Troubleshooting/Reassigning_Cache_Folder_To_A_Different_D...