10.5.7 breaks sparsebundles with large ba…
apple Verified ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
If you increased the band size of your Time Machine disk image or another sparsebundle, 10.5.7 won't mount it.
I had set the band size of my Time Machine image to 512MB bytes using hdiutil so I could back up a multi-terabyte drive without crashing the NAS from having too many band files. 10.5.7 thinks it's corrupted - "CBundleBackingStore::processBundle: invalid _bytesPerBand 536870912".
15 replies
Sign in or join Beachball Help to reply.
- 0
GNaschenweng ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I also have the same issue. Reports it as sparsebundle corrupted and can not mount. Had to delete it and lost all backups - nice one Apple.
- 0
David A. Gatwood ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Since you know what bands are and what a sparsebundle is and what a NAS is, I'm assuming you probably have an ADC account.
If so, this would be a good time to visit bugreport.apple.com and file a bug if you haven't already done so.
If not, there's no time like the present to sign up for a free online account. 😀
- 0
David A. Gatwood ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
For anybody else who runs into this, just rename the sparse bundle and it should create a new one. That way, your old backups aren't lost (though they won't do you much good for now).
You might also be able to recover from this problem by using hdiutil to clone the existing sparse bundle to a new sparse bundle with a different band size (like you had to do when you changed the band size in the first place). That said, I have no images to test with, so I can't say for sure if that will work.
- 0
Stefan Wild ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I have sent a message to Apple using the feedback form, as I am unable to get to the bug reporter, currently. I was running into the same problem at two sites, yesterday after updating two machines. The good news is that the images seem to stay intact as they are still mountable by 10.5.6 machines.
Regards,
Stefan - 0
Kevin McMurtrie ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
You can recover the old image. Revert /System/Library/PrivateFrameworks/DiskImages.framework/ from an older OS or install disc. You can then resize using hdiutil.
hdiutil convert -format UDSB -imagekey sparse-band-size=262144 -o new.sparsebundle old.sparsebundle
The docs now say that a maximum 128MB is supported (262144 * 512 = 128M). It's going to be another day or two before my conversion finishes so I hope it works and I hope the NAS doesn't crash with so many files in one directory.
- 0
Kevin McMurtrie ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I reported it today.
- 0
Abe ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
1. Resetting the SMC (didn't work by itself, but could be part of the solution).
2. Removing the sleepimage from /var/vm
3. Removing all com.apple related preferences (including the folders SystemConfiguration and DirectoryService) that changed since April 1 to a folder on the desktop.
4. Reboot"The above sequence of events seems to have solved the problem.
Thank you Esquared!!
- 0
Abe ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Sorry I must have accidently replied to the wrong thread.
- 0
Michael Newbery ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
THANKS!
I made sure I had a current backup using Time Machine before I updated---then found to my dismay that I could not access it. 😟
Recovering the old image is the hint I was hoping for.
- 0
ogattaz ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks a lot for your analysis.
After installing the update 10.5.7, what tool can be used to convert a sparsebundle who has 256 megabytes bands ?
Olivier
- 0
goi ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi,
just read that topic and found the same problem:
- I have a NAS usually using 2 GB sparsebands
- could not access the imageBUT the main question is, why did Apple limit the sparseband size?
regards
GOI
- 0
James O ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks for the workaround. Here's what I did to revert DiskImages.framework from Leopard DVD:
# Backup 10.5.7 DiskImages.framework
cd /System/Library/PrivateFrameworks
sudo mv DiskImages.framework/ DiskImages.framework-10.5.7
# Revert Leopard DVD DiskImages.framework
cd /Volumes/Mac OS X Install DVD/System/Library/PrivateFrameworks
sudo rsync -av DiskImages.framework /System/Library/PrivateFrameworks/# Convert Time Machine sparsebundle from 1GB bands to 128MB bands
mv MacBook Pro_macaddress.sparsebundle MacBook Pro_10.5.6.sparsebundle
hdiutil convert MacBook Pro_10.5.6.sparsebundle -format UDSB -tgtimagekey sparse-band-size=262144 -o MacBook Pro_macaddress.sparsebundle - 0
Michael Newbery ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
And just to follow up...
The conversion went fine as far as I can tell and TM is backing up to the converted image as I type. Thanks again.
- 0
ogattaz ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Bonjour,
I understand the proposed procedure to reinstall an old version of hdiutil.
But the DVD of Mac OS X that I bought with my iMac24 is a version 10.5.4, is not it too old?
It might not be a bad side effect?Regards
Olivier
- 0
James O ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
10.5.4 is not too old. I used DiskImages.framework from 10.5.0 DVD. Once you've converted your sparsebundle to have band size <= 128MB, you may go back to DiskImages.framework from 10.5.7.
Assuming you already moved DiskImages.framework to DiskImages.framework-10.5.7 and rsync'ed any DiskImages.framework from a Leopard DVD prior to 10.5.7 as detailed above.
cd /System/Library/PrivateFrameworks
-Move rsync'ed copy from Leopard DVD to backup directory name
sudo mv DiskImages.framework DiskImages.framework-10.5.4
-Move 10.5.7 copy back into place
sudo mv DiskImages.framework-10.5.7 DiskImages.framework
-Startup Time Machine againHopefully Apple will deliver a better fix as it would be nice to go back to using the sparsebundles with 512MB or 1GB band sizes.