Time Machine backup on Samba share fails with errors 512, 20 & 14











up vote
0
down vote

favorite












I've set up a Samba share for Time machine backups according to this guide.



My Mac recognizes the share correctly, but the initial backup fails with the generic error message that no Backup could be created on my share.



Running log stream --style syslog --predicate 'senderImagePath contains[cd] "TimeMachine"' --info gives the following log:



MacBook-Air-2:~ xxx$ log stream --style syslog  --predicate 'senderImagePath contains[cd] "TimeMachine"' --info
Filtering the log data using "senderImagePath CONTAINS[cd] "TimeMachine""
Timestamp (process)[PID]
2018-12-04 22:26:10.213195+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Starting manual backup
2018-12-04 22:26:10.338732+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Attempting to mount 'smb://pi@raspberrypi._smb._tcp.local./Time%20Machine%20Backups'
2018-12-04 22:26:10.897172+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Mounted 'smb://pi@raspberrypi._smb._tcp.local./Time%20Machine%20Backups' at '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E'
2018-12-04 22:26:11.816536+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Failed to find matching sparsebundle in directory '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E', directory contents: (
)
2018-12-04 22:26:11.845958+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Creating a sparsebundle using Case-sensitive Journaled HFS+ filesystem
2018-12-04 22:26:13.544412+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to create '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E/A76BCEEB-A3BD-5D63-82F4-8AEBB2F5ACBA.sparsebundle', results: {
}, error: 512 Fehler 512
2018-12-04 22:26:13.548494+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Backup failed with error 20: 20
2018-12-04 22:26:13.621842+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Unmounted '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E'
2018-12-04 22:26:13.622367+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove directory '(null)', error: 14 Bad address


The odd thing is: Contrary to the log a sparsebundle named 74F8F302-361C-4490-9E35-1F2598F9D16E/A76BCEEB-A3BD-5D63-82F4-8AEBB2F5ACBA.sparsebundle actually gets created in my share. So write permissions definitely aren't the problem.



macOS 10.14.1
Samba 4.8.0










share|improve this question


























    up vote
    0
    down vote

    favorite












    I've set up a Samba share for Time machine backups according to this guide.



    My Mac recognizes the share correctly, but the initial backup fails with the generic error message that no Backup could be created on my share.



    Running log stream --style syslog --predicate 'senderImagePath contains[cd] "TimeMachine"' --info gives the following log:



    MacBook-Air-2:~ xxx$ log stream --style syslog  --predicate 'senderImagePath contains[cd] "TimeMachine"' --info
    Filtering the log data using "senderImagePath CONTAINS[cd] "TimeMachine""
    Timestamp (process)[PID]
    2018-12-04 22:26:10.213195+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Starting manual backup
    2018-12-04 22:26:10.338732+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Attempting to mount 'smb://pi@raspberrypi._smb._tcp.local./Time%20Machine%20Backups'
    2018-12-04 22:26:10.897172+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Mounted 'smb://pi@raspberrypi._smb._tcp.local./Time%20Machine%20Backups' at '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E'
    2018-12-04 22:26:11.816536+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Failed to find matching sparsebundle in directory '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E', directory contents: (
    )
    2018-12-04 22:26:11.845958+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Creating a sparsebundle using Case-sensitive Journaled HFS+ filesystem
    2018-12-04 22:26:13.544412+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to create '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E/A76BCEEB-A3BD-5D63-82F4-8AEBB2F5ACBA.sparsebundle', results: {
    }, error: 512 Fehler 512
    2018-12-04 22:26:13.548494+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Backup failed with error 20: 20
    2018-12-04 22:26:13.621842+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Unmounted '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E'
    2018-12-04 22:26:13.622367+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove directory '(null)', error: 14 Bad address


    The odd thing is: Contrary to the log a sparsebundle named 74F8F302-361C-4490-9E35-1F2598F9D16E/A76BCEEB-A3BD-5D63-82F4-8AEBB2F5ACBA.sparsebundle actually gets created in my share. So write permissions definitely aren't the problem.



    macOS 10.14.1
    Samba 4.8.0










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I've set up a Samba share for Time machine backups according to this guide.



      My Mac recognizes the share correctly, but the initial backup fails with the generic error message that no Backup could be created on my share.



      Running log stream --style syslog --predicate 'senderImagePath contains[cd] "TimeMachine"' --info gives the following log:



      MacBook-Air-2:~ xxx$ log stream --style syslog  --predicate 'senderImagePath contains[cd] "TimeMachine"' --info
      Filtering the log data using "senderImagePath CONTAINS[cd] "TimeMachine""
      Timestamp (process)[PID]
      2018-12-04 22:26:10.213195+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Starting manual backup
      2018-12-04 22:26:10.338732+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Attempting to mount 'smb://pi@raspberrypi._smb._tcp.local./Time%20Machine%20Backups'
      2018-12-04 22:26:10.897172+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Mounted 'smb://pi@raspberrypi._smb._tcp.local./Time%20Machine%20Backups' at '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E'
      2018-12-04 22:26:11.816536+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Failed to find matching sparsebundle in directory '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E', directory contents: (
      )
      2018-12-04 22:26:11.845958+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Creating a sparsebundle using Case-sensitive Journaled HFS+ filesystem
      2018-12-04 22:26:13.544412+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to create '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E/A76BCEEB-A3BD-5D63-82F4-8AEBB2F5ACBA.sparsebundle', results: {
      }, error: 512 Fehler 512
      2018-12-04 22:26:13.548494+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Backup failed with error 20: 20
      2018-12-04 22:26:13.621842+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Unmounted '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E'
      2018-12-04 22:26:13.622367+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove directory '(null)', error: 14 Bad address


      The odd thing is: Contrary to the log a sparsebundle named 74F8F302-361C-4490-9E35-1F2598F9D16E/A76BCEEB-A3BD-5D63-82F4-8AEBB2F5ACBA.sparsebundle actually gets created in my share. So write permissions definitely aren't the problem.



      macOS 10.14.1
      Samba 4.8.0










      share|improve this question













      I've set up a Samba share for Time machine backups according to this guide.



      My Mac recognizes the share correctly, but the initial backup fails with the generic error message that no Backup could be created on my share.



      Running log stream --style syslog --predicate 'senderImagePath contains[cd] "TimeMachine"' --info gives the following log:



      MacBook-Air-2:~ xxx$ log stream --style syslog  --predicate 'senderImagePath contains[cd] "TimeMachine"' --info
      Filtering the log data using "senderImagePath CONTAINS[cd] "TimeMachine""
      Timestamp (process)[PID]
      2018-12-04 22:26:10.213195+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Starting manual backup
      2018-12-04 22:26:10.338732+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Attempting to mount 'smb://pi@raspberrypi._smb._tcp.local./Time%20Machine%20Backups'
      2018-12-04 22:26:10.897172+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Mounted 'smb://pi@raspberrypi._smb._tcp.local./Time%20Machine%20Backups' at '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E'
      2018-12-04 22:26:11.816536+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Failed to find matching sparsebundle in directory '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E', directory contents: (
      )
      2018-12-04 22:26:11.845958+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Creating a sparsebundle using Case-sensitive Journaled HFS+ filesystem
      2018-12-04 22:26:13.544412+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to create '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E/A76BCEEB-A3BD-5D63-82F4-8AEBB2F5ACBA.sparsebundle', results: {
      }, error: 512 Fehler 512
      2018-12-04 22:26:13.548494+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Backup failed with error 20: 20
      2018-12-04 22:26:13.621842+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Unmounted '/Volumes/com.apple.TimeMachine.Time Machine Backups-74F8F302-361C-4490-9E35-1F2598F9D16E'
      2018-12-04 22:26:13.622367+0100 localhost backupd[34893]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove directory '(null)', error: 14 Bad address


      The odd thing is: Contrary to the log a sparsebundle named 74F8F302-361C-4490-9E35-1F2598F9D16E/A76BCEEB-A3BD-5D63-82F4-8AEBB2F5ACBA.sparsebundle actually gets created in my share. So write permissions definitely aren't the problem.



      macOS 10.14.1
      Samba 4.8.0







      mac samba smb time-machine






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 4 at 21:47









      303

      32




      32






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          It turns out that the configuration I tried does not work with HFS+ formatted drives. Reformatting the drive with ext4 makes the error go away so the backup actually starts.






          share|improve this answer





















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1380843%2ftime-machine-backup-on-samba-share-fails-with-errors-512-20-14%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            It turns out that the configuration I tried does not work with HFS+ formatted drives. Reformatting the drive with ext4 makes the error go away so the backup actually starts.






            share|improve this answer

























              up vote
              0
              down vote













              It turns out that the configuration I tried does not work with HFS+ formatted drives. Reformatting the drive with ext4 makes the error go away so the backup actually starts.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                It turns out that the configuration I tried does not work with HFS+ formatted drives. Reformatting the drive with ext4 makes the error go away so the backup actually starts.






                share|improve this answer












                It turns out that the configuration I tried does not work with HFS+ formatted drives. Reformatting the drive with ext4 makes the error go away so the backup actually starts.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 4 at 23:03









                303

                32




                32






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1380843%2ftime-machine-backup-on-samba-share-fails-with-errors-512-20-14%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                     ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕