From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 0BCD41381FA for ; Sat, 3 May 2014 10:55:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A5FC1E0A89; Sat, 3 May 2014 10:55:23 +0000 (UTC) Received: from smtpq1.gn.mail.iss.as9143.net (smtpq1.gn.mail.iss.as9143.net [212.54.34.164]) by pigeon.gentoo.org (Postfix) with ESMTP id 832DFE0A5E for ; Sat, 3 May 2014 10:55:22 +0000 (UTC) Received: from [212.54.34.136] (helo=smtp5.gn.mail.iss.as9143.net) by smtpq1.gn.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1WgXbG-0000gV-1N for gentoo-user@lists.gentoo.org; Sat, 03 May 2014 12:55:22 +0200 Received: from 53579160.cm-6-8c.dynamic.ziggo.nl ([83.87.145.96] helo=data.antarean.org) by smtp5.gn.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1WgXbF-0005Zd-J6 for gentoo-user@lists.gentoo.org; Sat, 03 May 2014 12:55:22 +0200 Received: from andromeda.localnet (unknown [10.20.13.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by data.antarean.org (Postfix) with ESMTPSA id 9F53F4C for ; Sat, 3 May 2014 12:54:45 +0200 (CEST) From: "J. Roeleveld" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] boot problems Date: Sat, 03 May 2014 12:54:31 +0200 Message-ID: <1978058.oAuOLmVY6q@andromeda> User-Agent: KMail/4.11.5 (Linux/3.10.25-gentoo; KDE/4.11.5; x86_64; ; ) In-Reply-To: <5364C5E7.8040707@xunil.at> References: <5364C0F9.3000906@xunil.at> <9c690741-dc85-4511-91f3-2ff60e975e68@email.android.com> <5364C5E7.8040707@xunil.at> 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 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Ziggo-spambar: ---- X-Ziggo-spamscore: -4.8 X-Ziggo-spamreport: ALL_TRUSTED=-1,BAYES_00=-1.9,PROLO_TRUST_RDNS=-3,RDNS_DYNAMIC=0.982,TW_LV=0.077 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-Archives-Salt: 58d126cd-8a5a-4187-9e21-b97a11c5518b X-Archives-Hash: ef2ca54135938236879623ed622e27d2 On Saturday, May 03, 2014 12:33:11 PM Stefan G. Weichinger wrote: > Am 03.05.2014 12:27, schrieb J. Roeleveld: > > On 3 May 2014 12:12:09 CEST, "Stefan G. Weichinger" wrote: > >> I see boot problems on two of my machines ... very likely related to > >> lvm2 as far as I can tell so far. > >> > >> Downgraded and even disabled systemd, re-emerged stuff ... I am still > >> at > >> trying to find the reason. Maybe it is with the mdadm raids also ... > >> > >> I just want to ask you other gentoo users if anyone else hit this issue > >> since around yesterday? Maybe someone else also scratches his head > >> already ... > >> > >> Stefan > > > > Can you provide more info on the kind of boot issues you are having? > > > > Based on what you gave, only difference between your systems and mine is > > systemd. And my systems boot. This leads to the assumption the issue is > > caused by systemd. > > > > -- > > Joost > > > > Ps. This is NOT an anti-systemd remark :) > > Yeah, sure ;-) > > Reporting issues/bugs from a system running with systemd very often > leads to these fundamental statements "see what happens ... !?" :-) I tend to try not to. If you had mentioned a random package X instead of systemd, my comment would have mentioned random package X. I don't use systemd, but as it's pushed by Redhat and redhat, by default, uses LVM, I would expect that part to work correctly together. > I am still trying to spot the reason. As mentioned in my other reply > currently it seems to also timeout/hang with openrc for me. > > Right now I downgraded systemd, rebuilt dbus, dracut, procps ... lvm-utils? > From a live-cd I am able to mount /, start the 2 raid-arrays, activate > VGs and LVs ... everything useable. Ok, to get this straight. You have x amount of disks those are in 2 raid-arrays on top of that, you have LVM... Can you check that LVM is WAITING for the MDADM arrays to be build? This sounds like an issue I was having a while ago. I had to add an extra dependency to the start-up scripts at the time. > Currently I rebooted kernel 3.14.2 and get another: > > "A start job is running for Activation of LVM2 logical volumes" ... from > systemd-212-r2 (tested -r3 and stable 208 as well) > > Removing the "real_init" from the kernel line chooses openrc and also > leads to a hanging boot. > > So a next step seems to comment the LVs from fstab and check if it boots > then. Or enable interactive boot where you can press "I" to have every service ask if it needs to be started. Then skip LVM. Do you have parallel-boot enabled with OpenRC? If yes, disable that just to make sure that isn't causing the issue with OpenRC. With systemd, I would recommend checking the dependencies between mdadm and lvm. -- Joost