All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Ali H. Caliskan"
	<ali.h.caliskan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Timeout failure with rd.live.image boot option.
Date: Wed, 2 Sep 2015 13:02:08 +0200	[thread overview]
Message-ID: <55E6D730.5090805@redhat.com> (raw)
In-Reply-To: <CAFO=TmXxiYjsnkB3_=PUij4on8kJu+CcE-HU9pzkVvjvyjwSvQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 12.07.2015 13:22, Ali H. Caliskan wrote:
> While dracut version 041 boots fine, dracut 042/043 or the latest git
> version doesn't boot at all. Systemd complains about:
> 
> localhost systemd[1]: dev-mapper-live\x2drw.device: Job
> dev-mapper-live\x2drw.device/start failed with result 'timeout'.
> 
> Here is the entire rdsosreport.txt:
> 
> + cat /lib/dracut/dracut-043-42-gee44f62
> dracut-043-42-gee44f62
> + cat /proc/cmdline
> BOOT_IMAGE=boot/vmlinuz rd.live.image rd.live.overlay.size=1024
> root=LABEL=GNURAMALINUX_201507 initrd=boot/initramfs
[…]
> [    3.135257] localhost systemd[1]: Starting Remote File Systems.
> [   14.086475] localhost kernel: random: nonblocking pool is initialized
> [   91.008636] localhost systemd[1]: dev-mapper-live\x2drw.device: Job
> dev-mapper-live\x2drw.device/start timed out.
> [   91.008875] localhost systemd[1]: Timed out waiting for device
> dev-mapper-live\x2drw.device.
[…]

Would be nice to have a rdsosreport.txt with "rd.debug" added to the kernel
command line.


      parent reply	other threads:[~2015-09-02 11:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12 11:22 Timeout failure with rd.live.image boot option Ali H. Caliskan
     [not found] ` <CAFO=TmXxiYjsnkB3_=PUij4on8kJu+CcE-HU9pzkVvjvyjwSvQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-02 11:02   ` Harald Hoyer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55E6D730.5090805@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=ali.h.caliskan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.