What we have done is expanded the allowable space to be used, but we didn’t actually adjust the partition size. We start our Ubuntu Server to verify that our new drive is now 30GB of storage, however what we see is the Virtual Environment believes we have 30GB (32.2 specifically) but our /dev/sda1 partition is still at 19GBs?! $ sudo fdisk -lĭisk /dev/sda: 32.2 GB, 32212254720 bytesĢ55 heads, 63 sectors/track, 3916 cylinders, total 62914560 sectors If we could just simply move our slider (or type in a new value) for our desired HD space that would actually increase our storage space, that would be perfect! Result VMware Fusion VHD setting after adjusting from 20GB to 30GB. Now it would be really nice if VMware Fusion’s tools to increase the VHD worked as expected. I/O size (minimum/optimal ): 512 bytes / 512 bytes Sector size (logical/physical ): 512 bytes / 512 bytes You can see the VHD settings are for 20GB (really 21.5, guessing there is a rounding error somewhere), and that our primary partition is /dev/sda1 with 19GB drive. Here is my test VM as it stands right now. We can see that we have a 20GB VHD by several ways: Increase size? I don’t think that word means what you think it meansįirst let’s get a baseline of a default “Easy Install” of Ubuntu Server. Google searching throws a lot of ideas, therefore I’m providing what I’ve learned from a couple of hours of research. I need to increase the size of two different VHDs, however if you setup your Ubuntu Server via “Easy Install Mode” enlarging the VHD is not that strait forward.ĭoing a quick search to see what VMware has to say about this issue returns less than helpful information for Ubuntu Servers by stating man fdisk. There are many reasons for this, but I ran into this issue twice in one weekended because I enabled a JDS as a Distribution Point (thus MySQL was eating needing a lot of space) and wanting to test multiple NetBoot NBI sources (because 10.10.2 seems to be causing imaging troubles). Let us pretend that you have an Ubuntu Server which has been running for several years and it has been doing it’s assigned task(s) nicely, until one day you make a change to your methodology/assumptions/workflow/tasks therefore the allocated Virtual Drive (VHD) size is no longer sufficient.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |