- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Buggy firmware 6.10.0 on RN104?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Buggy firmware 6.10.0 on RN104?
Hi
Made the mistake to update to this 6.10.0 firmware.
It seems to be having all sorts of probems now that I was able to install it.
No icons on apps.
Can't enable or disable any service.
Can't install uninstall any app.
Are other RN104's having the same problems with 6.10.0?
Can I go back to 6.9.5?
Is Netgrear READING THIS!!!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
Unfortunally the ReadyNAS god's were having the day off and I did't get a reply. 😉
I re flashed 6.10.0 to see if would fix the problems above.
The system rebooted okay and I can see all my files.
RAIDar Reports 6.10.0 system Healthy
BUT!!!!!
For the live of me I can no longer get in to the ReadyNAS Web interface.
I get "ERR_CONNECTION_REFUSED"
Tried the IP, http://IP, https://IP, https://readynas, from other devices on the network and using diferent web browsers.
I can open the qBittorrent app
Kudos...
Peter
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
Hi Marc
Thanks for the reply.
Yes I have tried different browsers as well as mobile phones with no previous connections to this device with same error.
The ReadyNAS has a static IP 10.0.0.10 and the Gateway is 10.0.0.1
It has worked for years with this configuration.
Is there a way to load 6.9.5 back.
I have tried reverting it using a rescue USB but is fails with an error
Thanks
Peter
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
@petercae wrote:
Tried the IP, http://IP, https://IP, https://readynas, from other devices on the network and using diferent web browsers.
Did you try https://IP/admin ?
Can you boot into tech support mode (or log in with ssh)?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
Hi
Yes, https://10.0.0.10/admin and https://10.0.0.10/admin/index.html
Haven't tried tech support mode, not familiar with it.
Thanks
Peter
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
@petercae wrote:
Haven't tried tech support mode, not familiar with it.
Likely it will work (since the NAS does appear to be booting). The process is described on 28-29 of the hardware manual here: http://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf
You can confirm that it worked by trying to connect to the NAS with telnet. If you get a log-in prompt, the system is in tech support mode.
This mode would allow Netgear to access the system remotely, it would also allow someone with linux skills to mount the OS partition and data volume manually, and do troubleshooting on their own.
What apps do you have installed? It is possible (perhaps even probable) that an app incompatibility is interfering with the ReadyNAS application. Though it sounds like the apache server is working, since qBittorrent's web page is responsive.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
Thanks for that info.
The only app I have running is qbittorrent 3.3 I think
Just put the NAS in Tech Support Mode
Loged in as root (thanks google for password)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
@petercae wrote:
Logged in as root (thanks google for password)
You can mount the OS partition (and chroot) by entering
# rnutil chroot
That should be enough to troubleshoot, though /apps won't be there (since it is a mount point for /data/.apps). But you can mount the data volume also with
# btrfs device scan # btrfs fi show # mount /dev/md127 /data
This assumes the data volume is healthy (which seems to be the case, since qbittorent works, and I think you have access to the shares).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
Thanks again,
Yes I can run the commands but I am not familiar enough with linux or ReadyNAS to know where to look to fix this problem.
Took the HDs out and put an old HD in and ran factory reset from the boot menu but it gave an error, might be something with the old HD.
Put the HDs back and ran OS reset from the boot command but it didn't fix the problem.
I was able to ssd to the ReadyNAS as root, looked at the logs in var and didn't find any errors.
Suggestions?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
Generally to access the logs you run journalctl. I think in this case you'd be looking for errors related to readynasd or apache - you can use grep to filter on those. For example,
# journalctl | grep -i readynasd # journalctl | grep -i apache
Figuring out how to fix it is another matter. Though it seems counter-intuitive, it might be faster for you to back up the files, do a factory reset, rebuild the NAS, and restore your data from the backup.
Seems to me there is likely a command that would let you create the log zip file via ssh - but I don't know what it is. Perhaps @JohnCM_S can share that (or other tips on troubleshooting the this problem).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
Hi Thanks thanks again...
Yes it looks like Apache is the problem
I dont seem to be able to attach logs only images on this site
extract bellow
---------------------------------------------------------
May 09 07:40:32 ReadyNAS systemd[1]: Starting The Apache HTTP Server (Safe Mode)...
May 09 07:40:33 ReadyNAS apache2[2531]: AH00526: Syntax error on line 3 of /etc/frontview/apache/fv-admin.conf:
May 09 07:40:33 ReadyNAS apache2[2531]: DocumentRoot '/frontview/dashboard' is not a directory, or is not readable
May 09 07:40:33 ReadyNAS systemd[1]: apache2-safe.service: Control process exited, code=exited status=1
May 09 07:40:33 ReadyNAS systemd[1]: Failed to start The Apache HTTP Server (Safe Mode).
May 09 07:40:33 ReadyNAS systemd[1]: apache2-safe.service: Unit entered failed state.
May 09 07:40:33 ReadyNAS systemd[1]: apache2-safe.service: Failed with result 'exit-code'.
May 09 07:39:47 ReadyNAS readynasd[2341]: readynasd log started
May 09 07:39:48 ReadyNAS readynasd[2341]: readynasd started. (restarted=0)
May 09 07:39:48 ReadyNAS readynasd[2341]: DB (main) schema version: 24 ==> 24
May 09 07:39:49 ReadyNAS readynasd[2341]: DB (queue) schema version: new ==> 0
May 09 07:39:56 ReadyNAS readynasd[2341]: I/O warning : failed to load external entity "/frontview/dashboard/dictionary.xml"
May 09 07:40:14 ReadyNAS readynasd[2341]: Service 'apache2.service' went to unexpected state 'failed'. Expect to be 'inactive'('deactivating').
May 09 07:40:25 ReadyNAS readynasd[2341]: Service 'apache2.service' went to unexpected state 'failed'. Expect to be 'active'('activating').
May 09 07:40:26 ReadyNAS readynasd[2341]: Failed to call method GetUnitFileState: No such file or directory
---------------------------------------------------------------------------------------------------------------------------------------------
Can it be fixed or is it a facory reset?
Tried to do a OS reinstall with 6.10.0 and 6.9.5 and I get "DEBUG: $PORT $IP Recovery" error.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
@petercae wrote:
I dont seem to be able to attach logs only images on this site
You can attach .txt or .pdf also. Don't post the full log zip files, as there is some privacy leakage.
@petercae wrote:
May 09 07:40:33 ReadyNAS apache2[2531]: DocumentRoot '/frontview/dashboard' is not a directory, or is not readable
It looks like there is some corruption in /frontview. Does /frontview/dashboard exist?
FWIW, /frontview on my rn526 holds
root@NAS:/frontview# ls -al total 20 drwxr-xr-x 1 root root 54 Apr 30 05:50 . drwxr-xr-x 1 root root 262 Apr 30 05:51 .. drwxr-xr-x 1 root root 528 Apr 30 05:51 bin drwxr-xr-x 1 root root 46 Apr 30 05:50 conf drwxr-xr-x 1 root root 1046 Apr 30 05:54 dashboard drwxr-xr-x 1 root root 286 Apr 30 05:50 lib lrwxrwxrwx 1 root root 18 Apr 30 05:50 recovery -> dashboard/recovery
/frontview/dashboard holds
root@NAS:/frontview# ls -al dashboard total 18960 drwxr-xr-x 1 root root 1046 Apr 30 05:54 . drwxr-xr-x 1 root root 54 Apr 30 05:50 .. -rw-r--r-- 1 root root 2803 Dec 6 21:38 amazoncb.html -rw-r--r-- 1 root root 4199 Dec 6 21:38 amazondrivecb.html -rw-r--r-- 1 root root 475 Dec 6 21:38 auth.html -rw-r--r-- 1 root root 1411062 Mar 21 23:38 browse_6.10.10360.61000019.js -rw-r--r-- 1 root root 1372833 Apr 14 2018 browse_6.10.9772.61000019.js -rw-r--r-- 1 root root 18096 Mar 22 01:51 browse.html -rw-r--r-- 1 root root 551 Dec 6 21:38 csrf.html -rw-r--r-- 1 root root 9767 Mar 21 13:07 csrf.js drwxr-xr-x 1 root root 450 Apr 30 05:50 css -rw-r--r-- 1 root root 7743743 Apr 16 23:46 dictionary.xml -rw-r--r-- 1 root root 4054 Dec 6 21:38 dropboxcb.html -rw-r--r-- 1 root root 2702 Dec 6 21:38 dropboxmigrcb.html -rw-r--r-- 1 root root 1244 Jan 3 23:55 emailservicecb.html -rw-r--r-- 1 root root 513 Dec 6 21:38 error.html drwxr-xr-x 1 root root 96 Apr 30 05:50 extjs -rw-r--r-- 1 admin admin 3638 Feb 10 2018 favicon.ico drwxr-xr-x 1 root root 162 Apr 30 05:50 fonts -rw-r--r-- 1 root root 3257402 Mar 21 23:38 frontview_6.10.10360.61000019.js -rw-r--r-- 1 root root 3103680 Apr 14 2018 frontview_6.10.9772.61000019.js -rw-r--r-- 1 root root 1240 Dec 7 04:13 fwbroker.html -rw-r--r-- 1 root root 4127 Dec 6 21:38 googledrivecb.html drwxr-xr-x 1 root root 15938 Apr 30 05:54 help -rw-r--r-- 1 root root 19725 Mar 22 01:51 index.html -rwsr-x--- 1 root admin 29296 Mar 14 23:35 lfsdownload.cgi -rwsr-x--- 1 root admin 32056 Mar 14 23:35 lfsupload.cgi -rw-r--r-- 1 admin admin 307 Feb 10 2018 nonadmin_redirect.html -rw-r--r-- 1 root root 13026 Dec 6 21:38 oauth2EnDeCryption.js -rw-r--r-- 1 root root 4183 Dec 6 21:38 onedrivecb.html drwxr-xr-x 1 root root 378 Apr 30 05:50 recovery lrwxrwxrwx 1 root root 26 Apr 30 05:50 rnv_version -> /etc/readyNASVault.version -rw-r--r-- 1 root root 18743 Mar 4 17:13 user_locked.html -rw-r--r-- 1 root root 1151587 Mar 21 23:38 wizard_6.10.10360.61000019.js -rw-r--r-- 1 root root 1112166 Apr 14 2018 wizard_6.10.9772.61000019.js -rw-r--r-- 1 root root 18106 Mar 22 01:51 wizard.html drwxr-xr-x 1 root root 24 Apr 30 05:50 xml
There might be some differences with the RN104 - I can start up my RN102 and take a look.
@petercae wrote:
Can it be fixed or is it a factory reset?
Tried to do a OS reinstall with 6.10.0 and 6.9.5 and I get "DEBUG: $PORT $IP Recovery" error.
I'd do a factory reset. Even if you get past /frontview/dashboard there could be other files that are missing or corrupted. It'll be difficult to find them all.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
Hi Thanks,
I ssh to it and I worry about the default password for root!
It all looks similar.
Might get your expert eyes over it 😉
-----------------------------------------------------
root@ReadyNAS:/frontview# ls -l
total 16
drwxr-xr-x 2 root root 4096 May 9 20:16 bin
drwxr-xr-x 2 root root 4096 May 9 20:08 conf
drwxr-xr-x 8 root root 4096 May 9 20:08 dashboard
drwxr-xr-x 4 root root 4096 May 9 20:08 lib
lrwxrwxrwx 1 root root 18 May 9 20:08 recovery -> dashboard/recovery
-----------------------------------------------------
root@ReadyNAS:/frontview/dashboard# ls -l
total 18996
-rw-r--r-- 1 root root 2803 Dec 7 12:38 amazoncb.html
-rw-r--r-- 1 root root 4199 Dec 7 12:38 amazondrivecb.html
-rw-r--r-- 1 root root 475 Dec 7 12:38 auth.html
-rw-r--r-- 1 root root 1411062 Mar 22 13:38 browse_6.10.10360.61000019.js
-rw-r--r-- 1 root root 1372833 Apr 15 2018 browse_6.10.9772.61000019.js
-rw-r--r-- 1 root root 18096 Mar 22 15:55 browse.html
-rw-r--r-- 1 root root 551 Dec 7 12:38 csrf.html
-rw-r--r-- 1 root root 9767 Mar 22 03:07 csrf.js
drwxr-xr-x 2 root root 4096 May 9 20:08 css
-rw-r--r-- 1 root root 7749134 Mar 22 13:19 dictionary.xml
-rw-r--r-- 1 root root 4054 Dec 7 12:38 dropboxcb.html
-rw-r--r-- 1 root root 2702 Dec 7 12:38 dropboxmigrcb.html
-rw-r--r-- 1 root root 1244 Jan 4 14:55 emailservicecb.html
-rw-r--r-- 1 root root 513 Dec 7 12:38 error.html
drwxr-xr-x 4 root root 4096 May 9 20:08 extjs
-rw-r--r-- 1 admin admin 3638 Feb 11 2018 favicon.ico
drwxr-xr-x 2 root root 4096 May 9 20:08 fonts
-rw-r--r-- 1 root root 3257402 Mar 22 13:38 frontview_6.10.10360.61000019.js
-rw-r--r-- 1 root root 3103680 Apr 15 2018 frontview_6.10.9772.61000019.js
-rw-r--r-- 1 root root 1240 Dec 7 19:13 fwbroker.html
-rw-r--r-- 1 root root 4127 Dec 7 12:38 googledrivecb.html
drwxr-xr-x 3 root root 20480 May 9 20:08 help
-rw-r--r-- 1 root root 19725 Mar 22 15:55 index.html
-rwsr-x--- 1 root admin 26732 Mar 15 13:40 lfsdownload.cgi
-rwsr-x--- 1 root admin 29264 Mar 15 13:40 lfsupload.cgi
-rw-r--r-- 1 admin admin 307 Feb 11 2018 nonadmin_redirect.html
-rw-r--r-- 1 root root 13026 Dec 7 12:38 oauth2EnDeCryption.js
-rw-r--r-- 1 root root 4183 Dec 7 12:38 onedrivecb.html
drwxr-xr-x 5 root root 4096 May 9 20:08 recovery
lrwxrwxrwx 1 root root 26 May 9 20:08 rnv_version -> /etc/readyNASVault.version
-rw-r--r-- 1 root root 18743 Mar 5 08:13 user_locked.html
-rw-r--r-- 1 root root 1151587 Mar 22 13:38 wizard_6.10.10360.61000019.js
-rw-r--r-- 1 root root 1112166 Apr 15 2018 wizard_6.10.9772.61000019.js
-rw-r--r-- 1 root root 18106 Mar 22 15:55 wizard.html
drwxr-xr-x 2 root root 4096 May 9 20:08 xml
-----------------------------------------------------
I have about 9TB of data, mostly converted movie and audio collection that I would hate to have to backup.
Is there a guide to do a factory reset to 6.10.0?
I guess If I do a factory reset it will take me back to version 5 or older of the OS?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
@petercae wrote:
I worry about the default password for root!
Can you explain this more?
@petercae wrote:
It all looks similar.
Yes it does, and certainly /frontview/dashboard should be accessible. So the error is odd.
@petercae wrote:
Is there a guide to do a factory reset to 6.10.0?
I guess If I do a factory reset it will take me back to version 5 or older of the OS?
A factory reset would reinstall 6.10.0 onto the disks. Whenever you do a firmware update, the system writes the current firmware install package into the flash memory.
The guide is on pages 28-29 here: http://www.downloads.netgear.com/files/GDC/READYNAS-100/ReadyNAS_%20OS6_Desktop_HM_EN.pdf
The manual calls the procedure "factory default", not reset.
@petercae wrote:I have about 9TB of data, mostly converted movie and audio collection that I would hate to have to backup.
Well, if it isn't backed up somewhere, then at some point you will lose it. Of course even with a backup, restoring 9 TB of data will take a while, so it is a painful option.
Paid netgear support is another avenue, though they might want to sort out how you've used ssh.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
Hi Thanks,
Somehow my ssh root password is password!
I did look at the manual but there is not much to it.
If I want to try a "Factory Default" without losing the data on the disks, can I still use a scratch disk?
Is there a "Factory Default" Guide using a scratch disk?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
@petercae wrote:Somehow my ssh root password is password!
It's normally the same as the admin password of the NAS. But not something to worry about right now.
@petercae wrote:
If I want to try a "Factory Default" without losing the data on the disks, can I still use a scratch disk?
Is there a "Factory Default" Guide using a scratch disk?
Well, doing a "factory default" installs the software onto the disks (destroying whatever was on them before).
You could try doing a default to a scratch disk. If it works, it would only tell you that the flash has the correct contents. It won't solve the issue on your current disks. The process is simple - just power down, remove your current disks (labeling by slot, so you can properly install them later). Then follow the procedure in the manual. When done, you'd power down again, and reinsert your operational disks into their original slots.
It might be possible to copy off some folders in the OS partition to external storage, and then overwrite those folders on your operational disks. But it is high-risk (and you'd need to be very careful to preserve ownership and file permissions). Definitely not something to attempt without a backup.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
Hi Stephen
Thanks so much for your tireless help!
To me it seems to be irresponsible to install the OS in the same drives as the data without a way to reinstall the OS without wiping the data.
Peter
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Buggy firmware 6.10.0 on RN104?
@petercae wrote:To me it seems to be irresponsible to install the OS in the same drives as the data without a way to reinstall the OS without wiping the data.
I don't know if I'd go quite that far, but I do agree it would be good if there was a supported way to fully reinstall the OS (and also if there was a good way to back it up to the data partition). It would be tricky to re-apply the settings safely though.