Time Machine sparsebundle mount failed in attempt to recover new Mac from backup

After giveaway of old iMac I'm trying to recover backup from Time Machine sparsebundle to new Mac. I correctly quit (somewhere in the middle) first recovery process which worked well, second attempt was not possible to start. I get mount failed (and error 112) response from time machine sparsebundle. is there solution for this pls ? my whole backup is at risk. official apple support had no solution for this so far.

Mac mini (M2 Pro, 2023)

Posted on Apr 22, 2023 1:43 AM

Reply
Question marked as Top-ranking reply

Posted on Apr 24, 2023 8:49 PM

There will be complex command line statements you need to run in Terminal. You may need to translate the examples shown to match your precise path and filenames, etc.


First step: Backup the sparsebundle to another disk.


Turn off Time Machine

sudo tmutil disable


Make the sparsebundle read/write by issuing the following command and enter your password when prompted:


sudo chflags -R nouchg /Volumes/{name of your disk}/{name of}.sparsebundle


Next, mount the volume using this command which won't mount it normally but Disk Utility can access it.


sudo hdiutil attach -nomount -noverify -noautofsck /Volumes/{name of your disk}/{name of}.sparsebundle


Then try opening Disk Utility and running First Aid. If that fails to fix it, consider a commercial 3rd Party


https://www.easeus.com/mac/mac-data-recovery/ <-- cheaper and it might work

https://www.prosofteng.com/mac-data-recovery <-- best software on the planet but not inexpensive


It it will still not mount, then you've got a severely damaged sparsebundle that is irrecoverable.


Similar questions

11 replies
Question marked as Top-ranking reply

Apr 24, 2023 8:49 PM in response to DuMartin

There will be complex command line statements you need to run in Terminal. You may need to translate the examples shown to match your precise path and filenames, etc.


First step: Backup the sparsebundle to another disk.


Turn off Time Machine

sudo tmutil disable


Make the sparsebundle read/write by issuing the following command and enter your password when prompted:


sudo chflags -R nouchg /Volumes/{name of your disk}/{name of}.sparsebundle


Next, mount the volume using this command which won't mount it normally but Disk Utility can access it.


sudo hdiutil attach -nomount -noverify -noautofsck /Volumes/{name of your disk}/{name of}.sparsebundle


Then try opening Disk Utility and running First Aid. If that fails to fix it, consider a commercial 3rd Party


https://www.easeus.com/mac/mac-data-recovery/ <-- cheaper and it might work

https://www.prosofteng.com/mac-data-recovery <-- best software on the planet but not inexpensive


It it will still not mount, then you've got a severely damaged sparsebundle that is irrecoverable.


Apr 23, 2023 12:29 PM in response to DuMartin

You should be able to mount the disk and navigate the contents of the Time Machine in a read only state. Then copy what you need somewhere else.


Mount via CMD + K Connect to Server

smb://capsule._smb._tcp.local/<Time Machine>


Where <Time Machine> is the name of your Time Machine drive.


Double-click the sparse image and if it refuses to mount then it's damaged. Repairing it is rather technical. Let's jump that hurdle only if you cannot mount the sparse bundle.




Apr 26, 2023 7:25 AM in response to James Brickley

Thank you for assistance James, unfortunately first aid fails here... going to try 3rd party options.

Thanks. Martin



Running First Aid on “Backups of iMac” (disk6s1)


Checking file system and repairing if necessary and if possible.

Volume is already unmounted.

Performing fsck_apfs -y -x /dev/rdisk6s1

Checking the container superblock.

Checking the checkpoint with transaction ID 65852.

Checking the space manager.

Checking the space manager free queue trees.

Checking the object map.

Checking volume /dev/rdisk6s1.

Checking the APFS volume superblock.

The volume Backups of iMac was formatted by newfs_apfs (1933.80.3) and last modified by apfs_kext (1934.141.2).

Checking the object map.

error: btn: oid (458612122), xid (65852), type (0x40000003), subtype (0xb), flags (0x4) level (1)

error: btn: invalid key order: minkey is less than index 0 (should be equal)

minkey : 04 04 00 00 00 00 00 00 f8 0f 00 00 00 00 00 00

index 0 key : e6 84 02 00 00 00 00 00 ef 0f 00 00 00 00 00 00

index 1 key : f8 84 02 00 00 00 00 00 ef 0f 00 00 00 00 00 00

Checking if the parent's minkey can be updated...

error: btn: oid (387465710), xid (65818), type (0x40000003), subtype (0xb), flags (0x4) level (2)

error: btn: unable to repair minkey

Object map is invalid.

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

Verifying allocated space.

The volume /dev/rdisk6s1 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…

Aug 10, 2023 1:05 AM in response to DuMartin

Pretty similar use-case here...

TM on Synology NAS, 6TB of backups have suddenly become unusable ! :(


at first hdiutil reported 4 entries when doing the attach (one of which, the 2nd, was APFS, and not HFS as often mentioned elsewhere), but now I'm getting immediate errors like "Device not configured" or "Resource temporarily unavailable" ???


Same story as you, fsck_apfs reported an invalid object map (1st aid doesn't work neither), and can't solve the problem.


Tried Disk Drill and Mountain, no luck.


Is there any commercial software that could help recover parts of a corrupted TM backup ??? (looked at prmosoft, but corrupt APFS TM partitions seems somehow 'out-of-range' for them, will ask their support...)



This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Time Machine sparsebundle mount failed in attempt to recover new Mac from backup

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.