Displaying 20 results from an estimated 2000 matches similar to: "Discrepancies in Anaconda-ks.cfg after kickstart"
2013 Mar 09
1
kickstart %pre vda/sda troubles
hi,
The problem: for kvm/qemu disks are /dev/vdx devices when using the
virtio driver. For vmware, drives are /dev/sdx devices. For hp
servers, /dev/ccisss/whatever (sorry, no proliant with an array
controller handy to check it).
in order to just have one kickstart script to maintain I am trying to
use the %pre section but getting a bit stuck. This is what I have:
%pre
if [ -b /dev/sda ]
then
2008 Jul 04
1
Anaconda ignores "cmdline" directive
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
2007 Oct 13
1
Problem creating volgroups with kickstart installations (on xen)
I'm testing doing kickstart installations on Xen VMs. This is
the first time I'm trying out kickstart at all, so I rather think I'm
doing something wrong in the kickstart configuration than it is
a Xen issue.
I use a modified kickstart file from an earlier manual installation
with a very basic filesystem setup. It fails with
"SystemError: vgcreate failed for VolGroup00".
2012 Apr 13
1
harddisk partition not created right with centos 5.7
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 >
2006 Mar 22
0
partition problems in kickstart
I fought with this for a day, and now am crying for help....
The goal is 5 partitions: boot, notebook suspend, / , /home. and
swap. So I have to use LVM.
Here are my commands:
#System bootloader configuration
bootloader --location=mbr
#Clear the Master Boot Record
zerombr yes
#Partition clearing information
clearpart --all --initlabel --drives=hda
#Disk partitioning information
part pv.1
2015 Nov 19
2
CentOS7 kickstart failed ( no such option: --bytes-per-inode)
Dear All,
I'm trying to create a kickstart installer.
I specified an option --byes-per-inode to 'logvol' command, but I got a message "No such option: --bytes-per-inode" during installation.
Does anybody know a solution?
The following is the lines for disk partitioning definition specified in my kickstart file.
-------------------------
##
## Disk partitioning information
2019 May 08
5
kickstart compat C7 -> C8
Hi all,
I still use the following kickstart partition scheme for C7 installations (via virt-install):
Briefly, fixed size for /root and /boot, and the rest is filled up for /srv.
The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work with Fedora29 (EL8).
I get a "device is too small for new format" error. Any hints?
part /RESCUE --fstype="ext4"
2014 Jul 22
0
CentOS7+kickstart+thinpool = error/exception
Hi,
I'm trying to create a kickstart file that uses a thinly provisioned lvm
volume as root but I've run into trouble. I installed a System manually
using this option and this is the anaconda file produced:
part /boot --fstype="xfs" --ondisk=vda --size=500
part pv.10 --fstype="lvmpv" --ondisk=vda --size=7691
volgroup centos_centos7 --pesize=4096 pv.10
logvol
2012 Apr 12
1
CentOS 6.2 anaconda bug?
I have a kickstart file with the following partitioning directives:
part /boot --fstype ext3 --onpart=sda1
part pv.100000 --onpart=sda2 --noformat
volgroup vol0 pv.100000 --noformat
logvol / --vgname=vol0 --name=lvol1 --useexisting --fstype=ext4
logvol /tmp --vgname=vol0 --name=lvol2 --useexisting --fstype=ext4
logvol swap --vgname=vol0 --name=lvol3 --useexisting
logvol /data --vgname=vol0
2019 May 08
0
kickstart compat C7 -> C8
Leon Fauster via CentOS wrote:
> Hi all,
>
>
> I still use the following kickstart partition scheme for C7 installations
> (via virt-install):
> Briefly, fixed size for /root and /boot, and the rest is filled up for
> /srv.
>
> The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work
> with Fedora29 (EL8). I get a "device is too small for new
2019 May 08
0
kickstart compat C7 -> C8
On 2019-05-08 12:28, Stephen John Smoogen wrote:
> On Wed, 8 May 2019 at 13:24, mark <m.roth at 5-cent.us> wrote:
>
>> Leon Fauster via CentOS wrote:
>>> Hi all,
>>>
>>>
>>> I still use the following kickstart partition scheme for C7 installations
>>> (via virt-install):
>>> Briefly, fixed size for /root and /boot, and the
2019 May 08
2
kickstart compat C7 -> C8
On Wed, 8 May 2019 at 13:24, mark <m.roth at 5-cent.us> wrote:
> Leon Fauster via CentOS wrote:
> > Hi all,
> >
> >
> > I still use the following kickstart partition scheme for C7 installations
> > (via virt-install):
> > Briefly, fixed size for /root and /boot, and the rest is filled up for
> > /srv.
> >
> > The same kickstart
2007 Dec 18
1
LVM + kickstart -> dom0 && domUs
centos-virt,
I'm trying to create/install domU guests all in "one" step, following
Daniel's wiki page (I've found these pages really helpful, BTW):
http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU
I have a few questions about this process:
(1) How would it be modified (w/respect to defining the disk in the
domain configuration file) to use a disk layout where dom0
2019 May 08
2
kickstart compat C7 -> C8
> Am 08.05.2019 um 19:20 schrieb mark <m.roth at 5-cent.us>:
>
> Leon Fauster via CentOS wrote:
>> Hi all,
>>
>>
>> I still use the following kickstart partition scheme for C7 installations
>> (via virt-install):
>> Briefly, fixed size for /root and /boot, and the rest is filled up for
>> /srv.
>>
>> The same kickstart
2008 Mar 03
3
LVM and kickstarts ?
Hey,
Can anyone tell me why option 1 works and option 2 fails ? I know I
need swap and such, however in trouble shooting this issue I trimmed
down my config.
It fails on trying to format my logical volume, because the mount point
does not exist (/dev/volgroup/logvol)
It seems that with option 2, the partitions are created and LVM is setup
correctly. However the volgroup / logvolume was not
2007 May 29
1
Re: centos and http
>> Dave wrote:
>>> Hi,
>>>
>>> Thanks for your reply. Yah i do have apache running, your idea
>>> certainly would make things easier. How did you set up the http area?
>>> And where in it do you put the kickstart? I'd like this area to be
>>> accessible to my local network only, internet users shouldn't be able
>>>
2011 Apr 04
1
lvm and kickstart issues deploying CentOS5.5
Hi.
I'm currently trying to configure a kickstart script to do auto installs. We split up the partitions so that we have control on the mount security like setting no execute on the tmp portions etc .
I keep hitting the same error :
"Could not stat /dev/VolGroup00/LogVol_root --- No Such file or directory
The device apparently does not exist; did you specify is correctly "
Even
2014 Jul 16
1
anaconda, kickstart, lvm over raid, logvol --grow, centos7 mystery
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
2006 Apr 22
2
kickstart
Hello,
I've been trying to kickstart a install centos from a USB memory stick.
Everything with that is working fine, but I seem to be having a problem with
the ks.cfg file.
When I boot the install media from the usb drive, the the boot prompt I type
linux ks=hd:/dev/uba1/ks.cfg
Then I peek at the logs and it even says
* getting kickstart file
* getting kickstart file from harddrive
*
2012 Oct 15
2
ext3 partition on LVM lost all data
Hello Gentlemen,
I would like to ask a question about an issue I have with the Centos 6.3
installation.
I have installed a Centos 6.3 on a server we used before with 5.4 on
Friday. I have created a KS file to let me connect to the server via VNC
and have all repos and packages preconfigured. I only needed to
partition the hard drive using VNC.
During the partition process I selected which