public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "João Matos" <jaoneto@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Systemd reaches "target Emergency Mode" every boot
Date: Sun, 27 Jan 2013 18:23:15 -0300	[thread overview]
Message-ID: <CAP4tJZLatPinPwh3phUpD6FkKiVnYzs3kdAHgZZveYPJTMNEag@mail.gmail.com> (raw)
In-Reply-To: <CADPrc83g9GSJipFj4F4TEcJE8Tw7Fi1UMXeE48aGR_jo5efFgw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4038 bytes --]

2013/1/27 Canek Peláez Valdés <caneko@gmail.com>

> On Sun, Jan 27, 2013 at 12:31 PM, João Matos <jaoneto@gmail.com> wrote:
> >
> >
> >
> > 2013/1/26 Canek Peláez Valdés <caneko@gmail.com>
> >>
> >> On Sat, Jan 26, 2013 at 7:08 PM, João Matos <jaoneto@gmail.com> wrote:
> >> > Hi list,
> >> >
> >> > I'm having this problem for a while, but I've decided to solve it
> know.
> >> > Every time I boot my system (couple times a day), I have to hid Ctrl
> + D
> >> > when the boot process is interrupted by the "emergency mode".
> >> >
> >> > I think it started when I was compiling the kernel myself, and
> removing
> >> > lot
> >> > of stuff. Although, I checked and the mandatory options for systemd
> are
> >> > ok.
> >> >
> >> > When I run "journalctl -b -p err" the only information I get is:
> >> >
> >> > Jan 26 20:29:20 KONOHA NetworkManager[1497]: claim_connection:
> assertion
> >> > `nm_connection_get_path (NM_CONNECTION (connection)) == NULL' failed
> >> > Jan 26 20:29:24 localhost dhcpcd[1557]: wlan0: sendmsg: Cannot assign
> >> > requested address
> >> > Jan 26 20:30:42 localhost pulseaudio[2073]: [pulseaudio] pid.c: Daemon
> >> > already running.
> >> > Jan 26 20:30:42 localhost pulseaudio[2080]: [pulseaudio] pid.c: Daemon
> >> > already running.
> >> >
> >> >  It give me no clue.
> >> >
> >> > Attached the .conf from my gentoo-3.7.1
> >> >
> >> > After I hit Ctrl + D, the system works normally.
> >> >
> >> > Any help will be appreciated :)
> >>
> >> Are you using udev-197 with systemd-197? mgorny masked it, and said
> >> this in package.mask:
> >
> >
> > I'm using them. Last time I updated my system there weren't any warning.
> > Anyway, this problem is happening since the previous version.
> >
> >>
> >> # Does not boot. Something with udev is probably broken. Feel free
> >> # to unmask, debug and provide me with a patch.
> >>
> >> You need to be using the same version for udev and systemd (they are
> >> the same package). If you are using the same version for udev and
> >> systemd, are you using an initramfs? When was the last time you built
> >> it, if you do?
> >
> >
> > I don't have initramfs. Just the kernel. But it used to work normaly.
> >>
> >>
> >> Could you boot with "systemd.log_target=kmsg" and
> >> "systemd.log_level=debug", and post the whole output of "journalctl
> >> -b"? It prints only the logs from the last boot.
> >>
> >
> > journalctl -b attached.
>
> From your logs:
>
> Jan 27 15:16:27 KONOHA systemd[1]: Activating default unit:
> emergency.target
>
> You have emergency.target as default unit. The default.target can be
> set in different ways:
>
> - Check /usr/lib64/systemd/system/default.target
>

Nothing found here. The file is:

[Unit]
Description=Graphical Interface
Documentation=man:systemd.special(7)
Requires=multi-user.target
After=multi-user.target
Conflicts=rescue.target
Wants=display-manager.service
AllowIsolate=yes

[Install]
Alias=default.target


- Check /etc/systemd/system/default.target
>

doesn't exist.


> - Check if you use --unit=emergency.target in your grub config
> - Check if you pass the "emergency" kernel parametr in your grub config
>

Nothing wrong with grub.


> udev-197 in the tree installs everything to /; systemd-197 installs to
> /usr. I'm pretty sure that is not going to end well; I haven't
> upgraded to 197 in neither package.
>
> Check your default.target; for some reason is set to emergency.
>
> Regards.
> --
> Canek Peláez Valdés
> Posgrado en Ciencia e Ingeniería de la Computación
> Universidad Nacional Autónoma de México
>
>
I've also tryed "systemctl disable emergency.service" and "systemctl
disable emergency.target" before but got nothing.

Anyway, thank you for your help :). I'll try to downgrade. But I still
think it is about kernel config.

-- 
João de Matos
Linux User #461527
Graduando em Engenharia de Computação 2005.1
UEFS - Universidade Estadual de Feira de Santana

[-- Attachment #2: Type: text/html, Size: 5973 bytes --]

  reply	other threads:[~2013-01-27 21:23 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-27  1:08 [gentoo-user] Systemd reaches "target Emergency Mode" every boot João Matos
2013-01-27  2:42 ` Canek Peláez Valdés
2013-01-27 18:31   ` João Matos
2013-01-27 21:08     ` Canek Peláez Valdés
2013-01-27 21:23       ` João Matos [this message]
2013-01-27 22:14         ` João Matos
2013-01-27 22:28           ` Mike Gilbert
2013-01-28  3:07             ` João Matos
2013-01-28  5:21               ` Mike Gilbert
2013-01-28 14:44                 ` João Matos
2013-01-28 19:01       ` Stefan G. Weichinger
2013-01-28 19:08         ` Canek Peláez Valdés
2013-01-28 19:25           ` Stefan G. Weichinger
2013-01-28 19:34             ` Canek Peláez Valdés
2013-01-28 20:04               ` Canek Peláez Valdés
2013-01-28 21:08               ` Stefan G. Weichinger
2013-01-28 21:27                 ` Canek Peláez Valdés
2013-01-28 21:49                   ` Stefan G. Weichinger
2013-01-29 16:32                     ` [gentoo-user] *draft* for setting up network bridge with systemd (for qemu/kvm) Stefan G. Weichinger
2013-01-29 18:57                       ` Canek Peláez Valdés
2013-01-29 19:05                         ` Michael Mol
2013-01-29 19:22                           ` Stefan G. Weichinger
2013-01-29 19:33                             ` Canek Peláez Valdés
2013-01-29 19:48                               ` Stefan G. Weichinger
2013-02-05 22:00                                 ` Stefan G. Weichinger
2013-02-05 22:37                                   ` Stefan G. Weichinger
2013-01-29 19:23                           ` Canek Peláez Valdés
2013-01-29 19:33                             ` Stefan G. Weichinger
2013-01-29 19:49                               ` Canek Peláez Valdés
2013-01-29 20:00                                 ` Alon Bar-Lev
2013-01-29 20:21                                   ` Canek Peláez Valdés
2013-01-29 21:10                                     ` Kevin Chadwick
2013-01-29 22:04                                       ` Canek Peláez Valdés
2013-01-30 12:56                               ` Stefan G. Weichinger
2013-01-28 21:08         ` [gentoo-user] Systemd reaches "target Emergency Mode" every boot João Matos

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=CAP4tJZLatPinPwh3phUpD6FkKiVnYzs3kdAHgZZveYPJTMNEag@mail.gmail.com \
    --to=jaoneto@gmail.com \
    --cc=gentoo-user@lists.gentoo.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