If you want to proceed with partitioning the disk, click Continue. If a dialog appears that indicates it will take a long time to resize the startup volume, read the information in the dialog, then do one of the following: Read the information in the Partition Device dialog, then click Partition. Type a name for the volume in the Name field.įor MS-DOS (FAT) and ExFAT volumes, the maximum length for the volume name is 11 characters.Ĭlick the Format pop-up menu, then choose a file system format.Įnter the size or drag the resize control to increase or decrease the size of the volume. Verify the configuration as described in Verifying the Current VM Configuration and then encrypt the boot device as described in Encrypting Linux System Devices.Note: If you click Add Volume instead, you can click the Add button to create an additional APFS volume in the container, or click Cancel to return to the Disk Utility window without making any changes to the storage device. # /opt/hcs/bin/aws-prepare-boot.sh /dev/xvda3 For example, if you add a new device named /dev/xvda3, you would enter: Log back into the VM as root and run the script aws-prepare-boot.sh that is installed as part of the HyTrust DataControl Policy Agent package. The operation has completed successfully. The new table will be used at the next reboot. Warning: The kernel is still using the old partition table. OK writing new GUID partition table (GPT) to /dev/xvda.
Create boot partition code#
Number Start (sector) End (sector) Size Code Nameįinal checks complete.
Create boot partition free#
Total free space is 460765 sectors (225.0 MiB) Partitions will be aligned on 2048-sector boundaries Hex code or GUID (L to show codes, Enter = 8300): 0700Ĭhanged type of partition to 'Microsoft basic data'ĭisk /dev/xvda: 211812352 sectors, 101.0 GiBĭisk identifier (GUID): F27664E9-0E9F-434A-9AB6-62C730E0F0DFįirst usable sector is 34, last usable sector is 211812318 P primary (1 primary, 0 extended, 3 free)Į extended (container for logical partitions)įirst sector (16777183-18874367, default 16777216): If the disk contains MBR partitions, use fdisk to create the boot partition and reboot the VM.ĭevice Boot Start End Sectors Size Id Type # gdisk -l /dev/xvdaįound valid GPT with protective MBR using GPT. For GPT partitions, the GPT field in the Partition Label Scan section will display "present". I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes # fdisk -l /dev/xvdaĬhanges will remain in memory only, until you decide to write them.īe careful before using the write command.ĭisk /dev/xvda: 9 GiB, 9663676416 bytes, 18874368 sectors For MBR partitions, the operating system will be shown in the Disklabel type field. If you do not know whether the VM uses MBR or GPT partitions, log into the VM as root and enter one of the following commands.įdisk -l /dev/xvda. You must create the boot partition before you reboot the VM. If you do, RedHat will auto-extend the root file system to fill the new disk space.
Important: Do not reboot the VM at this point. Log into the EC2 console, make sure the VM is powered on, then increase the size of the root volume by 1 GB. You cannot perform this procedure if the VM is powered off. Make sure the VM is powered on and is accessible. For these VMs you must create a boot partition on a new AWS volume. Important: The following method cannot be used for VMs running CentOS 6.x, RHEL 6.x, or Amazon Linux. For details, see Creating a Boot Partition on a New AWS Volume.
This usually results in faster encryption speeds due to the higher number of IOPS available.Īlternatively, if you do not want to create a boot partition on your existing root volume, you can create a new volume that will become the boot partition. Because the root volume will be larger than a new volume created exclusively as a boot volume, AWS will assign more IOPS (Input/Output Operations per Second) to the root volume than to a new volume. We recommend that you create a boot partition on the existing AWS root volume and then boot from the root volume. Creating a Boot Partition on the Existing AWS Root Volume
0 kommentar(er)
