Closed jeremyhiggs closed 7 months ago
I bumped the debug level up to "3" and found this:
open_directory: unable to create CFC36EEB-B9CB-51AC-A5C3-C5A958D8A394_2023-12-06-222746.sparsebundle/bands. Error was NT_STATUS_ACCESS_DENIED
There are file access attempts previously that seem to have run fine:
jeremy opened file .com.apple.timemachine.supported-8bd88a3b-bee-4d3f-b430-1c8a1510ba36 read=Yes write=No (numopen=2)
unpack_nt_owners: owner sid mapped to uid 1000
unpack_nt_owners: group sid mapped to gid 1000
jeremy closed file .com.apple.timemachine.supported-8bd88a3b-bee-4d3f-b430-1c8a1510ba36 (numopen=0) NT_STATUS_OK
jeremy opened file .com.apple.timemachine.supported-8bd88a3b-bee-4d3f-b430-1c8a1510ba36 read=No write=No (numopen=2)
smbd_do_setfilepathinfo: .com.apple.timemachine.supported-8bd88a3b-bee-4d3f-b430-1c8a1510ba36 (fnum 305212056) info_level=1013 totdata=1
jeremy closed file .com.apple.timemachine.supported-8bd88a3b-bee-4d3f-b430-1c8a1510ba36 (numopen=1) NT_STATUS_OK
I was able to get this working:
sudo mount -t vfat /dev/sda3 /mnt/timemachine/ -o rw,uid=1000,gid=1000,umask=007,dmask=007
Until I added the umask flag (0000
initially) it wasn't working. 🤷🏻♂️
Describe the Bug
I receive the error "The backup disk image could not be created" when trying to backup for the first time
Expected Behavior
A successful backup!
Steps to Reproduce
How You're Launching the Container
/home/ubuntu/timemachine/jeremy.conf:
Container Logs
Additional Context
/mnt/timemachine/backup:
The
/mnt/timemachine/backup/jeremy
directory is empty. I have confirmed that my user (ubuntu, with uid 1000) can write to it.I saw in #84 that writing to NTFS would not be supported. The underlying filesystem is ext4, in this case. I tried vfat/FAT32, but that didn't seem to work, due to a lack of permissions support. I also found in a few instances people using ext4 without problems.
Any ideas?