My computer runs Windows 8. I have a VM Virtual Box Instance of Mac OSX. I made the hard disk 20GB at first, but now I need it to be bigger. I made a back up of the hard disk and then proceeded to resize the original hard disk to 30GB. Now I am trying to actually be able to use the extra 10GB I have added.
First I tried to do this through Disk Utility on the actual VM to no avail. When I tried to resize the partition to use the entire available space, and then clicked "apply" it simply did nothing. When I tried to resize the partition to use any less than the entire available space, it gave me the error MediaKit reports partition (map) too small.
Now I have loaded a GParted ISO onto the VM, and have been trying to use that to resize the hard disk but this is also to no avail. Here is an image of the situation with GParted:
When I try to resize "Yosemite Erase" (the hard disk) it says that the minimum and maximum space that it can take up are the same, 19.20GB, which is what it currently is. I tried moving the "Recovery HD" over to the other side of the unallocated space. But I still was unable to resize "Yosemite Erase" for the same reason; it just doesn't let me.
The warning "YosemiteErase" has says Unable to read the contents of this file system! Because of this some operations may be unavailable. The cause might be a missing software package. The following list of software packages is required for hfs+ file support: hfsprogs.
Does anyone know what I should do?
EDIT:
Nevermind. It turns out that GParted does a "fix" of the hard disk before the GUI boots which I originally had disregarded. However it turns out that when I try to extend the size of the hard disk in Disk Utility, it now works perfectly because of this fix.
I ran into this issue trying to install Kali Linux on a Mac.
I installed "hfsprogs" as the error suggested:
sudo apt-get install hfsprogs
...but the error in Gparted never went away and it never showed the "used" amount on the hfs+ share, despite Gparted showing that the plugin was now installed.
Gparted also tried to "fix" it for me as well, that seemed to have no effect.
I ended up booting into OSX and using Disk Utility to resize the HFS+ partition.
I suspect that the hfsprogs package allows some info about HFS+ partitions in Gparted, but doesn't enable resizing partitions.
Related
I tried to update my mojave to catalina in order to update Xcode... But impossible I have 27Gb Free space but all time this error:
an error occurred while installing the selected updates
And after each error I have 8Gb in less, so if I continue I while arrive to not have free space, I don't know how to delete this fail load on my system storage.
I found that 8Gb are add in private/var/folders (never touch this folders) just reboot in safe mode, this will erase temporary file...
As found here:
A clean install uses up around 20 GB of storage space. In addition,
you need to allow for space for your user data, applications, and
future updates. As if that weren’t enough, you should keep at least 10
to15 percent of the startup drive free to ensure adequate performance.
I normally suggest a good deal more free space than that, but here
we’re just talking about a minimum to ensure you can install and use
macOS Catalina.
So the solution may be freeing up to 30 GB of space, just to be sure.
You can try this utility to better identify some files to delete.
I am trying to install Linux in a computer that has Windows 7. The first step was shrinking the disk size but Windows did not allow any reduction. Thus I followed a number of steps to disable "unmovable" files
I disabled the Page File
I disabled hibernation
I disabled System Protection
After that nothing seemed to have changed so I checked the disk fragmentation and it was 11% fragmented. I have since then run at least 4 defrags and I have also defragged the free space using Defraggler.
As of now the disk looks like this
Right now, Windows refuses to shrink the partition by any amount (I imagine that the files at the end of the disk are the troublesome ones).
Coming from an Linux background I am unsure what else needs to be done in order to shrink the partition.
Are you using Windows disk management tool to do the shrink? Here's a link for that method.
https://www.howtogeek.com/howto/windows-vista/resize-a-partition-for-free-in-windows-vista/
Also make sure the recycle bin on that drive is empty.
I finally figured it out.
The easiest way is just to use a Live USB with GParted on it since that will allow you to move Windows protected files around (the windows OS is not loaded on the live distro).
If just defragmenting is concerned one can use Hiren's Boot CD and the included Defraggler for the same purpose.
I had the same problem on Windows 10. Turns out it was antivirus software that was running on the machine that prevented defragmentation happen properly. I actually had to temporarily uninstall antivirus. After that, the Disk Management tool was able to correctly shrink the volume.
I have a large (100gb+) database that I'm trying to run with the official postgres image.
I can't store the data in a docker volume because the ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 file in Docker for Mac has a size limitation of about 60gb.
I'm hesitant to mount a host directory as a volume because file access in mounted host directory volumes is much slower than regular volumes.
These are some useful links that go into more detail on these issues:
This discusses the size limitation of the Docker.qcow2 file
This also discusses the size limitation of the Docker.qcow2 file
This discusses the mounted host directory volume speed issue
This gives a nice description of how to replace the Docker.qcow2 file with a file that can grow larger
This discusses how the Docker.qcow2 file doesn't shrink as its contents are removed (this isn't directly related, but can further complicate the problem)
Do you all just eat the speed loss and mount a host directory? Do you manually create a qcow2 file that can grow larger with qemu (if you do this, do you need to maintain this file between upgrades)? Do you do something else to handle this issue?
The following script delete and re-create a new shrinked Docker.qcow2 file preserving the images passed as arguments.
https://blog.mrtrustor.net/post/clean-docker-for-mac/
Hope this helps.
For a situation like this, I would definitely recommend creating a qcow image that can grow larger.
It is a relatively straightforward process, and you get the performance benefits that are generally quite necessary when running a large database.
Docker for Mac 18.06 switches from the qcow2 file format to the raw file format, which improves speed and disk usage. The core issue still persists, in that Docker has a limited amount of space that it can use for all of its data. However, you can now set what that limit is within Preferences -> Disk -> Disk image size.
Docker for Mac version 17.12 was the first version to introduce the raw file format, but there were some bugs in the initial release that caused them to remove it as a feature temporarily. You can search that page for 'raw' to look back through the feature's history.
There's a great note here about how Docker for Mac reports its disk usage...
This will display the logical size:
ls -alh ~/Library/Containers/com.docker.docker/Data/vms/0/Docker.raw
While this will display the physical size:
du -h ~/Library/Containers/com.docker.docker/Data/vms/0/Docker.raw
I tried to resize my .vmdk as reported here.
I had some trible but I managed to clone my firsd disk.
Now I try to resize my new disk but I get again the following error:
VBoxManage.exe: error: Resize hard disk operation for this format is not implemented yet!
I have no idea how to fix this. Any suggestion?
Update
I colend my .vmdh hdd into a new .vi hdd.
I tried then to increase the size using
modifyhd NAME.vdi --resize 256000
Immidiatelly I got a completed work, no errors. I restart my windows session. But the size of the new .vdi is still the same. Any suggestion how to fix this?
Update 2
Ok now I used GParted iso to resize my partition as explained here.
In fact when I hopen the Virtual Machine I see tha the size is 250 G
So I started to install heavy things on my Linux account, but now Linux tells me that I have no space anymore, even though the used space is around 39 G.
Where is my mistake?
I tried to install windows7 from USB according to the instructions of following page.
http://www.intowindows.com/how-to-install-windows-7vista-from-usb-drive-detailed-100-working-guide/
But at the location where i select the partition it says me something like "device not found."(Cant give the exact machine as i came to somewhere else to search the internet, coz my machine's not working).
How can i overcome this?? I've formatted the whole disk. Got nothing to do now!!!
You have formatted the whole hard disk. That is the problem. It's a windows 7 specific problem. I'll describe the case in brief. the setup detects your pen drive as a part of the hard disk(at least something like this). Therefore you can overcome the issue by not letting this to happen.
Which means, you can make the pen drive read only (or make don't allow setup to use pen drives storage). One possible solution will be fill the empty space of the pen drive with bulky data. then there will be no space for the setup program to use in the pen.
Or else you can remove pen drive at the time where the setup is trying to access it (for the above mentioned purpose). How to know the exact time??? well it's trial and error. I myself have done it and it worked. It will require some Patience.
Of course, you can install some other os and then try install win7 after that.
Hope that helps..!!