New Time Machine error since upgrading to TrueNAS-12.0-RC1

[kjacques1]

Hello,

I have been using Time Machine on FreeNas 11.3 for a number of months without issue. I have upgraded to TruNas 12.0 RC1 and it is reporting the following error when trying to access the backup disk.

"An error occurred while enabling ownership on the backup disk. You may need to repair or erase the disk using Disk Utility. If the disk can’t be repaired, select a different disk for backups. Latest successful backup: October 12, 2020"

Any ideas?

 

[Tim1962]

I don't know if transferrable, I deleted the share, set up an identical one but selected multi user time machine. That worked for me. (And on the Mac, remove the TM destination then add the same one again.)

All a bit mystical but functioning

 

[anodos]

Generally, it shouldn't require creating a new backup. My home time machine backup has successfully gone from 11.2->11.3->12.0 transition without rebuild. If you haven't reconfigured yet, can you try sending me a debug via private message?

 

[kjacques1]

I'm making the new backup now with the multi-user turned on. I'll report back after testing to see if the behavior has improved.

 

[kjacques1]

Alas same behavior. How do I send a debug?

 

[anodos]

Alas same behavior. How do I send a debug?

Click "System->Advanced->Save Debug"

 

[TooMuchData]

I have the same problem. Under 12.0 TM fails and reports "The network backup disk does not support the required capabilities." Reboot 11.3-U5 and am currently performing a TM backup. I'm willing to tweak ssettings, but am not willing to delete the dataset (and past backups). Will look to see if there is an issue already reported.

 

[anodos]

I have the same problem. Under 12.0 TM fails and reports "The network backup disk does not support the required capabilities." Reboot 11.3-U5 and am currently performing a TM backup. I'm willing to tweak ssettings, but am not willing to delete the dataset (and past backups). Will look to see if there is an issue already reported.

What is output of "testparm -s"? If you have any shares with "vfs objects" in auxiliary parameters. Try commenting them out (put a "#" in front of them), restarting the SMB service, then possibly rebooting the Mac (to make sure SMB2 session state is clear).

 

[TooMuchData]

TM Backup completed successfully in 11.3-U5. Rebooted both Mac and TrueNAS. Problem still there.

The share in question has these vfs objects: "streams_xattr, zfs_space, zfsacl". Why are they OK in 11.3 but not 12.0?

Testparm -s ouput in attached file.

Commented out vfs objects and restarted SMB. TM seems happy now ("Preparing Backup").

Thanks for the help.

 

[anodos]

TM Backup completed successfully in 11.3-U5. Rebooted both Mac and TrueNAS. Problem still there.

The share in question has these vfs objects: "streams_xattr, zfs_space, zfsacl". Why are they OK in 11.3 but not 12.0?

It's just fallout from changes regarding how we're presenting configuration options. During migration from 11.3->12.0, we move people's SMB config to the new-style (just a few features exposed as checkboxes) if we can do it cleanly. If we can't, the old config gets written to the auxiliary parameters. vfs_fruit _must_ be set on all shares if it is set on one of them (this is just and FYI regarding an implementation detail). I'll just need to add more auxiliary parameter parsing to automatically add vfs fruit to vfs objects if there's an override in that GUI portion.

 

[Jono_K]

To fix this, did you need to comment out the aux params on all your SMB shares, or only the TM share?

 

[anodos]

To fix this, did you need to comment out the aux params on all your SMB shares, or only the TM share?

Only ones starting with "vfs objects ="

 

[runevn]

Only ones starting with "vfs objects ="

I have had the same problem. Removed my aux parameters "vfs objects = zfs_space zfsacl streams_xattr" from the share and now it works.

Just of curiosity is it something I should remove from all my SMB shares after upgrading or is only related to Time Machine?

Thanks for providing a solution!

 

[Jono_K]

Only ones starting with "vfs objects ="

Okay. I feel like an idiot this morning.

Comment out aux params for "vfs objects =" in all SMB shares.

So, I have about 20 different smb shares, one of which has TM enabled. All have a few different vfs objects as aux params. I'll need to change the aux params for all 20 shares from "vfs objects = ob1 ob2 ob3" to "vfs objects = #ob1 #ob2 #ob3" ?

No risk in disabling these parameters?

 

[iancynk]

So, I have about 20 different smb shares, one of which has TM enabled. All have a few different vfs objects as aux params. I'll need to change the aux params for all 20 shares from "vfs objects = ob1 ob2 ob3" to "vfs objects = #ob1 #ob2 #ob3" ?

No risk in disabling these parameters?

I commented it out by "#vfs objects = ob1 ob2 ob3". Time machine now works great.
Did it on all shares, even though I only use time machine on one share. So far no harm done.
(see also: https://www.truenas.com/community/threads/smb-time-machine-on-12-0-beta.86056/#post-596020 )

 

[fahadshery]

My time machine no longer appears in the 'Available disks' after upgrading to the truenas 12.0 core from 11.3 u5.
I also tried creating a new dataset assigning the dedicated user and group for permissions and tried both AFP and SMB shares but my Macbook pro is not picking up the available disks.
What else I could try?

 

[kjacques1]

This also happened to me where the disk no longer appears in available disks after a clean install of Big Sur. I was able to set it up via terminal though. The syntax I used:

sudo tmutil setdestination -ap smb://ken@192.168.0.23/Ken-TimeMachine-SMB

Make sure to change the part after // to your freenas userid, ip address, and name of share.

 

[anodos]

I have a ticket in which mDNS advertisements get broken in some cases when jails are enabled to start on boot. Perhaps check that we're advertising the requisite SRV record "dns-sd -B _adisk._tcp."

 

[fahadshery]

My testparm -s:

Code:

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
        kernel change notify = No
        load printers = No
        logging = file
        map to guest = Bad User
        max log size = 51200
        nsupdate command = /usr/local/bin/samba-nsupdate -g
        registry shares = Yes
        server role = standalone server
        server string = FreeNAS Server
        unix extensions = No
        idmap config *: range = 90000001-100000000
        fruit:nfs_aces = No
        idmap config * : backend = tdb
        directory name cache size = 0
        dos filemode = Yes

[timemachine]
        ea support = No
        guest ok = Yes
        kernel share modes = No
        mangled names = no
        path = /mnt/raid2TB/timemachine
        posix locking = No
        read only = No
        vfs objects = aio_fbsd tmprotect fruit streams_xattr shadow_copy_zfs ixnas
        fruit:locking = none
        fruit:time machine = yes
        fruit:resource = stream
        fruit:metadata = stream
        fruit:encoding = native
        nfs4:chown = true

I have tried creating AFP shares and SMB shares with different presets using the forum and reddit posts. nothing has worked for me.
I can't even see the Time Machine available in the available lists of discs to choose.
This update from FreeNas 11.3-U5 to 12.0 core has been a curse for me! I thought to wait for the U1 release and that might fix the issue. So I upgraded to 12.0 Core-U1 today and issue is still the same. Can any one point me to any direction? I am totally lost here and my Mac is going mental asking me to provide a disc for TM backup!

Any help would be a great help

 

[fahadshery]

This also happened to me where the disk no longer appears in available disks after a clean install of Big Sur. I was able to set it up via terminal though. The syntax I used:

sudo tmutil setdestination -ap smb://ken@192.168.0.23/Ken-TimeMachine-SMB

Make sure to change the part after // to your freenas userid, ip address, and name of share.

thanks this sets the time machine. But when you enter the 'destination' password. It just gets stuck in 'Preparing'