I just got a new Lacie NAS with their NAS OS 4. After making an initial Time Machine backup to this device I wanted to mount the resulting (encrypted) disk image but when doing so I just received an error message "Resource temporarily unavailable". Googling this error message returned a lot of Voodoo fixes. However, after playing around a bit, restarting a few times etc I realised that I had something called Time Machine service enabled for this share. Turning this service off immediately made the disk image available as expected.

**EDIT #2** @CJK and @mockman so using both your ideas I've created this god awful long script that does the trick for the first offset value in the xml and first marker value shown in the xml Now the goal would be to see how run or loop these handlers to get every Marker's start value and replace it with every asset-clip's offset value. Example: AFTER RUNNING SCRIPT the desired Results below>>> Notice that the offset values match the markers values {Hoping the Script ignores this line because no other exists to change} {Hoping the Script ignores this line because no other exists to change} Here's the entire fcpxml in it's raw complete format: Ym9vaxQDAAAAAAQQMAAAAHi61zvH+Xt9eDtxi789DbINi+KCtO1mu9FKykYF+ptlEAIAAAQAAAADAwAAABgAKAUAAAABAQAAVXNlcnMAAAALAAAAAQEAAGRhdmVzbWFjcHJvAAUAAAABAQAATXVzaWMAAAASAAAAAQEAAE11c2ljIGZvciBQcm9qZWN0cwAALwAAAAEBAABhZ2FpbnN0LWdyYXZpdHlfYnlfZXZnZW55LWJhcmR5dXpoYV9BcnRsaXN0LndhdgAUAAAAAQYAABAAAAAgAAAANAAAAEQAAABgAAAACAAAAAQDAABPUwAAAAAAAAgAAAAEAwAAT0AHAAAAAAAIAAAABAMAAEm4BwAAAAAACAAAAAQDAAAPyQcAAAAAAAgAAAAEAwAAN8kHAAAAAAAUAAAAAQYAALQAAADEAAAA1AAAAOQAAAD0AAAACAAAAAAEAABBwaczlkwtyRgAAAABAgAAAQAAAAAAAAAPAAAAAAAAAAAAAAAAAAAACAAAAAQDAAADAAAAAAAAAAQAAAADAwAA9QEAAAgAAAABCQAAZmlsZTovLy8MAAAAAQEAAE1hY2ludG9zaCBIRAgAAAAEAwAAABDQ2e0BAAAIAAAAAAQAAEHEhebagAAAJAAAAAEBAAAxQTAwQjhEMi0zNjIwLTQxQTEtODA0OC02NzBCQUI1ODRFM0MYAAAAAQIAAIEAAAABAAAA7xMAAAEAAAAAAAAAAAAAAAEAAAABAQAALwAAAAAAAAABBQAAzAAAAP7///8BAAAAAAAAABAAAAAEEAAAmAAAAAAAAAAFEAAABAEAAAAAAAAQEAAAMAEAAAAAAABAEAAAIAEAAAAAAAACIAAA/AEAAAAAAAAFIAAAbAEAAAAAAAAQIAAAfAEAAAAAAAARIAAAsAEAAAAAAAASIAAAkAEAAAAAAAATIAAAoAEAAAAAAAAgIAAA3AEAAAAAAAAwIAAACAIAAAAAAAABwAAAUAEAAAAAAAARwAAAIAAAAAAAAAASwAAAYAEAAAAAAAAQ0AAABAAAAAAAAAA= Ym9va8wCAAAAAAQQMAAAAHLUxWFmj8UGU72GTMAnlCWB/KtAonN8I+RDCiLsmrssyAEAAAQAAAADAwAAABgAKAUAAAABAQAAVXNlcnMAAAALAAAAAQEAAGRhdmVzbWFjcHJvAAYAAAABAQAATW92aWVzAAAZAAAAAQEAAFBleGVscyBWaWRlb3MgMTczMDM5NS5tcDQAAAAQAAAAAQYAABAAAAAgAAAANAAAAEQAAAAIAAAABAMAAE9TAAAAAAAACAAAAAQDAABPQAcAAAAAAAgAAAAEAwAAxRp+AAAAAAAIAAAABAMAADzrPQAAAAAAEAAAAAEGAACAAAAAkAAAAKAAAACwAAAACAAAAAAEAABBwpXm0YAAABgAAAABAgAAAQAAAAAAAAAPAAAAAAAAAAAAAAAAAAAACAAAAAQDAAACAAAAAAAAAAQAAAADAwAA9QEAAAgAAAABCQAAZmlsZTovLy8MAAAAAQEAAE1hY2ludG9zaCBIRAgAAAAEAwAAABDQ2e0BAAAIAAAAAAQAAEHEhebagAAAJAAAAAEBAAAxQTAwQjhEMi0zNjIwLTQxQTEtODA0OC02NzBCQUI1ODRFM0MYAAAAAQIAAIEAAAABAAAA7xMAAAEAAAAAAAAAAAAAAAEAAAABAQAALwAAAAAAAAABBQAAzAAAAP7///8BAAAAAAAAABAAAAAEEAAAaAAAAAAAAAAFEAAAwAAAAAAAAAAQEAAA6AAAAAAAAABAEAAA2AAAAAAAAAACIAAAtAEAAAAAAAAFIAAAJAEAAAAAAAAQIAAANAEAAAAAAAARIAAAaAEAAAAAAAASIAAASAEAAAAAAAATIAAAWAEAAAAAAAAgIAAAlAEAAAAAAAAwIAAAwAEAAAAAAAABwAAACAEAAAAAAAARwAAAIAAAAAAAAAASwAAAGAEAAAAAAAAQ0AAABAAAAAAAAAA= AVC Coding MPEG-4 AAC Ym9va8wCAAAAAAQQMAAAAELPIBuUH6inb74/CLc27nr2yrwiIVd8Ni9hDXz1lgueyAEAAAQAAAADAwAAABgAKAUAAAABAQAAVXNlcnMAAAALAAAAAQEAAGRhdmVzbWFjcHJvAAYAAAABAQAATW92aWVzAAAZAAAAAQEAAHByb2R1Y3Rpb24gSURfNDg4MjM0MS5tcDQAAAAQAAAAAQYAABAAAAAgAAAANAAAAEQAAAAIAAAABAMAAE9TAAAAAAAACAAAAAQDAABPQAcAAAAAAAgAAAAEAwAAxRp+AAAAAAAIAAAABAMAAFvrPQAAAAAAEAAAAAEGAACAAAAAkAAAAKAAAACwAAAACAAAAAAEAABBwpXn7AAAABgAAAABAgAAAQAAAAAAAAAPAAAAAAAAAAAAAAAAAAAACAAAAAQDAAACAAAAAAAAAAQAAAADAwAA9QEAAAgAAAABCQAAZmlsZTovLy8MAAAAAQEAAE1hY2ludG9zaCBIRAgAAAAEAwAAABDQ2e0BAAAIAAAAAAQAAEHEhebagAAAJAAAAAEBAAAxQTAwQjhEMi0zNjIwLTQxQTEtODA0OC02NzBCQUI1ODRFM0MYAAAAAQIAAIEAAAABAAAA7xMAAAEAAAAAAAAAAAAAAAEAAAABAQAALwAAAAAAAAABBQAAzAAAAP7///8BAAAAAAAAABAAAAAEEAAAaAAAAAAAAAAFEAAAwAAAAAAAAAAQEAAA6AAAAAAAAABAEAAA2AAAAAAAAAACIAAAtAEAAAAAAAAFIAAAJAEAAAAAAAAQIAAANAEAAAAAAAARIAAAaAEAAAAAAAASIAAASAEAAAAAAAATIAAAWAEAAAAAAAAgIAAAlAEAAAAAAAAwIAAAwAEAAAAAAAABwAAACAEAAAAAAAARwAAAIAAAAAAAAAASwAAAGAEAAAAAAAAQ0AAABAAAAAAAAAA= AVC Coding Only need to just focus changes on the: **spine** "data to manipulate section" **spine** area

I have old sparsebundle files on my Apple Time Capsule. I can't seem to mount them. Error I get is no volumes found. I can see package contents, and size on disk is 113.4 GB. I've tried: hdiutil attach -nomount -noverify -noautofsck /Volumes/Joy/.sparsebundle, however, that only loads as /dev/disk2, but against it it doesn't say GUID_Partition_scheme and there is no /dev/disk2s1 Apple_partition_map or /dev/disk2s2 Apple_HFSX. I've also tried to use Migration Assistant, it shows the Time Machine sparsebundle, but it says no volumes. Please advise. Can I create a new empty sparsebundle using hdiutil -create, and copy the package contents from the no volume sparsebundle to this new one? Any other ideas how to fix it? Thanks in advance.

I have a headless Mac mini that has a SMB-shared volume that my MacBook Pro is configured to backup to via Time Machine. Both are running the latest version of macOS Sequoia (15.3.2). I’m trying to change the password of my encrypted network Time Machine backups and am currently hitting a wall. To my knowledge this isn’t a documented feature for network Time Machine backups, but since Time Machine uses sparsebundles and there's a utility to change their encryption keys I presumed Time Machine could support it. What I’ve tried to do: 1. Change encryption password of sparsebundle by using sudo hdiutil chpass /Volumes/Backups/’s MacBook Pro.sparsebundle - I’ve Confirmed that I can manually mount ’s MacBook Pro.sparsebundle (by double clicking it and entering the new password) 2. Manually kick off Time Machine backup, it fails with a message that I need to update my password. So I click “Update password.” 3. It asks me to enter my new password - I enter the new password and click Enter 4. After a few seconds, I see the same error screen - the new password is being reported as incorrect (even though as mentioned I can open the sparsebundle myself with the new password) I’ve looked at syslogs for backupd and found a few that look interesting:

2025-03-18 22:54:32.936183+1100 0x9937a    Default     0x77ba5              514    7    backupd: (DiskImages2) [com.apple.DiskImages2:Default] +[DIEncryptionFrontend hasGUIaccess]: User session flags: 0x1 (0x1=root, 0x10=graphics, 0x20=hasTTY, 0x1000=IsRemote), secRes=0
2025-03-18 22:54:35.039877+1100 0x9937a    Error       0x77ba5              514    7    backupd: (DiskImages2) [com.apple.DiskImages2:Default] +[DIError errorWithDomain:code:description:verboseInfo:error:]: Cannot retrieve passphrase from user via TTY or GUI (err code 25)
2025-03-18 22:54:35.039967+1100 0x9937a    Default     0x77ba5              514    0    backupd: (libxpc.dylib) [com.apple.xpc:connection] [0x625bd8a00] invalidated because the current process cancelled the connection by calling xpc_connection_cancel()
2025-03-18 22:54:35.040084+1100 0x9937a    Error       0x77ba5              514    0    backupd: (TimeMachine) [com.apple.TimeMachine:DiskImages] Failed to attach using DiskImages2 to url '/Volumes/.timemachine//ADD2A9B1-B032-4287-B688-2277179038A2/Backups/'s MacBook Pro.sparsebundle', error: Error Domain=NSPOSIXErrorDomain Code=25 "Inappropriate ioctl for device" UserInfo={DIErrorVerboseInfo=Cannot retrieve passphrase from user via TTY or GUI}
2025-03-18 22:54:36.307690+1100 0x99379    Error       0x77ba5              514    0    backupd: (TimeMachine) [com.apple.TimeMachine:BackupDispatching] Backup failed: BACKUP_FAILED_DISK_IMAGE_WRONG_PASSWORD (53)

From the above it appears that DiskImage2 is unable to get the new password ("Cannot retrieve passphrase from user via TTY or GUI (err code 25)"). I’m not sure why this is happening, as I’ve provided the password when it prompted me to update it. Maybe this isn’t being passed on to the DiskImage2 process that's running as root? I’m not sure, but it definitely seems like it should work given it recognises the password needed to be updated. I’ve also tried removing the old password from my login and System keychains in Keychain Access in any record I could find that looked relevant, still the same error. Only fix I’ve found is to change the password back to the original (using the same sudo hdiutil chpass command). After changing the password back, I can start a manual backup and it can mount the sparsebundle successfully. I'm wondering if this means that Time Machine stores a copy of the sparsebundle password elsewhere? I've also read that Time Machine does some truncating of the password (https://apple.stackexchange.com/a/331768/621735) . The original password is saved in my 1Password vault and I can see that Keychain Access has a truncated version of it saved (26 characters). I've tried passwords <26 characters and I'm still running into the same issue, so I don't think it's related to this but I could be wrong?

My goal is to create a Sequoia Time Machine SMB backup target which I can also mount on the backed up macOS in question (using USB). I must be able to confirm that Time Machine will accept the locally mounted sparsebundle as a backup target, preferably before investing time in a large initial backup (I can't wait hours for an initial backup every time during trial-and-error). My efforts end in tmutil giving an error 45. #### Strategy 1. I let Sequoia's Time Machine create a sparsebundle on an external SMB share 2. I let Time Machine start the actual data transfer before I skip the first backup, to ensure that the sparsebundle is completely created, without actually having to wait for an entire full backup 3. I mount the file system that acted as host for the SMB share — which resides on USB storage and which supports UNIX file permissions — on the macOS Sequoia instance that created the Time Machine sparsebundle 4. The sparsebundle has owner and group 1000:1000, i.e. the SMB user on the external SMB server. I can mount this sparsebundle with user 501 (my admin account). There isn't a user 1000 on this system. 5. At this point tmutil setdestination -a /path/to/my/sparsebundle will complain with Permission denied, so I chown -R 501:0 the sparsebundle, and mount it again. 6. Now tmutil setdestination will instead report `The operation couldn’t be completed. Operation not supported (error 45) The backup destination could not be added.` At that point I'm not sure what the problem is. #### Question **How can I make sure a sparsebundle (APFS) created by me via Time Machine, over SMB, can also be mounted locally and be accepted as a backup destination?** I've done it before with HFS+ bundles on Mojave, and I've done it before with APFS bundles on Ventura, so I'm fairly confident it should be possible *somehow*. ##### Experiments I've tried countless experiments to see what the criteria are for... - Being allowed to **mount** the sparsebundle (I apparently don't have to be the owner for this, as demonstrated by mounting it while being owned by 1000, but when I change the owner to a user that actually exists on the system (e.g. 503) then I'm suddenly not allowed to mount it...) - Having the sparsebundle being mounted as **writeable**, as reported by Finder's status bar (haven't succeeded yet, but this doesn't even seem to be required in order for Time Machine to actually start using it, which I discovered by inspecting a mounted and working TM-bundle on Ventura) - Adding it as a **backup destination** using tmutil I'm still at a loss as to what exactly Time Machine wants. Other UNIX permissions? ACL magic? Some .plist entry? Here are the permissions of the sparsebundle, and as you can see the recursive ownership of 501:0 has taken place, and it's read-writeable:

$ ls -haln bundle-name.sparsebundle 
total 156
drwxrwxr-x@ 4 501  0    12B 12 Feb 21:00 .
drwxr-xr-x  3 501  0     4B 12 Feb 20:52 ..
-rw-rw-r--@ 1 501  0   6,0K 12 Feb 20:44 .DS_Store
-rw-rw-r--@ 1 501  0   575B 13 Feb 17:44 Info.bckup
-rw-rw-r--@ 1 501  0   575B 13 Feb 17:44 Info.plist
drwxrwxr-x@ 2 501  0    13B 13 Feb 04:07 bands
-rw-rw-r--@ 1 501  0   516B 12 Feb 20:52 com.apple.TimeMachine.MachineID.plist
-rw-rw-r--@ 1 501  0   502B 12 Feb 21:00 com.apple.TimeMachine.Results.plist
-rw-rw-r--@ 1 501  0   220B 12 Feb 20:53 com.apple.TimeMachine.SnapshotHistory.plist
-rw-rw-r--@ 1 501  0     0B 12 Feb 20:44 lock
drwxrwxr-x@ 2 501  0    13B 13 Feb 04:07 mapped
-rw-rw-r--@ 1 501  0     0B 12 Feb 20:44 token

I'm missing something. ##### Additional experiments - I've tried tmutil inheritbackup but it says my machine already owns the sparsebundle, which is as it should be. - I also tried looking at a **working** sparsebundle setup on a different macOS (Ventura) install, but it was still confusing. For example: when I added write permissions for myself *only to the root sparsebundle directory* using Finder's Info dialog, and mounted it by double-clicking, then I could no longer back up to it (TM complained it was now "write protected"). As soon as I removed that *purely additional write permission* I was once again allowed to back up to the bundle. That particular sparsebundle had a different UNIX file owner than me. ##### Related - Previous question that resulted in the conclusion that the bundle's host volume must be writeable (i.e. use a driver with write support) just to be restored from. That's not applicable in this case since I'm trying to do more than just restore, and because the host FS already is writeable. Also, that was before Apple migrated from HFS+ to APFS for Time Machine destinations, which has undoubtedly introduced new requirements.

I was experimenting with iMazing doing backups to my old Zyxl Nas542. I did tests with AFP, SMB and NFS. Everything was dead slow. After a while I found out the SMB performance on the Mac is low but could be fixed by setting [default] signing_required=no in a newly created sudo vi /etc/nsmb.conf and a reboot of the Mac. I got 116Mb/s for write and 75Mb/s for read on SMB3. Before write performance was at 2,5Mb/s Anyway, as the Backup writes a lot of small files and folders performance didn't improve on either protocol. 75GB Backup took still several hours. So I gave up. This morning I created a growable disk image (sparseimage) on the SMB mount with AFPS format. Then tried to create a backup there and the first backup finished in about 45min for 75GB. Subsequent backups didn't finish before too, now finish in about 10min. So is there anything I should be aware of using sparseimage for backup or is there anything else better to improve the backup to then as?

Somehow, I have ended up with a couple Sparsebundles that no longer have any of the usual plists in their root. All the "bands" seem to be there, though. Time Machine will (of course) not mount them, and Disk Utility has no idea what to do with them either. Is there any way to recover from this?

I'm trying to recover data from an encrypted sparsebundle on macOS Mojave (10.14.6) that I just discovered became corrupted at some point in the past. It was created several years ago. I have the password for it but I can't get it to mount, and attaching it via hdiutil (hdiutil attach -nomount -noverify -noautofsck -stdinpass Personal.sparsebundle) reveals that it has no file system anymore. My issue seems similar to the one in this thread , but I don't have the expertise to be able to work out a solution specific to my situation from what's been presented in klanomath's answer . Here are the same info results posted by that thread's op: **diskutil list /dev/disk3** /dev/disk3 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: +4.6 GB disk3 **diskutil info /dev/disk3** Device Identifier: disk3 Device Node: /dev/disk3 Whole: Yes Part of Whole: disk3 Device / Media Name: Disk Image Volume Name: Not applicable (no file system) Mounted: Not applicable (no file system) File System: None Content (IOContent): None OS Can Be Installed: No Media Type: Generic Protocol: Disk Image SMART Status: Not Supported Disk Size: 4.6 GB (4613734400 Bytes) (exactly 9011200 512-Byte-Units) Device Block Size: 512 Bytes Read-Only Media: No Read-Only Volume: Not applicable (no file system) Device Location: External Removable Media: Removable Media Removal: Software-Activated Virtual: Yes **fdisk /dev/disk3** Disk: /dev/disk3 geometry: 560/255/63 [9011200 sectors] Signature: 0x70F0 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ 1: E6 654 20 31 - 129 246 12 [1624655050 - 2384870584] 2: 74 860 66 38 - 581 106 0 [1253546114 - 3399439981] 3: 1E 517 38 4 - 333 65 17 [ 709288943 - 2881760601] 4: C4 32 116 61 - 816 121 22 [2129857911 - 2037640686] DRDOSs < 32M **gpt recover /dev/disk3** gpt recover: /dev/disk3: no primary or secondary GPT headers, can't recover **gpt -r -vv show /dev/disk3** gpt show: /dev/disk3: mediasize=4613734400; sectorsize=512; blocks=9011200 gpt show: /dev/disk3: MBR not found at sector 0 start size index contents 0 9011200 I'd really appreciate any help in trying to recover files from this bundle! Thank you.

For my backup I use an encrypted virtual disk on a sparsebundle file that is stored in an external hard drive attached on a router via USB. This file is accessed via samba but for one reason I decided to use the HD directly attached to my mac. So I changed permission to access the file, because previously they were assigned to the user created on the router to access via smb, but I haven't only chmod the directory. I chown it for my mac user. Now when I try to mount the .sparsebundle it mount but Time Machine says it's in a readonly state and I'm not even able to actually read it. I tried to search the web for some days but I wasn't able to find the solution. I tried to force fsck_hfs but below is the result. Anyone can help me? I specify that the physical volume on the external drive is an EXT4 filesystem because the router runs on Linux. Maybe it add information to find the solution. sudo hdiutil attach -nomount -noverify -noautofsck /Volumes/Data/Dati/Time\ Machine.sparsebundle/ /dev/disk3 Apple_partition_scheme /dev/disk3s1 Apple_partition_map /dev/disk3s3 Apple_HFS sudo fsck_hfs -rc -fd /dev/disk3s3 ** /dev/rdisk3s3 Executing fsck_hfs (version hfs-407.50.6). Invalid content in journal ** Checking Journaled HFS Plus volume. The volume name is Time Machine ** Checking extents overflow file. Unused node is not erased (node = 2784) ** Checking catalog file. ** Rebuilding catalog B-tree. Disk full error ** The volume Time Machine could not be repaired. Invalid content in journal (4, 0) **EDIT:** Actually it could be also a filesystem problem, not (only) a permission one hdiutil attach /Volumes/Data/Dati/Time\ Machine.sparsebundle/ hdiutil: attach failed - no mountable file systems For testing purpose I attached again the HDD to the router and reenabled the smb share. Here is some screenshot of my setup. The smb share mounted on macos, with the sparsebundle that always mount in readonly The HDD mounted on the homemade NAS (/dev/sda3) The configuration of the Samba share (access -> read and write, even if we cannot read it from the screenshot) The permission settings on the directory mounted on the router **EDIT 2:** Executed fsck directly from the smb share. I cannot understand the difference but the output is much more verbose: mbp:~ asdasd$ sudo hdiutil attach -nomount -noverify -noautofsck /Volumes/HDD-3TB/Time\ Machine.sparsebundle/ /dev/disk2 Apple_partition_scheme /dev/disk2s1 Apple_partition_map /dev/disk2s3 Apple_HFS mbp:~ asdasd$ sudo fsck_hfs -dyf /dev/disk2s3 journal_replay(/dev/disk2s3) returned 0 ** /dev/rdisk2s3 Using cacheBlockSize=32K cacheTotalBlock=32768 cacheSize=1048576K. Executing fsck_hfs (version hfs-407.50.6). Invalid content in journal ** Checking Journaled HFS Plus volume. The volume name is Time Machine ** Checking extents overflow file. Unused node is not erased (node = 2784) Unused node is not erased (node = 2785) Unused node is not erased (node = 2786) Unused node is not erased (node = 2787) Unused node is not erased (node = 2788) Unused node is not erased (node = 2789) Unused node is not erased (node = 2790) Unused node is not erased (node = 2791) Unused node is not erased (node = 2792) Unused node is not erased (node = 2793) Unused node is not erased (node = 2794) Unused node is not erased (node = 2795) Unused node is not erased (node = 2796) Unused node is not erased (node = 2797) Unused node is not erased (node = 2798) Unused node is not erased (node = 2799) Unused node is not erased (node = 2800) Unused node is not erased (node = 2801) Unused node is not erased (node = 2802) Unused node is not erased (node = 2803) Unused node is not erased (node = 2804) Unused node is not erased (node = 2805) Unused node is not erased (node = 2806) Unused node is not erased (node = 2807) Unused node is not erased (node = 2808) Unused node is not erased (node = 2809) Unused node is not erased (node = 2810) Unused node is not erased (node = 2811) Unused node is not erased (node = 2812) Unused node is not erased (node = 2813) Unused node is not erased (node = 2814) Unused node is not erased (node = 2815) ** Checking catalog file. hfs_swap_BTNode: invalid forward link (0xC4663BAF) hfs_swap_BTNode: invalid backward link (0x5C275BF7) hfs_swap_BTNode: invalid node kind (-86) hfs_swap_BTNode: invalid node height (125) hfs_swap_BTNode: invalid record count (0x7A07) Invalid record count (4, 138355) hfs_swap_BTNode: invalid forward link (0x4503418D) hfs_swap_BTNode: invalid backward link (0x2A4FB6A0) hfs_swap_BTNode: invalid node kind (13) hfs_swap_BTNode: invalid node height (204) hfs_swap_BTNode: invalid record count (0xA115) Invalid record count (4, 138349) hfs_swap_BTNode: invalid forward link (0xA89C3ED0) hfs_swap_BTNode: invalid backward link (0x01F29D8B) hfs_swap_BTNode: invalid node kind (58) hfs_swap_BTNode: invalid node height (244) hfs_swap_BTNode: invalid record count (0x4C27) Invalid record count (4, 117907) hfs_swap_BTNode: invalid forward link (0xBD984CDE) hfs_swap_BTNode: invalid backward link (0x605E0605) hfs_swap_BTNode: invalid node kind (82) hfs_swap_BTNode: invalid node height (255) hfs_swap_BTNode: invalid record count (0x545E) Invalid record count (4, 15346) hfs_swap_BTNode: invalid forward link (0x10253D99) hfs_swap_BTNode: invalid backward link (0xE20E4C52) hfs_swap_BTNode: invalid node kind (5) hfs_swap_BTNode: invalid node height (62) hfs_swap_BTNode: invalid record count (0x46A0) Invalid record count (4, 15350) hfs_swap_BTNode: invalid forward link (0x89065B23) hfs_swap_BTNode: invalid backward link (0xEC5EA33C) hfs_swap_BTNode: invalid node kind (109) hfs_swap_BTNode: invalid node height (138) hfs_swap_BTNode: invalid record count (0x22B2) Invalid record count (4, 15351) hfs_swap_BTNode: invalid forward link (0xCB62D10A) hfs_swap_BTNode: invalid backward link (0xE4D99839) hfs_swap_BTNode: invalid node kind (38) hfs_swap_BTNode: invalid node height (178) hfs_swap_BTNode: invalid record count (0xA660) Invalid record count (4, 15354) hfs_swap_BTNode: invalid forward link (0x96DA8F15) hfs_swap_BTNode: invalid backward link (0x0425140D) hfs_swap_BTNode: invalid node kind (55) hfs_swap_BTNode: invalid node height (193) hfs_swap_BTNode: invalid record count (0xB64A) Invalid record count (4, 15356) hfs_swap_BTNode: invalid forward link (0x1BFF8923) hfs_swap_BTNode: invalid backward link (0x322A6002) hfs_swap_BTNode: invalid node kind (-86) hfs_swap_BTNode: invalid node height (50) hfs_swap_BTNode: invalid record count (0x2556) Invalid record count (4, 15361) hfs_swap_BTNode: invalid forward link (0x55587FAC) hfs_swap_BTNode: invalid backward link (0xBFFCD97E) hfs_swap_BTNode: invalid node kind (53) hfs_swap_BTNode: invalid node height (31) hfs_swap_BTNode: invalid record count (0x3D2E) Invalid record count (4, 15363) hfs_swap_BTNode: invalid forward link (0xF0AB994A) hfs_swap_BTNode: invalid backward link (0xD761E74A) hfs_swap_BTNode: invalid node kind (52) hfs_swap_BTNode: invalid node height (241) hfs_swap_BTNode: invalid record count (0x83C7) Invalid record count (4, 15359) hfs_swap_BTNode: invalid forward link (0x8265BB41) hfs_swap_BTNode: invalid backward link (0xDBAB6D74) hfs_swap_BTNode: invalid node kind (-117) hfs_swap_BTNode: invalid node height (89) hfs_swap_BTNode: invalid record count (0xB62B) Invalid record count (4, 15366) hfs_swap_BTNode: invalid forward link (0xA075EE7A) hfs_swap_BTNode: invalid backward link (0xA396FB09) hfs_swap_BTNode: invalid node kind (4) hfs_swap_BTNode: invalid node height (249) hfs_swap_BTNode: invalid record count (0xE600) Invalid record count (4, 15367) hfs_swap_BTNode: invalid forward link (0x60AE6546) hfs_swap_BTNode: invalid backward link (0x2DC43D0E) hfs_swap_BTNode: invalid node kind (25) hfs_swap_BTNode: invalid node height (163) hfs_swap_BTNode: invalid record count (0x1620) Invalid record count (4, 15372) hfs_swap_BTNode: invalid forward link (0x14D20EF4) hfs_swap_BTNode: invalid backward link (0x6DA1EB27) hfs_swap_BTNode: invalid node kind (-43) hfs_swap_BTNode: invalid node height (13) hfs_swap_BTNode: invalid record count (0x3B82) Invalid record count (4, 15376) hfs_swap_BTNode: invalid forward link (0x4502411B) hfs_swap_BTNode: invalid backward link (0x27F70985) hfs_swap_BTNode: invalid node kind (-71) hfs_swap_BTNode: invalid node height (133) hfs_swap_BTNode: invalid record count (0x391E) Invalid record count (4, 15380) hfs_swap_BTNode: invalid forward link (0xD5E9CF80) hfs_swap_BTNode: invalid backward link (0x8D0C5384) hfs_swap_BTNode: invalid node kind (95) hfs_swap_BTNode: invalid node height (81) hfs_swap_BTNode: invalid record count (0x68C2) Invalid record count (4, 15384) hfs_swap_BTNode: invalid forward link (0xCD183754) hfs_swap_BTNode: invalid backward link (0x4162C8FC) hfs_swap_BTNode: invalid node kind (24) hfs_swap_BTNode: invalid node height (46) hfs_swap_BTNode: invalid record count (0x6AAA) Invalid record count (4, 15388) hfs_swap_BTNode: invalid forward link (0x30398884) hfs_swap_BTNode: invalid backward link (0x5D6E1DEF) hfs_swap_BTNode: invalid node kind (94) hfs_swap_BTNode: invalid node height (35) hfs_swap_BTNode: invalid record count (0xB4BA) Invalid record count (4, 15390) hfs_swap_BTNode: invalid forward link (0x9ED1D2C2) hfs_swap_BTNode: invalid backward link (0x927DFDD5) hfs_swap_BTNode: invalid node kind (-17) hfs_swap_BTNode: invalid node height (229) hfs_swap_BTNode: offset #0 invalid (0x9FF7) (blockSize 0x2000 numRecords 1843) Invalid node structure (4, 15392) hfs_swap_BTNode: invalid forward link (0x7293EA34) hfs_swap_BTNode: invalid backward link (0x1079EF12) hfs_swap_BTNode: invalid node kind (35) hfs_swap_BTNode: invalid node height (7) hfs_swap_BTNode: invalid record count (0x6341) Invalid record count (4, 15399) hfs_swap_BTNode: invalid forward link (0xC34E551E) hfs_swap_BTNode: invalid backward link (0xB58FFB11) hfs_swap_BTNode: invalid node kind (52) hfs_swap_BTNode: invalid node height (154) hfs_swap_BTNode: invalid record count (0x7A42) Invalid record count (4, 15406) hfs_swap_BTNode: invalid forward link (0x62012680) hfs_swap_BTNode: invalid backward link (0x25D211FD) hfs_swap_BTNode: invalid node kind (89) hfs_swap_BTNode: invalid node height (87) hfs_swap_BTNode: invalid record count (0x6038) Invalid record count (4, 15414) hfs_swap_BTNode: invalid forward link (0xE8995EC5) hfs_swap_BTNode: invalid backward link (0xACFEC80F) hfs_swap_BTNode: invalid node kind (115) hfs_swap_BTNode: invalid node height (240) hfs_swap_BTNode: invalid record count (0x6CED) Invalid record count (4, 15430) hfs_swap_BTNode: invalid forward link (0x4E0F412C) hfs_swap_BTNode: invalid backward link (0xEB45452D) hfs_swap_BTNode: invalid node kind (21) hfs_swap_BTNode: invalid node height (253) hfs_swap_BTNode: invalid record count (0x8B26) Invalid record count (4, 15439) hfs_swap_BTNode: invalid forward link (0x16E2F4F5) hfs_swap_BTNode: invalid backward link (0xB2D9EC11) hfs_swap_BTNode: invalid node kind (4) hfs_swap_BTNode: invalid node height (90) hfs_swap_BTNode: invalid record count (0x59F3) Invalid record count (4, 15443) hfs_swap_BTNode: invalid forward link (0xFE2CA3C7) hfs_swap_BTNode: invalid backward link (0x8E2D4CAA) hfs_swap_BTNode: invalid node kind (-11) hfs_swap_BTNode: invalid node height (238) hfs_swap_BTNode: invalid record count (0x8B13) Invalid record count (4, 15453) hfs_swap_BTNode: invalid forward link (0xB1B3FE24) hfs_swap_BTNode: invalid backward link (0x06F47091) hfs_swap_BTNode: invalid node kind (126) hfs_swap_BTNode: invalid node height (171) hfs_swap_BTNode: invalid record count (0x54F7) Invalid record count (4, 15457) hfs_swap_BTNode: invalid forward link (0x7B8EDD20) hfs_swap_BTNode: invalid backward link (0x86BB009C) hfs_swap_BTNode: invalid node kind (-30) hfs_swap_BTNode: invalid node height (82) hfs_swap_BTNode: invalid record count (0x9C0B) Invalid record count (4, 15459) hfs_swap_BTNode: invalid forward link (0x3385DB18) hfs_swap_BTNode: invalid backward link (0xD6BA8FAD) hfs_swap_BTNode: invalid node kind (-119) hfs_swap_BTNode: invalid node height (192) hfs_swap_BTNode: invalid record count (0x5DE7) Invalid record count (4, 15451) hfs_swap_BTNode: invalid forward link (0xF61BE3A7) hfs_swap_BTNode: invalid backward link (0xB9C758D4) hfs_swap_BTNode: invalid node kind (-8) hfs_swap_BTNode: invalid node height (132) hfs_swap_BTNode: invalid record count (0x9329) Invalid record count (4, 15466) hfs_swap_BTNode: invalid forward link (0xCE4305BC) hfs_swap_BTNode: invalid backward link (0xE513F9D8) hfs_swap_BTNode: invalid node kind (-103) hfs_swap_BTNode: invalid node height (227) hfs_swap_BTNode: invalid record count (0x5868) Invalid record count (4, 15470) hfs_swap_BTNode: invalid forward link (0xB6E6C582) hfs_swap_BTNode: invalid backward link (0xBF967F87) hfs_swap_BTNode: invalid node kind (16) hfs_swap_BTNode: invalid node height (95) hfs_swap_BTNode: invalid record count (0xD4BD) Invalid record count (4, 15474) hfs_swap_BTNode: invalid forward link (0x43C7A9AD) hfs_swap_BTNode: invalid backward link (0x55670FA5) hfs_swap_BTNode: invalid node kind (-61) hfs_swap_BTNode: invalid node height (43) hfs_swap_BTNode: invalid record count (0x6EFA) Invalid record count (4, 15476) hfs_swap_BTNode: invalid forward link (0xF930D5AA) hfs_swap_BTNode: invalid backward link (0x92E89158) hfs_swap_BTNode: invalid node kind (-66) hfs_swap_BTNode: invalid node height (97) hfs_swap_BTNode: invalid record count (0x3969) Invalid record count (4, 15478) hfs_swap_BTNode: invalid forward link (0x0356D5D6) hfs_swap_BTNode: invalid backward link (0x8C032195) hfs_swap_BTNode: invalid node kind (41) hfs_swap_BTNode: invalid node height (110) hfs_swap_BTNode: invalid record count (0x8BC2) Invalid record count (4, 15504) hfs_swap_BTNode: invalid forward link (0x719EAB8D) hfs_swap_BTNode: invalid backward link (0x866A3F4B) hfs_swap_BTNode: invalid node kind (60) hfs_swap_BTNode: invalid node height (52) hfs_swap_BTNode: invalid record count (0x4268) Invalid record count (4, 15510) hfs_swap_BTNode: invalid forward link (0xE9849E68) hfs_swap_BTNode: invalid backward link (0x4444F22C) hfs_swap_BTNode: invalid node kind (120) hfs_swap_BTNode: invalid node height (202) hfs_swap_BTNode: invalid record count (0xCA19) Invalid record count (4, 118664) Invalid node structure (4, 45169) Invalid sibling link (4, 45169) Node 45169's back link is 0x0; expected 0x7758 disk offset = 0xcd8fd000, size = 0x2000 Invalid sibling link (4, 45169) Node 45169's forward link is 0x0; expected 0xb074 disk offset = 0xcd8fd000, size = 0x2000 Invalid node height (4, 45169) Index key doesn't match first node key Invalid index key (4, 45169) Invalid node structure (4, 45189) Invalid sibling link (4, 45189) Node 45189's back link is 0x0; expected 0xb082 disk offset = 0xcd925000, size = 0x2000 Invalid sibling link (4, 45189) Node 45189's forward link is 0x0; expected 0xb081 disk offset = 0xcd925000, size = 0x2000 Invalid node height (4, 45189) Index key doesn't match first node key Invalid index key (4, 45189) Invalid node structure (4, 45185) Invalid sibling link (4, 45185) Node 45185's back link is 0x0; expected 0xb085 disk offset = 0xcd91d000, size = 0x2000 Invalid sibling link (4, 45185) Node 45185's forward link is 0x0; expected 0xb089 disk offset = 0xcd91d000, size = 0x2000 Invalid node height (4, 45185) Index key doesn't match first node key Invalid index key (4, 45185) Invalid node structure (4, 45200) Invalid sibling link (4, 45200) Node 45200's back link is 0x0; expected 0xb08e disk offset = 0xcd93b000, size = 0x2000 Invalid sibling link (4, 45200) Node 45200's forward link is 0x0; expected 0xb092 disk offset = 0xcd93b000, size = 0x2000 Invalid node height (4, 45200) Index key doesn't match first node key Invalid index key (4, 45200) Invalid node structure (4, 45206) Invalid sibling link (4, 45206) Node 45206's back link is 0x0; expected 0xb09a disk offset = 0xcd947000, size = 0x2000 Invalid sibling link (4, 45206) Node 45206's forward link is 0x0; expected 0xb09c disk offset = 0xcd947000, size = 0x2000 Invalid node height (4, 45206) Index key doesn't match first node key Invalid index key (4, 45206) Invalid node structure (4, 45212) Invalid sibling link (4, 45212) Node 45212's back link is 0x0; expected 0xb096 disk offset = 0xcd953000, size = 0x2000 Invalid sibling link (4, 45212) Node 45212's forward link is 0x0; expected 0x18d4b disk offset = 0xcd953000, size = 0x2000 Invalid node height (4, 45212) Index key doesn't match first node key Invalid index key (4, 45212) Invalid node structure (4, 45217) Invalid sibling link (4, 45217) Node 45217's back link is 0x0; expected 0xb09f disk offset = 0xcd95d000, size = 0x2000 Invalid sibling link (4, 45217) Node 45217's forward link is 0x0; expected 0xb0a5 disk offset = 0xcd95d000, size = 0x2000 Invalid node height (4, 45217) Index key doesn't match first node key Invalid index key (4, 45217) Invalid node structure (4, 45232) Invalid sibling link (4, 45232) Node 45232's back link is 0x0; expected 0xb0b5 disk offset = 0xcd97b000, size = 0x2000 Invalid sibling link (4, 45232) Node 45232's forward link is 0x0; expected 0xb0b7 disk offset = 0xcd97b000, size = 0x2000 Invalid node height (4, 45232) Index key doesn't match first node key Invalid index key (4, 45232) Invalid node structure (4, 101709) Invalid sibling link (4, 101709) Node 101709's back link is 0x0; expected 0xb0bc disk offset = 0xe92b5000, size = 0x2000 Invalid sibling link (4, 101709) Node 101709's forward link is 0x0; expected 0xb0bd disk offset = 0xe92b5000, size = 0x2000 Invalid node height (4, 101709) Index key doesn't match first node key Invalid index key (4, 101709) Invalid node structure (4, 45245) Invalid sibling link (4, 45245) Node 45245's back link is 0x0; expected 0x18d4d disk offset = 0xcd995000, size = 0x2000 Invalid sibling link (4, 45245) Node 45245's forward link is 0x0; expected 0xb0c1 disk offset = 0xcd995000, size = 0x2000 Invalid node height (4, 45245) Index key doesn't match first node key Invalid index key (4, 45245) Invalid node structure (4, 132677) Invalid sibling link (4, 132677) Node 132677's back link is 0x0; expected 0x20646 disk offset = 0xf84a5000, size = 0x2000 Invalid sibling link (4, 132677) Node 132677's forward link is 0x0; expected 0x7760 disk offset = 0xf84a5000, size = 0x2000 Invalid node height (4, 132677) Index key doesn't match first node key Invalid index key (4, 132677) Invalid node structure (4, 30560) Invalid sibling link (4, 30560) Node 30560's back link is 0x0; expected 0x20645 disk offset = 0xc66db000, size = 0x2000 Invalid sibling link (4, 30560) Node 30560's forward link is 0x0; expected 0x20655 disk offset = 0xc66db000, size = 0x2000 Invalid node height (4, 30560) Index key doesn't match first node key Invalid index key (4, 30560) Invalid node structure (4, 45251) Invalid sibling link (4, 45251) Node 45251's back link is 0x0; expected 0x18d50 disk offset = 0xcd9a1000, size = 0x2000 Invalid sibling link (4, 45251) Node 45251's forward link is 0x0; expected 0xb0d0 disk offset = 0xcd9a1000, size = 0x2000 Invalid node height (4, 45251) Index key doesn't match first node key Invalid index key (4, 45251) Invalid node structure (4, 45265) Invalid sibling link (4, 45265) Node 45265's back link is 0x0; expected 0x20683 disk offset = 0xcd9bd000, size = 0x2000 Invalid sibling link (4, 45265) Node 45265's forward link is 0x0; expected 0xb0d5 disk offset = 0xcd9bd000, size = 0x2000 Invalid node height (4, 45265) Index key doesn't match first node key Invalid index key (4, 45265) ** The volume Time Machine could not be verified completely. volume check failed with error 7 volume type is pure HFS+ primary MDB is at block 0 0x00 alternate MDB is at block 0 0x00 primary VHB is at block 2 0x02 alternate VHB is at block 1952453214 0x7460125e sector size = 512 0x200 VolumeObject flags = 0x07 total sectors for volume = 1952453216 0x74601260 total sectors for embedded volume = 0 0x00 CheckForClean - could not get VHB/MDB at block 1952453214 CheckHFS returned -1317, fsmodified = 0

I recently set up a Synology NAS to replace my previous Drobos. Never ever had any issues with the Drobos, just that they were an item that would put me in hot water if I needed to fix them ever, so off to Synology. Setting up the Synology as per their specs for Time Machine, all worked well… I allocated 4 TB of space as I’ve done for years on the Drobo since the inception of Time Machine. However, when setting up Time Machine on a Synology NAS, it creates a .sparseimage file, unlike if backing it to an external hard disk, which would create a .backup.db file. For some odd reason by having the Recycle Bin active in the NAS shared folder (Time Machine), the .sparseimage file never really worked as intended like on an external hard disk, when it got full, it complained (Time Machine), whereas normally on and external hard disk, it would delete the oldest files to make room for the newest stuff (shrink/grow). My research showed that if I disable the Recycle Bin on the Time Machine NAS shared folder, it will reclaim the space. It did (I was also told that first emptying the Recycle Bin was required for it to work). The only issue with that is that I lost access to months and months of backups (Time Machine), even though if I were to probe the .sparseimage file, I could see items that went back to August when I initially set up the new Synology NAS Time Machine shared folder. However, the backups for Time Machine work and the file size does not fill up the available space as it did previously with the Recycle Bin disabled. (see the reference at the bottom of [Synology: Configuring Time Machine and Quotas](https://sflanders.net/2015/11/23/synology-configuring-time-machine-quotas/#:~:text=IMPORTANT%3A%20User%20quotas%20support%20a,folder%20and%20not%20use%20quotas)) However, the item I’d like to do is get away from the NAS for Time Machine and use an external 4 TB SSD. There seems to be no clear documentation in the wild about how to do what I’m looking to do. I’d like to take the .sparseimage file from the NAS and convert it to the .backupdb required format that is necessary for external drive Time Machine devices. Anyone?

I hope someone could help me. I've forgot the Time Machine disk password, and I need it to restore backup to my new iMac. Searching on the web I read about John the Ripper, it could help me. I've installed it, but now I need to place the command into Terminal app to recover the password. Could someone write the code for me?

I have a Time Machine backup stored on a Synology NAS that got corrupted for some reason (probably a power failure). The folder containing the sparsebundle is mounted on the Mac using smbfs. I tried to run fsck_apfs but it fails with the following message:

error: spaceman cib out of order: 13, expected 4
   Space manager is invalid.
** The container /dev/disk5s2 could not be verified completely.

Is there a way to recover the space manager?

I'm somewhat pissed off with my almost 6TB TM backups that have become unusable, particularly after Apple had to replace my MBP (failed mobo). TM running on a Synology NAS. What I get now from 1st aid is this (same from fsck):

Checking file system and repairing if necessary and if possible.
Volume is already unmounted.
Performing fsck_apfs -y -x /dev/rdisk3s1
Checking the container superblock.
Checking the checkpoint with transaction ID 2116640.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking volume /dev/rdisk3s1.
Checking the APFS volume superblock.
The volume Backups of MacBook Pro PAN was formatted by newfs_apfs 
(1933.61.1) and last modified by apfs_kext (2142.101.3).

Checking the object map.
error: (oid 0xc26f758) om: btn: invalid o_oid (0x406)
error: (oid 0xc26f758) om: btn: invalid o_subtype (0xe, expected 0xb)
error: (oid 0xc26f758) om: btn: invalid o_type (0x3, expected 0x40000003)
Object map is invalid.

The volume /dev/rdisk3s1 was found to be corrupt and cannot be repaired.

Verifying allocated space.
The volume /dev/rdisk3s1 could not be verified completely.
File system check exit code is 8.

Restoring the original state found as unmounted.

File system verify or repair failed. : (-69845)

Operation failed…

Strangely enough, I previously could do a hdiutil attach and see the partitions inside, I've just restarted, and now always get a hdiutil: attach failed - Resource temporarily unavailable message, although with the exact same command as before? Any comment/idea appreciated !

I messed up my Time Machine backup in some way. I'm no longer able to mount the sparsebundle file as I get an error stating that there are no mountable filesystems. I used the hdiutil command to attach the sparsebundle file: hdiutil attach -nomount -readwrite flattop.sparsebundle which resulted in the following /dev/ devices: /dev/disk2 Apple_partition_scheme /dev/disk2s1 Apple_partition_map /dev/disk2s2 Apple_HFSX Afterwards I ran the fsch_hfs command to check the main volume (/dev/disk2s2): fsck_hfs -drf /dev/disk2s2 This resulted in a notice that the Time Machine Backups volume is corrupt and needed to be repaired: Unable to open block device /dev/disk2s2: Permission deniedjournal_replay(/dev/disk2s2) returned 13 ** /dev/rdisk2s2 (NO WRITE) Using cacheBlockSize=32K cacheTotalBlock=32768 cacheSize=1048576K. Executing fsck_hfs (version diskdev_cmds-540.1~34). Non-empty journal: start = 66310144, end = 94912512 Journal need to be replayed but volume is read-only ** Checking Journaled HFS Plus volume. ** Detected a case-sensitive volume. The volume name is Time Machine Backups ** Checking extents overflow file. Unused node is not erased (node = 3568) Unused node is not erased (node = 3574) Unused node is not erased (node = 3575) ** Checking catalog file. ** The volume Time Machine Backups was found corrupt and needs to be repaired. volume type is pure HFS+ primary MDB is at block 0 0x00 alternate MDB is at block 0 0x00 primary VHB is at block 2 0x02 alternate VHB is at block 2865568974 0xaacd1cce sector size = 512 0x200 VolumeObject flags = 0x07 total sectors for volume = 2865568976 0xaacd1cd0 total sectors for embedded volume = 0 0x00 As you can see there is also an error saying "Unable to open block device /dev/disk2s2: Permission deniedjournal_replay(/dev/disk2s2) returned 13". I thought this might be due to not running the fsck_hfs command as a su, so I tried it with sudo but this had the same result. My sparsebundle file is on a Synology DS408 NAS and has been running without a problem for about 2 years now :( Anyone an idea how to take this further? Kind regards, Niels R. UPDATE: As I suspected while writing this question I probably have a problem with read/write permissions. I now see the volume appearing in the Disk Utility and when I click on "Verify" I get the following output: Verifying volume “Time Machine Backups” Checking file systemJournal need to be replayed but volume is read-only Checking Journaled HFS Plus volume. Detected a case-sensitive volume. Checking extents overflow file. Unused node is not erased (node = 3568) Checking catalog file. Keys out of order The volume Time Machine Backups was found corrupt and needs to be repaired. Error: This disk needs to be repaired. Click Repair Disk. Can I simply chmod the sparsebundle file to set the right permissions?

I’m helping someone who has deleted their Time Machine backup by accident. All that is contained within the sparsebundle are .incomplete and .previous folders. I would like to recover as much data as possible so I need a way to combine all the changes from each folder essentially. Also I may first attempt to recover the deleted files with software, does anyone have preferences between R-Studio, UFS, or another software? And would scanning for deleted files work the same within a sparsebundle? Thanks!

I'm trying to create a sparse bundle image from Disk Utility directly on my NAS (through a mounted smb volume): I then get the following error after a few seconds: Creating a sparseimage the same way works perfectly. I however wanted to go to a sparse bundle as the file is afterwards synchronized with Google Drive and sparsebundle are seen as folders and are then more sync-friendly. I'm on 10.10.1. Info about the mounted volume:

I had an old 2017 MacBook Pro that was wiped and sent away. My problem is I need to get a file from a Time Machine backup that I have of that machine stored on my Synology NAS. I use this NAS as a Time Machine backup disk for all of my Macs. I'm able to mount the Sparsebundle on my 13" M1 Macbook Pro but I can't see any files. What I really need to do is go back to a certain date to recover a few megabytes worth of text files. Here is what it looks like in Finder when the sparsebundle is mounted: I tried holding down the Option key and clicking on the Time Machine icon to "Browse Other Backup Disks". I'm able to find the drive I'm looking for but the interface to go back in time freezes and is unable to go back or display other dates. Exploring the sparesbundle on the file explorer on the NAS shows files and there is data in the bands folder. The sparsebundle weighs in at about 144GB so I'm confident I should be able to access my deleted files on it somehow. I don't see a Backups.backupdb folder. I tried downloading the sparsebundle locally and messing with it on my local hard drive instead of over the network but it doesn't seem to make much of a difference. I got desperate and fired up the Migration Assistant app to see if I could restore the Time Machine backup to a fresh account but after a few hours staring at Loading Backup... I gave up. Any other ideas on how I can access this Time Machine backup to recover a few files?

mdls does not return anything when I run it on a mounted (originally encrypted) sparse bundle:

❯ ll ./test
.rw-r--r--@ 0 evar 14 Sep 18:34 ./test

❯ mdls ./test                                                                                                               
./test: could not find ./test.

Trying mdutil to turn on the indexing:

❯ sudo mdutil -d /Volumes/sth                                                                                               
/System/Volumes/Data/Volumes/sth:
Error: unable to perform operation.  (-400)
	Error: unknown indexing state.

PS: I use mdls to extract the tags a file has. I'm open to using any other solution for doing so.

My wife's Laptop died. Her backup was on a Synology NAS and we need to get at some files from the backup by accessing the Sparsebundle from another Mac. I made a copy of the Sparsebundle to work on from the other Mac but can't mount it. I've searched the internet for ways to repair it, but can't get by the step where you "attach" it in a terminal command. I found a script called TimeMachineRepairScript.sh that is supposed to do all the right things, such as setting permissions in all the right files. All of those steps work correctly. But when it gets to the step:

hdiutil attach -nomount -noverify -noautofsck '/Volumes/Transport/Mo'\''s MacBook Pro 2018.sparsebundle'

it hangs up there for a while. Then I get an error that says:

2022-06-23 11:43:38.939 hdiutil[1168:11281] -[DIHelperProxy(Thread) waitForHelperDone] timed out waiting for helper registration

All of the web pages that give instructions on repairing a Sparsebundle seem to breeze right by this step as if there should be no problem with it. But I can't get past it. Any ideas as to what's wrong or what I can do to fix it? Here's the full Terminal session:

danielkuchta@iMac ~ % cd Desktop
danielkuchta@iMac Desktop % chmod +x TimeMachineRepairScript.sh
danielkuchta@iMac Desktop % ./TimeMachineRepairScript.sh /Volumes/Transport/Mo\'s\ MacBook\ Pro\ 2018.sparsebundle
+ IMAGE='/Volumes/Transport/Mo'\''s MacBook Pro 2018.sparsebundle'
+ '[' -z '/Volumes/Transport/Mo'\''s MacBook Pro 2018.sparsebundle' ']'
+ chflags -v nouchg '/Volumes/Transport/Mo'\''s MacBook Pro 2018.sparsebundle'
+ chflags -v nouchg '/Volumes/Transport/Mo'\''s MacBook Pro 2018.sparsebundle/token'
+ chflags -v nouchg '/Volumes/Transport/Mo'\''s MacBook Pro 2018.sparsebundle/bands'
+ /usr/libexec/PlistBuddy -c 'Delete :RecoveryBackupDeclinedDate' '/Volumes/Transport/Mo'\''s MacBook Pro 2018.sparsebundle/com.apple.TimeMachine.MachineID.plist'
Delete: Entry, ":RecoveryBackupDeclinedDate", Does Not Exist
+ /usr/libexec/PlistBuddy -c 'Set :VerificationState 0' '/Volumes/Transport/Mo'\''s MacBook Pro 2018.sparsebundle/com.apple.TimeMachine.MachineID.plist'
+ set -e
++ hdiutil attach -nomount -noverify -noautofsck '/Volumes/Transport/Mo'\''s MacBook Pro 2018.sparsebundle'
++ awk '/HFS/ {print $1}'
2022-06-23 11:43:38.939 hdiutil[1168:11281] -[DIHelperProxy(Thread) waitForHelperDone] timed out waiting for helper registration
+ DEV=
+ echo '/Volumes/Transport/Mo'\''s MacBook Pro 2018.sparsebundle -> '
/Volumes/Transport/Mo's MacBook Pro 2018.sparsebundle -> 
+ fsck_hfs -fy -c 8gb ''
No such file or directory
Can't stat 
Can't stat : No such file or directory
danielkuchta@iMac Desktop %

I just updated from Yosemite to El Capitan. I have two backups, one being done with Time Machine and one with Carbon Copy Cloner. Both sparsebundles are stored on a NAS (Synology DS213). After the update everything still works as before. I can do backups and verifying them shows them as being there and functional. However, navigating to the Backup folder on the NAS using Finder shows the sparsebundles as folders, not as sparsebundles. So instead of: Backup.sparsebundle I now have: C33YRS~D Trying to open them launches Terminal. I restarted the MAC and also the NAS, the sparsebundles are still displayed as folders. What happened? Does anybody have the same issue? Can I just rename these files back to their original name or is there something else I am missing?