NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
ReadyNAS 516
8 Topics
NEW: v6.6.1 = No Apps, and Inactive Volumes
Good Evening Community and NETGEAR Staff - Needless to say at the moment, I am very frustrated; the ONLY thing that consoles me, is that it seems that I am in NO WAY the ONLY person experiencing issues [ I ALWAYS hate doing updates and this proves me right ]... By now this is not anything NEW - my problems start w/ Inactive Volumes, which leads to ALL of MY DATA suddenly *poof* = GONE; which of course explains why there are NO Apps ( PlexMedia, SickRage, VPN, etc... ) nor do I have the ability to ADD any new ones. After the update ( yesterday ) - everything appeared to come up as expected / normal - it wasnt until today when I was attempting to use PlexMedia that I noticed that the system was none responsive, I also attempted to access my shared network drives and saw that it too wasnt working - as I have in the past I decided to reboot the NAS and get it back ONLINE -little did I know that I was signing my own death certificate. After taking a while to shutdown, waiting for a bit and then cold booting the device - I learned that the system is hosed ( honestly I am hoping that its a buggy OS and that everything is safely in there somewhere otherwise WTF! -apologize but honestly frustration is kicking in )... Looking through the logs, ( like many others ) I too see errors about some files affected with a virus which is funny since the anti-virus app was none responsive after the upgrade ( yes I was prepaired for that, after getting the e-mail informing me - however wasnt that supposed to have occured back in the beggining of Jan' 2017 -here we are in Feb a little back dated or delayed -No? -I figured by now it would've been safe to go back into the water -Never learn ). So like everyone else I will do my best to be patient, and if I wind up having to pay for support - then it better come w/ a Guarantee that they will Recover what has clearly been corrupt by a buggy update.Update RN516 BIOS to support VT-x
After reading the forums, it appears that I need a BIOS udate for my ReadyNAS 516 to support 64-bit VM's since VT-x is not enabled in my current BIOS as my BIOS date is pre 07/03/2013. Here is my bios_ver.log: :::::::::::::: /sys/class/dmi/id/product_sku :::::::::::::: RN516 :::::::::::::: /sys/class/dmi/id/product_name :::::::::::::: ReadyNAS 516 :::::::::::::: /sys/class/dmi/id/product_uuid :::::::::::::: 00890023-D21D-B211-8000-841B5E2740D2 :::::::::::::: /sys/class/dmi/id/board_name :::::::::::::: ReadyNAS 516 :::::::::::::: /sys/class/dmi/id/board_asset_tag :::::::::::::: To be filled by O.E.M. :::::::::::::: /sys/class/dmi/id/chassis_serial :::::::::::::: To Be Filled By O.E.M. :::::::::::::: /sys/class/dmi/id/product_version :::::::::::::: 03/18/2013 ReadyNAS-516 V1.0 :::::::::::::: /sys/class/dmi/id/chassis_vendor :::::::::::::: NETGEAR :::::::::::::: /sys/class/dmi/id/modalias :::::::::::::: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2013:svnNETGEAR:pnReadyNAS516:pvr03/18/2013ReadyNAS-516V1.0:rvnNETGEAR:rnReadyNAS516:rvrTobefilledbyO.E.M.:cvnNETGEAR:ct3:cvrToBeFilledByO.E.M.: :::::::::::::: /sys/class/dmi/id/chassis_version :::::::::::::: To Be Filled By O.E.M. :::::::::::::: /sys/class/dmi/id/bios_date :::::::::::::: 03/18/2013 :::::::::::::: /sys/class/dmi/id/bios_version :::::::::::::: 4.6.5 :::::::::::::: /sys/class/dmi/id/product_serial :::::::::::::: <REMOVED BY MODERATOR> :::::::::::::: /sys/class/dmi/id/sys_vendor :::::::::::::: NETGEAR :::::::::::::: /sys/class/dmi/id/bios_vendor :::::::::::::: American Megatrends Inc. :::::::::::::: /sys/class/dmi/id/board_serial :::::::::::::: To be filled by O.E.M. :::::::::::::: /sys/class/dmi/id/uevent :::::::::::::: MODALIAS=dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2013:svnNETGEAR:pnReadyNAS516:pvr03/18/2013ReadyNAS-516V1.0:rvnNETGEAR:rnReadyNAS516:rvrTobefilledbyO.E.M.:cvnNETGEAR:ct3:cvrToBeFilledByO.E.M.: :::::::::::::: /sys/class/dmi/id/chassis_asset_tag :::::::::::::: To Be Filled By O.E.M. :::::::::::::: /sys/class/dmi/id/chassis_type :::::::::::::: 3 :::::::::::::: /sys/class/dmi/id/board_vendor :::::::::::::: NETGEAR :::::::::::::: /sys/class/dmi/id/board_version :::::::::::::: To be filled by O.E.M. Could I please get an updated BIOS for my unit. Thank you.Solved
Install NZBGet 17.1 on ReadyNAS OS 6.6.0 (working)
Hello everyone, I spent some time with @hugbug (offical developer of NZBGet) over the weekend and let him know about the issues we are having getting a working version for OS 6.6.0. He encouraged me to use the offical installer and pretty much guaranteed it would work on OS 6.6.0, while hesitant, I took him up on his offer since he was willing to support the install should anything go wrong. Here is what you need to do to get NZBGet current version working, and best of all the update within app now works! (Note: My machine is RN516, your mileage may vary. This will not give you a visible app in the apps section of front end, but it will persist and auto-start on reboot). This will work very similiar to Sonarr as it just runs all the time in the background and start on reboot of the NAS. Webgui is always availble this way. If you are on 6.5.2, run NZBGet and backup your settings/config to your local computer Uninstall NZBGet Upgrade to OS 6.6.0 Download the installer wget -O - http://nzbget.net/info/nzbget-version-linux.json | \ sed -n "s/^.*stable-download.*: \"\(.*\)\".*/\1/p" | \ wget --no-check-certificate -i - -O nzbget-latest-bin-linux.run Start the installer (default path) sh nzbget-latest-bin-linux.run Start the installer (custom path, I chose /apps/nzbget) sh nzbget-latest-bin-linux.run --destdir /path/to/install/nzbget Test that you get the command console <nzbget-directory>/nzbget -s If you get an error about the config file not being read, you need to make sure a copy of it is in one of the directories it specifies in the error message. Just drag or make a copy of the default config file and drop it into one of the required directories such as /.nzbget Now start a web-browser and open URL http://ip-address-of-linux-machine:6789. You should see NZBGet web-interface. Default login credentials are username: nzbget, password: tegbzn6789. Once you have access to webgui, you can restore your settings you backed up in the old version. (everything backs up perfectly except the paths section. If you try to restore those form the old ReadyNAS app you will get a 404 error not found. This is because the ReadyNAS app and Official NZBGet installer use different folder structures. I had to manually recreate my paths to match the same folders but it only takes a few minutes. Run as a service (Daemon mode) <nzbget-directory>/nzbget -s Let's make NZBGet persist and auto-start on reboot (credit to HTPC setup guide for Debian installations for this one, don't use hugbug's script it doesn't work) Fire up WinSCP browse to and create /etc/init.d/nzbget or nano to create the empty file: nano /etc/init.d/nzbget Paste this code and save the file (Change the path in these 2 areas to reflect your path i.e./usr/local/bin/nzbget -D, /usr/local/bin/nzbget -Q) #!/bin/sh # Start/stop the NZBget daemon. # case "$1" in start) echo -n "Start services: NZBget" /usr/local/bin/nzbget -D ;; stop) echo -n "Stop services: NZBget" /usr/local/bin/nzbget -Q ;; restart) $0 stop $0 start ;; *) echo "Usage: $0 start|stop|restart" exit 1 ;; esac exit 0 Make the configuration file executable and update the init.d to be used at boot chmod +x /etc/init.d/nzbget && update-rc.d nzbget defaults Create /downloads folder or you will get errors that looks like this during the boot sequence: mkdir /path/to/downloads (These nzb.conf errors can be solved by creating the /downloads directory) Start services: NZBgetnzbget.conf(49): Invalid value for option "InterDir" (/downloads/inter/): could not create directory : nzbget.conf(70): Invalid value for option "TempDir" (/downloads/tmp/): could not create directory : nzbget.conf(67): Invalid value for option "QueueDir" (/downloads/queue/): could not create directory : nzbget.conf(61): Invalid value for option "NzbDir" (/downloads/nzb/): could not create directory : Now NZBGet will start automatically on boot! That's it, you are up and running with NZBGet on ReadyNAS OS 6.6.0 Again special thanks to developer of NZBGet hugbug for making this dream a reality, enjoy :)
automatically boot and shutdown for backup
Hallo, i have a ReadyNAS 516 with my data and a old ReadyNAS314 which i want to use for backup. I got it running and backing up fine. But i cant find a option to shutdown RN314 after backup is finished. I found the power timer. But this allows me just to start up at a time (okay, thats what i want) and shut down at a time (this i dont want). Is there a way to tell RN314 to shut down after the backup is finished (and not too early)? Thank you Lennardo6.6KViews0likes7CommentsMigrate from ReadyNAS 314 to ReadyNAS 516
Hello, I am looking to migrate my 4 disks from my ReadyNAS 314 to purchasing a new ReadyNAS 516. Can someone provide me step by step instructions on what I need to do to move over? Will my app structure stay intact, Plex Media Server, SickRage etc, or do I have to re-install those apps? Is it as easy as moving the 4 existing disks one by one to the ReadyNAS 516 and everything will be exactly as it was? That would be great! Any advice is appreciated. Thanks!Solved2.7KViews0likes4CommentsSurveliliance App ReadyNAS 516
Hello, We were having an issue installing the Surveliliance App so I upgraded the firmware to 6.5.1, it did have the right version then, 1.4 2-3 but the install failed. Even though it failed it showed up in the installed apps page but when I try to turn the app on I get an error, Empty Resource Error, bad NML call, 22002010000. I am also unable to uninstall Surveliliance or install different apps. This unit is on a secure network with no internet access. I've read some posts about using SSH to get into the unit but I when I go to enable I get a warning that enabling may cause Netgear to deny support. Any help will be appreciated.SolvedHelp setting up a Virtual Machine on a ReadyNAS 516
I am wanting to run a virtual machine on my ReadyNAS 516 device running the latest firmware (6.5.1) on my domain. I am tech-savy and a fast learner, but I am new to this. Right now I have a physical machine to allow an employee at a different office to work by remote desktoping to it, but I would like to run a virtual machine on the ReadyNAS to allow them to work off of it instead. I believe this sort of thing is possible, but I'm not quite sure how to go about doing it. If anyone could point me in the right direction I would greatly appreciate it! :smileyhappy:7.3KViews0likes1Comment