NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
GiuseppeMa
Jul 17, 2017Aspirant
ReadyNas 6.x SSH / SMB Crash
Hey.... It seems that this is a neverending topic. Also on our System SSH is not starting anymore. Deinstallation of Log Analyzer- the installtion never work probably - with a reboot.... "solve" ...
GiuseppeMa
Oct 25, 2017Aspirant
Boot into Bootmanager don´t work also.
After unsucessfull try to factory default a hardware change of the complete should "solve the issue".
Plugin the Disc´s - also in different sequence - the system recognize the OS and data - and also the "old error" was back. :(
Second try (again Hardware change) with deleting the disc before - "solve" the issue.
Now the system run´s without any additional apps. :)
blackavenger
Oct 25, 2017Aspirant
I upgraded FW from OS 4 to OS 6.8.1 on my Ultra 4. Moving and syncing data took some time but worked quite well. When everything was up and running including backup from PC to NAS and from NAS to external USB drive I decided to install an app.
Unfortunately I chose Loganalyzer.
Installation failed so I started to check what was wrong via ssh: owner/group was guest/guest and permissions was 777 on most system files. SMB did not work. I started to google and correct things manually. After some time I gave up and decided to use this (desperate) solution:
Thread:
refers to:
Dirty fix ReadyNAS OS6 treestructure permissions, users and groups. Use at our own risk:
https://gist.github.com/paalfe/c4c87be63c7519d1dbe8#file-dirtyfix-readynas-os6-treestructure-sh
This script restores ownership and permissions to the original values. I solved many problems, but not all, may be because it is three years old.
SMB still did not work, but I found: run smbd/nmbd by hand. That means you open a terminal and execute:
Code:
smbd -F -d <integer> -S -s <config file>
nmbd -F -d <integer> -S -s <config file>
and check the output. start at debug level 2 or 3 and increase it if you have got no usable output.
I think I corrected file permissions of the config file, don't remember exactly. After restart, SMB worked!
Other useful commands:
>journalctl -xe to see what was in the error logs
>systemctl --state=failed finds the systemd services which fail to start at boot time.
Still not working:
- Discovery of new FW (has to install manually)
- In my list of directories on the NAS data is blue and free space is white. Snapshots was yellow before my Loganalyser adventure. Now there is no yellow bar at all.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!