similar to: kickstart question

Hi to all, from syslinux 4.06 and 5.00 pre 12 came the same dump. Background: While trying to install syslinux on small (700 MB) FAT16 Partition on HP Server got Red Screen of Death with a register dump. Illegal OpCode EAX=00001F01 EBX=000001A4 ECX=00000000 EDX=00000019F EBP=0000FBFA ESI=000007BE EDI=00000800 DS=0000 ES=0000 FS=0000 GS=0000 CS:EIP=0000:000083A6 SS:ESP=1000:0000AFF6

Hey folks, I'm at colocaiton in the middle of a big rebuild and it seems I have a faulty CD rom in the server that I need to put Centos on via Kickstart. So I cannot boot the Centos 5.4 net install CD. Is PXE kickstart easy to set up? I have a laptop here with DHCP already going. I google and a bunch of stuff comes up but it does not look simple. I'm just shooting htis out ther eon

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 have a couple lines like: part / --ondisk=sda --fstype ext3 --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /home --ondisk=sda --fstype ext3 --size=1 --asprimary --grow in my kickstart file. Is there a way to have 1 kickstart file that works for hda and sda both??? So I would like to have 1 kickstart file that works for either a hda

I'm having what appears at first glance to be a kickstart+anaconda issue on CentOS 7.4. As near as I can tell in the program.log in the anaconda environment, the partitioning instructions downloaded with the kickstart from cobbler appear to simply not be applied. Then /mnt/sysimage is not mounted, the logs are not copied to /mnt/sysimage/root and the installation stalls due to the anamon

I can do a yum update in my post kickstart (which is what I am doing now actually). However, I want to save network time at installations. If I copy down the files from centos/5.3/updates/x86_64/RPMS and place them in a directory local on my network, can I just "rpm -U /mnt/directory/updates/x86_64/RPMS*" in my post section? Assuming I have nfs mounted the directory of course...

I am trying to add an efi partition to my working kickstart file. bootloader --driveorder=sda --append="rhgb quiet biosdevname=0 net.ifnames=0" clearpart --all --initlabel part / --ondisk=sda --fstype xfs --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /boot/efi --ondisk=sda --fstype efi --size=1000 --asprimary part /home --ondisk=sda

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"

It seems I can't smarm monitor disks on RAID controllers? I tried on several machines with two different controllers and on all I get this when starting up smartd: Jul 27 14:36:43 c1 smartd[5944]: Opened configuration file /etc/smartd.conf Jul 27 14:36:43 c1 smartd[5944]: Configuration file /etc/smartd.conf parsed. Jul 27 14:36:43 c1 smartd[5944]: Device: /dev/sda, opened Jul 27 14:36:43

I have continued on with my attempts to get p2v working will little success. I have changed my server to Fedora 16 and finally got an XP with a single SATA disk (sda) to work. I think that this means that the current virt-p2v.iso just doesn't work with the packages that are available on Centos 6 at the moment. However, the machines that I currently need to actually migrate all have

update server autobuild to set up a new isolated vm environment and go through the server installer process and rails tests --- autobuild.sh | 65 ++++++++++++++++++++++++++++++++++++++++++ ovirt-installer-test-answers | 21 +++++++++++++ ovirt-server-test.ks | 37 ++++++++++++++++++++++++ 3 files changed, 123 insertions(+), 0 deletions(-) create mode 100644

Hi, I have updated the kernel to 2.4.21-27.0.2 on Centos 3.4 (was 3.3 when I did the kernel update) and have modified grub.conf to use the single CPU kernel: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. #

Hello friends, I am experiencing some weird beheaviour on one of my computers. I appologize for the laconic subject, but I really don't know anything more than that. I'll tell the story in chronological order. I have an HP server with five SCSI disks. The disks are _not_ in RAID. I installed FC2 on one disk. I installed a 2.6.11.7 and used it for boot. The server runs some software

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"

Hi everybody. I have an HP StorageWorks array connected to one of my servers, connected via an LSI controller (lspci reports: SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08)) on an HP DL385 running CentOS 5.5 x86_64. I have set up multipath and all is working but, when I create a snaphost and export it as a new LUN from the HP web interface, it

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

On Thu, August 4, 2016 7:13 pm, Paul Heinlein wrote: > On Thu, 4 Aug 2016, Valeri Galtsev wrote: > >> Dear Experts, >> >> Could somebody point to kicstart HOWTO specific for CentOS 7? >> >> On CentOS 7 I somehow am always given human intervention questions >> about drive which defeats unattended ks install. >> >> At least one snag I hit

Original the array was attach to an HP server via a Smart Array Controller.(which I didn't setup, I just inherited the problem) This controller no longer recognizes the array even though the front panel of the array indicates its intact. I then took the array and plugged it into my Centos server and it recognized it ... cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun:

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

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)