14
6
I have an encrypted volume on OSX Lion.
How do I make it larger?
14
6
I have an encrypted volume on OSX Lion.
How do I make it larger?
21
I'm assuming you have opened Disk Utility and you can see your disk image in the list
Make sure your .sparsebundle
/ .sparseimage
is unmounted / ejected
Select your disk image
Select Images
, then select Resize...
Enter your password
Resize that mofo
Double-click the disk image in the list to mount it
Choose your path
If you select the actual volume in the list (the volume in the image, not the image) and the available space matches the new resized size, then you are done
It doesn't match? Well... This means you have a disk image with a partition map. Read on.
Unmount / eject that sucker
Select the disk image (the .sparsebundle
/ .sparseimage
)
Select the Partition
tab
Drag the corner to enlarge partiton to the maximum size
Select apply
There is no step 9! Treat yourself to a large, toasty, disk image / chilled beverage
All it takes is a short Google search to discover the answer. Ray's Weblog has a solution:
A Sparse Bundle Image will increase in size automatically but will not shrink automatically. Before shrinking the sparse bundle, mount it and empty the trash to get rid of any deleted items from the image.
Unmount the image and follow the commands below.
To compact (image size stays the same):
hdiutil compact ~/Documents/filename.sparsebundle hdiutil compact -help (for a list of options)
To increase the image size (eg., 20G to 30G)
hdiutil resize -size 30g ~/Documents/filename.sparsebundle hdiutil resize -help (for a list of options)
Mount the image then do a Get Info on the Volume to see the new size.
"The selected image cannot be resized" at step 6 – Michael – 2018-04-12T14:39:15.117
1Ignored method is worked for me. With Disk Utility I got "The selected image cannot be resized" (not encrypted image*) – BoShurik – 2019-10-26T11:44:22.263
what about the volume in the bundle? from what i see, you can't resize that. – hvgotcodes – 2012-06-08T03:07:23.800
Are we talking about a
.sparsebundle
, or a.sparseimage
? – evan.bovie – 2012-06-08T03:24:09.623Could you repair the broken images in this post? Upload them to the SE imgr host (just use the image button on the editor toolbar). – Martijn Pieters – 2013-10-18T15:12:05.023
@MartijnPieters I'll do that, but TinyGrab must have made some server code change that broke embeds. – evan.bovie – 2013-10-22T15:59:25.003
@emb1995: ah, they are indeed still there; TinyGrab replaced the actual image with a webpage showing the image instead. I grabbed the images from those pages (skipping past the silly overlay) and uploaded them to the Stack imgr host instead. – Martijn Pieters – 2013-10-22T16:09:46.470
@MartijnPieters Thanks for the edit! It functioned the same way before, but they must have had some server-side code that detected when a request was from an embed or a straight-up browser request. I've already submitted a support ticket to TinyGrab. – evan.bovie – 2013-10-22T17:00:45.307
@emb1995: I copied the URL from the edit window, pasted it into a new tab, and that loads a HTML page with the image and some UI. That is not an embed request. – Martijn Pieters – 2013-10-22T17:02:00.797
@MartijnPieters: I meant the fact that a request for a URL within an
<img>
has request headers like:Accept:image/webp,*/*;q=0.8
. A normal request from an address bar / link click has request headers like:Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
. TinyGrab's server code could detect this and respond with either the image alone or their overlay. This would allow for easy embeds by using the short link instead of needing toinspect element
->copy URL
; they are using some JS/HTML voodoo to prevent image theft or whatever their motivations are. – evan.bovie – 2013-10-23T01:15:50.110