similar to: Kickstart putting /boot on sda2 (anaconda partition enumeration)?

I'm using the kickstart file we developed for v5 on 6.2 in VM (kvm/qemu running on a CentOS 5.6), but it fails: Error partitioning. Could not allocate requested partitions: not enough free space on disks. There's nothing wrong with the disk. Both fdisk and parted works fine, I can view, partition and write a partition table and the disk is 10.5GB. However, looking through

I am testing some kickstarts on ESXi virtual machine with pair of 16GB disks. Partitioning is lvm over raid. If i am using "logvol --grow i get "ValueError: not enough free space in volume group" Only workaround i can find is to add --maxsize=XXX where XXX is at least 640MB less than available. (10 extents or 320Mb per created logical volume) Following snippet is failing with

Has anyone managed to create an encrypted disk partition with CentOS 8 kickstart? 1 reqpart --add-boot 2 part /boot --fstype ext3 --size=1024 --ondrive=sda 3 part pv.1 --size=1 --grow --ondrive=sda --encrypted --pashphrase="bla" 4 volgroup vol0 pv.100000 5 logvol / --vgname=vg_00 --name=lv_root --size=102400 --fstype=ext4 ... No matter what I specify in line 3, the installer bombs out.

I have 2 questions dealing with 2 different kickstart files. 1) my kickstart sections for RAID disk setup and kickstart reports it cannot find sda. Why is that. sda is there and works. clearpart --all --initlabel part raid.01 --asprimary --bytes-per-inode=4096 --fstype="raid" --onpart=sda1 --size=20000 part swap --asprimary --bytes-per-inode=4096 --fstype="swap"

Hello all, I have 3 Supermicro 1u servers, each with dual 250gb SATA drives. I have a server with CentOS 5 64bit setup for pxebooting and kickstart installs. I have a kickstart install file that doesn't specify the disks specifically. It works like a champ, and the operating system installs and completes. I have a kickstart install file that specifies the disk devices (sda,

Hi, I am struggling with kickstart. What I want to achieve is a reinstall, but some data partitions should survive the install, i.e. they should not be formatted. With a single disk this works, here is the relevant part from the kickstart file (I shortened the name of the volume group) ... zerombr clearpart --none --initlabel part /boot --fstype="xfs" --label=boot --onpart=vda1 part

Hello Guys, after hours of uncessfull create example before i forward special parition tests. part ignoe --onpart But Installation hang out for parition the harddisk. jump to another console partitions are ok ? Which line/lines is/are missing? Andy #version=DEVEL # System authorization information auth --enableshadow --passalgo=sha512 # Use CDROM installation media cdrom # Use graphical

I'm ill, i'm german ... the script is looks ok, copy from a slim installation of anaconda. Insert only the "pre part" and part /boot --onpart=/dev/sda1 part / --onpart=/dev/sda2 part swap --onpart=/dev/sda3 As i wrote: Jump over to another console and the partitions are there. Sincerely Andy Am Mittwoch, den 15.02.2017, 11:16 -0800 schrieb John R

On Sun, 21 Aug 2016 at 12:51 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/19/2016 11:35 PM, Phil Manuel wrote: > > The install fails under UEFi due to the fact the partitions are not > cleared, and it doesn?t have any space to continue. Is there an extra step > I need to do to remove the original partitions before the new layout will > work ? > > >

I'd like to automate the upgrade from CentOS 4.6 to 5.1 as much as possible. Since upgrades per se are not really recommended, I'm planning to do a kickstart installation. However, I want to leave one of the existing partitions (/scratch) untouched during the installation. Here is my current layout (LogVol00 is swap so not shown in the df output below): # df -hl

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 my notes from that work at the moment. My kickstart files for non-RAID UEFI boots use something like this:

I want to replace an existing 32bit with a 64bit installation (Centos 5). There's an existing LVM with lots of partitions. Most are used for Xen guests. The system itself uses only one of them plus a separate /boot partition that is not on LVM. What's the best course of action here? Should I do the reinstall with kickstart or better manually and reuse the existing filesystem? As I

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

Hello It is my first question here and I would like to thanks all of you to keep alive this stream and to give answers (I regulary read). Thanks for the good job. After installing CENTOS4.2 and "play with" I type the command swapon -s to verify everythings is ok but the command does nor return info as it should do. Is it something known ? Thanks Jean-Pierre Castello HP France mobile :

I'll be setting up a vSphere 4 environment hosting CentOS 5.4 on Netapp FAS and was curious how you guys are handling the automation of partition alignment within your linux guests. I'd like to use cobbler for dynamically creating kickstart scripts and wasn't sure if I could align my disk during install some how. Are there kickstart arguments to force the alignment on a 4k boundary?

Hi, This is a purpose patch to avoid the message: unknown filesystem label SWAP-sda2. Instead of validate the label with 'eq', use '=~' and /$label/i. https://bugzilla.redhat.com/show_bug.cgi?id=666578 Thanks Douglas -------------- next part -------------- A non-text attachment was scrubbed... Name: libguestfs-1.8.0-unknown-filesystem-label.diff Type: text/x-patch Size: 549

Hi, Is it safe to run tune2fs -c -1 -i 0 /dev/sda2 on mounted file system Basically, this is a command to disable fsck based on reboot count & last fsck time. -- Regards, Sherin

https://bugzilla.samba.org/show_bug.cgi?id=4310 Summary: Not correct transferring files Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Linux Status: NEW Severity: critical Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: peter.schubnell@gmx.de

I moved from acts_as_tree to acts_as_nested_set because I need the all_children method. I''ve seen an alternative way to add this method to acts_as_tree here: http://www.chuckvose.com/articles/2006/05/24/recursive-children But I''d prefer to use the more efficient way of acts_as_nested_set (and not to have to revert to my old code). Anyway, here''s my issue: if I

Hey, I solved my "The installation source given by device ['sdb2'] could not be found". Apparently ignoredisk is so strong it not only ignores the disks to be partitioned but also the disks holding the installation source... Now I ran into: ? In interactive step cleardiskssel, can't continue In anaconda.log I saw: ? step installtype does not exist ? step confirminstall