One last attempt at saving corrupted Time Machine sparsebundle

Following or sort of following instructions here, which I found a link to from here. Well, actually didn’t click the source link, until I couldn’t figure out how to link to the post on the second link, the comment with those instructions.

My sparsebundle isn’t using HFS. I’m using Disk Utility first aid again.

I also mounted the network share with Finder. I actually made a new Time Machine backup, and deleted the corrupted file, but that drive is backed up, so I just copied the corrupted files to the Raspberry Pi, so my computer can be rebooted or crash or anything, and it won’t stop the Mac mini from trying to repair it.

I didn’t run one of the first commands the first time I tried fixing it, the chflags command.

Also, that network share, doesn’t have the Time Machine flags in Samba. You have to make it’s own share folder if you want that. I just want to repair the image. I can copy it elsewhere if I want to use it.

How do I copy the new backups to the old backup file?

Don’t waste time with disk recovery software, at least Disk Drill or whatever, it found no files. If you mount it, there appears to be data, yet Disk Drill can’t find anything. Didn’t try restoring anything.

I was originally trying some other recovery software, but decided I didn’t want a yearly program, no idea if it auto renews, or you just get updates for a year. You can pay $29 extra for Disk Drill, and get updates forever. Still a lot of money. But I think it can recover data from EXT4. So it could be useful in the future, if multiple drives crap out at the same time.

Finder won’t let you copy anything from the sparsebundle. As that is what I was going to do, copy to a new non corrupt image. Can’t delete the corrupt stuff either. Linux might be able to read it, but not write. Yes, I want my old backups. Somebody should make a Linux program to recover it, I’ll pay for it, if it’s cheaper then disk recovery software.

I wonder if this lets you work with sparsebundle files. Or maybe you use the other thing, but instead of read only driver, use that. Too bad, my kernel is too new. So I won’t buy it. Yes, such a program, would also need to work with the latest Linux kernel, and continue as I update my computer. My kernel is 6.1.8-1-default. Using VMs is too much work.

Too bad macOS can’t fix stuff it creates.

One data recovery program is I think $90 per month. You can probably cancel it, but that’s still a rip off. Doesn’t say what the lifetime version is. Do you pay that every life? Every year? Every 100 years?

I needed to update the Mac mini, that’s why I created a new Time Machine backup. And it’s funny how somebody thinks USB is more reliable for Time Machine, then Ethernet. Servers use Ethernet, and have no issues usually. So USB is less reliable in my opinion. Now Ethernet + USB, that’s as unreliable as USB directly. But probably not less reliable.

Couldn’t save it, deleted it from Raspberry Pi, well not the Pi’s backup drive, if it’s backing up with rsync, it might have the “–delete” option. But rsync backups is a bad idea, if the source drive is failing and corrupted data is being replaced. So a backup of the Time Machine image, wouldn’t have saved it, unless I noticed soon enough.

I could change to a better backup method but I’m lazy. Well, wouldn’t change from Time Machine on the Mac, for the Linux computer. Perhaps I will for my pics folder. Problem is, it keeps multiple days, which may require more space.

Perhaps check dmesg for USB errors on each drive before running rsync, so the backup isn’t possibly destroyed.