similar to: CentOS 6.2 anaconda bug?

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 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

I'm trying to setup a LVM mirror on 2 iSCS targets, but can't. I have added both /dev/sda & /dev/sdb to the LVM-RAID PV, and both have 500GB space. [root at HP-DL360 by-path]# pvscan PV /dev/cciss/c0d0p2 VG LVM lvm2 [136.59 GB / 2.69 GB free] PV /dev/sda VG LVM-RAID lvm2 [500.00 GB / 490.00 GB free] PV /dev/sdb VG LVM-RAID lvm2 [502.70 GB /

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

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 have an smbd process that is using alot of cpu on HP-UX 11.11 using Samba 2.2.3a. It looks like the application on the client side is trying to open and close a ton of files, many of which do not exist. When I do a trace on the smbd process, I see repeated calls to lstat64 to what looks like all of the device files on my unix server. Here is a little bit of the trace. It goes through all of the

Sorry - I did not include that I am actually "updating" a system from C6 to C7 and it has an existing RAID /dev/md0 and /dev/md1. 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" >

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

I am trying to use: ocfs-support-1.0.10-1 ocfs-2.4.21-EL-smp-1.0.11-1 ocfs-tools-1.0.10-1 with RedHat AS 3.0, 2-node cluster with shared SCSI. 2 dell 1650s, dual CPUs, PERC 3/DC cards chained to a PowerVault 220S. I am using lvm, and here is my layout: [root@cluster1 archive]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda2 32G 5.1G 25G

Hi, I am using CIFS 2.01.01 on HPUX11V2. CIFS is running in ADS security-mode. Winbind is used to map the userers from the W2K3-Domain (german) to an tdb-file. The user mapping works fine, but I have problems with the ACLS: setting the ACLS to a file or folder from windows leads in "access denied". I'm the owner of the object and have full access. The really crazy thing is,

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

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)

Hi all, I've started playing with kvm on CentOS 5.5, with not much success so far. In a nutshell, I have the same problem as http://lists.centos.org/pipermail/centos-virt/2010-April/001854.html I followed the RHEL5 virtualization guide to set up a bridge interface br0, and then used virt-install (rather than virt-manager - I like automation) to set up the vm. It hangs at some point.

Hi list. I am testing CentOS 5.2 now. I experience much slower IO under HVM Guests with the newer kernels, so I started some measurements. DOM-0 is a fully upgraded CentOS 5.2. DOM-U is CentOS 5.0 not upgraded at all for testing purposes. DOM-U sits on an LVM Volume. No other services are running. Hardware was freshly rebooted every time. within DOM-0 dd if=/dev/vgpentanol/lvol2 of=/dev/null

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

When doing a network install with a kickstart file, how 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

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

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

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

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"