I just updated to version 6.7  and the only issue that i am running to is the SMB share for the time machine. It starts to work and after a couple of minutes it stops working on my Macbook Pro. All it says is stopping and it wait for the next time to run again and it just keeps happening. Any one has the same issue that has resolve it and that can help me please.

 

Thank you.

Has anyone ran into this issue? 

+1

I am not having the same issue per se, rather I am unable to view the SMB share in Time Machine. I can create with all of the variables and then when in time machine, add disk, nothing is visible. In contrast, when I create a share for Time Machine using AFP, it shows up and am able to use it.

19 minutes ago, mfwade said:

I am not having the same issue per se, rather I am unable to view the SMB share in Time Machine. I can create with all of the variables and then when in time machine, add disk, nothing is visible. In contrast, when I create a share for Time Machine using AFP, it shows up and am able to use it.

Are you able to back up through wireless using afp protocol? I am able to do it through smb but for some reason it starts and then stops. It does not complete. What you mean by the variables? 

Same problem for me. It seems that the "Time Machine support via SMB" is not working if Active Directory implementation is enabled at the SMB settings on V 6.7.

While checking the /etc/rc.d/rc.samba script, I found out that if [ "$SECURITY" = "ads" ] then no "fruit:..." settings will be done at /etc/samba/smb-names.conf.

Without these settings, there is no Time Machine support via SMB. See also here: https://www.mankier.com/8/vfs_fruit

If I'm adding the fruit settings manually (and restart the SMB deamon) then I'm able to see the SMB-Share at Time Machine for adding the share.

But I also remember, that there are some issues on this implementation of fruit/samba. If im not wrong, maybe this is the reason why it is not working as expected...

7 minutes ago, Reini said:

Same problem for me. It seems that the "Time Machine support via SMB" is not working if Active Directory implementation is enabled at the SMB settings on V 6.7.

While checking the /etc/rc.d/rc.samba script, I found out that if [ "$SECURITY" = "ads" ] then no "fruit:..." settings will be done at /etc/samba/smb-names.conf.

Without these settings, there is no Time Machine support via SMB. See also here: https://www.mankier.com/8/vfs_fruit

If I'm adding the fruit settings manually (and restart the SMB deamon) then I'm able to see the SMB-Share at Time Machine for adding the share.

But I also remember, that there are some issues on this implementation of fruit/samba. If im not wrong, maybe this is the reason why it is not working as expected...

I dont have any of the fruit code in the smb setting under unraid. It finds the smb and I am able to connect and it starts. It seems like there is a timeout or something is stopping it. 

1 hour ago, Tucubanito07 said:

Are you able to back up through wireless using afp protocol? I am able to do it through smb but for some reason it starts and then stops. It does not complete. What you mean by the variables? 

Yea, I am able to backup over the wire and wireless with the AFP protocol. The variables are all set in Unraid (web GUI) when setting up the ‘share’.

 

-MW

Just now, mfwade said:

Yea, I am able to backup over the wire and wireless with the AFP protocol. The variables are all set in Unraid (web GUI) when setting up the ‘share’.

 

-MW

By any chance do you know the variables that I need to use please? 

2 hours ago, mfwade said:

Yea, I am able to backup over the wire and wireless with the AFP protocol. The variables are all set in Unraid (web GUI) when setting up the ‘share’.

 

-MW

If this works well, the it would be great to know the right settings.

On the other side, I read "Note: AFP is now deprecated and macOS users are encouraged to use SMB only." at: 

 

 

So, AFP don't run stable and the SMB-Share isn't visible in Time Machine wile ADS is enabled, hmmm ...

Edited May 13, 20197 yr by Reini

2 hours ago, Tucubanito07 said:

I dont have any of the fruit code in the smb setting under unraid. It finds the smb and I am able to connect and it starts. It seems like there is a timeout or something is stopping it. 

Have you configured unRAID-SMB with joining to an Active Directory domain controller ?

I used the following however, I am unable to provide the Time Machine screenshot as I did not configure my VPN to allow discovery.

 

-MW

 

11 minutes ago, Reini said:

Have you configured unRAID-SMB with joining to an Active Directory domain controller ?

I don't know how to do that. I have gone to SMB and enabled the Time share. After that i have one disk just for the share. It seems like it times-out. That is my only issue. i dont know if there is a setting set to run for like 4 minutes and then stop.

3 minutes ago, mfwade said:

I used the following however, I am unable to provide the Time Machine screenshot as I did not configure my VPN to allow discovery.

 

-MW

 

This is exactly how i have it setup. I have the split level set to manually. Would that affect anything?

I don't believe that would affect anything other than how files and folders are written to disk.

 

-MW

15 minutes ago, mfwade said:

I don't believe that would affect anything other than how files and folders are written to disk.

 

-MW

I'll post a picture of mine when I get home. Thanks guys for all the help. 

I change the settings to match yours. Lets see if that works. I did not had AFP on. I only had SMB on with Yes/Time Machine. 

 

It works just like the SMB version however, it will back up for a little bit and then just stops working. I am using the 5GHZ band right next to the router and it keeps stopping for no reason. It seems like is on a timer or set to a maximum of data and then it stops. So weird.

Whenever reporting an issue, always include diagnostics.zip from Tools/Diagnostics page, captured after the issue has happened.

That said, try this:

On Settings/AFP set "Enable AFP" to No.

On Settings/SMB set "Enhanced macOS interoperability" to Yes

Then select your Time Machine share and under SMB Security Settings set "Export" to Yes/TimeMachine.

If you are attempting to use a share that was previously and AFP/TimeMachine target, I believe this should work, but if there are still issues, you should try creating a new share for your Time Machine target and let your Mac create a fresh backup.

7 hours ago, Reini said:

Same problem for me. It seems that the "Time Machine support via SMB" is not working if Active Directory implementation is enabled at the SMB settings on V 6.7.

While checking the /etc/rc.d/rc.samba script, I found out that if [ "$SECURITY" = "ads" ] then no "fruit:..." settings will be done at /etc/samba/smb-names.conf.

Without these settings, there is no Time Machine support via SMB. See also here: https://www.mankier.com/8/vfs_fruit

If I'm adding the fruit settings manually (and restart the SMB deamon) then I'm able to see the SMB-Share at Time Machine for adding the share.

But I also remember, that there are some issues on this implementation of fruit/samba. If im not wrong, maybe this is the reason why it is not working as expected...

Right I didn't have the resources available to test combination of AD with/TimeMachine, so as to not possibly fubar AD further, decided not to add the necessary 'fruit' settings when AD is selected.  You should be able to add these lines to Settings/SMB/Samba extra configuration:

fruit:aapl = yes
fruit:resource = file
fruit:metadata = netatalk
fruit:locking = none
fruit:encoding = native
fruit:nfs_aces = no

And then let me know if this works. 👍

19 minutes ago, limetech said:

Right I didn't have the resources available to test combination of AD with/TimeMachine, so as to not possibly fubar AD further, decided not to add the necessary 'fruit' settings when AD is selected.  You should be able to add these lines to Settings/SMB/Samba extra configuration:

fruit:aapl = yes
fruit:resource = file
fruit:metadata = netatalk
fruit:locking = none
fruit:encoding = native
fruit:nfs_aces = no

And then let me know if this works. 👍

I have this under the SMB. Will that be ok?

 

#vfs_recycle_start
#Recycle bin configuration
[global]
   syslog only = Yes
   log level = 0 vfs:0
#vfs_recycle_end

[rootshare]
path = /mnt/user
comment =
browseable = yes
valid users = tucubanito07
write list = tucubanito07
vfs objects =

fruit:aapl = yes
fruit:resource = file
fruit:metadata = netatalk
fruit:locking = none
fruit:encoding = native
fruit:nfs_aces = no

38 minutes ago, Tucubanito07 said:

I have this under the SMB. Will that be ok? 

You need to put the fruit stuff before [rootshare] so that the settings are global and not specific to 'rootshare' - why do you have 'rootshare' anyway?

2 minutes ago, limetech said:

You need to put the fruit stuff before [rootshare] so that the settings are global and not specific to 'rootshare' - why do you have 'rootshare' anyway?

ok. I will do that. So i can manage my rootshares by smb on my windows 10 computer.

Tucubanito07,

 

Let me know how you make out with your settings. I will open a new thread for my issues with Time Machine backups. 

 

-MW

59 minutes ago, Tucubanito07 said:

ok. I will do that. So i can manage my rootshares by smb on my windows 10 computer.

Unraid is designed to export individual shares.  What you are doing is circumventing, among other things, built-in share security.  I'm assuming you know what you're doing.  This post is for others who read this: my recommendation is don't do what @Tucubanito07 is doing here unless you too, know what you're doing.