TrueNAS 12-RELEASE not seen by Mac OS

[forfiter]

I've just upgraded three of my mac machines (all three different models, two laptops and one desktop) to Mac OS Big Sur 11.1 and they both are no longer able to "see" the True Nas - When selecting Time Machine disks there's no disks to be found, in the browser the "nas.local" doesn't load the TrueNAS login page, the "ping nas.local" in Terminal doesn't seem to be able to resolve TrueNAS hostname to IP. Interestingly, Finder can see and mount shares at the same time, and I do can ping the TrueNAS IP directly, so it seems to be a problem with SMB/mDNS?

What can I do about it? How do I even begin troubleshooting the problem? Without being able to use Time Machine, my entire TrueNAS box is now a completely useless power wasting box of rust...

 

[anodos]

I've just upgraded three of my mac machines (all three different models, two laptops and one desktop) to Mac OS Big Sur 11.1 and they both are no longer able to "see" the True Nas - When selecting Time Machine disks there's no disks to be found, in the browser the "nas.local" doesn't load the TrueNAS login page, the "ping nas.local" in Terminal doesn't seem to be able to resolve TrueNAS hostname to IP. Interestingly, Finder can see and mount shares at the same time, and I do can ping the TrueNAS IP directly, so it seems to be a problem with SMB/mDNS?

What can I do about it? How do I even begin troubleshooting the problem? Without being able to use Time Machine, my entire TrueNAS box is now a completely useless power wasting box of rust...

Run command midclt call service.restart mdns.

 

[forfiter]

Run command midclt call service.restart mdns.

I did, it returned "True" and there's no change on neither of the machines, they can't seem to see/resolve "nas.local" at all.

 

[anodos]

I did, it returned "True" and there's no change on neither of the machines, they can't seem to see/resolve "nas.local" at all.

What is output of ls -l /usr/local/etc/avahi/services?

 

[forfiter]

What is output of ls -l /usr/local/etc/avahi/services?

It's below:

-rw-r--r-- 1 root wheel 827 Dec 24 11:52 ADISK.service
-rw-r--r-- 1 root wheel 201 Dec 24 11:52 AFPOVERTCP.service
-rw-r--r-- 1 root wheel 238 Dec 24 11:52 DEV_INFO.service
-rw-r--r-- 1 root wheel 194 Dec 24 11:52 HTTP.service
-rw-r--r-- 1 root wheel 196 Dec 24 11:52 HTTPS.service
-rw-r--r-- 1 root wheel 205 Dec 24 11:52 MIDDLEWARE_SSL.service
-rw-r--r-- 1 root wheel 202 Dec 24 11:52 MIDDLEWARE.service
-rw-r--r-- 1 root wheel 198 Dec 24 11:52 SFTP_SSH.service
-rw-r--r-- 1 root wheel 194 Dec 24 11:52 SMB.service
-rw-r--r-- 1 root wheel 193 Dec 24 11:52 SSH.service

 

[anodos]

It's below:

-rw-r--r-- 1 root wheel 827 Dec 24 11:52 ADISK.service
-rw-r--r-- 1 root wheel 201 Dec 24 11:52 AFPOVERTCP.service
-rw-r--r-- 1 root wheel 238 Dec 24 11:52 DEV_INFO.service
-rw-r--r-- 1 root wheel 194 Dec 24 11:52 HTTP.service
-rw-r--r-- 1 root wheel 196 Dec 24 11:52 HTTPS.service
-rw-r--r-- 1 root wheel 205 Dec 24 11:52 MIDDLEWARE_SSL.service
-rw-r--r-- 1 root wheel 202 Dec 24 11:52 MIDDLEWARE.service
-rw-r--r-- 1 root wheel 198 Dec 24 11:52 SFTP_SSH.service
-rw-r--r-- 1 root wheel 194 Dec 24 11:52 SMB.service
-rw-r--r-- 1 root wheel 193 Dec 24 11:52 SSH.service

Okay. Look like the service files are properly generated. What happens if you run following commands:
service avahi-daemon stop
avahi-daemon --debug

 

[Patrick M. Hausen]

A tool for your Mac that came in handy for me repeatedly in the past is "Discovery": http://www.tildesoft.com

Lets you examine all mdns service announcements bouncing around in your network.

 

[forfiter]

Okay. Look like the service files are properly generated. What happens if you run following commands:
service avahi-daemon stop
avahi-daemon --debug

That's what I get:

root@nas:~ # service avahi-daemon stop
Stopping avahi-daemon.
root@nas:~ # avahi-daemon --debug
Found user 'avahi' (UID 200) and group 'avahi' (GID 200).
Successfully dropped root privileges.
avahi-daemon 0.7 starting up.
Loading service file /usr/local/etc/avahi/services/ADISK.service.
Loading service file /usr/local/etc/avahi/services/AFPOVERTCP.service.
Loading service file /usr/local/etc/avahi/services/DEV_INFO.service.
Loading service file /usr/local/etc/avahi/services/HTTP.service.
Loading service file /usr/local/etc/avahi/services/HTTPS.service.
Loading service file /usr/local/etc/avahi/services/MIDDLEWARE.service.
Loading service file /usr/local/etc/avahi/services/MIDDLEWARE_SSL.service.
Loading service file /usr/local/etc/avahi/services/SFTP_SSH.service.
Loading service file /usr/local/etc/avahi/services/SMB.service.
Loading service file /usr/local/etc/avahi/services/SSH.service.
Joining mDNS multicast group on interface ix0.IPv4 with address 192.168.168.2.
New relevant interface ix0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for 192.168.168.2 on ix0.IPv4.
Server startup complete. Host name is nas.local. Local service cookie is 1338253256.
Service "nas" (/usr/local/etc/avahi/services/SSH.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/SMB.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/SFTP_SSH.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/MIDDLEWARE_SSL.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/MIDDLEWARE.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/HTTPS.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/HTTP.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/DEV_INFO.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/AFPOVERTCP.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/ADISK.service) successfully established.

 

[forfiter]

This is what Discovery shows me, nothing nas related to be seen there...

 

[anodos]

That's what I get:

root@nas:~ # service avahi-daemon stop
Stopping avahi-daemon.
root@nas:~ # avahi-daemon --debug
Found user 'avahi' (UID 200) and group 'avahi' (GID 200).
Successfully dropped root privileges.
avahi-daemon 0.7 starting up.
Loading service file /usr/local/etc/avahi/services/ADISK.service.
Loading service file /usr/local/etc/avahi/services/AFPOVERTCP.service.
Loading service file /usr/local/etc/avahi/services/DEV_INFO.service.
Loading service file /usr/local/etc/avahi/services/HTTP.service.
Loading service file /usr/local/etc/avahi/services/HTTPS.service.
Loading service file /usr/local/etc/avahi/services/MIDDLEWARE.service.
Loading service file /usr/local/etc/avahi/services/MIDDLEWARE_SSL.service.
Loading service file /usr/local/etc/avahi/services/SFTP_SSH.service.
Loading service file /usr/local/etc/avahi/services/SMB.service.
Loading service file /usr/local/etc/avahi/services/SSH.service.
Joining mDNS multicast group on interface ix0.IPv4 with address 192.168.168.2.
New relevant interface ix0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for 192.168.168.2 on ix0.IPv4.
Server startup complete. Host name is nas.local. Local service cookie is 1338253256.
Service "nas" (/usr/local/etc/avahi/services/SSH.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/SMB.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/SFTP_SSH.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/MIDDLEWARE_SSL.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/MIDDLEWARE.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/HTTPS.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/HTTP.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/DEV_INFO.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/AFPOVERTCP.service) successfully established.
Service "nas" (/usr/local/etc/avahi/services/ADISK.service) successfully established.

Okay. It looks like the service has started just fine, you can hit ^c (control +"c") to kill avahi if you haven't done this yet. Then restart avahi service avahi-daemon onerestart

Once you have done this on you, let's see what's advertising SMB on the network dns-sd -B _smb._tcp. (from MacOS).

 

[forfiter]

Okay. It looks like the service has started just fine, you can hit ^c (control +"c") to kill avahi if you haven't done this yet. Then restart avahi service avahi-daemon onerestart

Once you have done this on you, let's see what's advertising SMB on the network dns-sd -B _smb._tcp. (from MacOS).

That's all I see:

Browsing for _smb._tcp.
DATE: ---Thu 24 Dec 2020---
13:03:13.339 ...STARTING...

 

[anodos]

That's all I see:

Browsing for _smb._tcp.
DATE: ---Thu 24 Dec 2020---
13:03:13.339 ...STARTING...

Are your client and server on different subnets?

 

[forfiter]

Are your client and server on different subnets?

Not to the best of my knowledge and for sure not intentionally. The nas is 192.168.168.106 connected to a wifi router via eth cable and all my clients (Macs) are in the 192.168.168.0/24 network connected to the same router via 5Ghz wifi network. Also, as I said previously, I can ping the nas IP, but I can't ping it using "nas.local".

 

[Patrick M. Hausen]

Unifi access points? Some people reported problems with multicast and some of those.

 

[forfiter]

Unifi access points? Some people reported problems with multicast and some of those.

Nope, Netgear R7000 running latest Merlin firmware. It wasn't a problem until FreeNAS -> TrueNas and Catalina -> Big Sur upgrade that I just made last night.

 

[anodos]

Perhaps double-check with a wired connection to same switch where the NAS is connected.

 

[blacksteel75]

I'm seeing the same problems with mDNS broadcasts since upgrading from 11.3-U5 to 12.0-U1. I have Macs running both Big Sur and Catalina but none of them see the TrueNAS server in the "Network" location from Finder. This causes problems with Time Machine backups.

I have one time machine share configured using the multi-user time machine preset, no aux parameters. I can connect to the SMB share using "Connect to server" and entering smb:// with the IP or hostname. Time Machine in MacOS doesn't always seem to find the server though regardless.

I'm not running AFP. Only SMB shares.

Currently, when I run dns-sd -B _smb._tcp. from a Mac, I do not see the TrueNAS server in the list of instances. Just the other Macs, and a Raspberry PI that I have running the avahi daemon. The RPi seems to run this daemon without any issues.

If I reboot TrueNAS, the TrueNAS server shows up in dns-sd -B _smb._tcp. briefly for some time, and appears in Network in Finder, but at some point it just disappears.

I've run the troubleshooting steps
service avahi-daemon stop avahi-daemon --debug but there isn't any obvious errors. Output is similar to what is shown in an earlier post in this thread. The service is running when I check it's status.

There's no error messages in the system log, /var/log/messages, and I can't find an avahi-daemon log to examine.

I did notice that there is a log file called /var/log/mdnsresponder.log that was last updated before I upgraded from 11.3-U5 to 12.0U1. This seems like it might be related to the issue?

Thanks for any recommendations!

 

[forfiter]

I'm seeing the same problems with mDNS broadcasts since upgrading from 11.3-U5 to 12.0-U1. I have Macs running both Big Sur and Catalina but none of them see the TrueNAS server in the "Network" location from Finder. This causes problems with Time Machine backups.

I have one time machine share configured using the multi-user time machine preset, no aux parameters. I can connect to the SMB share using "Connect to server" and entering smb:// with the IP or hostname. Time Machine in MacOS doesn't always seem to find the server though regardless.

I'm not running AFP. Only SMB shares.

Currently, when I run dns-sd -B _smb._tcp. from a Mac, I do not see the TrueNAS server in the list of instances. Just the other Macs, and a Raspberry PI that I have running the avahi daemon. The RPi seems to run this daemon without any issues.

If I reboot TrueNAS, the TrueNAS server shows up in dns-sd -B _smb._tcp. briefly for some time, and appears in Network in Finder, but at some point it just disappears.

I've run the troubleshooting steps
service avahi-daemon stop avahi-daemon --debug but there isn't any obvious errors. Output is similar to what is shown in an earlier post in this thread. The service is running when I check it's status.

There's no error messages in the system log, /var/log/messages, and I can't find an avahi-daemon log to examine.

I did notice that there is a log file called /var/log/mdnsresponder.log that was last updated before I upgraded from 11.3-U5 to 12.0U1. This seems like it might be related to the issue?

Thanks for any recommendations!

Sadly, my problem still persists, with the exactly same symptoms - looks like TrueNAS 12 is invisible to Mac machines. I was able to hack around it with 'tmutil' and forcing Time Machine to use IP instead of mDNS hostname, but it seems like it breaks something else and it damaged all my existing backups, I had to erase them and start backups again, losing all history and in result, losing actual backups (I tried to use fsck_hfs to fix them, but it didn't work on any of them, sadly).

In addition to that, I'm also seeing Samba processes panicking left and right on a daily basis.

 

[anodos]

Sadly, my problem still persists, with the exactly same symptoms - looks like TrueNAS 12 is invisible to Mac machines. I was able to hack around it with 'tmutil' and forcing Time Machine to use IP instead of mDNS hostname, but it seems like it breaks something else and it damaged all my existing backups, I had to erase them and start backups again, losing all history and in result, losing actual backups (I tried to use fsck_hfs to fix them, but it didn't work on any of them, sadly).

In addition to that, I'm also seeing Samba processes panicking left and right on a daily basis.

The samba issues are fixed in the 12.0-stable branch and will be part of the 12.0-U1.1 release that is coming soon. A bug fix for a memory leak exposed a race condition in the handling of certain timed events. It wasn't caught prior to U1 release, but if you want to verify that it's taken care of for U1.1 you can PM me and I'll send you a dev snapshot where it should be fixed.

If you can PM me a copy of
/usr/local/etc/avahi/services/ADISK.service and
/usr/local/etc/avahi/services/SMB.service

I'll take a look at them and see if something is being misconfigured.

 

[sean_h]

Did this issue ever get resolved? I find I have exactly the same problem; the TrueNas box advertises itself on the local network for only a few minutes before dropping out. After that it can be accessed by IP, but not by its hostname. Attached is the output from the dns-sd command (taken from a MacOS). At the time the Rmv entry appeared in the list, the homeserver entry disappeared from the Mac's Finder. I was doing nothing else between the two entries.

Relevant details:
TrueNas version: TrueNAS-12.0-U3.1
MacOS Version: 11.3.1 Big Sur
I started noticing this issue shortly after upgrading from FreeNAS to TrueNAS Core