From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-144802-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 1F04A13870D
for <garchives@archives.gentoo.org>; Mon, 28 Jan 2013 14:45:13 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 7A4B521C074;
Mon, 28 Jan 2013 14:45:04 +0000 (UTC)
Received: from mail-ia0-f169.google.com (mail-ia0-f169.google.com [209.85.210.169])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 9D86021C05B
for <gentoo-user@lists.gentoo.org>; Mon, 28 Jan 2013 14:45:02 +0000 (UTC)
Received: by mail-ia0-f169.google.com with SMTP id j5so4366709iaf.28
for <gentoo-user@lists.gentoo.org>; Mon, 28 Jan 2013 06:45:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=x-received:mime-version:in-reply-to:references:from:date:message-id
:subject:to:content-type;
bh=D53e/flYo3Cp6rt77f6BVmueJwDIWTOvU9zvFHHfL7o=;
b=iWQndmJZtzWkYONcXKqj7MGb6PLLkEbAFJW5c5KDhsXbdC3yi7BO9ZqurLuBg6tT/C
VmnxoUYXYTrgppReJIul1LQnrvwT7///ZfoKZjb8+MFo/L0QTHZqNn+PK9Q8YpsakKoa
1klN48h4+JmlfZDewq8Q+wuspib32D0hjD4wWUH/zSfzTIRAgOnY70OFwnkKX/dOESJm
R2xKmw92oJ326dUK/x1sJD36eYNdc2FfylRtsaIrsc73hGk/3eWo8L2iXXHOcvXQWRop
QuBfyvDUr3fNtnWdH+LGz+hM5Wz90nESEgVZOcfTEd07mXed5quY0P+wap30yG6XYWvq
gXxg==
X-Received: by 10.50.179.100 with SMTP id df4mr5209588igc.60.1359384301842;
Mon, 28 Jan 2013 06:45:01 -0800 (PST)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.42.216.210 with HTTP; Mon, 28 Jan 2013 06:44:41 -0800 (PST)
In-Reply-To: <CAJ0EP41hEZ_Yhq1kDkWgZXD9NrkYw1m0SZXsip9NiczcFpKX1A@mail.gmail.com>
References: <CAP4tJZ+huW+9nNVLKa6nZy698-8og4J+w1ysYavW+mg16htowQ@mail.gmail.com>
<CADPrc80w=pbfe=PULbFV-JK8v6ftEVzqS3t=proKFxFftW8yAQ@mail.gmail.com>
<CAP4tJZ+QsYxAAct5w-1PF10de6mPp0U12Acd4xNgCyca8fg0Xg@mail.gmail.com>
<CADPrc83g9GSJipFj4F4TEcJE8Tw7Fi1UMXeE48aGR_jo5efFgw@mail.gmail.com>
<CAP4tJZLatPinPwh3phUpD6FkKiVnYzs3kdAHgZZveYPJTMNEag@mail.gmail.com>
<CAP4tJZLH1YSxnbdHbPzjhV0bp3TVriMGPT-y3ip9MYUGGBQWdQ@mail.gmail.com>
<CAJ0EP40ppKSWuF23t3dOd+7=xgT+ajPZAXjjJnNQu0f07F4M5Q@mail.gmail.com>
<CAP4tJZLQ+BjjoCa+P3nVKmxFLxPrkO+xW3SFJOp4wkYV59OQgA@mail.gmail.com> <CAJ0EP41hEZ_Yhq1kDkWgZXD9NrkYw1m0SZXsip9NiczcFpKX1A@mail.gmail.com>
From: =?ISO-8859-1?Q?Jo=E3o_Matos?= <jaoneto@gmail.com>
Date: Mon, 28 Jan 2013 11:44:41 -0300
Message-ID: <CAP4tJZ+rftyHN5KmhG-1u_SkXNg4OP91sYfTBGpWgi59FDBTOA@mail.gmail.com>
Subject: Re: [gentoo-user] Systemd reaches "target Emergency Mode" every boot
To: gentoo-user@lists.gentoo.org
Content-Type: multipart/alternative; boundary=14dae93405fd6caf6304d45a528b
X-Archives-Salt: 6407c65d-ec06-4b14-843c-0030d4ba0f5a
X-Archives-Hash: f8eba90258e4fa1f732941d02a6a8d29
--14dae93405fd6caf6304d45a528b
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
2013/1/28 Mike Gilbert <floppym@gentoo.org>
> On Sun, Jan 27, 2013 at 10:07 PM, Jo=E3o Matos <jaoneto@gmail.com> wrote:
> > title Gentoo Linux 3.7.1 systemd
> > root (hd0,0)
> > kernel /boot/thekernel2 root=3D/dev/sda1 rootfstype=3Dext4 init=3D/bin/=
systemd
> > vga=3D0x31B resume=3D/dev/sda3 journalctl -b
> >
>
> Why do you have "journalctl -b" in there? That makes no sense.
>
> Also, the "-b" is what is causing systemd to start emergency.target.
>
Well, removing it did solve my problem!
The interesting fact is that the problem started, but I had no log info
during the boot process. So I put "journalctl -b" to see the boot info.
Since them I have the boot info (not just a black screen).
Probably the problem was solved long time ago and the "-b" didn't let me
notice it.
Thank you. :)
--=20
Jo=E3o de Matos
Linux User #461527
Graduando em Engenharia de Computa=E7=E3o 2005.1
UEFS - Universidade Estadual de Feira de Santana
--14dae93405fd6caf6304d45a528b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">2013/1/28 Mike Gilbert <span dir=3D"ltr"><<a href=3D"mailto:flop=
pym@gentoo.org" target=3D"_blank">floppym@gentoo.org</a>></span><br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">
<div class=3D"im">On Sun, Jan 27, 2013 at 10:07 PM, Jo=E3o Matos <<a hre=
f=3D"mailto:jaoneto@gmail.com">jaoneto@gmail.com</a>> wrote:<br>
> title Gentoo Linux 3.7.1 systemd<br>
> root (hd0,0)<br>
> kernel /boot/thekernel2 root=3D/dev/sda1 rootfstype=3Dext4 init=3D/bin=
/systemd<br>
> vga=3D0x31B resume=3D/dev/sda3 journalctl -b<br>
><br>
<br>
</div>Why do you have "journalctl -b" in there? That makes no sen=
se.<br>
<br>
Also, the "-b" is what is causing systemd to start emergency.targ=
et.<br></blockquote><div><br></div><div>Well, removing it did solve my prob=
lem!<br><br></div><div>The interesting fact is that the problem started, bu=
t I had no log info during the boot process. So I put "journalctl -b&q=
uot; to see the boot info. Since them I have the boot info (not just a blac=
k screen).<br>
<br></div><div>Probably the problem was solved long time ago and the "=
-b" didn't let me notice it.<br><br></div><div>Thank you. :)<br></=
div><div>=A0</div></div><br><br clear=3D"all"><br>-- <br>Jo=E3o de Matos<br=
>
Linux User #461527<br>
Graduando em Engenharia de Computa=E7=E3o 2005.1<br>UEFS - Universidade Est=
adual de Feira de Santana
</div></div>
--14dae93405fd6caf6304d45a528b--