Time Machine SMB share not available under fresh install of FreeNAS 11.3

[GreaseMonkey88]

Problem: Time Machine SMB share not advertised in Time Machine system preferences.

I can connect to the SMB share through the finder in macOS Catalina, but I cannot use it as a Time Machine target. I've tried like everything, even did a fresh install of FreeNAS 11.3, but no luck so far.

Also, the FreeNAS server is not shown as a Mac file server in the finder, but as a PC machine. I have another FreeNAS 11.3 server running, which works just fine and shows up in the finder as a Mac server. No problems with Time Machine either.

 

[dashtesla]

Actually same here I also use the Time Machine for my backups but I think it's related to all the other SMB Permission issues we're having with the latest releases, though before this when It was still working I was having mixed luck with time machine I often get failed backups even though I could map a network drive.

It should however show up as an option, and i'm 100% sure it did show up on 11.2 before even on my broken system.

There's a new release of Catalina 10.15.3 might wanna upgrade see if it's still not working.

 

[anodos]

Post output of "testparm -s"

 

[GreaseMonkey88]

There you go:

root@BigStorage[~]# testparm -s
Load smb config files from /usr/local/etc/smb4.conf
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
aio max threads = 2
bind interfaces only = Yes
disable spoolss = Yes
dns proxy = No
enable web service discovery = Yes
interfaces = 127.0.0.1 10.0.0.43
kernel change notify = No
load printers = No
logging = file
map to guest = Bad User
max log size = 51200
netbios aliases = BigStorage
nsupdate command = /usr/local/bin/samba-nsupdate -g
server min protocol = SMB2_02
server multi channel support = Yes
server role = standalone server
server string = BigStorage
unix extensions = No
username map = /usr/local/etc/smbusername.map
username map cache time = 60
idmap config *: range = 90000001-100000000
fruit:nfs_aces = No
idmap config * : backend = tdb
allocation roundup size = 0
case sensitive = Yes
directory name cache size = 0
dos filemode = Yes
include = /usr/local/etc/smb4_share.conf
strict sync = No


[TimeMachineBigStorage]
aio write size = 0
ea support = No
guest ok = Yes
mangled names = illegal
path = /mnt/RedPro-8TB-Pool/TimeMachine
read only = No
vfs objects = zfs_space ixnas fruit streams_xattr
nfs4:acedup = merge
nfs4:chown = true
fruit:volume_uuid = 05ef51ef-515f-4039-b430-f29ebd96880c
fruit:time machine = yes
fruit:resource = stream
fruit:metadata = stream

 

[anodos]

One more request: post output of midclt call sharing.smb.query

 

[GreaseMonkey88]

root@BigStorage[~]# midclt call sharing.smb.query
[{"id": 4, "path": "/mnt/RedPro-8TB-Pool/TimeMachine", "home": false, "timemachine": true, "name": "TimeMachineBigStorage", "comment": "", "ro": false, "browsable": true, "recyclebin": false, "showhiddenfiles": false, "shadowcopy": false, "guestok": true, "guestonly": false, "abe": false, "hostsallow": [], "hostsdeny": [], "vfsobjects": ["catia", "fruit", "ixnas", "streams_xattr", "zfs_space", "zfsacl"], "vuid": "05ef51ef-515f-4039-b430-f29ebd96880c", "auxsmbconf": "", "enabled": true}]
root@BigStorage[~]#

 

[anodos]

Is server visible when you run command dns-sd -B _adisk._tcp. from Mac? What about dns-sd -B _smb._tcp.

 

[GreaseMonkey88]

I ran both commands, but unfortunately only my working FreeNAS server was found. The one in question is not found.

I think you are pointing in the right direction. Maybe there is something wrong with zeroconf/mDNS. I compared the SMB server and SMB share .conf files with the good working FreeNAS server and they are both identical.

 

[anodos]

I ran both commands, but unfortunately only my working FreeNAS server was found. The one in question is not found.

I think you are pointing in the right direction. Maybe there is something wrong with zeroconf/mDNS. I compared the SMB server and SMB share .conf files with the good working FreeNAS server and they are both identical.

Run command 'midclt call mdnsadvertise.restart' on the affected server and then repeat the process.

 

[GreaseMonkey88]

No, unfortunately no change.

 

[anodos]

No, unfortunately no change.

What if you restart mdnsd service mdnsd onerestart and then restart the mdns advertisements with the previous commands? What is output of midclt call service.query?

 

[GreaseMonkey88]

Restarting mdnsd did not work, my Macs can't find the server.

Here is the output of midclt call service.query

root@BigStorage[~]# midclt call service.query
[{"id": 2, "service": "afp", "enable": false, "state": "STOPPED", "pids": []}, {"id": 4, "service": "cifs", "enable": true, "state": "RUNNING", "pids": []}, {"id": 5, "service": "dynamicdns", "enable": false, "state": "STOPPED", "pids": []}, {"id": 6, "service": "ftp", "enable": false, "state": "STOPPED", "pids": []},{"id": 7, "service": "iscsitarget", "enable": false, "state": "STOPPED", "pids": []}, {"id": 9, "service": "nfs", "enable": false, "state": "STOPPED", "pids": []}, {"id": 10, "service": "snmp", "enable": false, "state": "STOPPED", "pids": []}, {"id": 11, "service": "ssh", "enable": true, "state": "RUNNING", "pids": [1207]}, {"id": 12, "service": "tftp", "enable": false, "state": "STOPPED", "pids": []}, {"id": 14, "service": "ups", "enable": false, "state": "STOPPED", "pids":[]}, {"id": 16, "service": "rsync", "enable": false, "state": "STOPPED", "pids": []}, {"id": 18, "service": "smartd", "enable": true, "state": "RUNNING", "pids": [1193]}, {"id": 21, "service": "lldp", "enable": false, "state": "STOPPED", "pids": []}, {"id": 22, "service": "webdav", "enable": false, "state": "STOPPED","pids": []}, {"id": 23, "service": "s3", "enable": false, "state": "STOPPED", "pids": []}]

I also teset all three commands (dns-sd -B _adisk._tcp. / dns-sd -B _smb._tcp. / dns-sd -B _http._tcp.) on the server in question, and it found only itself, nothing else although there are more servers found running these commands on my Macs. Just as it was not connected to the network...

 

[anodos]

Restarting mdnsd did not work, my Macs can't find the server.

Here is the output of midclt call service.query

root@BigStorage[~]# midclt call service.query
[{"id": 2, "service": "afp", "enable": false, "state": "STOPPED", "pids": []}, {"id": 4, "service": "cifs", "enable": true, "state": "RUNNING", "pids": []}, {"id": 5, "service": "dynamicdns", "enable": false, "state": "STOPPED", "pids": []}, {"id": 6, "service": "ftp", "enable": false, "state": "STOPPED", "pids": []},{"id": 7, "service": "iscsitarget", "enable": false, "state": "STOPPED", "pids": []}, {"id": 9, "service": "nfs", "enable": false, "state": "STOPPED", "pids": []}, {"id": 10, "service": "snmp", "enable": false, "state": "STOPPED", "pids": []}, {"id": 11, "service": "ssh", "enable": true, "state": "RUNNING", "pids": [1207]}, {"id": 12, "service": "tftp", "enable": false, "state": "STOPPED", "pids": []}, {"id": 14, "service": "ups", "enable": false, "state": "STOPPED", "pids":[]}, {"id": 16, "service": "rsync", "enable": false, "state": "STOPPED", "pids": []}, {"id": 18, "service": "smartd", "enable": true, "state": "RUNNING", "pids": [1193]}, {"id": 21, "service": "lldp", "enable": false, "state": "STOPPED", "pids": []}, {"id": 22, "service": "webdav", "enable": false, "state": "STOPPED","pids": []}, {"id": 23, "service": "s3", "enable": false, "state": "STOPPED", "pids": []}]

I also teset all three commands (dns-sd -B _adisk._tcp. / dns-sd -B _smb._tcp. / dns-sd -B _http._tcp.) on the server in question, and it found only itself, nothing else although there are more servers found running these commands on my Macs. Just as it was not connected to the network...

That might be an issue with interface indexes (if there's an error in interface index calculatoin. Try removing the SMB bind IP address.

 

[GreaseMonkey88]

That might be an issue with interface indexes (if there's an error in interface index calculatoin. Try removing the SMB bind IP address.

I had that removed yesterday, but even then no change.

So I finally shutdown the hole system yesterday evening, the FreeNAS VM and the ESXi host. Today I turned it back on and all of a sudden it works! Although I restarted the FreeNAS VM multiple times yesterday... We will see tomorrow, if it still works. But thanks for you help!

 

[anodos]

I had that removed yesterday, but even then no change.

So I finally shutdown the hole system yesterday evening, the FreeNAS VM and the ESXi host. Today I turned it back on and all of a sudden it works! Although I restarted the FreeNAS VM multiple times yesterday... We will see tomorrow, if it still works. But thanks for you help!

Ah, it was a VM. I have noticed reports erratic behavior with mDNS in virtualized FreeNAS (possibly odd interaction or permissions between the host and the VM), but these can also occur in 11.2.

 

[GreaseMonkey88]

Ok. Well, I had this FreeNAS machine even in 11.2 running on ESXi. And my other FreeNAS machine is also a VM on ESXi which runs just fine. If I can support you in any way with further test or else, I‘m happy to help!