similar to: kickstart driverdisk

Hi, I am Ken.. I am trying to add dud(driver update disk) to centos5.6 using network method, I can successfully add dud to centos5.6 using http and ftp method, but fail when using nfs method. However those all three methods are officially supported in the centos5.6. As indicated in the centos5.6 website, we can see they not only support http, ftp, but also nfs.

I've previously used includes in CentOS 4.4 and they worked fine. But in CentOS 5.5, trying to specify a driver disk via an include does not work. If I instead specify it directly, it loads fine. When it fails (because it can't see the disk drive - needs the driver disk to see the hard disk), in Console 2 I can see that /tmp/drvdisk exists and has the line I wrote to it. I see nothing

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"

I've got two pendrives. I want to install a Debian on them. RAID1. Ok... ... After I installed it in RAID1, it works perfectly, ok! :) When I pull out one of the pendrive [good pendrive], it still boots up, hurrah :) But: ... When I pull out the other pendrive [i plug in the first one i tried] it say's: GRUB hard disk error What can I do? I already tried: grub-install /dev/sdc

Hello. A couple of years ago I installed two file-servers using kickstart. The server has two 1TB sata disks with two software raid1 partitions as follows: # cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sdb4[1] sda4[0] 933448704 blocks [2/2] [UU] md0 : active raid1 sdb1[1] sda2[2](F) 40957568 blocks [2/1] [_U] Now the drives are starting to be failing and next week

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)

This is what I have for configuring software raid on sata drives in my kickstart config <snip kickstart.cfg> clearpart --initlabel --all part swap --size=2048 --ondisk=sdb part swap --size=2048 --ondisk=sda part raid.01 --size=101 --ondisk=sda part raid.02 --size=101 --ondisk=sdb part raid.04 --size=1 --grow --ondisk=sdb part raid.03 --size=1 --grow --ondisk=sda raid / --fstype ext3

Hi, I have a test system that booted fine using "Legacy Bios? mode and using the following Kickstart snippet configured the disks correctly:- # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part raid.01 --fstype="raid" --ondisk=sda --size=500 part raid.02 --fstype="raid" --grow

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

By default, a kickstart installation will spread the configured partitions over all disks that are found, and the only way around that is to use --ondisk or ignoredisk. But I was wondering how reliable this method is. E.g. if there are four SATA ports on the system board, can I blindly assume that port one will always correspond to sda, port two to sdb, and so on? Can I assume that a second

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

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

Hello, I'm trying to install CentOS 6.0 64bit on a HP ProLiant ML110 G7 with a HP Smart Array B110i SATA RAID Controller. One logical drive (RAID 1+0) on the RAID Controller is already build. CentOS Installation can't find the logical Drive, but it shows me the zwo physical drives (sda+sdb). After searching the web, I found following hints:

I am trying to install 6.2 on a machine. I am using PXE as I have done so a number of times. My hard disk is being detected as sdb and not sda. My kickstart config is wanting it at sda. There are no other disks in the unit. It has and SD slot and an esata although BIOS does not appear to have a disable for either of those devices. Is there anyway to "force" the disk to sda ? or find

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

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

Using CentOS 5.1, though with a few hours work I could update to 5.2.. I can install to SAN with a single path no problem but I'd like to be able to use dm-multipath. From the kickstart docs it seems this is supported but there is no information as to what the various options mean http://www.centos.org/docs/5/html/5.1/Installation_Guide/s1-kickstart2-options.html -- multipath (optional)

Hi recently I noticed in the messages log, the following error May 18 15:59:52 mail kernel: sdb: assuming drive cache: write through May 18 15:59:52 mail kernel: sdb : READ CAPACITY failed. May 18 15:59:52 mail kernel: sdb : status=0, message=00, host=1, driver=00 May 18 15:59:52 mail kernel: sdb : sense not available. May 18 15:59:52 mail kernel: sdb: assuming Write Enabled May 18

Is there an easy way to specify the proper device location for the kickstart configuration file if it is on a USB flash or USB floppy drive? Depending on the hard disk configuration they might by /dev/sda, /dev/sdb, etc. On SuSE'autoyast instalattions, the system searches all available devices for an ``info'' configuration file. Does CentOS 5.x do something similar to find a

Is there a way in the %post section of install to continue to have the VT3 logging but also log that to a file. Somehow using tee perhaps? I have found --log=/tmp/post-install.log but then that shows nothing on VT3. I would like to have both if possible. Log to VT and a file. THanks, Jerry