| 1 |
On Sat, Mar 21, 2015 at 11:21 AM, Daniel Frey <djqfrey@×××××.com> wrote: |
| 2 |
> Hi list, |
| 3 |
|
| 4 |
Hi. |
| 5 |
|
| 6 |
> In one of my earlier posts I mentioned I wasn't having any issues with |
| 7 |
> systemd. Well, I guess I lied, although I didn't know about it at the |
| 8 |
time. |
| 9 |
> |
| 10 |
> My laptop works fine, no issues. |
| 11 |
> |
| 12 |
> My desktop, however, has an issue, but only while rebooting. I use mdadm |
| 13 |
> to access my IMSM raid, and during the reboot process, the last message |
| 14 |
> I see is (from memory, so it's not exact): |
| 15 |
> |
| 16 |
> "Stopping mdmon..." |
| 17 |
> |
| 18 |
> And it hangs there. |
| 19 |
> |
| 20 |
> The journal shows this: |
| 21 |
> ===== |
| 22 |
> -- Reboot -- |
| 23 |
> Mar 18 20:48:42 osoikaze systemd-journal[485]: Journal stopped |
| 24 |
> Mar 18 20:48:42 osoikaze systemd-shutdown[1]: Sending SIGTERM to |
| 25 |
> remaining processes... |
| 26 |
> Mar 18 20:48:41 osoikaze systemd[1]: Shutting down. |
| 27 |
> |
| 28 |
> ===== |
| 29 |
> |
| 30 |
> mdmon is normally stopped right at the end, so it should be a part of |
| 31 |
> 'Sending SIGTERM to remaining processes'. The Journal stops, then from |
| 32 |
> what I gather, it hangs on the next one, which is mdmon. I have left it |
| 33 |
> for a half an hour and it doesn't do anything. |
| 34 |
> |
| 35 |
> When rebooting: |
| 36 |
> |
| 37 |
> ===== |
| 38 |
> Mar 18 20:49:39 osoikaze kernel: md/raid10:md126: active with 4 out of 4 |
| 39 |
> devices |
| 40 |
> Mar 18 20:49:39 osoikaze kernel: md/raid10:md126: not clean -- starting |
| 41 |
> background reconstruction |
| 42 |
> Mar 18 20:49:39 osoikaze kernel: md: bind<sdi> |
| 43 |
> Mar 18 20:49:39 osoikaze kernel: md: bind<sdh> |
| 44 |
> Mar 18 20:49:39 osoikaze kernel: md: bind<sdg> |
| 45 |
> Mar 18 20:49:39 osoikaze kernel: md: bind<sdf> |
| 46 |
> Mar 18 20:49:39 osoikaze kernel: md: bind<sdi> |
| 47 |
> Mar 18 20:49:39 osoikaze kernel: md: bind<sdg> |
| 48 |
> ===== |
| 49 |
> |
| 50 |
> Indicating that mdmon was not stopped properly. (The array starts a |
| 51 |
> rebuild.) Checking /proc/mdstat confirms this. |
| 52 |
> |
| 53 |
> Now this is the odd thing: `systemctl poweroff` works fine! It shuts |
| 54 |
> everything down, and turns my workstation off without corrupting the |
| 55 |
> RAID array! |
| 56 |
> |
| 57 |
> So why does `systemctl reboot` not want to work? I'm a little confused. |
| 58 |
|
| 59 |
What kind of initramfs are you using? Supposedly, the only difference |
| 60 |
between poweroff and reboot is that the former turns off the machine and |
| 61 |
reboot does a reset. In either case, systemd pivots back to the initramfs |
| 62 |
before umounting everything, so perhaps there lies the problem. |
| 63 |
|
| 64 |
> I also noticed this in the USE flags for systemd: |
| 65 |
> - - sysv-utils : Install sysvinit compatibility |
| 66 |
> symlinks and manpages for init, telinit, halt, poweroff, reboot, |
| 67 |
> runlevel, and shutdown |
| 68 |
> |
| 69 |
> Should I enable that USE flag? |
| 70 |
|
| 71 |
No. In Gentoo in particular the SysV compatibility is completely useless. |
| 72 |
|
| 73 |
> (By the way, KDE shows the same behaviour. If I shutdown with the K |
| 74 |
> Menu, it works. Reboot from the K Menu hangs.) |
| 75 |
|
| 76 |
KDE (as GNOME, Xfce, and everything else) uses logind, so it's equivalent |
| 77 |
to do "systemctl poweroff" or click "Power Off" in your DE. |
| 78 |
|
| 79 |
I would bet on the initramfs. |
| 80 |
|
| 81 |
Regards. |
| 82 |
-- |
| 83 |
Canek Peláez Valdés |
| 84 |
Profesor de asignatura, Facultad de Ciencias |
| 85 |
Universidad Nacional Autónoma de México |
Archives