NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Readynas 424 SSH service not starting (no error)
Hi all, I updated from 6.10.3 -> 6.10.4 today, against my better judgement (I've had issues with updating firmware in the past) and again, I'm having issues, the firmware update screwed with mono, so...
Killerjerick wrote:the only thing that I did around the time of the issues was attempt to install a full version of FFMPEG, which is why in my case I assumed I had accidentally installed it to the OS partition, but that seems to not be the case, judging from log files.
Are you saying you didn't successfully install FFMPEG at all, or that you think you didn't install it to the OS partition. Because if you did successfully install it via SSH and a .deb package, it most definitely would have installed to the OS partition. While that alone shouldn't fill your OS partition, it could be pointing to it as workspace, which could become problematic if you've actually used it.
But another possibility is that this installation's dependancies installed an update to a package already in the NAS with one that's incompatible with the Netgear portion or over-wrote a configuration file that it needs. While an OS re-install will, I believe, restore most Debian packages that are a part of the OS to their proper version, it doesn't over-write all configuration files because it doesn't want to mess with your properly installed apps.
So while you are in support mode, it would be good to still check that the OS partition isn't too full.
As well as editing the default services file you may also need to create a symlink whilst the OS partition is mounted (if it doesn't already exist):
ln -s /lib/systemd/system/ssh.service /sysroot/etc/systemd/system/multi-user.target.wants/ssh.service
You might also need to chroot in order to get the commands you want to use.
Instead of starting with the mdadm-assemble command suggested by rn_enthusiast you could start with
# rnutil chroot
That should start RAID, mount the OS partition, and chroot in one step.
Going into the chroot is not needed for rn_enthusiast's commands or the one I mentioned. You can do it if you want, once you chroot into the sysroot you would remove references to sysroot in any of the commands until you exit the chroot again.
You are changing a config file. No need for chroot to do that :) It would just complicate matters as you need to exit out of it again, etc.
Also, the rnutil chroot command will start the data raid. There isn't really a need for that.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
