search for: autopartioning

On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/25/2016 11:35 PM, Phil Manuel wrote: >> >> The relevant kickstart section is:- >> >> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda >> bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 >> autopart

Hi all, This the latest output from anaconda.log:- 06:08:54,828 DEBUG anaconda: new disk order: [] 06:08:54,832 DEBUG anaconda: new disk order: [] 06:08:54,851 DEBUG anaconda: stage1 device cannot be of type disk 06:08:54,865 DEBUG anaconda: _is_valid_disklabel(sda1) returning True 06:08:54,867 DEBUG anaconda: _is_valid_size(sda1) returning True 06:08:54,867 DEBUG anaconda:

> On 28 Aug 2016, at 10:04 AM, Chris Murphy <lists at colorremedies.com> wrote: > > On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer > <gordon.messmer at gmail.com <mailto:gordon.messmer at gmail.com>> wrote: >> On 08/25/2016 11:35 PM, Phil Manuel wrote: >>> >>> The relevant kickstart section is:- >>> >>> part /boot/efi

I am trying to finish off a kickstart file for a computer lab on CentOS 6.5 machines. I don't want to have a separate /home as I'm going to add an entry in fstab for it to nfs mount /home from a server. Is there a way to have it autopart the rest of the file system without /home? Wanting to keep autopart for size since not all hard drives across the labs are the same. Matt

Gordon Messmer wrote: > On 08/25/2016 11:35 PM, Phil Manuel wrote: >> The relevant kickstart section is:- >> >> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda >> bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 >> autopart --type=lvm > > A couple of things to consider: > * The documentation for

On 08/25/2016 11:35 PM, Phil Manuel wrote: > The relevant kickstart section is:- > > part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda > bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 > autopart --type=lvm A couple of things to consider: * The documentation for "autopart" states that "The autopart command

Howdy, The default partitioning scheme appears to be: swap /boot / small amount of space /home remainder of space. Is there any way via kickstart to have it just create swap with the recommended size, /boot, and then just / with the remainder without manually specifying the names of the lvs/vgs etc? I figured there would be an autopart -atomic option but that doesn't seem to exist. Any

Hello Group, I am building a company application based on Centos 5.7 OS. The application was working earlier and creating right partitions both for hardware as well as VM. But since we introduced Centos 5.7 OS and start building application with 5.7 anaconda the hardware partitions are duplicate of VM partitions *while creating hardware partition my code looks like.* cat >

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

Hello, I?m using virt-install to build a guest system with CentOS. The system boots up, times out with dracut-initqueue timeout and drops me into an emergency shell. If I exit the shell the install continues and I get a working machine. Any ideas? virt-install \ -n TEST \ -r 8192 \ --os-type=linux \ --disk=/vm-images/test.img,device=disk,bus=virtio,size=100,format=raw \

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.

Hello, I need to automate installation of CentOS 7.0 using PXE and kickstart. My server is diskless, I'm installing CentOS on a 25GB LUN on a FC SAN with 4 paths. This LUN is the only one accessible by the server. Anaconda processes successfully the installation. But on reboot, I get stuck on a prompt after BIOS. I think I have an issue with storage configuration / bootloader

On Tue, 23 Aug 2016 at 02:18 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/21/2016 11:56 PM, Phil Manuel wrote: > > part /boot/efi --fstype="efi" --size=200 --ondisk=sda > > And I have tried the latter with location as mbr still fails > > What am I missing ? > > > I very vaguely remember struggling with this as well, but I can't find

Hi All, I am having problems with a kickstart install of CentOS 8 When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file. Then I see the following message "kickstart install Started cancel waiting for multipath siblings for nvme0n1" This is what I have in the kickstart file # Clear the Master Boot Record zerombr #

I got a Dell T110-II server on 2013-July-19. It has two 1Tbyte drives that the PERC H200 controls, RAID 1. I tried to install FreeBSD-9.1-RELEASE from a DVD from FreebsdMall. The autopart segfaulted, evidently because it could not find any disks. I think there is a PR about the segfaulting (bad bug, no messages). I worked around the problem by going to the loader prompt when the initial

On Mon, 5 Jul 2021 at 07:15, Hooton, Gerard <g.hooton at ucc.ie> wrote: > > Hi All, > I am having problems with a kickstart install of CentOS 8 > When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file. > Then I see the following message > "kickstart install Started cancel waiting for multipath

I was attempting one way to solve: https://bugzilla.redhat.com/show_bug.cgi?id=1400332 "RFE: virt-builder should support templates with encrypted filesystems" However this approach doesn't really work because templates containing encrypted partitions cannot be compressed, and therefore the guest template would be a multi-gigabyte download. I better approach will likely be to use

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

Jay Vyas <jayunit100@gmail.com> writes: > # The following is the partition information you requested > # Note that any partitions you deleted are not expressed > # here so unless you clear all partitions first, this is > # not guaranteed to work > # Uncommented by j > zerombr > clearpart --all > autopart > #ip=192.168.122.99 > network --bootproto=static

--- builder/website/fedora-ppc64.sh | 97 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 97 insertions(+) create mode 100755 builder/website/fedora-ppc64.sh diff --git a/builder/website/fedora-ppc64.sh b/builder/website/fedora-ppc64.sh new file mode 100755 index 0000000..1e22eba --- /dev/null +++ b/builder/website/fedora-ppc64.sh @@ -0,0 +1,97 @@ +#!/bin/bash - +# virt-builder +#