From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 336161381FA for ; Wed, 14 May 2014 14:41:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6D956E0AB6; Wed, 14 May 2014 14:41:38 +0000 (UTC) Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com [209.85.217.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2EBBAE0A99 for ; Wed, 14 May 2014 14:41:37 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id p9so1494039lbv.39 for ; Wed, 14 May 2014 07:41:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=0DmpVKFC+coBKS8+H2Uhb7EeFgIm9JOf4m0BjtrQQCE=; b=gIALEbPMqlM63caWaPRBpKuKESnCw+3E663jpU9zoqUxtkefQvdvnUustI7JiCdKnZ 3SDszewAwQASyDrahsdN2KXeQ1pxHCx5TY369ipgByeLTnn4BomIjymY2KDQiBMu2Lga 6e7VGK+wZgxsdIZMgWmXVH9X5XsaT1464B8O2VjQNpCKFRxWjgkPhdi16GpCQ4k9QmOp xI0HQYBLkoysVadiGqrsNSedKk1S7JDCwq/BQgoKGMloNFeRBJfxsShkEh2utPBm13TV ANhJA9/JvwBMdYEsbeCtA0J16b5eI5rtYTgntS1+jPESgBDlf6gr2XZnUkhypbMwTGab lirg== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.152.4.39 with SMTP id h7mr2946166lah.12.1400078495684; Wed, 14 May 2014 07:41:35 -0700 (PDT) Received: by 10.112.54.138 with HTTP; Wed, 14 May 2014 07:41:35 -0700 (PDT) In-Reply-To: <8253.1400060407@ccs.covici.com> References: <23736.1399879340@ccs.covici.com> <17435.1399889735@ccs.covici.com> <13680.1399912266@ccs.covici.com> <17066.1399913526@ccs.covici.com> <8253.1400060407@ccs.covici.com> Date: Wed, 14 May 2014 08:41:35 -0600 Message-ID: Subject: Re: [gentoo-user] problems getting systemd to work From: =?UTF-8?Q?Jc_Garc=C3=ADa?= To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 15846da1-78a6-466b-99a6-4fba8da6f873 X-Archives-Hash: 6f07fe9603fb2b3d5b449e7940659e49 2014-05-14 3:40 GMT-06:00 : > Canek Pel=C3=A1ez Vald=C3=A9s wrote: > >> On Mon, May 12, 2014 at 11:52 AM, wrote: >> > Canek Pel=C3=A1ez Vald=C3=A9s wrote: >> > >> >> On Mon, May 12, 2014 at 11:31 AM, wrote: >> >> [snip] >> >> > OK, I will try dracut, >> >> >> >> I hope it works with dracut. This is my kernel command line and >> >> RAID/LVM related stuff from GRUB2: >> >> >> >> GRUB_CMDLINE_LINUX=3D"init=3D/usr/lib/systemd/systemd quiet nosplash" >> >> GRUB_PRELOAD_MODULES=3D"lvm mdraid1x" >> >> >> >> And this is my dracut.conf (minus comments): >> >> >> >> add_dracutmodules+=3D"crypt lvm mdraid systemd" >> >> add_drivers+=3D"autofs4 ipv6 dm-crypt aes sha256" >> >> fscks=3D"umount mount /sbin/fsck* e2fsck" >> >> >> >> That's it. I didn't touched anything else to make dracut+systemd work >> >> with LVM and RAID (and LUKS, but that doesn't matter). >> >> >> >> Also, dracut comes with extensive and very clear documentation; check >> >> the man pages included. >> >> >> >> > but I still want to know what systemd is doing, >> >> > what processes its spawning, etc. -- how can I find this out -- I >> >> > thought to use the confirm_spawn, but it times out and keeps going,= what >> >> > can I do instead? >> >> >> >> You can use bootchart: >> >> >> >> man 1 systemd-bootchart >> >> >> >> It will produce a chart with all the processes, and how long it takes >> >> for every one of them. But remember, the order depends on which one >> >> finishes before, and that can change from boot to boot. >> >> >> >> > Thanks people for all your responses, this is a great list. >> >> >> >> Regards. >> >> -- >> >> Canek Pel=C3=A1ez Vald=C3=A9s >> >> Profesor de asignatura, Facultad de Ciencias >> > >> > Well, since I am unable to see, the graph would not do me any good, an= y >> > way to get it in text form? What I want to see (and I know the order >> > may change) is which starts first and so on, to make sure targets, >> > etc. do what I want them to do. >> >> Try adding this to your kernel command line: >> systemd.log_target=3Dconsole systemd.log_level=3Ddebug. It will add a lo= t >> of output, including what is being executed. >> >> Everything is documented in the man page: man 1 systemd. > > Well, I rebooted under dracut, but it did not do the lvmscan and so the > job trying to find the root file system timed out after 90 seconds. It > took me to the emergency shell which I had specified, and I was able to > do the lvm_scan and them magically root got mounted under sysroot, but I > had no idea what to do next to maybe get things going. > > So how can I get dracut to do its lvm_scan -- I even added the line > add_dracutmodules+=3D"lvm" This is a must if you are not running 'dracut --lvmconf' > but no joy. > I saved the rdsosreport.txt and if that is of any use, I can post it. > In the dracut manpage, I found the '--print-cmdline' argument , it generates a suggested kernel command line , I hadn't used it before, but this what it printed: rd.lvm.lv=3Dgentoovg/usr rd.lvm.lv=3Dgentoovg/root root=3D/dev/mapper/gentoovg-root rootflags=3Ddefaults rootfstype=3Dext4 So I guess, its neccesary to have this in the command line. At the time I struggled for an entire day with the same timeout when my LVs where not recognized, did research trial/error with dracut and genkernel, got them both working, stayed with dracut because I liked it, I tried to avoid this struggle for you on my first response, but I see is going to take you longer... > -- > Your life is like a penny. You're going to lose it. The question is: > How do > you spend it? > > John Covici > covici@ccs.covici.com > PD: RTFM.