Time Machine error 19 "Operation not supported by device"

[daTroll]

I'm running UnRAID 6.10.0-rc4 on a Zotac MI646-BE  (Core i5 1135G7). Four macs are in the household: 2021 iMac, 2016 MBP, 2018 Mac mini and 2019 iMac 27". The first is an M1 CPU, all the others are Intel. All are running macOS 12.3.1 Monterey.

 

Three of the macs are happy to use one common TM share on the unRAID server. These macs have between 250GB and 750GB of files each. The 2019 iMac 27" has 2.6TB of files and for this one I'm unable to complete any incremental backup. Only the first backup completes (after more than two days). I have tried to redo the initial backup four times, the last time to a dedicated share only for this machine. Here is the log output on the iMac, invariably I always get the same error. Can anyone of you please suggest what I shall do next?

 

2022-04-08 11:25:47  Starting manual backup

2022-04-08 11:25:50  Attempting to mount 'smb://tomas@unTroll._smb._tcp.local/TM-Troll'

2022-04-08 11:25:52  Mounted 'smb://tomas@unTroll._smb._tcp.local/TM-Troll' at '/Volumes/.timemachine/unTroll._smb._tcp.local/CF962027-28BD-4656-BBBA-B13722B58EC0/TM-Troll' (1.61 TB of 4.19 TB available)

2022-04-08 11:25:52  Initial network volume parameters for 'TM-Troll' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 60, QoS: 0x0, attributes: 0x1C}

2022-04-08 11:25:53  Configured network volume parameters for 'TM-Troll' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 30, QoS: 0x20, attributes: 0x1C}

2022-04-08 11:26:09  Skipping periodic backup verification: not needed for an APFS sparsebundle

2022-04-08 11:26:10  'Troll.sparsebundle' does not need resizing - current logical size is 3.98 TB (3,984,588,800,000 bytes), size limit is 3.98 TB (3,984,588,800,000 bytes)

2022-04-08 11:26:10  Mountpoint '/Volumes/.timemachine/unTroll._smb._tcp.local/CF962027-28BD-4656-BBBA-B13722B58EC0/TM-Troll' is still valid

2022-04-08 11:26:10  Checking for runtime corruption on '/Volumes/.timemachine/unTroll._smb._tcp.local/CF962027-28BD-4656-BBBA-B13722B58EC0/TM-Troll/Troll.sparsebundle'

2022-04-08 11:26:49  Failed to attach using DiskImages2 to url '/Volumes/.timemachine/unTroll._smb._tcp.local/CF962027-28BD-4656-BBBA-B13722B58EC0/TM-Troll/Troll.sparsebundle', error: Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading}

2022-04-08 11:26:53  Failed to unmount '/Volumes/.timemachine/unTroll._smb._tcp.local/CF962027-28BD-4656-BBBA-B13722B58EC0/TM-Troll', Disk Management error: {

2022-04-08 11:26:53  Failed to unmount '/Volumes/.timemachine/unTroll._smb._tcp.local/CF962027-28BD-4656-BBBA-B13722B58EC0/TM-Troll', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=No Error.}

 

Edited April 8, 2022 by daTroll

[daTroll]

untroll-diagnostics-20220408-1201.zip

[daTroll]

Despite my user name, I’m not trying to troll you.  My request for help is genuine. I’m the same “daTroll” that you can find on Twitter and FB.

[jimsefton]

Sorry I don't know the answer but I have exactly the same error!

 

[daTroll]

At last I got an acknowledgment that my posts were visible to someone!

 

A few days ago, I spotted this not completely unrelated post: https://larryjordan.com/articles/time-machine-causes-conflicts-with-external-storage-and-final-cut-pro-10-6-2/

 

I will now proceed to report the issue to Apple under macOS/Time Machine here: https://www.apple.com/feedback/ Maybe you would like to do the same, jimsefton?

[jimsefton]

Yeah, will have a look when I get chance. Just tried upgrading to latest RC5 and had to roll back as it detected 3 of my drives as “wrong”. Not having much luck at the moment with Unraid.

[daTroll]

I notice that rc5 contains an update to samba:

    rc.samba: disable SMB Multi Channel by default; add control to Settings/SMB Settings page

 

So I tried enabling SMB multi channel, but it still fails with the same error.

 

By the way, here is the MacOS terminal command I use to get the tail end (the most recent 1 hour, you can edit the --last parameter to whatever suits you) of what Time Machine has done:

 

    printf '\[3J' && log show --predicate 'subsystem == "com.apple.TimeMachine"' --info --last 1h | grep -F 'eMac' | grep -Fv 'etat' | awk -F']' '{print substr($0,1,19), $NF}'

[wgstarks]

3 hours ago, daTroll said:

So I tried enabling SMB multi channel, but it still fails with the same error.

Multi Channel support was disabled because having it enabled was causing poor performance when connecting from a Mac via SMB. You’ll probably want to leave it off.

[jimsefton]

Interestingly I got rc5 to work and now my timemachine is backing up again.

[daTroll]

3 hours ago, wgstarks said:

You’ll probably want to leave it off.

Yup, I went back to the (new) default. It will be interesting to see if the performance for the backups from other three Macs is improved, but I still have no joy with making my main rig do an incremental backup..

[wgstarks]

1 hour ago, daTroll said:

Yup, I went back to the (new) default. It will be interesting to see if the performance for the backups from other three Macs is improved, but I still have no joy with making my main rig do an incremental backup..

You may need to use other settings as well. Here is my settings from SMB configurations extras-
 

#macOS config start
[Global]
   vfs objects = catia fruit streams_xattr
   fruit:nfs_aces = no
   fruit:zero_file_id = yes
   fruit:metadata = stream
   fruit:encoding = native
   spotlight backend = tracker

[Media]
   path = /mnt/user/Media
   veto files = /._*/.DS_Store/
   delete veto files = yes
   spotlight = yes

[Media] is the name of the share these settings are being applied to. You will need to change this to fit your needs.

[daTroll]

20 hours ago, wgstarks said:

You may need to use other settings as well. Here is my settings from SMB configurations extras-

 

Wow, thanks for the tips! My incremental backup is finally running. I also notice a significant speed increase by disabling SMB multichannel. B-)

[wgstarks]

IF I am understanding the vfs_fruit options correctly all those per share options can also be used globally. I haven’t tested that though. I imagine it might have some unwanted effect on connections from windows machines or even macs running different versions of the OS since apple likes to change things.

[Krolitian]

On 4/28/2022 at 2:04 PM, wgstarks said:

You may need to use other settings as well. Here is my settings from SMB configurations extras-
 

#macOS config start
[Global]
   vfs objects = catia fruit streams_xattr
   fruit:nfs_aces = no
   fruit:zero_file_id = yes
   fruit:metadata = stream
   fruit:encoding = native
   spotlight backend = tracker

[Media]
   path = /mnt/user/Media
   veto files = /._*/.DS_Store/
   delete veto files = yes
   spotlight = yes

 

This fixed my backups too! Thanks so much!

[unJack]

And mine as well, incredible, hadn't had backups for the last six weeks!

[foux]

Hi there! Anybody manage to use this on 6.11 beta?

 

On my end it makes Samba crash :

Sep 18 20:18:56 Vili  smbd[22056]: [2022/09/18 20:18:56.939499,  0] ../../lib/cmdline/cmdline.c:56(_samba_cmdline_talloc_log)
Sep 18 20:18:56 Vili  smbd[22056]:   talloc: access after free error - first free may be at ../../tevent_req.c:291
Sep 18 20:18:56 Vili  smbd[22056]: [2022/09/18 20:18:56.939544,  0] ../../lib/cmdline/cmdline.c:56(_samba_cmdline_talloc_log)
Sep 18 20:18:56 Vili  smbd[22056]:   Bad talloc magic value - access after free
Sep 18 20:18:56 Vili  smbd[22056]: [2022/09/18 20:18:56.939560,  0] ../../lib/util/fault.c:172(smb_panic_log)
Sep 18 20:18:56 Vili  smbd[22056]:   ===============================================================
Sep 18 20:18:56 Vili  smbd[22056]: [2022/09/18 20:18:56.939574,  0] ../../lib/util/fault.c:173(smb_panic_log)
Sep 18 20:18:56 Vili  smbd[22056]:   INTERNAL ERROR: Bad talloc magic value - access after free in pid 22056 (4.16.5)
Sep 18 20:18:56 Vili  smbd[22056]: [2022/09/18 20:18:56.939589,  0] ../../lib/util/fault.c:177(smb_panic_log)
Sep 18 20:18:56 Vili  smbd[22056]:   If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
Sep 18 20:18:56 Vili  smbd[22056]: [2022/09/18 20:18:56.939604,  0] ../../lib/util/fault.c:182(smb_panic_log)
Sep 18 20:18:56 Vili  smbd[22056]:   ===============================================================
Sep 18 20:18:56 Vili  smbd[22056]: [2022/09/18 20:18:56.939617,  0] ../../lib/util/fault.c:183(smb_panic_log)
Sep 18 20:18:56 Vili  smbd[22056]:   PANIC (pid 22056): Bad talloc magic value - access after free in 4.16.5
Sep 18 20:18:56 Vili  smbd[22056]: [2022/09/18 20:18:56.939720,  0] ../../lib/util/fault.c:245(log_stack_trace)
Sep 18 20:18:56 Vili  smbd[22056]:   BACKTRACE:
Sep 18 20:18:56 Vili  smbd[22056]:    #0 log_stack_trace + 0x39 [ip=0x14d1de0fc159] [sp=0x7ffc6061a920]
Sep 18 20:18:56 Vili  smbd[22056]:    #1 smb_panic + 0x9 [ip=0x14d1de0fc4c9] [sp=0x7ffc6061b260]
Sep 18 20:18:56 Vili  smbd[22056]:    #2 <unknown symbol> [ip=0x14d1de020af8] [sp=0x7ffc6061b270]
Sep 18 20:18:56 Vili  smbd[22056]:    #3 fsp_set_fd + 0x46b8 [ip=0x14d1de437e48] [sp=0x7ffc6061b2a0]
Sep 18 20:18:56 Vili  smbd[22056]:    #4 tevent_common_invoke_immediate_handler + 0x17a [ip=0x14d1de00dcfa] [sp=0x7ffc6061b2d0]
Sep 18 20:18:56 Vili  smbd[22056]:    #5 tevent_common_loop_immediate + 0x16 [ip=0x14d1de00dd16] [sp=0x7ffc6061b330]
Sep 18 20:18:56 Vili  smbd[22056]:    #6 tevent_wakeup_recv + 0xf5b [ip=0x14d1de013a7b] [sp=0x7ffc6061b340]
Sep 18 20:18:56 Vili  smbd[22056]:    #7 tevent_signal_get_tag + 0xb7 [ip=0x14d1de011d77] [sp=0x7ffc6061b3a0]
Sep 18 20:18:56 Vili  smbd[22056]:    #8 _tevent_loop_once + 0x91 [ip=0x14d1de00cb61] [sp=0x7ffc6061b3c0]

 

[wgstarks]

Have you seen this thread- https://forums.unraid.net/bug-reports/prereleases/macos-optimization-r2087/

[foux]

1 minute ago, wgstarks said:

Have you seen this thread- https://forums.unraid.net/bug-reports/prereleases/macos-optimization-r2087/

I didn't, I'll browse through it! Thanks a lot for pointing it.

[wgstarks]

Probably the best place to post this since it’s directly related to unRAID trying to improve performance with macOS and SMB on the latest beta releases.

[danringer]

So, Mac user here,

Before Unraid, I was running a rpi with an external drive setup for Time Machine.  It works ok given the limitations of the rpis usb/nic/io etc.  Now with unraid I wanted to make that more robust.  

• Watched Spaceinvaderone's videos, would work once then unable to complete incremental backups.  Same Failed to attach using DiskImages2 errors.  
• added the suggested changes to smb conf, same failure for incremental backups
• got excited for 6.11 and the macOS optimizations, same failure.
• gave up and ran the docker version, initial backup and hourlies for the past 36 hours. Success!

now, according the the smb.conf from the docker app version, they use several different options in smb conf:

[global]
   access based share enum = no
   hide unreadable = no
   inherit permissions = no
   load printers = no
   log file = /var/log/samba/log.%m
   logging = file
   max log size = 1000
   security = user
   server min protocol = SMB2
   server role = standalone server
   smb ports = 445
   workgroup = WORKGROUP
   vfs objects = acl_xattr fruit streams_xattr
   fruit:aapl = yes
   fruit:nfs_aces = yes
   fruit:model = TimeCapsule8,119
   fruit:metadata = stream
   fruit:veto_appledouble = no
   fruit:posix_rename = yes
   fruit:zero_file_id = yes
   fruit:wipe_intentionally_left_blank_rfork = yes
   fruit:delete_empty_adfiles = yes

[TimeMachine]
   path = /opt/timemachine
   inherit permissions = no
   read only = no
   valid users = myusername
   vfs objects = acl_xattr fruit streams_xattr
   fruit:time machine = yes
   fruit:time machine max size = 1 T

notably, 

[Global]
   vfs objects = acl_xattr fruit streams_xattr
   fruit:aapl = yes
   fruit:nfs_aces = yes
   fruit:model = TimeCapsule8,119
   fruit:metadata = stream
   fruit:veto_appledouble = no
   fruit:posix_rename = yes
   fruit:zero_file_id = yes
   fruit:wipe_intentionally_left_blank_rfork = yes
   fruit:delete_empty_adfiles = yes

and with the descriptions of the new optimizations here: 

there is mention of some of the desired options being overruled when a Mac isn't the first to use the share or that some of the fruit options that may be required for Time Machine to function properly needing to be added to [Global] may negatively impact the overall samba shares on unraid.

Quote

Be careful when mixing shares with and without vfs_fruit. OS X clients negotiate SMB2 AAPL protocol extensions on the first tcon, so mixing shares with and without fruit will globally disable AAPL if the first tcon is without fruit.

My overarching frustration is that the option exists in the share export dropdown, yes, Timemachine or yes, TimeMachine (hidden), and this lends me to believe that the service that is not working is something that my license paid for.  
If we can't get it working, I'd rather see the developer for the docker app https://github.com/mbentley/docker-timemachine be compensated and his option be added to unraid as the "official" way to use unraid for a timemachine server.
 

tl;dr remove the export option (yes, Time Machine) and add the docker app TIMEMACHINE APPLICATION as the officially supported option

 

my USD$0.02,

-Dan