Once you’ve got DiskWarrior open, it’s time to repair the disk! The attached volume is very likely called “Unknown Disk”, just select the one that’s most likely to be your attached sparsebundle. fsck_hfs just doesn’t cut it, but DiskWarrior will often always work its beautiful magic and get drives mounting for me again.
Okay, now that the sparsebundle has been attached to OS X, it’s time to open one of my favourite programs of all time: DiskWarrior. Here’s the output of when I mount my faulty.sparsebundle: /dev/disk3 Apple_partition_schemeĪttaching faulty.sparsebundle to OS X via Terminal. You’ll get a list of the BSD /dev node along with with the human-readable GUID of the partition (do man hdiutil to find out what I mean).
#Mac os x disk image no mountable file systems fix mac os
Here’s my final command to attach the sparsebundle to Mac OS X: hdiutil attach -nomount -noverify -ignorebadchecksums /path/to/faulty.sparsebundleĪfter a few seconds you’ll get prompted to enter the password to unlock the sparsebundle (if it’s encrypted) and then it’ll be attached to OS X. We’ll also add a few flags to tell hdiutil that we don’t want to verify or check the checksums of the image (which are probably causing it to fail mounting in the first place). Never fear, the command line is here! Using the hdiutil command in Terminal, we can attach the sparsebundle to the filesystem without actually mounting it.
Here are the steps I followed to mount the “corrupt” sparsebundle and recover all the data in the process.įirst up, as you would have tried, mounting the sparsebundle through DiskImageMounter.app doesn’t work. My initial thoughts are “Shittt… all the data is gone”, but I know that just because I get a generic error message, doesn’t mean I can’t fiddle around and get it working again. Even cloning the sparsebundle and trying on another computer resulted in the same problem. Whenever they logged in and tried to mount their home-foldered sparsebundle, the error “No mountable file systems” would appear. Recently I had an issue where a friends Legacy FileVault sparsebundle became corrupt when they upgraded to OS X Mavericks. Unable to attach "faulty.sparsebundle" (No mountable file systems)
0 kommentar(er)
