search for: noformat

.... 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 pv.00 --fstype="lvmpv" --onpart=vda2 --noformat volgroup v --noformat logvol / --fstype=xfs --name=wurzel --vgname=v --useexisting logvol /home --fstype=ext4 --name=home --vgname=v --noformat ... you see, / will be reformatted, /boot will be reformatted, but /home will not. Now a machine with md raid 1. I tried the following. ... #zero...

I was just wondering how (or indeed if) people use the %include directive in Kickstart configuration files when building systems via NFS. I've been trying to modularise our Kickstart files a little to make things more readable, having generic defaults and role specific stuff split out into separate configs. I've tried this configuration... [root at archive kickstart]# cat

...not much info... https://bugzilla.redhat.com/show_bug.cgi?id=565873 My kickstart: ? cmdline ? skipx ? install ? harddrive --partition=sdb2 --dir=/centos ? keyboard fr-pc ? lang en_US ? timezone? Europe/Paris ? reboot ? logging --level=info ? #ignoredisk --only-use=sda ? part /boot? --onpart sda1 --noformat ? part /????? --onpart sda2 --noformat ? part swap ? --onpart sda3 --noformat ? part /usr?? --onpart sda5 --noformat ? part /var?? --onpart sda6 --noformat ? part /home? --onpart sda7 --noformat ? bootloader --driveorder=sda,sdb --location=mbr ? ... Thx, JD

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 --name=lvol4 --noformat The purpose is reinstalling...

I am using a kickstart file for CentOS 7 raid / --device=md0 --fstype="xfs" --level=1 --useexisting raid /home --noformat --device=md1 --level=1 --useexisting It is erroring out on the --useexisting. The exact text is: RAID volume "0" specified with "--useexisting" does not exist. What did I do wrong? Jerry

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

...ashkernel=auto rhgb quiet" # 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 #clearpart --none #volgroup VolGroup00 --pesize=32768 --useexisting --noformat pv.253002 #logvol None --fstype=ext3 --name=LogVol00_data --vgname=VolGroup00 --useexisting --noformat #logvol /home --fstype=ext4 --name=LogVol00_home --vgname=VolGroup00 --useexisting #logvol / --fstype=ext4 --name=LogVol00_root --vgname=VolGroup00 --useexisting #logvol swap --name=LogVol00_sw...

...olGroup00/LogVol02' [35.72 GB] inherit ACTIVE '/dev/VolGroup00/LogVol00' [2.91 GB] inherit I've tried various alternatives of specifying the disk layout in the kickstart file, and here is my latest attempt: part /boot --fstype ext3 --onpart sda1 part pv.2 --noformat --onpart sda2 volgroup VolGroup00 --noformat --useexisting --pesize=32768 logvol swap --useexisting --fstype swap --name=LogVol00 -- vgname=VolGroup00 logvol / --useexisting --fstype ext3 --name=LogVol01 -- vgname=VolGroup00 But when I try to install CentOS 5.1 via kickstart, anacond...

I have a computer that dual boots between Windows and CentOS. Each has it's own hard drive. I suddenly have a problem with Windows, and may need to reinstall. I need it for applications like After Effects, Premiere, and other things that I am currently in the middle of a project with. It seems the system has become usnstable, it's preventing me from continuing to work, and I

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

...Hit send to quick. Jerry On Wed, Aug 29, 2018 at 3:52 PM Jerry Geis <jerry.geis at gmail.com> wrote: > I am using a kickstart file for CentOS 7 > > raid / --device=md0 --fstype="xfs" > --level=1 --useexisting > raid /home --noformat --device=md1 > --level=1 --useexisting > > It is erroring out on the --useexisting. > > The exact text is: > RAID volume "0" specified with "--useexisting" does not exist. > > What did I do wrong? > > Jerry > >

..., /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 --size 1058 --noformat part /boot --fstype ext3 --size 100 --ondisk=hda part swap --start=4603 --end=4864 part pv.6 --size=0 --grow --ondisk=hda volgroup VolGroup00 --pesize=32768 pv.6 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=10240 logvol /home --fstype ext3 --name=home --vgname=VolGroup00 --siz...

...ow do I prevent the partition label on the root filesystem from being changed? I'm building a system with multiple flavors of CentOS in separate partitions and I would really like to have the partition labels be something meaningful. So far, the only idea I've come up with is to use the --noformat flag on the partition definintion in the kick start file and then format it in the %pre section.

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?

I am trying to install CentOS 4.6 to a pair of 750GB hard drives. I can successfully install to either of the drives as a single drive, but when I try to use both drives and mirror the partitions, I start having problems. Anaconda crashes as it is trying to format the drives. This is what I'm trying to create: /dev/md0: 200MB, /boot /dev/md1: 2GB, swap /dev/md2: rest of the

I am an experienced MS administrator of W2003 servers & Exchange systems. I have 5+ years UNIX mid-level experience but not in centOS. Grounded in SCO UNIX (the real SCO UNIX). We want to use CentOS on a recently grave yarded Dell poweredge 400SC server. This is a P4 3.0 Ghz, w/4GB memory, 2 SATA 250 GB disks. We want to use this server w/CentOS5, to provide file and print resources to 100