search for: initqueue

..., 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] localhost kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready [ 19.977052] localhost kernel: tg3 0000:0b:00.0 eno1: Link is up at 1000 Mbps, full duplex [ 19.977118] localhost kernel: tg3 0000:0b:00...

...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] localhost kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link > is not ready > [ 19.977052] localhost kernel: tg3 0000:0b:00.0 eno1: Link is up at > 1000 Mbps, full duplex > [ 1...

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] dracut-initqueue[256]: Warning: dracut-initqueue timeout - starting timeout scripts [ 185.183111] dracut-initqueue[256]: Warning: dracut-initqueue timeout - starting timeout scripts [ 185.183395] dracut-initqueue[25...

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 \ --ram=8192 \ --ne...

...ll 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 boot. > [ 197.821409] localhost.localdomain systemd[1]: Received SIGRTMIN+20 from > PID 254 (plymouthd). > [ 197.822328] localhost.localdomain dracut-initqueue[252]: Warning: > /dev/centos/root does not exist > [ 197.823044] localhost.localdomain drac...

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 >

...m happy about /any/ hint. > 1) ip route seems ok, but what does your /etc/resolv.conf looks like? /etc/resolv.conf is 100% ok once I am in the dracut emergency shell and name resolution works fine. However I don't know how it looks at the time of the error message - that is during dracut-initqueue - and I have no idea how I could check that. > 2) could you try with 7.3.1611, 7.2.1511 is no longer supported. Unfortunateyl not. Due to special hardware (Infiniband, FPGA) and special lustre drivers we are currently bound to this specific release. frank

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

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=

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/

Just did an in-place update from 6.1 to 6.2 on my eeepc 901 (Atom CPU). during boot, (if I hit ESC to see the boot messages) it says "starging udev" then nothing else for a few seconds, then a huge register dump scrolls by. it's too big to see the beginning of it. If I boot from the prior kernel and look in /var/log/messages, I don't see any evidence of the failed boot.

...lsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 glWinInitVisuals:1596: glWinInitVisuals glWinInitVisualConfigs:1503: glWinInitVisualConfigs glWinSetVisualConfigs:1581: glWinSetVisualConfigs init_visuals:1055: init_visuals null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread...

...ter grub attempted to boot the 4.9 kernel, and it sat there indefinitely. After some digging around I removed the "console=hvc0" setting /etc/default/grub, ran grub2-mkconfig, and tried booting 4.9 again. This time it actually showed messages, leading up to this: [ 186.550326] dracut-initqueue[542]: Warning: dracut-iniqueue timeout - starting timeout scripts [ 186.570380] dracut-initqueue[542]: Warning: dracut-iniqueue timeout - starting timeout scripts [ 187.120156] dracut-initqueue[542]: Warning: dracut-iniqueue timeout - starting timeout scripts [ 188.633714] dracut-initqueue[542]:...

...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. dracut-initqueue[551]: Warning: /dev/root does not exist Starting Dracut Emergency Shell... Warning: /dev/root does not exist ... I found zillion references to similar problems, including PXE-related (I do not use PXE, but "-l" with...

...(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 ... [ 194.011062] dracut-initqueue[227]: Warning: dracut-initqueue timeout - starting timeout scripts [ 194.546622] dracut-initqueue[227]: Warning: dracut-initqueue timeout - starting timeout scripts [ 194.547515] dracut-initqueue[227]: Warning: Could not boot. [ 194.557324] dracut-initqueue[227]: Warning: /dev/disk/by-uuid/bbafa...

...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 boot. [ 197.821409] localhost.localdomain systemd[1]: Received >> SIGRTMIN+20 from >> PID 254 (plymouthd). >> [ 197.822328] localhost.localdomain dracut-initqueue[252]: Warning: >> /dev/centos/root does not exist >> [ 197....

...detected capacity change from 0 to 10203693056 md127: unknown partition table systemd-cryptsetup[358]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/6972a564-542d-498b-b3a0-7d71c2e966a2. md127: unknown partition table md127: unknown partition table dracut-initqueue[296]: Scanning devices dm-0 for LVM logical volumes fedora-foo1/root fedora-foo1/swap fedora-foo1/root fedora-foo1/swap dracut-initqueue[296]: inactive '/dev/fedora-foo1/root' [7.42 GiB] inherit dracut-initqueue[296]: inactive '/dev/fedora-foo1/swap' [2.00 GiB] inherit systemd-f...

...detected capacity change from 0 to 10203693056 md127: unknown partition table systemd-cryptsetup[358]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/6972a564-542d-498b-b3a0-7d71c2e966a2. md127: unknown partition table md127: unknown partition table dracut-initqueue[296]: Scanning devices dm-0 for LVM logical volumes fedora-foo1/root fedora-foo1/swap fedora-foo1/root fedora-foo1/swap dracut-initqueue[296]: inactive '/dev/fedora-foo1/root' [7.42 GiB] inherit dracut-initqueue[296]: inactive '/dev/fedora-foo1/swap' [2.00 GiB] inherit systemd-f...

...l 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 boot. > [ 197.821409] localhost.localdomain systemd[1]: Received SIGRTMIN+20 > from PID 254 (plymouthd). > [ 197.822328] localhost.localdomain dracut-initqueue[252]: Warning: > /dev/centos/root does not exist > [ 197.823044] localhost.localdomain dra...

...>> >> 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 boot. [ 197.821409] localhost.localdomain systemd[1]: Received >>> SIGRTMIN+20 from >>> PID 254 (plymouthd). >>> [ 197.822328] localhost.localdomain dracut-initqueue[252]: Warning: >>> /dev/centos/root doe...