NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

FrontView

1000 Topics

4.2.31 on my Ultra 6 has killed my NAS? Drive is read only and frontview hangs.
So I logged into my Ultra 6 and noticed there was a firmware upgrade available from May 2017! Since I get at least two emails from my NAS every day I assume it should have emailed me about this, but anyway, that's a minor problem. I installed the upgrade and then.... time machine no longer worked. My two laptop macs no longer could log in. I rebooted the ReadyNAS (since sometimes it gets in a mode where nothing can log into it) and it didn't help. Probing a little further, I attempted to change the Time Machine access password to be sure I had it correct. The web interface hung! A hard reset and disk check later and some errors were corrected. All SMART reading good and no errors. So I tried again. Same result. Every time I tried to change the time machine access password the UI and effectively the ReadyNAS hung. The next step was re-installing the OS, using the reset hole and front panel buttons. I did this. Another disk check. Now I can attempt to change the time machine access password and it appears to work, except the "volume size" of the time machine space is set back to the default 3000 every time I apply changes. Digging deeper, it appears my partitions are mounted read-only which would explain a lot. # touch /c/doc/SymformContrib/delete_this touch: cannot touch `/c/doc/SymformContrib/delete_this': Read-only file system During boot in kern.log I have this EXT4-fs error (device dm-0): ext4_mb_generate_buddy:726: group 10 blocks in bitmap, 32768 in gd Sep 14 10:59:30 sleepy kernel: Aborting journal on device dm-0-8. Sep 14 10:59:30 sleepy kernel: EXT4-fs (dm-0): Remounting filesystem read-only Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5602: Journal has aborted Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5602: Journal has aborted Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_ext_remove_space:2437: Journal has aborted Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5602: Journal has aborted Sep 14 10:59:30 sleepy kernel: EXT4-fs error (device dm-0) in ext4_orphan_del:2098: Journal has aborted Sep 14 10:59:31 sleepy kernel: EXT4-fs error (device dm-0) in ext4_reserve_inode_write:5602: Journal has aborted The first line seems to be some Linux bug which may have been fixed. My data is there. The filesystem is read only. This seems to be showing up other bugs (such as the entire device hanging). Does anyone have any suggestions beyond "Backup your 12GB data, install OS6 and start again"? Many thanks in advance.
redpola
Sep 19, 2017 Place Use your ReadyNAS
1.1KViews
0likes
5Comments
ReadyNas NV+ v1 no FrontView access, SSH not installed
I powered on my old ReadyNas NV+ v1 yesterday after a few months offline (it's normally disconnected until I need to retrieve or add archival data). The shares are accessible and email notifications seem to work fine however I cannot figure out how to access FrontView. I've read a number of threads and all of them hint to the fact that the firmware (4.1.15 according to RAIDar) might have some conflict with addons or something similar. I've tried various browsers and computers, reset the OS twice, tried to connect over ethernet cable (I'm using a Macbook running macOS Sierra) but to no avail—FrontView is not responding. Unfortunately I don't seem to have SSH active (I'm a novice user that only uses his NAS for the most basic of tasks) so I've run out of ideas. Can anyone help me? Thanks
benfi
Jul 26, 2017 Place Use your ReadyNAS
3.2KViews
0likes
7Comments
Restore user account from ssh
Hello dear community, I used to have several users that I created as I recieved the NAS and was experimenting a year ago. It seems that I removed some user accounts, but I still can see them in passwd, home directory are still there. # getent passwd [...] admin:x:98:98::/home/admin:/bin/bash [...] titimoi:x:100:98:my_email_address@email.com:/home/titimoi:/bin/false another_user:x:103:98:another_email@email.com:/homeanother_user:/bin/false and # ls /home/ admin another_user titimoi Note that I can login to frontview with "another_user" and "titimoi" In Frontview I see only "admin" in Account > User. Questions : - can you help me show "titimoi" and "another_account" in frontview so that I can manage then easiely, what file should I have a look at ? Cheers,
titimoi
May 18, 2017 Place Use your ReadyNAS
4.3KViews
0likes
13Comments
Frontview How do you put it on a PC when the readynas already is operating.
Preactive
Feb 06, 2017 Place Use your ReadyNAS
1.7KViews
0likes
2Comments
FrontView Loading Improperly - EEPROM Issue
Hi everyone! I've been a lurker here for quite some time, and this community has been especially helpful! Finally ran into something I couldn't tackle, though - I'm having the the issues described in these threads, where the EEPROM data is overwritten when USB recovery is used: community.netgear.com/t5/Using-your-ReadyNAS/Unable-to-access-frontview/m-p/946896 community.netgear.com/t5/Using-your-ReadyNAS/Frontview-webpage-loading-partial/m-p/962775 community.netgear.com/t5/Using-your-ReadyNAS/Frontview-problem-readynas-pro-4/m-p/1058765 I was hoping somebody could help me with this. I'm more than capable of working with Linux, but none of the other posts have included the solution publically. Also - I don't generally run any of the stock netgear software/firmware, instead running CentOS as a deduplicated iSCSI storage target, but recently I've been considering selling my unit (not right now, but I wanted to ensure that I COULD return it to stock IF I wanted to). I see that some of the others with this problem have had a one-time fix for this issue. Since I play with custom software on this unit all the time, I'm sure it will happen again. If it's possible to get the solution, rather than just have someone apply the fix, that would definitely be preferable. Thanks!
Solved
tfrederick74656
Jan 11, 2017 Place Use your ReadyNAS
3.1KViews
0likes
3Comments
RN 102 cannot access frontview web admin
Hi folks, after a black out I cannot access the web admin of RN 102. I can SSH root into the box the shares are mounted and availavle usb external drives is not mounted I could update fw via ssh no problem, I am now on bet 6.6.1 t700 followed procedure for USB restore, no luck followed procedure for OS reintall, procedure was completed, but problem still there RAIDar is stuck in "management service is offline" What can I do? What logs can I check?
theluke79
Nov 26, 2016 Place Use your ReadyNAS
3.1KViews
0likes
3Comments
Frontview and supported browsers
I'm confused. I'm sure I used to be able to use Google Chrome from both Win7 and Win10 PCs to access Frontview on my NAS. The issue is one where it loads, after being presented with a warning about security certificates, but the console is minimal, with no active "buttons" In experimenting I've noted the following: From Win10 Pro/64 PC using Chrome 54.0.2840.59 m the problem happens Same platform, Firefox 49.0.1, same issue Same platform, Internet Explorer 11.0.1024017146, ignore the warning, Frontview behaves normally iPad 3 Chrome app, ignore, the warning, Frontview behaves normally Now I've tried the certificate key generation export/import thing from the NAS to Chrome on the WIn10 PC but that's not helped I'll admit I am not well versed in the matter of certificates but arguably it shouldn't be this hard to get one of the most popular browsers to work correctly with Frontview! If I'ver missed or misunderstood something then I stand to be guided! Help!
Solved
Numb3r6
Nov 06, 2016 Place Use your ReadyNAS
4.1KViews
0likes
6Comments
NV+ v1 Nach Update auf 4.1.15 kein Zugriff auf FrontView / Kein Zugriff auf neue Shares
Hallo zusammen, in der letzten Nacht habe ich auf zwei (!) vorhandenen NV+ das Update auf 4.1.15 eingespielt. Bei einem der beiden lief es relativ problemlos. Beim zweiten NAS allerdings gab es massive Probleme. Nach dem Update lässt sich der Apache leider nicht mehr starten. Wenn ich versuche diesen per SSH neu zu starten, erhalte ich die folgende Fehlermeldung: Restarting web server: apache2env: /usr/sbin/apache2ctl: No such file or directory failed! Screenshoot: Weder auf dem funktionierenem NAS noch auf dem NAS bei dem der Apache sich nicht starten lässt (und somit das FrontView nicht erreichbar ist) ist diese Datei vorhanden. Aus lauter Verzweifelung habe ich voller Erwartung das OS-Backup gestartet. Leider mit dem gleichem Ergebnis. Apache startet nicht. Netterweise sind alle Konfigs auch überschrieben und jetzt ist die feste IP weg und er holt sich diese über den DHCP. Mit ifconfig habe ich jetzt temporär die IP wieder statisch bekommen aber FrontView/Apache bleibt weiterhin tot. Nun habe ich schon die /etc/network/interfaces manuell bearbeitet und die statische IP wieder eingetragen aber das ist ja auch keine dauerhafte Lösung. ========================= Beim zweiten NAS wollte ich zur Datensicherung jetzt zusätzliche Shares anlegen um dort die Daten vom ersten NAS sichern zu können. Dabei kann ich im Anschluss leider nicht auf die *neuen* Shares zugreifen (Weder Samba noch NFS - Zugriff erfolgt mit Ubuntu also bitte keine Tipps zu den bekannten Windows-Problemen!). Bislang hatte ich den Sicherheitsmodus auf Share gestellt. Da ich aber gelesen habe, dass der Gastmodus nur unter der Benutzerbasierten Userverwaltung sichtbar wird, habe ich auf diese umgestellt. Auch wenn ich dann dort jeweils den Gastzugang aktiviere, und die Rechte neu setze kann ich nicht auf die Shares zugreifen. Frage 1 [NAS 1]: Wie bringe ich den Apache dazu seinen Dienst wieder aufzunehmen? Frage 2 [NAS 2]: Wie kann ich auf die neuen Shares zugreifen? Möglichst im Share-Modus! Beste Grüße
Solved
Heliophob_
Sep 29, 2016 Place Einsatz von ReadyNAS
3.5KViews
0likes
6Comments
Is FrontView ProFTPd Custom Configuration Broken?
I am running ReadyNAS 6.4.2 and need to do some custom configuration for proftpd, beyond what FrontView permits. The default configuration for proftpd is in /etc/proftpd/proftpd.conf . This configuration file in turn include multiple conf files from /etc/frontview/proftpd which can be adjusted from FrontView. The /etc/proftpd/proftpd.conf includes an instruction not to modify this file directly (presumably because it may change on release and would not be backed up as part of the FrontView configuration). Instead it includes a /etc/frontview/proftpd/proftpd.conf.overrides file where presumably users can override the proftpd configuration without these drawback. So far, fair enough. The problem is that /etc/proftpd/proftpd.conf includes /etc/frontview/proftpd/proftpd.conf.overrides as its first line, not its last! So the net effect is that the overrides are overridden by the default rather than overriding the defaults. That is not very useful and can't have been the intention, can it?
Solved
CarlEdman
May 24, 2016 Place Use your ReadyNAS
3.5KViews
0likes
6Comments
ReadyNas NV+ Development > Questions (Regarding: Frontview / Device Source Code)
Hey the Netgear Commmunity I would like to do some development on the ReadyNas NV+ V1 like if EOL and old but still functinal. Although there is still some bug fixes firmwares coming out, i dont think any huge update will be done. Frontview: I would like to redesign the Frontview and make more modern lol (from what i see from the folder contain html, css, js ...), So is there any information that could be provided on how everything connect together (a little backgroud story to give and idea), also any additinal information that could be helpfull. Device Source Code: The provided source is the kernel and addons right ? Is it possible to build the os from scratch or not ? What exacly missing etc ?
Retired_Member
Dec 28, 2015 Place Use your ReadyNAS
2.8KViews
0likes
4Comments