similar to: driver disk in kickstart...

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

Hey, I am trying to upgrade my kickstart usb key to 6.0 and I ran into a few issues. I boot with: ? append initrd=initrd.img ks=hd:sdb2:/ks.cfg repo=hd:sdb2:/centos and in the ks.cfg I have: ? harddrive --partition=sdb2 --dir=/centos and on sdb2 I have: ? sdb2:/centos/CentOS-6.0-x86_64-bin-DVD1.iso ? sdb2:/centos/CentOS-6.0-x86_64-bin-DVD2.iso It fails from the beginning unless I add /images

Hi, I am creating CentOS install usb keys and, apart from a few problems, it mostly works... 1. OT: My server HP does not seem to want to boot on it if I set the write protection on. 2. Anaconda tries to fetch the ks.cfg too early... It detects sda, then detects the RAID adapter, then re-detects sda with a "waiting for device to settle before scanning". Anaconda tries to access

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.

Hi I have a running kernel with the same kernel version of that in the kickstart that contains the Buslogic driver which would enable me to install a vmware client using kickstart. Is there an 'easy' way to take the initrd that contains the correct drivers and inject these into the initrd of the kickstart kernel? Or does anyone have a kickstart initrd available with the Buslogic

Hi, I have alot of kickstart and scripting going on as I provision lots of machines, and every now and then I run into a pesky machine or three that's still got that Adeptec zero-channel RAID card sitting on the board. Normally I like to rip it our and throw something more robust in, but if it's a cache machine or whatever, I leave it in. It makes my kickstart file useless until I

Hi guys, I have my driverdisk created and the files are on a USB pendrive. How do I make the USB pendrive /dev/sdb and not /dev/sda??? I am wanting the installation to take place on sda and the driver disk to be sdb? My driver disk is a network driver disk, r8168. Jerry

Hi, I modified my kickstart to do some custom partioning and formating in a pre-install script. I am trying to align the partitions on the RAID stripe (and format with a correct stride). But, sfdisk complains that it does not start/end on a cylinder boundary (used -L option to limit complaining). Since the cylinder size is not a multiple of the stripe size, I cannot align on both. I tried to

Hi, I am trying to adapt my kickstart usb key to optionally auto-setup mdraid on two disks...? But I have one server that keeps attaching the usb key to sda instead of sdc... My kickstart creates the raid devices on sdb and sdc partitions; but then I expect it not to work once the key is unplugged and the disks fall back to sda and sdb... Can I just modify mdadm.conf at the end, just

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

On 11/01/2017 05:02 PM, James A. Peltier wrote: > Leaving ksdevice= off the command line will prompt you for the location of the kickstart file and the device you want to use to kickstart > Well, things just got weird with this.? The first couple of times I included the biosdevname etc, on the command line with ksdevice=eth0 it worked perfectly.? Sometime yesterday (and I verified this a

I'm trying to set up a custom installation of CentOS using kickstart i tried many thing from how to's and tutorial web pages but nothing worked ;( Here is my USB key tree : |-- CentOS | |-- all my rpms | `-- last rpm |-- TRANS.TBL |-- boot.cat |-- boot.msg |-- custom.iso |-- general.msg |-- images | |-- README | |-- TRANS.TBL | |-- boot.iso | |-- diskboot.img | |-- minstg2.img | |--

On Fri, 3 Nov 2017, Mark Haney wrote: > On 11/01/2017 05:02 PM, James A. Peltier wrote: >> Leaving ksdevice= off the command line will prompt you for the location of >> the kickstart file and the device you want to use to kickstart >> > Well, things just got weird with this.? The first couple of times I included > the biosdevname etc, on the command line with

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,

Kickstart fails for statically built custom booting kernel, although the custom kernel is built form the same version stock kernel source. My anaconda and kernel source are both of stock versions on Centos 5. At the kickstart 'F3' screen, the following error messages appear: Modules to insert tg3 ... ... ERROR: no network devices in choose network device! ERROR: no network drivers

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

I've managed to install CentOS 5.1 on S5000PAL with fakeraid Intel Embedded Raid Technology II Raid1 (LSI chipset) with some help of kickstart declaration 'driverdisk --source=http://.../driver.img' Then I've had some problems with yum update - new kernel didn't know about megasr.ko. I've solved it with commands: cd /lib/modules/ cp 2.6.18-53.el5PAE/updates/megasr.ko

Hi all, I've got a Centos 5.1 kickstart that I must continue to use. How can I update the kick start image so that it recognizes Intel gigabit 82576 nic? BTW, I compiled the driver I need and have this igb.ko file. How do I incorporate that into my initrd.img file that I see on the kickstart CD that is probably my kickstart boot OS. Thank you very much in advance. aurf -

Hallo Steff, mach dir keine Sorgen es wird nix gesperrt reduziert oder ?hnliches bei ?berschreitung xD Ich muss gleich einkaufen, Besorgungen machen f?r den Urlaub. Bin um 13:00 Uhr wieder da. Bis sp?ter heute .. Mit freundlichen Gr??en Klaus Beeck ---------------------------------------------------------------------------- --- Visionthinks???????????????????????????????????????

Hi Folks: I am getting a "No driver found" dialogue when I try to build a guest using virt-install using a kickstart file. I am stuck. I am not sure how to fix or even debug this problem. Can anyone suggest a way forward? Here are the commands that I am using: $ # ================================================================ $ # Create the volume $ #