• [6.10] TimeMachine backups continue to fail "failed to attach using diskimages2" "operation not supported by device"


    wgstarks
    • Minor

    I first posted regarding this in the prerelease section here but just testing and reporting for 6.10. See the initial bug report for more details.

     

    Summary:

    TimeMachine completes one backup but then cannot mount that sparsebundle for future backups. This error is being reported by multiple unraid and synology users.

    • Like 1
    • Upvote 1



    User Feedback

    Recommended Comments



    2 hours ago, wgstarks said:

    You should give the TimeMachine docker a try. It’s working great for me.

    Okay. But what did change in 6.10 that Time Machine would not work anymore. There are still the Share/SMB Export Options > Yes/Time Machine
    There is some issue here in 6.10...
    Do Limetech know it?

    Link to comment

    Well, this is a bug report thread so safe to assume that LT is aware. IMO time machine support over SMB is a moving target. AFAIK there isn’t any SMB standard so Apple has their version of SMB. Linux has their version of SMB. Windows has Samba (which is also different). There is open source software (which unRAID uses) which works to keep all of the different protocols working together but I’m sure that’s a constant problem. In my case I fixed this issue by re-installing macOS Monterey which would seem to indicate it wasn’t ever an issue with unRAID. For many people there was never an issue at all. I know this isn’t much comfort when you are one of the few who do have issues, that’s why I recommend the TimeMachine docker. Since all those devs do is support TimeMachine it’s their top priority.

     

    Just my opinion.😁

    Link to comment


    Wanted to share that the other recent thread concerning this issue helped me out, I was able to add some SMB Extra Settings and that seems to have fixed the problem for at least one of my Macs. The issue doesn't seem to be fully resolved though. 

    Link to comment

    @kubed_zero

    All my hopes were going into the SMB-Extras-settings.

    But in my case it didn't work.

     

    ==== The Timemachine-Log after last (working) Backup under 6.9.2 (No special SMB-Extras set) ====

    2022-06-25 20:44:13rogress] .••••      .
    2022-06-25 20:45:05redSizing] Skipping further sizing for finished volume xxxxxxxx
    2022-06-25 20:45:05rogress] Finished copying from volume "xxxxxxxx - Daten"
    2022-06-25 20:45:05Collection] Found 0 perfect clone families, 1 partial clone families. Shared space 9,1 MB (9080412 bytes).
    2022-06-25 20:45:05al] Saved clone family cache for 'xxxxxxxx - Daten' at /Volumes/Time Machine-Backups/Backups.backupdb/xxxxxxxx/2022-06-25-203850.inProgress/xxxxxxxx/.xxxxxxxx.clonedb
    2022-06-25 20:45:08ntDoneAnalysis] .•++**__-•••.
    2022-06-25 20:45:08rogress] Time Estimates Evaluation
    2022-06-25 20:45:08mages] Found disk2s2 xxxxxxxx
    2022-06-25 20:45:09mages] Found disk2s2 xxxxxxxx
    2022-06-25 20:45:09al] Unmounted '/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/xxxxxxxx/2022-06-25-203848/xxxxxxxx - Daten'
    2022-06-25 20:45:09al] Unmounted local snapshot: com.apple.TimeMachine.2022-06-25-203848.local at path: /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/xxxxxxxx/2022-06-25-203848/xxxxxxxx - Daten source: xxxxxxxx - Daten
    2022-06-25 20:45:09mages] Found disk2s2 xxxxxxxx
    2022-06-25 20:45:09al] Unmounted '/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/xxxxxxxx/2022-06-25-185038/xxxxxxxx - Daten'
    2022-06-25 20:45:09mages] Found disk2s2 xxxxxxxx
    2022-06-25 20:45:09al] Unmounted local snapshot: com.apple.TimeMachine.2022-06-25-185038.local at path: /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/xxxxxxxx/2022-06-25-185038/xxxxxxxx - Daten source: xxxxxxxx - Daten
    2022-06-25 20:45:13al] Marked as reference snapshot: com.apple.TimeMachine.2022-06-25-203848.local
    2022-06-25 20:45:13al] Backup result: {
    2022-06-25 20:45:13al] Completed backup: 2022-06-25-204509
    2022-06-25 20:45:13al] Mountpoint '/Volumes/Time Machine-Backups' is still valid
    2022-06-25 20:45:14al] Failed to mount 'disk1s3', dissenter {
    2022-06-25 20:45:15al] Copying recovery system
    2022-06-25 20:45:15al] Failed to copy recovery set, error: No such file or directory
    2022-06-25 20:45:15pThinning] Thinning 1 backups using age-based thinning, expected free space: 1 TB actual free space: 1 TB trigger 50 GB thin 83,33 GB dates: (
    2022-06-25 20:47:10al] Mountpoint '/Volumes/Time Machine-Backups' is still valid
    2022-06-25 20:47:10mages] Found disk2s2 xxxxxxxx
    2022-06-25 20:47:10mages] Found disk2s2 xxxxxxxx
    2022-06-25 20:47:40ight] Spotlight finished indexing for '/Volumes/Time Machine-Backups'

     

    ==== The Timemachine-Log after first (not working) Backup attempt under 6.10.3  (SMB-Extras set) ====

    2022-06-25 21:06:05pScheduling] Not prioritizing backups with priority errors. lockState=0
    2022-06-25 21:06:05al] Starting manual backup
    2022-06-25 21:06:05ing] Attempting to mount 'smb://yyyyyyyy@unBackup._smb._tcp.local/unMachine'
    2022-06-25 21:06:06ing] Mounted 'smb://yyyyyyyy@unBackup._smb._tcp.local/unMachine' at '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine' (1 TB of 4 TB available)
    2022-06-25 21:06:06al] Initial network volume parameters for 'unMachine' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 60, QoS: 0x0, attributes: 0x1C}
    2022-06-25 21:06:06al] Configured network volume parameters for 'unMachine' {disablePrimaryReconnect: 1, disableSecondaryReconnect: 0, reconnectTimeOut: 30, QoS: 0x20, attributes: 0x1C}
    2022-06-25 21:06:07Management] TMPowerState: 2
    2022-06-25 21:06:07al] Skipping periodic backup verification due to power conditions: (null)
    2022-06-25 21:06:07al] 'yyyyyyyy.backupbundle' does not need resizing - current logical size is 11,4 TB (11.397.019.360.768 bytes), size limit is 3,8 TB (3.798.891.797.913 bytes)
    2022-06-25 21:06:07al] Mountpoint '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine' is still valid
    2022-06-25 21:06:07al] Checking for runtime corruption on '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine/yyyyyyyy.backupbundle'
    2022-06-25 21:06:45mages] Failed to attach using DiskImages2 to url '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine/yyyyyyyy.backupbundle', 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-06-25 21:06:45al] Failed to unmount '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine', Disk Management error: {
    2022-06-25 21:06:45al] Failed to unmount '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=Kein Fehler.}
    2022-06-25 21:06:45al] Waiting 60 seconds and trying again.
    2022-06-25 21:06:45llation] Cancelling backup because volume '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine' was unmounted.
    2022-06-25 21:06:45llation] Requested backup cancellation or termination
    2022-06-25 21:06:46llation] Backup cancelled (22: BACKUP_CANCELED)
    2022-06-25 21:06:46al] Failed to unmount '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine', Disk Management error: {
    2022-06-25 21:06:46al] Failed to unmount '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=Kein Fehler.}
    2022-06-25 21:06:46llation] Cleared pending cancellation request

     

    ==== The Timemachine-Log after first (working) Backup after downgrade again to 6.9.2 (SMB-Extras not set) ====

    2022-06-26 08:40:52rogress] .••••••    .
    2022-06-26 08:41:01ight] Spotlight indexing queue is full (256 depth, 0 operations overflowed)
    2022-06-26 08:41:27ight] Spotlight indexing queue is empty.
    2022-06-26 08:41:56rogress] Finished copying from volume "zzzzzzzzz - Daten"
    2022-06-26 08:41:56Collection] Found 6 perfect clone families, 1 partial clone families. Shared space 11,9 MB (11882900 bytes).
    2022-06-26 08:41:59al] Saved clone family cache for 'zzzzzzzzz - Daten' at /Volumes/Time Machine-Backups/Backups.backupdb/zzzzzzzzz/2022-06-26-080502.inProgress/zzzzzzzzz/.zzzzzzzzz
    2022-06-26 08:42:19ntDoneAnalysis] .•+______-••.
    2022-06-26 08:42:19rogress] Time Estimates Evaluation
    2022-06-26 08:42:19mages] Found disk2s2 zzzzzzzzz
    2022-06-26 08:42:20al] Unmounted '/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/SaberBookPro/2022-06-26-080500/zzzzzzzzz - Daten'
    2022-06-26 08:42:20mages] Found disk2s2 zzzzzzzzz
    2022-06-26 08:42:20al] Unmounted local snapshot: com.apple.TimeMachine.2022-06-26-080500.local at path: /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/zzzzzzzzz/2022-06-26-080500/SaberBookPro - Daten source: zzzzzzzzz - Daten
    2022-06-26 08:42:20mages] Found disk2s2 zzzzzzzzz
    2022-06-26 08:42:20al] Unmounted '/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/zzzzzzzzz/2022-06-25-203848/zzzzzzzzz - Daten'
    2022-06-26 08:42:20mages] Found disk2s2 zzzzzzzzz
    2022-06-26 08:42:20al] Unmounted local snapshot: com.apple.TimeMachine.2022-06-25-203848.local at path: /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/zzzzzzzzz/2022-06-25-203848/zzzzzzzzz - Daten source: zzzzzzzzz - Daten
    2022-06-26 08:42:31al] Marked as reference snapshot: com.apple.TimeMachine.2022-06-26-080500.local
    2022-06-26 08:42:31al] Backup result: {
    2022-06-26 08:42:31al] Completed backup: 2022-06-26-084227
    2022-06-26 08:42:31al] Mountpoint '/Volumes/Time Machine-Backups' is still valid
    2022-06-26 08:42:33al] Copying recovery system
    2022-06-26 08:42:33al] Failed to copy recovery set, error: No such file or directory
    2022-06-26 08:42:33pThinning] Thinning 2 backups using age-based thinning, expected free space: 993,42 GB actual free space: 994,17 GB trigger 50 GB thin 83,33 GB dates: (
    2022-06-26 08:53:01al] Mountpoint '/Volumes/Time Machine-Backups' is still valid
    2022-06-26 08:53:02mages] Found disk2s2 zzzzzzzzz
    2022-06-26 08:53:02mages] Found disk2s2 zzzzzzzzz
    2022-06-26 08:53:32ight] Spotlight finished indexing for '/Volumes/Time Machine-Backups'
    2022-06-26 08:53:42al] Unmounted '/Volumes/Time Machine-Backups'
    2022-06-26 08:53:45al] Unmounted '/Volumes/.timemachine/unBackup._smb._tcp.local/zzzzzzzzz/unMachine'

     

    Under 6.9.2 all ist still fine.

    Right after upgrade to 6.10.X the Backup-Jobs not working anymore.

    Directly after downgrade to 6.9.2 the job starts without issues.

    • Like 1
    Link to comment

    That appears to be the same errors I had. Fixed it by reinstalling macOS from the restore system. Easy process that preserves all your data and prefs. Similar to an OS update.

     

    Another option might be to install the TimeMachine docker on unRAID.

    Link to comment
    22 minutes ago, wgstarks said:

    That appears to be the same errors I had. Fixed it by reinstalling macOS from the restore system. Easy process that preserves all your data and prefs. Similar to an OS update.

     

    Another option might be to install the TimeMachine docker on unRAID.

     

    Eh... neither of those are acceptable solutions in my mind. The out of the box Time Machine functionality should work without a need for a third party solution, and reinstalling MacOS after just having done so in the past month also seems less-than-ideal.

     

    52 minutes ago, saber1 said:

    Directly after downgrade to 6.9.2 the job starts without issues.

    I'm going to give this a shot, since there's nothing in 6.10.x that is beneficial to me. Will report back. 

    Link to comment
    27 minutes ago, kubed_zero said:
    1 hour ago, saber1 said:

    Directly after downgrade to 6.9.2 the job starts without issues.

    I'm going to give this a shot, since there's nothing in 6.10.x that is beneficial to me. Will report back. 

     

    Yep this worked 100%. All Macs, M1/Intel, are backing up successfully to preexisting and new backups on a single Time Machine Unraid share now that I've downgraded to 6.9.2 from 6.10.3. Unfortunate that this is necessary, hopefully @limetech will reopen these bugs and investigate further. 

     

    So just to summarize:

    • Unraid 6.10.3 uses smbd version 4.15.7, while Unraid 6.9.2 uses smbd version 4.12.14 (checked with "smbd --version")
    • All other SMB-related configs seem identical, such as /etc/samba/smb-shares.conf, /etc/samba/smb-names.conf, /etc/samba/smb.conf, and *a lack of* /boot/config/smb-extra.conf (meaning no SMB Extras defined)
    • Time Machine backups proceed normally on Unraid 6.9.2 from both Intel and M1 Macs running MacOS 12.4, while the same incremental backups fail on Unraid 6.10.3 with a Console log Mac-side along the lines of "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading}
    • The below SMB Extras config added to 6.10.3 allowed some but not all Macs to back up. Removing it caused then-working Macs to start failing again.
    [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
    [TimeMachine]
            path = /mnt/user/TimeMachine
            comment =
            browseable = yes
            # Private
            writeable = no
            read list =
            write list = backup
            valid users =  backup
            vfs objects = catia fruit streams_xattr
            fruit:time machine = yes
            fruit:time machine max size = 1200000M
            case sensitive = auto
            preserve case = yes
            short preserve case = yes
    • I also keep my Time Machine share constrained to a single disk, as I've had cross-disk issues in the distant past
    • Like 2
    Link to comment
    29 minutes ago, kubed_zero said:

    @JorgeB @wgstarks I don't see a way to reopen this issue, maybe I'm missing permission to do so. Could you reopen if you have time? 

    There have been good reports of the Time Machine docker container functioning well so this might be a good alternative.  Cannot very it myself as I do not use a Mac.

    Link to comment

    @itimpi

    For shares we have the option to export especially for Time Machine:

    375829183_Bildschirmfoto2022-06-26um17_53_16.thumb.png.d1303191a72f4a294c2049004be43ac0.png

     

    I prefer to use this option instead of an extra Docker if it isn't needed.

    So something is wrong in 6.10.X

     

    Reinstalling macOS is no option, as it works in 6.9.2 like a charm.

     

    • Upvote 1
    Link to comment
    3 minutes ago, saber1 said:

    So something is wrong in 6.10.X

    The problem I see is that with combinations of Linux kernel and Samba updates in new releases there may well be changes affecting this that are outside Limtech’s control and difficult to identify and correct and thus re-occurring stability problems in the capability.   The advantage of using a docker container is that it can provide a stable environment independently of changes happening at the host level.

    Link to comment
    saber1

    Posted (edited)

    1 hour ago, itimpi said:

    The advantage of using a docker container is that it can provide a stable environment independently of changes happening at the host level.

    That makes sense.
    Can anyone confirm that with the Docker macOS will find the previous made backups?
    Or do we have to start from scratch? @wgstarks

    Edited by saber1
    Link to comment
    3 minutes ago, saber1 said:

    That makes sense.
    Can anyone confirm that with the Docker macOS will find the previous made backups?
    Or do we have to start from scratch? @wgstarks

    I started from scratch. Didn’t experiment with trying to use the existing backup so I can’t really say.

    Link to comment
    1 hour ago, itimpi said:

    The problem I see is that with combinations of Linux kernel and Samba updates in new releases there may well be changes affecting this that are outside Limtech’s control and difficult to identify and correct and thus re-occurring stability problems in the capability.   The advantage of using a docker container is that it can provide a stable environment independently of changes happening at the host level.

    Eh, my opinion is that if Limetech includes the feature in the base OS, it should work properly and not break on a version upgrade. Perhaps this is a result of updating the Samba package, and not a kernel update issue. We'll have to do more testing to evaluate what broke it. Anyway, I don't want to run Docker on my NAS (would prefer a separate system considering Unraid is already a VM on my ESXi cluster) so I'll just stick on 6.9.2 until the built-in feature works again 

    Link to comment
    2 hours ago, kubed_zero said:

    I don't see a way to reopen this issue,

    You should see a drop down menu near the bottom of the page that currently shows “Solved”.

    Link to comment
    2 minutes ago, wgstarks said:

    You should see a drop down menu near the bottom of the page that currently shows “Solved”.

    Nope, I think only you (as the issue creator) and admins have that ability

    Link to comment

    I've also been chasing this issue down. The docker container fails for me with the error:

    Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading}

    I updated unRAID from 6.9.2 to 6.10.0 at the same time I updated macOS to 12.4, so I'm not sure which broke it.

    I've also done a reinstall of macOS from the recovery menu (rebooting holding a key combo, etc) to no avail.

    Link to comment
    5 hours ago, joshbgosh10592 said:

    I've also been chasing this issue down. The docker container fails for me with the error:

    Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading}

    I updated unRAID from 6.9.2 to 6.10.0 at the same time I updated macOS to 12.4, so I'm not sure which broke it.

    I've also done a reinstall of macOS from the recovery menu (rebooting holding a key combo, etc) to no avail.

    I would suggest posting in the support thread for the docker. Just click the docker name and select support.

    Link to comment
    14 hours ago, wgstarks said:

    I would suggest posting in the support thread for the docker. Just click the docker name and select support.

    I actually have, assuming the URL "Support" takes me to is correct:

     

    Link to comment

    I would like to add please that I too am experiencing this exact issue since moving to 6.10 and with three Macs running MacOS 12.x

     

    New Time Machine backups work OK, but subsequent runs fail to mount. Was fine on earlier versions of Unraid.

     

    I've seen the suggestions about SMB extra config, but I can see in smb-shares.conf that these are already added by Unraid when exporting the Time Machine shares: vfs objects = catia fruit streams_xattr

     

    Edit to add a copy of the error from the logs:

    (TimeMachine) [com.apple.TimeMachine:DiskImages] Failed to attach using DiskImages2 to url '/Volumes/.timemachine/NAS._smb._tcp.local/BBEA0555-A339-4C12-9707-3C07F3F8735B/_TimeMachine_MacBookAir/MacBook Air.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}

     

    Edited by Oldbean57
    Added error log
    Link to comment
    6 minutes ago, Oldbean57 said:

    I would like to add please that I too am experiencing this exact issue since moving to 6.10 and with three Macs running MacOS 12.x

     

    New Time Machine backups work OK, but subsequent runs fail to mount. Was fine on earlier versions of Unraid.

     

    I've seen the suggestions about SMB extra config, but I can see in smb-shares.conf that these are already added by Unraid when exporting the Time Machine shares: vfs objects = catia fruit streams_xattr

     

     

    Again, I have had a great experience with the TimeMachine docker. It’s up to you if you want to wait to see if the issues that a few people are having with TM get resolved but if you decide to use the docker I wrote a how-to for configuring it for multiple machines.

    https://forums.unraid.net/topic/123985-timemachine-application-support-thread/?do=findComment&comment=1134386

     

    • Thanks 1
    Link to comment
    Just now, wgstarks said:

    Again, I have had a great experience with the TimeMachine docker. It’s up to you if you want to wait to see if the issues that a few people are having with TM get resolved but if you decide to use the docker I wrote a how-to for configuring it for multiple machines.

    https://forums.unraid.net/topic/123985-timemachine-application-support-thread/?do=findComment&comment=1134386

     

    Thank-you wgstarks - I did mean to add that I do intend to use that Docker in the meantime so I can get some backups running, so thanks for highlighting that option.
    I just wanted to make sure the Unraid team had visibility that it's affecting a number of people! 

    • Upvote 1
    Link to comment
    1 minute ago, Oldbean57 said:

    did mean to add that I do intend to use that Docker in the meantime so I can get some backups running,

    Another option is just to downgrade to 6.9.2. Time Machine has been working flawlessly on all my machines for the past few weeks since performing the downgrade!

    • Thanks 1
    Link to comment

    I originally fixed my issue by re-installing macOS. It’s an easy process. The user experience is really no different than installing an update. Just takes a few minutes longer since it’s installing the entire OS rather than just the modified software. Same as what the combo updates did before Apple discontinued them.

    Link to comment
    11 minutes ago, wgstarks said:

    I originally fixed my issue by re-installing macOS. It’s an easy process. The user experience is really no different than installing an update. Just takes a few minutes longer since it’s installing the entire OS rather than just the modified software. Same as what the combo updates did before Apple discontinued them.

    I just wish that had solved the issue for me. I've even done it twice with no success. 

    • Upvote 1
    Link to comment



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.