similar to: How can kickstart be (re)started manually from the dracut emergency shell?

This problem still bites us. I've tried to play around with DHCP settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. I'm happy about /any/ hint. Cheers frank On 04/24/2017 11:57 PM, Frank Thommen wrote: > Hi, > > kickstarting fails due to problems with host resolution, even though the > network seems to be properly configured through DHCP. eno1 and eno2 are

Hi, kickstarting fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt ------------------------------------------------ [...] [ 14.780428]

Hi On 15/05/17 19:30, Tru Huynh wrote: > Hi, > > On Mon, May 15, 2017 at 03:04:03PM +0200, Frank Thommen wrote: >> This problem still bites us. I've tried to play around with DHCP >> settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. >> >> I'm happy about /any/ hint. > 1) ip route seems ok, but what does your /etc/resolv.conf looks like?

Hello, I?m using virt-install to build a guest system with CentOS. The system boots up, times out with dracut-initqueue timeout and drops me into an emergency shell. If I exit the shell the install continues and I get a working machine. Any ideas? virt-install \ -n TEST \ -r 8192 \ --os-type=linux \ --disk=/vm-images/test.img,device=disk,bus=virtio,size=100,format=raw \

Hi, On Mon, May 15, 2017 at 03:04:03PM +0200, Frank Thommen wrote: > This problem still bites us. I've tried to play around with DHCP > settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. > > I'm happy about /any/ hint. 1) ip route seems ok, but what does your /etc/resolv.conf looks like? 2) could you try with 7.3.1611, 7.2.1511 is no longer supported. Tru >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/11/15 09:59, Jos Vos wrote: > Hi, > > On CentOS 6.7 (all updates) kickstarting a CentOS 7 VM (in the way > it always has worked for other versions, incl. Fedora 22 VM's), > does not work for me. I use virt-install with a local copy of the > "images/pxeboot" tree. It all stops with: > > ... [ OK ]

Hi, On CentOS 6.7 (all updates) kickstarting a CentOS 7 VM (in the way it always has worked for other versions, incl. Fedora 22 VM's), does not work for me. I use virt-install with a local copy of the "images/pxeboot" tree. It all stops with: ... [ OK ] Reached target Paths. [ OK ] Reached target Basic System. dracut-initqueue[551]: Warning: Could not boot.

> > But, what happens if you let the kernel post install scripts do the work > or setting up the initrd things? Initially, I just rebooted from LiveCD and left Grub,kernel and dracut do their job with the defaults, but unfortunately, boot process stops at initrd (dracut) stage with the following error: [ 197.768159] localhost.localdomain dracut-initqueue[252]: Warning: Could > not

On Mon, 15 May 2017 at 20:05 zulu, Frank Thommen wrote: > lustre driver https://downloads.hpdd.intel.com/public/lustre/latest-feature-release/el7.3.1611/

Yannis Milios wrote: >> But, what happens if you let the kernel post install scripts do the >> work or setting up the initrd things? > > Initially, I just rebooted from LiveCD and left Grub,kernel and dracut do > their job with the defaults, but unfortunately, boot process stops at > initrd (dracut) stage with the following error: > > [ 197.768159]

I am trying to install a CentOS qemu/kvm virtual machine using a virt-install script[1]. Since Anaconda text user interface does not permit to users to edit filesystem type and mount points[2], I decided to use a kickstart file to customize such settings. To create a kickstart file, I used a trick: I installed a CentOS machine using Anaconda graphical user interface, and I made all customizations

> Yannis Milios wrote: >>> But, what happens if you let the kernel post install scripts do the >>> work or setting up the initrd things? >> >> Initially, I just rebooted from LiveCD and left Grub,kernel and dracut >> do >> their job with the defaults, but unfortunately, boot process stops at >> initrd (dracut) stage with the following error:

Hi, while kickstarting our virtual machines with PXE we often run into kickstart/anaconda failing with [...] [...] dracut-mount[xxx]: Warning: Can't mount root filesystem [...] dracut-mount[xxx]: Warning: /dev/root does not exist [...] dracut-mount[xxx]:/lib/dracut-lib.sh: line 1030: echo write error: No space left on device Starting Dracut Emergency Shell... Warning: /dev/root

Hi Everyone, I have a server that I recently applied all updates to to bring it to 1804. After rebooting the server, it would no longer boot and is instead dropping into a dracut shell. Here's a snippet of the output printed to the console (lines will likely wrap): [ 184.163787] dracut-initqueue[256]: Warning: dracut-initqueue timeout - starting timeout scripts [ 184.672525]

I've just tried putting usr in a subvol. Installation proceeds normally, no errors, but I'm dropped to a dracut prompt which indicates mount of /usr failed. dmesg follows: [ 14.025215] systemd[1]: Starting dracut initqueue hook... [ 14.077890] Btrfs loaded [ 14.129987] device label fedora_f18v devid 1 transid 31 /dev/sda1 [ 14.313607] device label fedora_f18v devid 1 transid 31

I tried to add --initrd-inject file://tmp/anaconda-ks.cfg and [...] file:/ [...] but the result is the same. Complete script file at https://paste.fedoraproject.org/paste/jA-lW5ZtyVDS0yHxbahkBF5M1UNdIGYhyRLivL9gydE=

Send CentOS mailing list submissions to centos at centos.org -----Original Message----- From: CentOS <centos-bounces at centos.org> On Behalf Of centos-request at centos.org Sent: Tuesday, July 31, 2018 5:30 PM To: centos at centos.org Subject: (EXT) CentOS Digest, Vol 162, Issue 29 Send CentOS mailing list submissions to centos at centos.org To subscribe or unsubscribe via the World

I'm trying to set-up a ContOS 7 DomU server. I have used the PXE set-up images like I normally would for earlier versions of CentOS. Here is my config file:- name      = "centos7" memory    = 2048 disk      = ['phy:/dev/xen6/centos7,xvda,w' ] vif = [ 'mac=xx:xx:xx:xx:xx:xx' ] kernel    = "/root/xen/centos7-64/vmlinuz" ramdisk   =

A recently created and fully functional CentOS 7.3 VM fails to boot after applying CR updates: ... ;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f CentOS Linux 7 (Core)1;-1f1;-1f

On 18/04/2017 15:54, Frank Thommen wrote: > Hi, > > I am currently struggling with the right way to configure a bonding > device via kickstart (via PXE). > > I am installing servers which have "eno" network interfaces. Instead of > the expected bonding device with two active slaves (bonding mode is > balance-alb), I get a bonding device with only one active slave