ReadyNas104 - SMB not starting File Ownership problems.

Hi All,

Hope you can help me out, I have a level of technical knowledge in as much as I think I know what has happened somehow, but need some help in determining what I need to do to fix the problem.

I have a ReadyNas 104 running (Now) OS 6.6.1 (It was running 6.6.0 at the start of the problem). I t has two 1TB drives configured with RAID 1 and the data only is backed up to a remote NAS every night via RSYNC, which is still working after this problem as it has successfully backed up overnight.

Yesterday we moved ISP's and so I shutdown everything in the office prior to setting up a new router and then bringing everything back on line.

After getting the router set up the next thing to do was power up the NAS, which i thought should be just a matter of turning it back on and it woudl all work, as the ip addrress range and setting of the new router were the same as the old one. On power up the NAS seemed to boot OK, but I was unable to see it on the network from my windows PC.  I could get to the Control Panel, but I could not see any of the shares.  After switching back to the old router and trying again I realised that the issue was not router related, but something to do with the NAS.  I then switched back to the new router.

I noticed that some of the settings on the NAS had changed, all the shares had gone back to file ownership og guest:guest, so I fixed this using the reset option in the shares settings, which solved that issue.  I was able to access the Shares via FTP and I also have SSH access to the NAS.  After SSH'ing in I noticed that all the files on the NAS had been changed to ownership of guest:guest.

I have performed an OS Reinstall from the boot menu in the hope that this would resolve the file ownership and permission errors, it does seem to have helped with some of them, but I am still unable to restart SMB.  I ran journalctl -xe to see what was in the error logs :

Mar 24 06:53:30 AI-NAS systemd[1]: Starting Samba SMB Daemon...
-- Subject: Unit smb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit smb.service has begun starting up.
Mar 24 06:53:30 AI-NAS systemd[1]: Started WSD/LLMNR Discovery/Name Service Daemon.
-- Subject: Unit wsdd2.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit wsdd2.service has finished starting up.
--
-- The start-up result is done.
Mar 24 06:53:30 AI-NAS wsdd2[9357]: starting.
Mar 24 06:53:31 AI-NAS systemd[1]: smb.service: Main process exited, code=exited, status=1/FAILURE
Mar 24 06:53:31 AI-NAS systemd[1]: Failed to start Samba SMB Daemon.
-- Subject: Unit smb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit smb.service has failed.
--
-- The result is failed.
Mar 24 06:53:31 AI-NAS systemd[1]: smb.service: Unit entered failed state.
Mar 24 06:53:31 AI-NAS systemd[1]: smb.service: Failed with result 'exit-code'.
Mar 24 06:53:31 AI-NAS systemd[1]: Stopping WSD/LLMNR Discovery/Name Service Daemon...
-- Subject: Unit wsdd2.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit wsdd2.service has begun shutting down.
Mar 24 06:53:31 AI-NAS wsdd2[9357]: Terminated received.
Mar 24 06:53:31 AI-NAS wsdd2[9357]: Terminated received.
Mar 24 06:53:31 AI-NAS wsdd2[9357]: cannot read netbios name from testparm
Mar 24 06:53:31 AI-NAS wsdd2[9357]: cannot read netbios name from testparm
Mar 24 06:53:31 AI-NAS wsdd2[9357]: terminating.
Mar 24 06:53:31 AI-NAS systemd[1]: Stopped WSD/LLMNR Discovery/Name Service Daemon.
-- Subject: Unit wsdd2.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit wsdd2.service has finished shutting down.
Mar 24 06:53:41 AI-NAS readynasd[2711]: Service 'smb.service' goto unexpected state 'failed'. Expect to be 'a
ctive'('activating').
Mar 24 06:53:41 AI-NAS systemd[1]: Starting Samba NMB Daemon...
-- Subject: Unit nmb.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nmb.service has begun starting up.
Mar 24 06:53:42 AI-NAS systemd[1]: nmb.service: Control process exited, code=exited status=1
Mar 24 06:53:42 AI-NAS systemd[1]: Failed to start Samba NMB Daemon.
-- Subject: Unit nmb.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nmb.service has failed.
--
-- The result is failed.
Mar 24 06:53:42 AI-NAS systemd[1]: nmb.service: Unit entered failed state.
Mar 24 06:53:42 AI-NAS systemd[1]: nmb.service: Failed with result 'exit-code'.
Mar 24 06:53:53 AI-NAS readynasd[2711]: Service 'nmb.service' goto unexpected state 'failed'. Expect to be 'a
ctive'('activating').
Mar 24 06:53:53 AI-NAS readynasd[2711]: Protocol 'replicate' is stopped
Mar 24 06:54:01 AI-NAS cron[2130]: (*system*poweroff) WRONG FILE OWNER (/etc/cron.d/poweroff)
Mar 24 06:54:01 AI-NAS cron[2130]: (*system*frontview-volumeschedule) WRONG FILE OWNER (/etc/cron.d/frontview-volumes
chedule)
Mar 24 06:54:01 AI-NAS cron[2130]: (*system*spindown) WRONG FILE OWNER (/etc/cron.d/spindown)
Mar 24 06:54:01 AI-NAS cron[2130]: (root) WRONG FILE OWNER (crontabs/root)
Mar 24 06:55:01 AI-NAS cron[2130]: (*system*poweroff) WRONG FILE OWNER (/etc/cron.d/poweroff)
Mar 24 06:55:01 AI-NAS cron[2130]: (*system*frontview-volumeschedule) WRONG FILE OWNER (/etc/cron.d/frontview-volumes
chedule)
Mar 24 06:55:01 AI-NAS cron[2130]: (*system*spindown) WRONG FILE OWNER (/etc/cron.d/spindown)
Mar 24 06:55:01 AI-NAS cron[2130]: (root) WRONG FILE OWNER (crontabs/root)
Mar 24 06:55:21 AI-NAS connmand[2138]: ntp: adjust (slew): +0.000672 sec

From this point I am now a bit lost as to which files are causing the problems and what owners should be associated with them.

Any help with resolving this would be much appreciated.

Mark, sort of tech support for one man band office.