NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Move /home to another volume
I used to have two JBOD disks, one 3TB and one 4TB. The first one had /home mounted. I removed the 3TB to make room for a new 8TB disk. Copied files from the 4TB disk to the new one. Then put the 3TB...
There are systemd mount files for homes and apps. The path to mount is specified inside these files. You may need to manually update these.
Also check /etc/fstab to make sure the old volume isn’t still mentioned in that.
thanks a lot, the systemd config change did it. Alhough the question remains why this isn't reflected in the web gui. But then I am still using 6.8.1.
mdgm-ntgrwrote:There are systemd mount files for homes and apps. The path to mount is specified inside these files. You may need to manually update these.
Also check /etc/fstab to make sure the old volume isn’t still mentioned in that.
while the system works now unsing SMB and other services, I can no longer use the admin page. Browser tells me it's offline, after logging in and overriding the browser's certificate panic.
Readynasd seems to have issues starting up properly:
systemctl status readynasd
● readynasd.service - ReadyNAS System Daemon
Loaded: loaded (/lib/systemd/system/readynasd.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Sun 2018-04-15 00:35:55 CEST; 14min ago
Process: 6828 ExecStart=/usr/sbin/readynasd -v 3 -t (code=exited, status=255)
Main PID: 6828 (code=exited, status=255)
Status: "Importing DB"
Apr 15 00:35:55 BingNAS systemd[1]: readynasd.service: Unit entered failed state.
Apr 15 00:35:55 BingNAS systemd[1]: readynasd.service: Failed with result 'exit-code'.
Apr 15 00:35:55 BingNAS systemd[1]: readynasd.service: Service hold-off time over, scheduling restart.
Apr 15 00:35:55 BingNAS systemd[1]: Stopped ReadyNAS System Daemon.
Apr 15 00:35:55 BingNAS systemd[1]: readynasd.service: Start request repeated too quickly.
Apr 15 00:35:55 BingNAS systemd[1]: Failed to start ReadyNAS System Daemon.
Apr 15 00:35:55 BingNAS systemd[1]: readynasd.service: Unit entered failed state.
Apr 15 00:35:55 BingNAS systemd[1]: readynasd.service: Failed with result 'start-limit-hit'.Is there any other config file that must be modified?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
