NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
update
15 Topics
Unable to update WNDAP360 firmware to 3.6.9.0 (Security update)
Hi all, I seem to be unable to update my AP's FW level from 3.5.5.0 to 3.6.9.0.I have a total of 5 to update. I first tried updating through our WMS5316 controller. It took about 10 minutes before the browser interface returned, but they were still showing at 3.5.5.0. I then tried updating one of the AP's directly, but same results. No apparent error, but after reboot, no upgrade. I tried updatng using IE, Firefox, and Chrome, but no joy. Anyone else having problems with this firmware update, or able to offer suggestions? Since this is a security update I'm a bit worried.Solved4.6KViews0likes3CommentsRN104 6.7.4 update causing problems on 2 x RN104
We have updated 6 ReadyNas 104 devices today with firmware 6.7.4 to patch the recent documented Samba vulnerability and 2 unts are now not functionning. 1 is stuck at 99% booting an we are unable to revive it using the USB recovery. Another unit looks to keep crashing and although i can browse some of the the data (when it is up and running), 1 folder which is around 700GB just hangs accessing the data. Then the NAS looks to reboot as the Admin page shows the booting status bar. Both these NAS's had iSCSI LUN configured too, whereas some of the other devices i updateted successfully were SMB shares only, no iscsi. Has anybody else had any issues? Any help appreciated4.1KViews2likes6Comments
RN214 hangs at 99% booting after update to 6.7.4 (upnphttpd, rddclient failed, dba import failed)
After updating from 6.6.1 to 6.7.4 my RN214 hangs at 98% (first time) and now at 99% (with "upnphttpd.service" message). - I see "ReadyNAS Admin Page is offline" in browser. - Raidar shows storage with "management service is offline" status. - Diagnostics shows just "Disk 3 has 1 Current Pending Sectors, Disk 3 has 1 Uncorrectable Sectors". - All windows shares are acceptable - LUNs doesn't work (i have VMWare virtual machine with attached iSCSI disk to system iSCSI disk, and that system stucks at bios screen). - Reboot doesn't help. - Reinstall OS doesn't help. - Storage has been purchased more than 90 days ago, so there is no complimentary technical support for now. - And, finally, i have no data backup, so i can't do factory reset (of course, i can copy all files from windows shares, but content of iSCSI-disks is much more important for me). Things I see in logs http.log Jun 05 12:28:25 LONDON apache_access[2301]: 192.168.10.139 "GET /admin/ HTTP/1.1" 200 Jun 05 12:28:27 LONDON apache2[2309]: [error] [client 192.168.10.139] Connect rddclient failed, referer: https://192.168.10.7/admin/ Jun 05 12:28:27 LONDON apache_access[2301]: 192.168.10.139 "POST /dbbroker HTTP/1.1" 200 Jun 05 12:28:30 LONDON apache2[2422]: [error] [client 192.168.10.139] Connect rddclient failed, referer: https://192.168.10.7/admin/ initrd.log [2017/06/02 19:19:39 UTC] Updated from ReadyNASOS 6.6.1 (ReadyNASOS) to 6.7.4 (ReadyNASOS). [2017/06/05 09:09:34 UTC] Updated from ReadyNASOS 6.7.4 (ReadyNASOS) to 6.7.4 (ReadyNASOS). mem_info.log MemTotal: 2065488 kB MemFree: 1453256 kB MemAvailable: 1876636 kB readynasd.log Jun 05 12:28:24 LONDON readynasd[18815]: Error rndb_import() ==> rc=3 Jun 05 12:28:24 LONDON readynasd[18815]: dba import failed Jun 05 12:28:25 LONDON readynasd[18871]: readynasd log started Jun 05 12:28:25 LONDON readynasd[18871]: readynasd started. (restarted=0) smdb.log [2017/06/05 12:19:19.881135, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password: authentication for user [Anton] -> [Anton] -> [anton] succeeded [2017/06/05 12:20:04.845425, 2] ../source3/auth/auth.c:315(auth_check_ntlm_password) check_ntlm_password: Authentication for user [Administrator] -> [Administrator] FAILED with error NT_STATUS_NO_SUCH_USER system.log Jun 05 12:28:27 LONDON apache_access[2301]: 192.168.10.139 "POST /dbbroker HTTP/1.1" 200 Jun 05 12:28:29 LONDON dbus[2026]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper) Jun 05 12:28:29 LONDON dbus[2026]: [system] Successfully activated service 'org.opensuse.Snapper' Jun 05 12:28:30 LONDON apache2[2422]: [error] [client 192.168.10.139] Connect rddclient failed, referer: https://192.168.10.7/admin/ systemd-journal.log Jun 05 12:28:34 LONDON systemd[1]: Starting ReadyNAS System Daemon... Jun 05 12:28:34 LONDON readynasd[19085]: readynasd log started Jun 05 12:28:34 LONDON readynasd[19085]: readynasd started. (restarted=0) Jun 05 12:28:34 LONDON readynasd[19085]: DB (main) schema version: 23 ==> 23 Jun 05 12:28:34 LONDON readynasd[19085]: DB (queue) schema version: new ==> 0 Jun 05 12:28:35 LONDON readynasd[19085]: rndb_sql_get_scaler_mprintf is called with SQL which has vector output. (ncol=1, nrow=2). Jun 05 12:28:35 LONDON readynasd[19085]: SQL Error for SELECT FROM `group`. Jun 05 12:28:35 LONDON readynasd[19085]: rndb_account_import() ==> 3 (384ms)Solved6.8KViews0likes10CommentsUpdate 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
Amazon Web Traffic Upon OS Upgrade Reboot
Hello, I completed the ReadyNAS OS 6.6.1 update and soon after rebooting and reviewing logs, there was an abundant amount of traffic talking to what appears to be Amazon over port 80 using the following IP addresses: 52.8.157.247 52.9.151.236 52.52.17.157 54.153.23.250 I was unsure of why my ReadyNAS was talking to Amazon, and if this is in fact Amazon, as there were many pages of log messages with these four IP addresses talking through port 80. I have a hunch that it may be AWS, but can never be too safe. Thanks.1.8KViews0likes1Comment
RN102 no longer starts up following failed update to FW 6.6.0
Hi, hope someone can help. I got a notification to update my firmware which I did, it then initiated a second update which was to 6.6.0. I don't think I'd updated for some time so it had to update to an earlier version first. The second update never completed, the power light just continued to blink slowly for over an hour until I decided to restart it by removing the power. It now does the same thing, power light blinking slowly. I've tried USB updating to 6.6.0 using a memory stick that has definately worked in the past for a firmware update on this device. As the 6.6.0 udate didn't seem to complete I tried the 6.5.2 update too but no change. When trying the perform the update the lights on the RN102 flash rapidly and the USB stick shows acticity briefly then stops. Any suggestions would be much appreciated, I use this for NAS for work so I'm in a bit of a predicament! Thanks in advance for any help.Solved4.4KViews0likes2CommentsSqueezebox Server after Update Firmware 6.6.0
HI Together, I have a ReadyNAS204 with the Squeezebox-Mediaserver for my Squeezeboxes (SB). After the firmware update to 6.6.0 the Server unfortunately no longer works and is not longer offered in the application galarie for a new download. Does anybody know Netgear will support the server in future? Or is there any opportunity to setup the SBs with a alternative Server? THX TobiPlex Updated and lost my liberys...but
Yesterday my Plex app updated on my ReadyNAS 214, however my library and metadata are no longer there and had to create a new server....but when im in plex choosing a folder i can see in the /app folder and see that my old plex media server folder is still there with all my Metadata, but im unable to access the /app folder in windows explore or in the NAS admin page. how do i turn on hidden folders within the NAS so i can copy my data over to the other folder that aperantly Plex decited to make?Solved5.6KViews0likes14Comments
Impossible to install Apps (update problem with 6.4.2OS) #26554085
Hello guys! I hope this is the right section for this topic... I'm using my ReadyNAS with 6.4.2 OS on a NETGEAR ReadyNAS 102. Since a while, it seems to be impossible to install App in the web-based admin utility both choosing the apps proposed in the default list and uploading *.deb files (I'm trying to install monsta_1.4.2_all.deb). A message about an update problems of the apps list appear for less than 1 sec (impossible to read it), then the admin utility close and re-start. I tryed to activate SSH and I used a atp-get update command. The got this error, before to exit: Err https://deb.nodesource.com wheezy/main armel Packages HttpError404 Fetched 11.6 MB in 44s (264 kB/s) W: GPG error: https://deb.nodesource.com wheezy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1655A0AB68576280 W: Failed to fetch https://deb.nodesource.com/node_0.10/dists/wheezy/main/binary-armel/Packages HttpError404 E: Some index files failed to download. They have been ignored, or old ones used instead. I asked to Netgear's support, but I got only a request to buy a support package even to read my message... I'm sure I could find more friendly advise here! Thank you very much! Daniele[OS6 ARM] Readynas and impossible update
Hello. On my ARM based ReadyNAS, it's impossible to validate update. If I do a manual or automatic update, the device remains in OS6 6.2.4, and I have this warning on every logon... Is there a tip to update (force) it with a SSH connection ?2.8KViews0likes5Comments
