NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
After update to 6.6.0, can't access anything on Admin page
After updating my ReadyNAS 2100 from firmware 6.5.1 to 6.6.0 this morning, I can no loger access anything on the admin page. IF I can get the admin page to load after login, the page is blank. If I c...
Hi guys, just an update here. The issue I had after the 6.6.0 update turned out to be a permissions issue with the ReadyNAS users. Apparently there were some orphaned accounts (ui's as the tech called them) created by the ReadyNAS OS (which I still don't understand how), but 2 1/2 hours with support fixed the issue. Just as a side note, I had the exact same issue on the same device when I did the update to 6.5.1 some time back. Again, support fixed that issue as well, so I'm still confused as to how this could happen again when no changes have been made since the last firmware update. Wish I could give a little more info on this, but the technician closed the chat log before I got a chance to copy it for my records. Thanks to all who posted replys to this thread.
1.) I have same/similar problem. Just after upgrade to 6.6.0 + manually performed "apt-get upgrade" using SSH.
=> After that I've noticed that admin page is not accessible. Since I've got some experience with linux, here is how I solved the problem.
Some details first:
root@nas-ag1:~# cat /etc/*release
PRETTY_NAME="ReadyNASOS 6.6.0"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@nas-ag1:~# uname -a
Linux nas-ag1 4.1.30.alpine.1 #1 SMP Thu Sep 22 16:34:49 PDT 2016 armv7l GNU/Linux
2.) My problem was that Apache2 wasn't running
root@nas-ag1:~# systemctl start apache2
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
root@nas-ag1:~# systemctl status apache2.service
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2016-10-15 11:26:38 CEST; 27s ago
Process: 7320 ExecStart=/usr/sbin/apache2 $OPTIONS -k start (code=exited, status=203/EXEC)
Process: 7244 ExecStartPre=/frontview/bin/fvapps (code=exited, status=0/SUCCESS)
Main PID: 2300 (code=exited, status=0/SUCCESS)
Oct 15 11:26:38 nas-ag1 systemd[1]: Starting The Apache HTTP Server...
Oct 15 11:26:38 nas-ag1 systemd[7320]: apache2.service: Failed at step EXEC spawning /usr/sbin/apache2: No such file or dire
ctory
Oct 15 11:26:38 nas-ag1 systemd[1]: apache2.service: Control process exited, code=exited status=203
Oct 15 11:26:38 nas-ag1 systemd[1]: Failed to start The Apache HTTP Server.
Oct 15 11:26:38 nas-ag1 systemd[1]: apache2.service: Unit entered failed state.
Oct 15 11:26:38 nas-ag1 systemd[1]: apache2.service: Triggering OnFailure= dependencies.
Oct 15 11:26:38 nas-ag1 systemd[1]: apache2.service: Failed with result 'exit-code'.
root@nas-ag1:~# ls -lisa /usr/sbin/apache2
7360 0 lrwxrwxrwx 1 root root 33 Sep 23 20:53 /usr/sbin/apache2 -> ../lib/apache2/mpm-worker/apache2
root@nas-ag1:~# ls -lisa /usr/lib/apache2/mpm-worker/
total 8
7326 4 drwxr-xr-x 2 root root 4096 Sep 23 20:36 .
5908 4 drwxr-xr-x 5 root root 4096 Oct 15 11:14 ..
=> Therefore there was no file for Apache2 service to start, however, regardless proper APT package (apache2-mpm-worker) was installed.
root@nas-ag1:~# dpkg --list | grep apache2
ii apache2 2.2.31-0.netgear2 armel Apache HTTP Server metapackage
ii apache2-mpm-worker 2.2.31-0.netgear2 armel Apache HTTP Server - high speed threaded model
ii apache2-utils 2.4.10-10+deb8u7 armel Apache HTTP Server (utility programs for web servers)
ii apache2.2-bin 2.2.31-0.netgear2 armel Apache HTTP Server common binary files
ii apache2.2-common 2.2.31-0.netgear2 armel Apache HTTP Server common files
ii libapache2-mod-auth-token 1.0.6 armel mod_auth_token is a famous apache module that allows you to
rc libapache2-mod-authnz-external 3.2.6-1.netgear1 armel authenticate Apache against external authentication services
ii libapache2-mod-authz-unixgroup 1.0.3-1.netgear2 armel access control based on on unix group membership for Apache
3.) I tried re-installing both apache2 and apache2-mpm-worker.
Same result.
It's also interesting, that there is apache2 binary for prefork apache alternative (regardless the prefork is not installed)
root@nas-ag1:/usr/lib/apache2/mpm-prefork# ls -lisa /usr/lib/apache2/mpm-prefork
total 372
5909 4 drwxr-xr-x 2 root root 4096 Oct 15 10:30 .
5908 4 drwxr-xr-x 5 root root 4096 Oct 15 11:14 ..
7230 364 -rwxr-xr-x 1 root root 368828 Sep 23 20:54 apache2
4.) Anyway, the missing file should come from APT package apache2.2-bin:
dpkg -S /usr/lib/apache2/mpm-worker/apache2
apache2.2-bin: /usr/lib/apache2/mpm-worker/apache2
5.) So I tried reinstalling the problematic package:
apt-get install aptitude
aptitude reinstall apache2.2-bin
6.) And missing file recovered...:
root@nas-ag1:/usr/lib/apache2/mpm-worker# ls -lisa /usr/lib/apache2/mpm-worker/apache2
7739 376 -rwxr-xr-x 1 root root 381184 Sep 23 20:54 /usr/lib/apache2/mpm-worker/apache2
7.) After that, it had to fix problem with uninstalled libapache2-mod-authnz-external.
apt-get install apache2=2.2.31-0.netgear2
apt-get install apache2-utils=2.2.31-0.netgear2
apt-get install libapache2-mod-authnz-external
systemctl start apache2
systemctl status apache2
apache2.service - The Apache HTTP Server
...
Active: active (running) since Sat 2016-10-15 11:40:54 CEST; 13s ago
...
####################################################################################################
=> Maybe this helps someone (with SSH access). However, you may have different situation. Good luck!
####################################################################################################
BTW: Here is my current packages list (= I have nothing special):
root@nas-ag1:/usr/lib/apache2/mpm-worker# apt --installed list | grep -v 6.6.0 | grep -v stable
WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts.
Listing...
libboost-iostreams1.49.0/now 1.49.0-3.2 armel [installed,local]
libdb5.1/now 5.1.29-5 armel [installed,local]
libexiv2-12/now 0.23-1 armel [installed,local]
libgcrypt11/now 1.5.0-5+deb7u3 armel [installed,local]
libgnutls26/now 2.12.23-13 armel [installed,local]
libnl1/now 1.1-7 armel [installed,local]
libnml/now 197 armel [installed,local]
librddclient/now 5903 armel [installed,local]
librnimage1/now 1.0.1 armel [installed,local]
plexmediaserver-ros6-binaries/now 0.9.15.2.1663-7efd046 armel [installed,local]
rdbroker/now 1.2.63+2.678122a armel [installed,local]
readysync/now 1.2.63+2.678122a armel [installed,local]
rn-dictionary/now 20160926 all [installed,local]
wget/now 1.16-1.netgear1 armel [installed,local]
rstribrn wrote:
...Just after upgrade to 6.6.0 + manually performed "apt-get upgrade" using SSH.
FWIW, Netgear definitely doesn't recommend this.
I know. I read the warning when I enabled SSH access (just after I bought my RN204). Reason: Disabling (annoying) LED diode flickering.
I use Linux systems at work/home for more than a decade, so I can quite easily fix problems like this...
Anyway, good luck with this problem. Hopefully you'll find some easy user-friendly solution.
Rostislav Stříbrný
Hi I have a similar problem experienced by others in the forum. I have been using a RN104 NAS Drive (12TB total) for over a year now and upgraded to v6.5.1 unfortunately I can no longer get into the dashboard. The drive is functioning correctly. I use Windows to move files in an out. All settings on the NAS are basic. I can use RAIDar 6.x to get logs etc but when I go to log in it simply comes up with the splash screen and version.
I noted that disk two has had some errors. Will this cause this sort of issue?
I was thinking of taking all drives out and just putting a small drive (one ) in to upgrade the firmware and then once upgraded put the old disks (x4) back in. Will this work or will it do nothing?
I think the NAS drive is good for home and I primarily use it for media center and backup of computers.
Any help would be appreciated.
Regards
Tonez90 (Tony)
Tonez90 wrote:
I was thinking of taking all drives out and just putting a small drive (one ) in to upgrade the firmware and then once upgraded put the old disks (x4) back in. Will this work or will it do nothing?
If you do this, what normally happens with OS-6 NAS is that the boot loader compares the OS on the disks with the OS on the flash. Whichever OS is newer wins (If the flash is newer, the OS on the disks is upgraded; if the OS on the disks is newer, then the flash is upgraded).
I don't think its likely to solve anything for you. What firmware were you running before?
As I did not turn on SSH and there does not seem to be a solution to regaining access to the admin web page -
The RN 104 disks are working, if I bought a RN 214 made sure it was the same 6.6.0 firmware and put the disks in the same order from the RN 104 to the RN 214 would I then be able to access my data? Instead of having to buy additional hard drives and transfer bit by bit the data folder at a time.
Thanks
The OS is installed from the flash in the unit onto the disks so the problem will remain when moving to another chassis.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
