mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: yeyouqun <yeyouqun1981-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: initrd-xxx.img create dracut not correct
Date: Fri, 08 Mar 2013 08:02:06 +0100	[thread overview]
Message-ID: <51398CEE.5090502@redhat.com> (raw)
In-Reply-To: <513964D9.7060700-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Am 08.03.2013 05:11, schrieb yeyouqun:
> 
> Recently I upgraded linux kernel to 3.6.10 and upgrade dracut version to 024,
> system starts up OK on 3.6.10. But when I upgraded kernel from 3.6.10 to 3.8.2,
> dracut failed to start up the system. Message when start up reads:
> 
> ......
>    dracut: dracut-dracut-024-
>     rpcbind: cannot create socket for udp6
>     rpcbind: cannot create socket for tcp6
>     mount: unknoun filesys
>     udev: starting version 147
>     systend-udevd (139): /proc/139/oom_adj is deprecated, please use
>     /proc/139/oom_score_adj instead.
>     dracut Warning: Could not boot.
>     dracut Warning: Could not boot.
>     Dropping to debug shell.
>     /bin/sh: can't access tty; job control turned off
> ......
> 
> But when I unpack the initrd-3.8.2.img, the /lib/modules directory shows as below:
> 
> modules ---- 3.8.2
>          |
>          |__ 3.6.10
> 
> all the kernel modules reside in "3.6.10" directory and other files, such as
> "modules.dep" and etc. reside in 3.8.2, I think this is the reason why system
> can't start up.
> 
> I upgraded kernel by the steps as(in kernel source tree of 3.8.2):
> 
>     make
>     make modules_install
>     make install
> 
> Any one can tell how to fix this behavior of dracut?

What's the output of:

# dracut --debug test.img 3.8.2

  parent reply	other threads:[~2013-03-08  7:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08  4:11 initrd-xxx.img create dracut not correct yeyouqun
     [not found] ` <513964D9.7060700-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-03-08  7:02   ` Harald Hoyer [this message]
     [not found]     ` <513C528C.2010200@gmail.com>
     [not found]       ` <513C528C.2010200-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-03-11  9:31         ` Harald Hoyer
     [not found]           ` <513DA469.80505-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-03-12  1:14             ` yeyouqun
     [not found]               ` <513E8164.8000908-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-03-12  8:37                 ` Harald Hoyer
     [not found]                   ` <513EE93F.1090909-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-03-12  9:08                     ` yeyouqun
     [not found]                       ` <513EF097.4040405-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-03-12  9:12                         ` Harald Hoyer
     [not found]                           ` <513EF163.3020106-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-03-12  9:14                             ` yeyouqun
2013-03-12  9:34                             ` yeyouqun

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=51398CEE.5090502@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=yeyouqun1981-Re5JQEeQqe8AvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox