public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Frey <djqfrey@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] OK, so not everything works properly with systemd
Date: Sat, 21 Mar 2015 10:21:13 -0700	[thread overview]
Message-ID: <550DA889.30000@gmail.com> (raw)

Hi list,

In one of my earlier posts I mentioned I wasn't having any issues with
systemd. Well, I guess I lied, although I didn't know about it at the time.

My laptop works fine, no issues.

My desktop, however, has an issue, but only while rebooting. I use mdadm
to access my IMSM raid, and during the reboot process, the last message
I see is (from memory, so it's not exact):

"Stopping mdmon..."

And it hangs there.

The journal shows this:
=====
-- Reboot --
Mar 18 20:48:42 osoikaze systemd-journal[485]: Journal stopped
Mar 18 20:48:42 osoikaze systemd-shutdown[1]: Sending SIGTERM to
remaining processes...
Mar 18 20:48:41 osoikaze systemd[1]: Shutting down.

=====

mdmon is normally stopped right at the end, so it should be a part of
'Sending SIGTERM to remaining processes'. The Journal stops, then from
what I gather, it hangs on the next one, which is mdmon. I have left it
for a half an hour and it doesn't do anything.

When rebooting:

=====
Mar 18 20:49:39 osoikaze kernel: md/raid10:md126: active with 4 out of 4
devices
Mar 18 20:49:39 osoikaze kernel: md/raid10:md126: not clean -- starting
background reconstruction
Mar 18 20:49:39 osoikaze kernel: md: bind<sdi>
Mar 18 20:49:39 osoikaze kernel: md: bind<sdh>
Mar 18 20:49:39 osoikaze kernel: md: bind<sdg>
Mar 18 20:49:39 osoikaze kernel: md: bind<sdf>
Mar 18 20:49:39 osoikaze kernel: md: bind<sdi>
Mar 18 20:49:39 osoikaze kernel: md: bind<sdg>
=====

Indicating that mdmon was not stopped properly. (The array starts a
rebuild.) Checking /proc/mdstat confirms this.

Now this is the odd thing: `systemctl poweroff` works fine! It shuts
everything down, and turns my workstation off without corrupting the
RAID array!

So why does `systemctl reboot` not want to work? I'm a little confused.

I also noticed this in the USE flags for systemd:
- - sysv-utils                     : Install sysvinit compatibility
symlinks and manpages for init, telinit, halt, poweroff, reboot,
runlevel, and shutdown

Should I enable that USE flag?

(By the way, KDE shows the same behaviour. If I shutdown with the K
Menu, it works. Reboot from the K Menu hangs.)

Dan


             reply	other threads:[~2015-03-21 17:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-21 17:21 Daniel Frey [this message]
2015-03-21 17:27 ` [gentoo-user] OK, so not everything works properly with systemd Canek Peláez Valdés
2015-03-21 21:38   ` Daniel Frey
2015-03-21 21:46     ` Canek Peláez Valdés
2015-04-01  2:26       ` Daniel Frey
2015-04-01  2:42       ` Daniel Frey
2015-03-21 17:51 ` Tom H

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=550DA889.30000@gmail.com \
    --to=djqfrey@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