NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Netgear Apps & Add-ons
879 Topics
Google Drive Sync. Issues and observations
I have been testing Google drive on this device with every firmware release since 6.7.x. I am currently running 6.9.3. I wanted to list a number of issues and observations I have made in regards to this app. I hope it will help others in the community as well as get some help for myself. Since I will be covering so many topics I may want to break this out into multiple threads but for how it is just a master list. #1 Netgears website is really annoying. It doesn't give you a way to report a bug without paying for support service. It doesn't even give you a link and a suggestion to come here into the forums for help from the community and maybe some help from Netgear. That is extremely unfreindly for a user who is looking for help. #2 The fact that this main instruction page is missing vital information is sad. https://kb.netgear.com/000038420/ReadyNAS-OS-6-7-Sync-with-Google-Drive# It should mention that there is an EXTREMELY useful button that you can use to watch what the app is currently/historicaly doing. So many people on thi very forum are asking questions that could be answered if they just knew to click that button and watch. They whould know when the device is syncing or just doing an index scan ect. #3 This app has a VERY bad flaw in how it is designed to Startup and run. I call this the Live sync not started issue. When you start or restart the sync service it will go through the following steps in this order. Start the sync service Index the local files Index the cloud files Download/upload the missing files OR download a duplicate file if the files are slightly different. (that is something that causes problems and I will discuss more on this later.) Last it will start the LIVE sync service. It is very possible in envronments like mine that this restart could take a couple days. So in my case the live sync won't be running for a couple days. Here is why. I have 9TB of data synced on one of these devices. The local file index is fast and only takes a second or two. But the cloud index takes about 30-40 minutes. That is all on Google's side. After that 30-40 minute wait the app has a list of files that it needs to download/upload. If that is a long list then it chould take several hours or even days. In my case I had added 3TB of data that was not synced to the Google Cloud side. I restarted the sync service and after 35 mintues it started to download the missing 3TB of data. It took 38 hours to download. Then the live sync was started. So I had gone for almost 2 full days with the live sync service NOT running. All of the files that were added/removed or modified during that time were not getting synced. At the end of the 38 hours the live sync started and it ONLY started syncing the file changes it saw from that point on. 38 hours of files changes were completely missed and skipped even though the sync app was running. In order to capture these missing file edits I had to restart the service again and let it Find the files that were added/removed. Again it took about 2 hours and the live sync service was down during that time. I consider this to be a bug. It should be fixed before this app comes out of beta. The live sync should start right after the file index scans. I think some of the users complaining that BiDirectional sync doesn't work are running into this problem. They just don't realize that their Test edits are being ignored until the log says live sync is started. #5 As I mentioned in that last topic the sync will sometimes run into a file that has been modified/renamed when the live sync isn't running. The app just downloads a duplicate copy and renames it. In my opinion this should be a user setting. I would rather be able to tell the app which copy to keep. I would set it to keep the Cloud version and overwrite the local copy or visa versa in other environments. Or just tell it to keep the file with the most recent modified date. #6 This one is really frusterating. I call it the Flagged for abuse lockup. It only affects downloads. Uploads are not affected directly. In the 9TB of data are some files that Google has flagged for abuse. Allegedly these files break some form of copywright or something. When Google flaggs a file for abuse it can't be synced using any sync app on any platform. Even the apps that google has provided "Google Sync", "Google drive sync", "Google Drive file Stream" they all fail to copy the files. I am ok with this behaviour. I am not happy with how this ReadyNAS app is handleing it. This app will attempt to download the flagged file and it will just get stuck. The log will say the date and time that it started the download but then it will do nothing. This app can download up to 3 files at a time from what I can see. So if only one flagged file is encountered it will still continue to function with up to 2 downloads at once. If it encounters more flagged files it will eventually think it is still downloading all the files it can handle. At that point it will not download or upload any files at all. The entire sync service is just stuck. There are no error messages. It just stops working. All you can do is restart the service and hope those files are the last ones it runs into. I have been removing these flagged files from our envinronment but this Flagged for abuse lockup has got to be considered a bug and it should be fixed. The app should use the Google drive API to identify the file as being flagged and instead of trying to download the file it should just write a line in the log saying the file is flagged for abuse and will not be downloaded. If Google hasn't provided that ability in the API then you need to setup a timout on the download attempt and give up after a time and write that into the log. This app should NOT leave Beta with this bug still in place. I am running out of time for today so I will end here for now. Please pass some of this information along to the developers of this app. I hope this helps identify some problems to work on before the app comes out of Beta. I also hope this helps some of the users to understand whay they may be encountering.
ReadyNAS OS 6.9.3 | Run on existing x86 (4.2) #notsupported
There are a few threads on this, showing how to convert 6.0 firmware to run on the 4.2 platform. I am combining the information here, so it is easier to digest. This is UNSUPPORTED by NETGEAR. Do so at your own risk, without support from NTGR. You need to factory default after converting your NAS to the new platform, BACKUP YOUR DATA! ReadyNAS OS 6 will only work on 64-bit systems (Ultra/Pro), the NVX/2100v1 models are 32-bit and thus are not supported. Here are pre-built images for the lazy: R4toR6_Prep_Addon.bin (26 KB) (upload first, don't reboot, avoids the need for manual factory default in between) R4toR6_6.9.5.bin (67.6 MB)(upload after add-on) After you upload the addon/firmware and reboot, it will update the firmware and start a factory default. Your system should be back up in less than 10 minutes running the new firmware. If you want to build the image on your own, you can follow the steps from this wiki article: $ wget -q ftp://downloads.netgear.com/files/GDC/READYNAS-100/ReadyNASOS-6.0.4-x86_64.zip $ unzip -q ReadyNASOS-6.0.4-x86_64.zip $ head -n1 ReadyNASOS-6.0.4-x86_64.img info::name=ReadyNASOS,version=6.0.4,time=1364529349,size=49301504,md5sum=4086b247f29be084549f2b150ada8a70,arch=x86_64,descr=ReadyNASOS $ echo -n 'info::name=RAIDiator-x86,version=6.0.4,time=1364529349,size=49301504,md5sum=4086b247f29be084549f2b150ada8a70,arch=x86,descr=ReadyNASOS for 4.2!' > newhead $ dd conv=notrunc if=newhead of=ReadyNASOS-6.0.4-x86_64.img Basically, changes the ::name and ::arch in the header to match with what RAIDiator 4.2 expects. More information can be found in this thread: OS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT36KViews4likes134Comments
Built in Antivirus 6.6.1
Hello, I can't for the life of me find where to configure this new antivirus... Any suggestions? I searched "antivirus" here and sorted by date, but I can't believe nobody's been asking about this recently. Point me in the right direction, please? Thanks!10KViews3likes22CommentsHow can I update SoftEther VPN App to Newest Version - ReadyNAS 10400
Hello all - if anyone is interested in knowing the solution mentioned in this topic here then here is it. Unfortunatelly the topic is already closedso cannot add solution directly there. Tested on NETGEAR ReadyNAS 10400. Current version of the VPN App is 1.5 which contains SoftEther VPN Server version 4.12. I successfully updated the SoftEther VPN Server to latest version as of today 4.19 - Build 9605. The solution is to download latest binary build for ARM (my ReadyNAS is ARM v7) and then copy it to the folder /apps/vpnserver/bin/arm/ . In this location there is a compilation script which can rebuild the vpnserver and vpncmd executables (ELF) using the latest binary release of the downloaded SoftEther VPN Server. Steps - ssh root access is required: 1) Stop the VPN Server App in ReadyNAS Web UI 2) ssh to the ReadyNAS box (i.e. using PuTTy) 3) Become root by executing "sudo su" if your user is sudoer or logon directly as user root 4) Install build tools to be able to execute the SoftEther build: apt-get update apt-get install make libc6-dev gcc gdb libtag1-dev uuid-dev 5) download latest ARM EABI Binary release of the SoftEther VPN Server - in my case 4.19-Build 9605 wget http://www.softether-download.com/files/softether/v4.19-9605-beta-2016.03.06-tree/Linux/SoftEther_VPN_Server/32bit_-_ARM_EABI/softether-vpnserver-v4.19-9605-beta-2016.03.06-linux-arm_eabi-32bit.tar.gz 6) Untar the archive tar xvf softether-vpnserver-v4.19-9605-beta-2016.03.06-linux-arm_eabi-32bit.tar.gz The directory vpnserver is created. 7) Copy the content of the vpnserver directory (the archive extract) over the files in the directory /apps/vpnserver/bin/arm/ 8) cd to /apps/vpnserver/bin/arm/ and build the new ELF executables: cd /apps/vpnserver/bin/arm/ ./.install.sh - you have to view & accept the license agreement, after that the new executables (vpnserver and vpncmd) should be build using the files extracted from the latest binary release of the SoftEther VPN Server 9) Now copy everything from /apps/vpnserver/bin/arm/ also one level up to /apps/vpnserver/bin (dunno why it's duplicated there) 10) make sure you return the ownership of the files to the admin user: cd /apps/vpnserver chown -R admin:admin bin/ 11) Cleanup the extracted vpnserver directory and the downloaded archive 12) Start the VPN Server App from ReadyNAS Web UI and Enjoy new version (don't forget to use compatible VPN Client tools) Maybe someone can write fully automated script ... including the download from the SoftEther VPN Server location ;-)19KViews3likes21CommentsUpgrade : linux-image-extra not up-to-date for ReadyNAS OS 6.10.5
Hi, On ReadyNAS OS 6.10.5, the kernel was updated to version 4.4.218 but the linux-image-extra package in the repository doesn't exist for this version. The only available version is still 4.4.190-610040005. This breaks some application like Docker which needs some extra kernel modules. A workaround is to downgrade to 6.10.4.RN102 Dropbox authorization won't redirect
Hi, I just upgraded my RN102 firmware to 6.5 and went to authorize Dropbox. I toggle the switch to "On" and a new window pops up that says "Authorization... please wait" but that window just stays there and never goes away. I've tried this on a number of different browsers and no luck. Any advice on how I can get this working properly? Thanks!Solved
Built in AntiVirus is a MESS
Since the built in backup facility in the readynas does not support volume snapshots, I have been trying to use windows backup on my client machines to accomplish backups. I have been trying 2 different machines for about a week with no success. The backups fail with windows error 0x81000039 "The backup was not successful. The error is: Backup encountered an error when accessing the remote shared folder" I tried many different possible solutions, the last of which was to turn OFF the Antivirus function of the server. This is the standard antivirus. I havent even tried the Antivirus Plus download. After turning this feature off, backup works fine. This is the second time Antivirus has been implicated in system problems. The first time was during the diagnosis of a crashing problem when the Level 3 tech Jerry Fulgencio (#9028) told me that I could not run antivirus and snapshots at the same time. I would like to use the advertised Antivirus feature, but at this point, it seems that it has a hard time working properly in this environment! The client PCs are running Windows 7 Ultimate 64bit. The backups include file backup and volume snapshots. What can I do to get Antivirus to work? There isn't even a forum topic for this built in and downloadable (Antivirus + by Netgear) application. This in my opinion a marketed feature that is problematic at BEST! Actually, I'm starting to wonder if anyone in this forum is running V6 software. Is there such bad blood because of a lack of upgrade path. From what I've seen, the folks on the older software may be at an advantage.Developer support for app development (Jellyfin media system)
Hello, I'm trying to create a new app for ReadyNAS. I'd like to package Jellyfin, a media server. Is this the appropriate place for developer questions? I found this documentation, but quickly ran into an issue setting up the VirtualBox VM for ReadyNAS OS 6. Here is the issue I'm having when I try to boot my VM: That looks like a kernel panic? Also, I notice some apps seem to be very out of date on my NAS (transmission for example). Is there a git repo I can submit patches to so they get updated? Are they abandoned by the developers? I also notice that Docker is available for x86_64 models but not for my ARM RN-102. Is there a reason for that? Docker supports ARM; should I try to create an ARM version or is there any way I could submit an update for the existing Docker app?
