similar to: Force anaconda to use GPT labels on all drives?

Hi messmer, seems that anaconda supports partitioned RAID devices. Disk selection see one mdraid device and permits to create partition on it. Il 13/03/2016 01:04, Gordon Messmer ha scritto: > On 03/12/2016 08:22 AM, Alessandro Baggi wrote: >> From several how-to concerning raid1 installation, I must put each >> partition on a different md devices. > > Not necessarily. You

Hi Giuseppe... ! Thanks for the hint. ill try it. So from the docs, I'm seeing this: "As of Fedora 16 there must be a biosboot partition for the bootloader to be installed successfully onto a disk that contains a GPT/GUID partition table, which includes disks initialized by anaconda. This partition may be created with the kickstart option part biosboot --fstype=biosboot --size=1.

Does anyone know how anaconda partitioning enumerates disk partitions when specified in kickstart? I quickly browsed through the anaconda installer source on github but didn't see the relevant bits. I'm using the centOS 6.10 anaconda installer. Somehow I am ending up with my swap partition on sda1, /boot on sda2, and root on sda3. for $REASONS I want /boot to be the partition #1 (sda1)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone have any thoughts on why anaconda might be prompting me to reinitialize the disk during the kickstart of a Centos6.4 install on hyperV when a) the kickstart file contains "zerombr" as referred to in the installation guide[1] b) installation proceeds with no prompt on KVM hypervisors and succeeds? I have read the release notes[2]/tech

I'm having what appears at first glance to be a kickstart+anaconda issue on CentOS 7.4. As near as I can tell in the program.log in the anaconda environment, the partitioning instructions downloaded with the kickstart from cobbler appear to simply not be applied. Then /mnt/sysimage is not mounted, the logs are not copied to /mnt/sysimage/root and the installation stalls due to the anamon

Hi list, I'm new with UEFI and GPT. For several years I've used MBR partition table. I've installed my system on software raid1 (mdadm) using md0(sda1,sdb1) for swap, md1(sda2, sdb2) for /, md2 (sda3,sdb3) for /home. From several how-to concerning raid1 installation, I must put each partition on a different md devices. I've asked times ago if it's more correct create the

Hello, Our environment: CentOS 5.2 (updated over time with "yum update", current "yum update" lists about 7 packages out of date), x86_64. Running Xen, building Xen DomU's with kickstart. We are trying to debug the %post part of the kickstart process for DomU and are hitting difficulties in accessing the output. For a start, the "cmdline" directive in the

The immediate issue is with Fedora/ppc64 and /ppc64le which currently use extended partitions, breaking the virt-builder ‘--size’ parameter, eg: $ virt-builder --arch ppc64le fedora-26 --size 20G ... [ 21.6] Resizing (using virt-resize) to expand the disk to 20.0G virt-resize: error: /dev/sda5: partition not found in the source disk image (this error came from '--expand' option

If you use a kickstart file to build unattended servers (eg virt-install) then new disks or virtual volumes will cause problems unless you have "zerombr true" in the kickstart file eg zerombr yes clearpart --all --initlabel part /boot --fstype=ext4 --asprimary --size=100 part swap --asprimary --size=512 part / --fstype=ext4 --asprimary --grow --size=1 (CentOS 6.2 didn't

Greetings. There must be some minor changes to anaconda. I'm getting the error: "Cannot open repomd.xml file...." the file seems to be located in the repodata directory... I'm using the following .cf taken directly from the CentOS 4.4 install : install url --url ftp://centos.westmancom.com/5.0/os/i386/ #cdrom lang en_US.UTF-8 langsupport --default=en_US.UTF-8 en_US.UTF-8

I recently tried to install several distros on a usb stick, with the peculiarity of creating in it a GPT label rather than the usual dos label. Installed Grub2 using the parted bios_grub flag on a partition, I proceeded to copy several distros on the remaining partitions. Grub2 worked fine, chainloading syslinux on each of the partitions. Or rather it worked all fine until I reached the fifth

> It doesn't specifically.? Anaconda will create two EFI boot entries, > each referring to one of the mirror components: > > # efibootmgr -v > BootCurrent: 0001 > Timeout: 1 seconds > BootOrder: 0001,0000 > Boot0000* CentOS Linux > HD(1,GPT,534debcc-f3d6-417a-b5d4-10b4ba5c1f7d,0x800,0x5f000)/File(\EFI\CENTOS\SHIM.EFI) > Boot0001* CentOS Linux >

Hi, I'm currently teaching Linux system administration to a class at the local "chambre de commerce". The course is based mainly on a minimal CentOS 7 installation. Usually my preferred tool for handling manual GPT partitioning is gdisk, which is not installed on a minimal install. I just gave the good old fdisk a spin, which enables GPT partition table creation with the

Hello everyone, I'm having an issue installing AsteriskNOW 2.0.2 on a Dell server. When I go to intall it, with BIOS legacy mode for partition tables, I get as far as setting pu the partition tables. However, the installer then informs me that GPT partition table schemes are required and that I have to resolve the issue. I changed from BIOS/MBR/Legacy mode to GPT/UEFI boot mode but then

Hi Giuseppe and thanks for the response............ Heres some more info: Here is my kickstart... maybe the "--bootloader" argument is wrong in some way? # Put this in pastebin or some other public url # Kickstart file automatically generated by anaconda. #version=DEVEL install cdrom lang en_US.UTF-8 keyboard us network --onboot yes --device eth0 --bootproto dhcp --noipv6 timezone

On 03/12/2016 08:22 AM, Alessandro Baggi wrote: > From several how-to concerning raid1 installation, I must put each > partition on a different md devices. Not necessarily. You could put LVM on top of the RAID device, and create logical volumes. > I've asked times ago if it's more correct create the md device, > partitioning it and create fs on each partition created on

On Thu, Feb 15, 2018 at 05:31:42PM -0500, Stephen John Smoogen wrote: > On 15 February 2018 at 17:19, Yves Bellefeuille <yan at storm.ca> wrote: > > I have a UEFI system, but I want to install CentOS on a MBR (not GPT) > > hard disk. > > > > The installation program keeps telling me that I must create an "EFI > > system partition on a GPT disk mounted at

Ok, did some experiments. Here's the scoop. You will need a live USB key of CentOS 6 with a persistence layer (overlay) and the EPEL gdisk package installed to make this thing boot. On a system with Chameleon already installed, boot the CentOS 6 install media. Installing Chameleon without OSX is an adventure that I've not done, so a 'testing' OSX install (10.6) with the

Hello! I'm posting some experiences with GRUB0/1 + sys/extlinux + MBR/GPT in a pendrive with 15 partitions. This could be helpful improving sys/extlinux. I did make a bootable pendrive with 14 distros using a GPT partition table and a tricky solution to let sys/extlinux boot from every partition chainloaded from GRUB (GRUB0 or GRUB1). Having a MBR schema, sys/extlinux can't be

If there is a GPT partition layout, then what should be read and restored for each partition is the GPT type and not the MBR ID. Related to RHBZ#1060404. --- resize/resize.ml | 46 +++++++++++++++++++++++++++++++++++----------- 1 file changed, 35 insertions(+), 11 deletions(-) diff --git a/resize/resize.ml b/resize/resize.ml index 8683df7..a2670e5 100644 --- a/resize/resize.ml +++