NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN51600 - Issue getting the admin page to work
Status: Drive shares are accesssable.
Admin Page down.
when starting the readynasd service on the device I get the following:
Aug 26 17:51:07 NAS-2 systemd[1]: Starting ReadyNAS System Dae...
Additional Info:
By the way this is not a network problem. I have isolated this to the readynasd daemon not starting correctly. When i try to access the admin page i get the Admin page down after it churns for a while. If i look into the debug on the web browser i get:
Line Number 1, Column 1: dbbroker:1:1
This site makes use of a SHA-1 Certificate; it’s recommended you use certificates with signature algorithms that use hash functions stronger than SHA-1.[Learn More] dbbroker
XML Parsing Error: no root element found
Location: https://nas-2/dbbroker
the Original issue was the Root filesystem on the NAS filled, and after cleaning up logs and some mysql issues i was able to get plenty of space back but i'm left wit this issue.
-Geoff
Try
# mv /var/readynasd/db.sq3- # sqlite3 /var/readynasd/db.sq3- .dump | sqlite3 /var/readynasd/db.sq3
I actually tried that before, it worked but the first time i restarted the readynasd it corrupted the file again and gave the same error.
Would you like me to post the output of the dump? if that will help i would be glad to.
Ended up formatting the 4GB root volume. You do have a long firmware update history going all the way back to 6.0.8!
[2014/07/27 18:43:38] Factory default initiated due to new disks (no RAID, no partitions)! [2014/07/27 18:44:02] Defaulting to X-RAID2 mode, RAID level 5 [2014/07/27 18:44:08] Factory default initiated on ReadyNASOS 6.0.8. [2014/07/27 17:51:26] Updated from ReadyNASOS 6.0.8 (1371611904) to 6.1.8 (1398980083). [2014/09/23 18:27:04] Updated from ReadyNASOS 6.1.8 (1398980083) to 6.1.9 (1409791183). [2015/02/08 21:13:05] Updated from ReadyNASOS 6.1.9 () to 6.2.2 (ReadyNASOS). [2015/06/05 21:19:15] Updated from ReadyNASOS 6.2.2 (ReadyNASOS) to 6.2.4 (ReadyNASOS). [2015/12/30 17:47:01] Updated from ReadyNASOS 6.2.4 (ReadyNASOS) to 6.4.1 (ReadyNASOS). [2016/02/21 21:56:47] Updated from ReadyNASOS 6.4.1 (ReadyNASOS) to 6.4.2 (ReadyNASOS). [2016/05/22 14:40:06] Updated from ReadyNASOS 6.4.2 (ReadyNASOS) to 6.5.0 (ReadyNASOS). [2016/09/15 17:57:18] Updated from ReadyNASOS 6.5.0 (ReadyNASOS) to 6.5.1 (ReadyNASOS). [2017/10/01 03:03:20 UTC] Updated from ReadyNASOS 6.5.1 (ReadyNASOS) to 6.8.1 (ReadyNASOS). [2018/07/14 00:22:47 UTC] Updated from ReadyNASOS 6.8.1 (ReadyNASOS) to 6.9.3 (ReadyNASOS). [2018/08/27 11:43:40 UTC] Updated from ReadyNASOS 6.9.3 (ReadyNASOS) to 6.9.3 (ReadyNASOS). [2018/08/28 03:43:09 UTC] Updated from ReadyNASOS 6.9.3 (ReadyNASOS) to 6.9.3 (ReadyNASOS).
Now the management service appears to be running fine.
For good measure I updated the BIOS (though this is unrelated to the problem that you had). You already had a BIOS with VT-x enabled, but the BIOS update has given you a USB3 F/W update and made it much easier to boot off a NTGR USB Service Key e.g. for USB Boot Recovery. Now if a NTGR USB Service Key is connected to the front USB port it should automatically boot off it when you power the system on. There's no longer any need to press the O.K. button at just the right time to boot off USB.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
