NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
restore
10 TopicsReadyNAS Pro Pioneer - Solutions Please - Bad controller?
Ah the most dreaded topic. I've gotten a bit complacent since it's been so reliable, I double back up but not everything :( and of course I need it sigh. So I shut my pro pioneer down to replace the battery in the UPS it was connected too. Now it won't power up! I figure no big deal, I have a 550w power supply lying around, I'll just plug it all together to get it running again. I get the wiring all sorted out and the power supply keeps tripping out. I tested no drives plugged and it still trips out. I tested with the 3 molex disconnected and it looks like it boots ok (I didn't bother going very far with it) I tested individual molex and it looks like only the top one is ok that doesn't trip the system. the bottom two make power supply trip out or something. I guess bad controller? Anything else I should try? what are my options? Thank you for your timeSolved5.4KViews0likes20CommentsFull recovery
My apologies if this has been answered before; I searched but did not find anything that addresses how to do a complete recovery from start to finish. I'm swapping out my spinning platter disks and replacing them with SSD. Because the SSD is smaller than the previous HDD (1tb spinning, 512gb solid) I can't just swap them out one at a time and rebuild (as far as I know). Instead I made full backups of the data directory and the configuration. I've been able to recover the full configuration (except for the hostname, that had to be manually changed). But I see no way to set up a recovery job that restores all shares and the home directories. I can individually recover each share (although that will be time consuming, I'd rather kick off a single process) but I see no way of recovering the home directories; I can't select home as a destination for the recovery process.Solved4.8KViews0likes2CommentsWNDAP350 CLI Factory Default syntax
Hi, Firmware has left me with a cut down 'cloud connect' type GUI. I need to reset via CLI as suggested by the firmware upgrade notes as the button reset did not restablish the full GUI. I have tried the suggested restore-configuration /etc/default-config And an error appears asking for restore host username password All CLI command lines are prefeixed by netgear70B528 which I assume is 'host' But this fails with bad address. So I subsituted the default IP address for host. This time it said connection refused (or similar). Is this because I need to enable something via the CLI first? If so what? I tried the CLI restore-configuration command and this simply did the same as the button reset. What do I do? AndySolved4.8KViews0likes3CommentsRestore function broken: Apps do not work correctly after full restore
When rebuilding a Ultra 6 Plus that had a bad RAID (800GB missing in a 14.4TB array), I had serious problems getting Apps to work. Original System: U6+ (4GB RAM), OS 6.4.1, 14.4TB array. Apps installed: Transmission (as backup: installed but not normally active), Sickrage was NOT installed on the original system. Rebuild procedure: Removed disks and zeroed, Factory reset, started with 1 3.6TB HD to rebuild array. Did a restore from previous build, then added Transmission, Sickrage from Apps>Available Apps. Here's what happened: Transmission: config.json file showed rpc port set to 9091, rpc whitelist at 127.0.0.1. Fixed by SSH'ing in then manually editing file to change port to 8181 (to match ReadyNAS "Launch" specs) and adding 192.168.0.* to whitelist. Web interface available. Sickrage: No files present in /apps/sickrage/app-config. Zip. Nada. Nothing. I considered adding everything in by hand, then decided to rebuild differently. to see if I could fix it. By doing another factory reset then adding apps BEFORE the restore, everything appears to be correct (Transmission: good settings.json file, Sickrage has files in /apps/sickrage/app-config). HOWEVER, when doing an initial update within Sickrage, it breaks the app. The config files are there, but the web interface no longer comes up. I then uninstalled then reinstalled Sickrage to see if it would come up: After reinstalling, there were once again No files present in /apps/sickrage/app-config, so the default install seems to be broken. Apparently, doing a full restore permanently kills the ability to add/change/upgrade/reinstall apps. Is this a Apps problem, or a problem with how OS6 treats App installation after a restore? I suspect the latter. Would choosing to do a partial restore be possible? Is this a "Services" or "Misc" Restore problem? I would rather not have to rebuild my shares, users, services manually. However, if it is the only way to work around the problem with this obviously broken Restore, I'll do so. Logs downloaded and available upon request. Comments, anyone? I'll be doing yet another factory reset and a partial restore to see if I can get around this. <sigh>Restore apps from backup
Hi Everyone, Running into a bit of an issue. I was having some performance issues with my RN102 (OS 6.6.1), so I decided a factory reset was in order. I backed up the entire /data volume, as well as "Everything" in the configuration, then reset the NAS. I've restored the configuration, and a reverse backup from the backup disk to each individual share is in progress, but I'm not sure how to restore the apps I had installed. Is there any way to do this, or do I have to install them again individually? If I have to re-install, will my settings be restored, or will I have to reconfigure each app as well?4.1KViews0likes26CommentsRN2120v2 - Can't (completely) replicate settings between two readynas using Configuration Backup
Hi all, i have to set up several ReadyNas 2120v2 with same settings, i have to do this in an isolated subnetwork (no internet) so i'm using "Configuration Backup" in System menu. I downloaded the "configuration archive" from the first ReadyNas, checking "Everything" button. So i uploaded the configuration file to a new ReadyNas previously upgraded with the same firmware of the first ReadyNas (6.6.0), using the "Restore" function. After the reboot, i noticed that the ReadyNas restored hasn't fully configured like the first ReadyNas. While Shares, accounts and active services are replicated, Host name and Network settings remain unchanged. Any suggestions would be appreciated. Thank you.3.5KViews0likes7CommentsRN10223D really dead!
So, my ReadyNas is dead. It does not respond to any commands. I have removed the harddrives and removed all partitions (on a Windows 10). I have used a the USB Recovery Tool to flash new firmware (Version 6.6.0 (arm)). I don't know if the flash went OK but it was running for a while and then shut down by itself as expected. I have tried "Reinstall OS" as well as "Factory default. I can get into the boot menu but as I choose something like disk test, OS reinstall the only thing that happen is that the power LED is flashing for about 4-5 seconds, turns solid blue and then ... nothing. It does not accouire an IP address from my router. Am I missing something? My knowledge about Netgear is somewhat limited so any help would be appreciated. Thank you in advance, LarsSolved3.1KViews0likes10CommentsRestore process needs to work for future firmware updates
I consider it a competitive disadvatage that the restore process for my Netgear wireless R7000 router (and by all indcations, all Netgear routers) require manually reentering configuration information after some firmware updates. Instead, there should be version independent information stored in the backups along with meta data that would allow future update processes to update version independent information (e.g., stored IP addresses of dis/alllowed systems) along with meta data that would indicate during or just prior to the update procedure what feature information that differs between releases must be managed manually, ideally in a way the could be easily digitially captured and/or printed. This would greatly decrease the customer inconvenience after excectuing a 'hard reset' on the routers.Solved2.7KViews1like3CommentsIf I restore a previous config, will it change the admin password?
Hi, I did some experiments and messed up my config, but I still have access to the router through the web interface. I have an old-ish backup with a stable config, and I wanted to restore it. My problem is that I don't remember the admin password I was using when I first made that backup, as I changed it some time ago. I'm afraid that after the restore the password might revert to an older version I can't remember, and I would lose access to the router. So here's my question: when we restore from a backup, does that change the admin password too? or is it left as is? I realise that in the worst scenario, I could always reset to factory defaults and rebuild the config from scratch, but in that case, I might as well try to fix the config from its current state, at this point I'm not sure which of these would entail more work. Still, if I were able to restore from the backup without fear of it changing my password, that would be the best way. Thanks!Solved1.9KViews0likes2Comments