Ubuntu 14.04.2 + Vmware 9.0 Extended disk partition

The Ubuntu 14.04.2 Desktop LTS version was installed under VMware 9.0, followed by a download of the Ubuntu kernel source tree and

Code compiled the kernel, after the completion of the Ubuntu system to install the source reading tools and some other auxiliary tools, the results found that the magnetic

Disk space is not enough, you can not reinstall the system to repeat these actions or copy a large amount of data it? It's a waste of time.

The Fortunately, VMware has made it easy for us.

Here, in fact, my ultimate goal is to reach the capacity to enlarge the disk partition. This is going to take two steps:

The first step is to expand the capacity of the disk that was created when you installed the Ubuntu system.

This can be done conveniently through VMware's own tools. The operation steps are as follows two figure:

650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M02/83/52/wKioL1dwxYXR3G9ZAAHH8XXP4I8644.jpg "title=" Vmware 9.0 harddisk Expand 01.jpg "alt=" Wkiol1dwxyxr3g9zaahh8xxp4i8644.jpg "/>

650) this.width=650; "src=" http://s2.51cto.com/wyfs02/M01/83/54/wKiom1dwxxWgFaYOAAHq7Po3Il4791.jpg "title=" Vmware 9.0 harddisk Expand 02.jpg "alt=" wkiom1dwxxwgfayoaahq7po3il4791.jpg "/> Fill in the amount of disk capacity that you eventually want, which is easy and quick to complete. More about VMware Disk operations

Details can be found in the documentation under the VMware Software help directory or the VMware official website documentation.

The second step is to use the tool gparted to expand the capacity of the disk partition.

Go to SourceForge to download the gparted ISO image and file. Configure the VMware CD/DVD (IDE) entry to load the ISO image

"Connect at Power on" (This is important), or even if the CD boot is set in the VMware BIOS,

It will not boot the system from the gparted image file, and everything behind it cannot be done naturally.

Next, configure the boot priority for the VMware BIOS and set the CDROM to the first priority. The shortcut key for Vmware 9.0 to enter the BIOS is F2,

I am crazy to press Ah, also failed to go in, this is my temporarily not able to understand the question , there is an online article that this is the reason for the start speed is too fast, but things

This is not the case, because at least 2 facts are in evidence to deny this judgment: first, I had to press the ESC key in VMware 9.0 to select the Startup setting

The ESC key, and the second, by modifying the. VMX configuration file extended start delay, still no

to succeed . I am here to access the VMware BIOS using the method of modifying the VMware configuration file . Open the guest OS (here I am

Ubuntu 14.04.2), locate the suffix. vmx file, open it with a text editor, and add a sentence on its last line :

Bios.forcesetuponce= "TRUE"

the above can be forced to boot once the BIOS, and then boot the system will no longer enter the BIOS. In fact, VMware does this by updating the. VMX configuration file to set the value of the configuration item to False. In addition, before you add the above statement to the. VMX Provisioning file , you need to first

The. vmx file does not have a Bios.forcesetuponce configuration entry, and if the configuration item already exists, modify its value directly to true on the line

The If this item is repeatedly configured, VMware will error when starting the guest OS.

The following is the configuration of the VMware BIOS, which configures CD-ROM drive as the preferred boot device.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M01/83/55/wKiom1dw0P_w_sWWAAK280gzzzE734.jpg "title=" Vmware BIOS Boot settings.jpg "alt=" Wkiom1dw0p_w_swwaak280gzzze734.jpg "/>

The next step is to go to GParted for the final steps: disk partitioning extension.

Before the root partition is extended:

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M02/83/54/wKioL1dw19_zGBNDAAcG2vOZEd8912.jpg "title=" 20160627_104307.jpg "alt=" Wkiol1dw19_zgbndaacg2vozed8912.jpg "/>

After the root partition is expanded, the extension is rebuilt, after the partition is swapped:

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M02/83/5A/wKiom1dw8SvSl8QZAAGUq1EQP7c572.jpg "title=" GParted Ext xxx.jpg "alt=" Wkiom1dw8svsl8qzaaguq1eqp7c572.jpg "/>

The above display/DEV/SDA1 partition has been extended to 33.92GiB. Before entering the screen above, there will be some targets for gparted

Configuration or selection, select all by default (that is, hit enter directly).

My original disk partition was very simple, with only one root partition in the primary partition, and one swap partition in the extended partition. Because the extension

The first two partitions are next to each other, and if you want to extend them, you need to remove the original extended partition (including the swap partition) and

Use the Resize/move menu to expand the primary partition to expand the size of the root partition, the remaining space is used to create a new extended partition, and re-establish the swap partition from the extended partition, and finally, with the Apply menu will actually be more rewritten back to the disk, complete and exit the GParted tool.

After completing the two steps above, reboot the system and the system is ready to work. But we still have some finishing touches to do, at the start

The interface will see a hint message such as:

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/83/54/wKioL1dw2G6xze8lAA94T1FSk3M042.jpg "title=" 20160627_112044.jpg "alt=" Wkiol1dw2g6xze8laa94t1fsk3m042.jpg "/> The above message is said to have uuid= 9F8F36CB-4A9F-4AAB-97BD-B27B86F86F00 disk drive not ready or not at all

Exist. This information is scary enough, but fortunately we can still get into the system. The UUID is applied to disk Management to avoid multiple disks or

Other disk drive loading sequence changes, each partition is identified with a unique UUID, which avoids the question

Problem.

Back to our question, what exactly is the cause of this informational message? Because it's related to disk drive loading, I'll look at

The configuration file/etc/fstab, which indicates that the UUID in the hint message corresponds to the configuration entry for the swap partition, and then uses sudo blkid to view the heavy

After adjusting the UUID of the partitioned swap, we found that the UUID of the swap partition has changed (this is necessary because the UUID is unique,

The rule of UUID generation is based on the combination of system time and so on. Here, the problem is clear, the message that the UUID corresponding to the old

Swap partition is no longer present, to resolve this problem, you need to change the UUID of the swap partition in/etc/fstab to the new UUID.

Also, since the Ubuntu system wakes from hibernation and uses the UUID of the swap partition, the configuration file needs to be modified

/etc/initramfs-tools/conf.d/resume, or the system will not resume correctly from hibernation and the system will restart. Update the UUID of the swap partition in the configuration file to the new swap partition UUID, and then run the command

sudo update-initramfs-u-K $ (UNAME-R)

Update the INITRD.IMG-XXX image file for the current kernel under directory/boot/, if you have more than one kernel image in the/boot directory, use

The-k parameter specifies the kernel version that you want to update, otherwise only updates the corresponding file for the default boot kernel version, instead of updating your current run

The corresponding file of the kernel initrd.img file.

At this point, after the modification is complete, the previous message will not appear again after rebooting the system.

At this point, the expansion of the disk partition has been done. When we can't stop, right? There is no such thing as a man. Except for the above mentioned

To the disk tool, Ubuntu there are some other tools that are worth learning, such as LSBLK will print some information about the disk block, Fdisk can view the disk mount, usage, disk partitions, etc., MKFS on the disk to establish a Linux file system, TUNE2FS modify the disk

File system Information. Other files related to disk information, such as/dev/disk/by-uuid,/proc/disk information files, etc.

And so on.

This article is from the "Jimokuangxiangqu" blog, make sure to keep this source http://4594296.blog.51cto.com/4584296/1793324

Ubuntu 14.04.2 + Vmware 9.0 Extended disk partition