So, lately I have been having an issue with time machine backups not initiating because the disk could not be located. The only solution I have found is to remote into the FreeNAS box and manually restart the AFP sharing service.
It has been smooth for a solid five months until I had scheduled daily short S.M.A.R.T. tests and weekly long ones. After that is when this problem popped up. I am not sure if it has anything to do with the problem, but I know that the global ZFS snapshots had caused a similar issue with the box when I first got it running, so I had to disable snapshots on the Time Machine volume (or is it technically a directory..?) to prevent that issue.
Also, I am an amateur when it comes to this. I have educated myself to the best of my ability. I am familiar with Linux, Windows, and MacOS. The only solution I can think of as a work around is to have a scheduled script to run after the conclusion of each S.M.A.R.T. test that resets the AFP sharing service. I am just at a loss as to how to do this because I do not know a whole lot when it comes to commands (I just know very basic stuff from Linux).
Possible relevant information:
FreeNas Box running FreeNAS-9.3-STABLE-201506292130
16GB ECC ram
6TB storage, plenty of free space allocated to Time MachineAnd, as a side note: Has anyone gotten Windows10 Preview to recognize their FreeNAS over the network? I heard that it may be a known issue, but haven't heard any solutions.
Thanks.