I went on a bit of a binge with SABnzbd, everything had been working well, thought I'd let it run & watch TV with the kids. I attempted to load the readyNAS admin page on my ipad to monitor things from the family room, and it timed out. Now it just won't come back under explorer, or iOS Safari.
I've shut down & restarted the NAS a couple times without any luck. I've re-installed the OS twice, again no luck. The SABnzbd webpage continues to work, as do all the window shares. ReadyCloud can see the device, but not browse the file structure (may be due to the OS re-install resetting passwords?) Raidar shows the device up & running (6.2.1 all drives green) shares work, admin page no dice.
I did not install SSH - device is too new, hadn't really gotten around to it yet.
nmap doesn't have the NAS listening on any well known web ports:
Well after some time on the phone with support, I'm going to have to rebuild. Interestingly enough, as I copy files off the NAS I can copy 10-15GB and then it stalls out. The only way to recover from this is to shut off and power up the system.
Shutdown takes several minutes (sometimes 10 or more) - is that normal?
First thing I'm going to do when this is rebuilt is install SSH...
I'm not sure this isn't my fault - when I first got it I installed and removed many apps (through the installer) and I suspect the last one buggered the Apache config on the way out. If I'd installed ssh, I could have a look why it's no longer listening on port 80 or 443, but I didnt
I had hoped their tech support would have a backdoor, but alas...
Anyway, it gets once. If it continues to f up after this, I don't have all day to play with my nas very often. It should just work.
I set up access to one of my workstations & let them drive - tech support was unable to access the system at all, even with a direct connection to the NAS from the workstation.
Just started moving my files back to the NAS - a bit sleep deprived, but I'm missing the "Backup" share - I don't recall creating that. Anyway, there's a "hidden" share with the same name (//NAS/backup) containing Linux files. This does not appear under shares in the admin site.
//NAS/backup/user[/device] is mounted at startup for my systems - so I need to decide if I should recreate the share in admin, or if that was part of the conflict & move workstation backups under home.
And I turned on SSH as soon as the system came back to life
I have the same problem with a readynas 102. Once a day when i download using sabnzbd, sabnzbd crash and then my admin page crash also with a "Device is not connected". I have to reboot the Nas by unplugged power, ssh and power button not respond.
Well I guess it is possible the app you have installed has issues addressed by the newer version on RNXtras.com. I don't know what has changed between those two versions.
I'm having the same problem with a 102. Just updated to the newest firmware in the last few days and can no longer access the admin page. I've tried reboots and reinstalling the OS. All data and services are intact: windows shares, ftp, bt sync, mysql. Nmap only reports ports 21, 139, 445, and 3306. Of course, ssh is turned off so that option is out. I had recently installed and then uninstalled the Survellience app (because it doesn't support foscam).
I'm having the same problem with a 102. Just updated to the newest firmware in the last few days and can no longer access the admin page. I've tried reboots and reinstalling the OS. All data and services are intact: windows shares, ftp, bt sync, mysql. Nmap only reports ports 21, 139, 445, and 3306. Of course, ssh is turned off so that option is out. I had recently installed and then uninstalled the Survellience app (because it doesn't support foscam).
Hi Toolman, since SSH is turned off - can you please put your device in to tech support mode and let me know when this is done (PM me)? Please note that data will be unavailable while device is in tech support mode.
Hi I have a ready NAS 104 and has the same issue. cannot connect to the admin page. tried different browser- not working tried different computer- not working ping was successful can access the files and folders I did a OS reinstall.- http://kb.netgear.com/app/answers/detail/a_id/22891 still not working. Can some one give me some recommendations? Thanks
Does SABnzbd have any logs? Do those give any clues?
If it doesn't have any logs does it leave any clues in systemd-journal.log ?
Hi,
Sorry for this delay but it's start again. I updated sabnzbd to the latest version 0.7.20 and I don't have any information in sabnzbd logs. In systemd-journal.log I have this :
Mar 15 19:48:40 MyNas systemd[1]: ctscand.service: main process exited, code=killed, status=9 Mar 15 19:48:41 MyNas systemd[1]: Unit ctscand.service entered failed state. Mar 15 19:48:44 MyNas systemd[1]: ctscand.service holdoff time over, scheduling restart. Mar 15 19:49:21 MyNas systemd[1]: ctscand.service: main process exited, code=exited, status=255 Mar 15 19:49:21 MyNas systemd[1]: Unit ctscand.service entered failed state. Mar 15 19:49:25 MyNas systemd[1]: ctscand.service holdoff time over, scheduling restart. Mar 15 19:49:35 MyNas systemd[1]: ctscand.service: main process exited, code=exited, status=255 Mar 15 19:49:35 MyNas systemd[1]: Unit ctscand.service entered failed state. Mar 15 19:49:36 MyNas systemd[1]: fvapp-sabnzbd.service: main process exited, code=killed, status=9 Mar 15 19:49:37 MyNas ctscand-watchdog[18989]: WATCHDOG_SEC: 150 Mar 15 19:49:37 MyNas ctscand-watchdog[18989]: Unable to create pid file: File exists
And when sabnzbd crash I lost connection to the admin page and other stuff and I have to do an systemctl restart readynasd to work again. I don't know if it's sabnzbd crash or system crash when sabnzbd download a file.
Can anyone help me?
Thanks ps: I create a new post maybe it's better https://www.readynas.com/forum/viewtopic.php?f=7&t=80389
I had the same issue here, upgraded to firmware 6.2.2 without issue but after uninstalling an app I lost access to admin page, OS reinstall did not work. Netgear support wanted $79 to fix the issue as I was out of my 90 day warranty however following a post from another thread fixed my issue perfectly, I used the scratch disk method:
StephenB wrote:
Ash_Silva wrote:
Is there a workaround for this bug? Or do I need to perform another OS reinstall and see if it comes good?
An OS reinstall won't help.
If you have ssh enabled, it is easily fixed. Support (or someone else from netgear) can fix it remotely. They shouldn't charge, but they might attempt to apply normal support policies.
If you have a scratch disk handy (not part of the array) you can fix it on your own w/o ssh.
-Power down the RN104 -Remove all the disks (labeling by slot) -Insert just the scratch disk and power up. The RN104 will install the current OS on the scratch disk -You will now be able to log into the web ui (using "password" as the admin password). Update the firmware to 6.2.3 beta (manually downloading from this forum). -After the update completes (reboot, etc), power down the NAS, and reinstall the original disks. Then power up.
The NAS will then install 6.2.3 onto the old disks automatically, which will repair your problem.
It's interesting to see so many people having this issue and Netgear is eager to help with their extended support contract, how about they just fix the firmware?
It's interesting to see so many people having this issue and Netgear is eager to help with their extended support contract, how about they just fix the firmware?
(a) they have fixed the firmware - it is in 6.2.3 beta, which you can download here.
(b) Based on posts here, support is not charging to fix it. Though in some cases they need a bit of convincing on what the problem is.
I reviewed your case. Looking at our chat transcript I didn't see any specific mention of the app uninstallation problem. Whilst we should have picked up this possibility from what you said I would have recommended specifically mentioning that.
We do have an exception for fixing the app uninstallation problem.
As you can see we have already fixed the problem in our 6.2.3 beta firmware.
We have added a safe mode in 6.2.3 beta so that should a similar issue arise in the future you should still be able to access the web admin interface but may see symptoms like none of your installed apps being listed as installed.
Netgear have released firmware 6.2.3 (not beta) and no 1 on the list of fixes is "Fixed issue where removing certain apps would bring the web interface offline." I applied the firmware but don't really want to run the risk of uninstalling an app to test if it works, if I ever try this I will re-post here.
Full list of Enhancements & Bug Fixes: Fixed issue where removing certain apps would bring the web interface offline. Lower SMB allocation roundup size, so Windows 8.1 shows reasonable Disk Used values. Fixed incorrect default Gmail alert settings. Kernel security updates and various bug fixes. Revert higher fan RPMs with Seagate disks. Fixed potential system hang with Anti-Virus enabled. Fixed potential system hang on 4-bay units with disk spindown enabled. Suppress duplicate anti-virus warnings. Does not send email alerts about virus definition updates. Prevent SNMP connections from spamming the system logs. Fixed premature snipping of logs when downloading log .zip file. Don't try to spin down SSDs. Fixed snapshot access via "Previous Versions" in Windows on shares with multi-byte characters in the share name. Fixed downloading files from USB drives through ReadyCloud. Various upstream security updates. Fixed NFS discovery issue with Kodi / XBMC. Fixed SMB discovery issue when the NAS is operating as the NETBIOS master browser. Enhances system log download contents. Fixed iTunes 12.1 incompatibility. Increased max ADS connections, to gracefully handle very busy AD environments. Improve volume information sent to RAIDar client. Added HTTP server "safe mode" fallback in case of misconfiguration. Scheduler change to hopefully resolve random freezing on RN10x. Fixed exposing of visible snapshots in some cases. Upstream security fixes. More changes for RN104 hang. Improve UI auto-reconnect mechanism. Better handling of joining very strict ADS environments. System timer tweaks for RN10x. Patched CVE-2015-0240. Fixed GUI crash when there was an inactive volume present. Disabled perf events in ARM kernel. Improved information gathered for log zip file. Fixed memory leak in LLMNR responder. Fixed out-of-memory condition in iTunes server caused by large zero-filled files. Reserve more system memory on busy systems, to page allocation failures. Fixed downgrades to 6.2.2. Filter out duplicate bit rot events. Fixed false VCore voltage alerts from RN3130. Changed I/O scheduler on RN10x. Fixed NFS thread count setting being overwritten on update. Fixed bad DVBLink interaction with RNx16 buttons. Fixed overly picky path input validation when creating backup jobs. Don't fail to start management daemon when encountering an unsupported UPS. Added a confirmation dialog when removing apps. Fixed UI connection repair mechanism with certain browsers on HTTPS connections. Disabled x86 kernel memory compaction support. Fixed SMB permissions breakage after changing NAS hostname. Latest OpenSSL security fixes. Added full ca-certificates bundle to fix apps that use HTTPS. Fixed possible CPU spinner bug after canceling an SMB transfer. Fixed IPv6 address display in UI. Fixed invalid scheduled disk test result reporting. Deployment Notes / Limitations: Wake on LAN (WOL) will not be supported on the ReadyNAS 4220 at this time using the 10GbE port. Use the 1GbE port for WOL. There is no error message presented in the local admin GUI when the USB key is missing from the system for encrypted volumes. The LCD display will present a message that the USB key is missing. If the USB key is missing for encrypted volumes, the user has to wait for a 10 minute timeout. After the timeout, the encrypted volume will appear as inactive in the local admin GUI. If a FLEX-RAID volume has be expanded, the volume cannot be switched back to X-RAID mode. If you wish to remove a USB storage device, you should first eject the drive in the local admin GUI before removing the USB device from the ReadyNAS to prevent errors on the file system of the USB device. ReadyNAS 102, 104, and 2120 only support creating iSCSI LUNs 8TB and smaller. ReadyNAS 102, 104, and 2120 only support volumes up to 16TB. ReadyNAS devices updated to ReadyNAS 6.2.0 or later cannot be downgraded to ReadyNAS 6.1.x or earlier.
A number of users have tried it while 6.2.3 was in beta and the fix does work. In any case we have implemented a safe apache config so that we can more gracefully fix similar issues should they arise in the future.
Since this upgrade to 6.2.3 my readynas has been locking up several times per day, only unplugging the power then powering back up gets the unit back online.
I miss the stable 6.1 release I had before, the nas ran for 10+ months without incident before the 6.2 upgrade.
One thing I've noticed, lots of people having this locking up issue in the beta release of 6.2.3, how come it managed to get past beta to full release?
I will post this new issue in a new thread.
andyhaw wrote:
Netgear have released firmware 6.2.3 (not beta) and no 1 on the list of fixes is "Fixed issue where removing certain apps would bring the web interface offline." I applied the firmware but don't really want to run the risk of uninstalling an app to test if it works, if I ever try this I will re-post here.
Full list of Enhancements & Bug Fixes: Fixed issue where removing certain apps would bring the web interface offline. Lower SMB allocation roundup size, so Windows 8.1 shows reasonable Disk Used values. Fixed incorrect default Gmail alert settings. Kernel security updates and various bug fixes. Revert higher fan RPMs with Seagate disks. Fixed potential system hang with Anti-Virus enabled. Fixed potential system hang on 4-bay units with disk spindown enabled. Suppress duplicate anti-virus warnings. Does not send email alerts about virus definition updates. Prevent SNMP connections from spamming the system logs. Fixed premature snipping of logs when downloading log .zip file. Don't try to spin down SSDs. Fixed snapshot access via "Previous Versions" in Windows on shares with multi-byte characters in the share name. Fixed downloading files from USB drives through ReadyCloud. Various upstream security updates. Fixed NFS discovery issue with Kodi / XBMC. Fixed SMB discovery issue when the NAS is operating as the NETBIOS master browser. Enhances system log download contents. Fixed iTunes 12.1 incompatibility. Increased max ADS connections, to gracefully handle very busy AD environments. Improve volume information sent to RAIDar client. Added HTTP server "safe mode" fallback in case of misconfiguration. Scheduler change to hopefully resolve random freezing on RN10x. Fixed exposing of visible snapshots in some cases. Upstream security fixes. More changes for RN104 hang. Improve UI auto-reconnect mechanism. Better handling of joining very strict ADS environments. System timer tweaks for RN10x. Patched CVE-2015-0240. Fixed GUI crash when there was an inactive volume present. Disabled perf events in ARM kernel. Improved information gathered for log zip file. Fixed memory leak in LLMNR responder. Fixed out-of-memory condition in iTunes server caused by large zero-filled files. Reserve more system memory on busy systems, to page allocation failures. Fixed downgrades to 6.2.2. Filter out duplicate bit rot events. Fixed false VCore voltage alerts from RN3130. Changed I/O scheduler on RN10x. Fixed NFS thread count setting being overwritten on update. Fixed bad DVBLink interaction with RNx16 buttons. Fixed overly picky path input validation when creating backup jobs. Don't fail to start management daemon when encountering an unsupported UPS. Added a confirmation dialog when removing apps. Fixed UI connection repair mechanism with certain browsers on HTTPS connections. Disabled x86 kernel memory compaction support. Fixed SMB permissions breakage after changing NAS hostname. Latest OpenSSL security fixes. Added full ca-certificates bundle to fix apps that use HTTPS. Fixed possible CPU spinner bug after canceling an SMB transfer. Fixed IPv6 address display in UI. Fixed invalid scheduled disk test result reporting. Deployment Notes / Limitations: Wake on LAN (WOL) will not be supported on the ReadyNAS 4220 at this time using the 10GbE port. Use the 1GbE port for WOL. There is no error message presented in the local admin GUI when the USB key is missing from the system for encrypted volumes. The LCD display will present a message that the USB key is missing. If the USB key is missing for encrypted volumes, the user has to wait for a 10 minute timeout. After the timeout, the encrypted volume will appear as inactive in the local admin GUI. If a FLEX-RAID volume has be expanded, the volume cannot be switched back to X-RAID mode. If you wish to remove a USB storage device, you should first eject the drive in the local admin GUI before removing the USB device from the ReadyNAS to prevent errors on the file system of the USB device. ReadyNAS 102, 104, and 2120 only support creating iSCSI LUNs 8TB and smaller. ReadyNAS 102, 104, and 2120 only support volumes up to 16TB. ReadyNAS devices updated to ReadyNAS 6.2.0 or later cannot be downgraded to ReadyNAS 6.1.x or earlier.
Since this upgrade to 6.2.3 my readynas has been locking up several times per day, only unplugging the power then powering back up gets the unit back online.
Can you send me your logs (see the Sending Logs link in my sig)?
andyhaw wrote:
One thing I've noticed, lots of people having this locking up issue in the beta release of 6.2.3, how come it managed to get past beta to full release?
We delayed the 6.2.3 release looking for a software fix for the issue.
Despite all that we did to revert things to how they were in 6.1.9 there were still some lockup issues that could not be reproduced. So we have moved on to a new strategy in troubleshooting this problem.
6.2.3 has a number of improvements over 6.2.2 and we could not delay it any longer. Most users have found 6.2.3 beta firmware and 6.2.3 to be the best 6.2.x release yet.
andyhaw wrote:
I will post this new issue in a new thread.
That would be a good idea. Seeing this thread is now going off topic I am locking this thread.
