| 1 |
Hi list, |
| 2 |
|
| 3 |
In one of my earlier posts I mentioned I wasn't having any issues with |
| 4 |
systemd. Well, I guess I lied, although I didn't know about it at the time. |
| 5 |
|
| 6 |
My laptop works fine, no issues. |
| 7 |
|
| 8 |
My desktop, however, has an issue, but only while rebooting. I use mdadm |
| 9 |
to access my IMSM raid, and during the reboot process, the last message |
| 10 |
I see is (from memory, so it's not exact): |
| 11 |
|
| 12 |
"Stopping mdmon..." |
| 13 |
|
| 14 |
And it hangs there. |
| 15 |
|
| 16 |
The journal shows this: |
| 17 |
===== |
| 18 |
-- Reboot -- |
| 19 |
Mar 18 20:48:42 osoikaze systemd-journal[485]: Journal stopped |
| 20 |
Mar 18 20:48:42 osoikaze systemd-shutdown[1]: Sending SIGTERM to |
| 21 |
remaining processes... |
| 22 |
Mar 18 20:48:41 osoikaze systemd[1]: Shutting down. |
| 23 |
|
| 24 |
===== |
| 25 |
|
| 26 |
mdmon is normally stopped right at the end, so it should be a part of |
| 27 |
'Sending SIGTERM to remaining processes'. The Journal stops, then from |
| 28 |
what I gather, it hangs on the next one, which is mdmon. I have left it |
| 29 |
for a half an hour and it doesn't do anything. |
| 30 |
|
| 31 |
When rebooting: |
| 32 |
|
| 33 |
===== |
| 34 |
Mar 18 20:49:39 osoikaze kernel: md/raid10:md126: active with 4 out of 4 |
| 35 |
devices |
| 36 |
Mar 18 20:49:39 osoikaze kernel: md/raid10:md126: not clean -- starting |
| 37 |
background reconstruction |
| 38 |
Mar 18 20:49:39 osoikaze kernel: md: bind<sdi> |
| 39 |
Mar 18 20:49:39 osoikaze kernel: md: bind<sdh> |
| 40 |
Mar 18 20:49:39 osoikaze kernel: md: bind<sdg> |
| 41 |
Mar 18 20:49:39 osoikaze kernel: md: bind<sdf> |
| 42 |
Mar 18 20:49:39 osoikaze kernel: md: bind<sdi> |
| 43 |
Mar 18 20:49:39 osoikaze kernel: md: bind<sdg> |
| 44 |
===== |
| 45 |
|
| 46 |
Indicating that mdmon was not stopped properly. (The array starts a |
| 47 |
rebuild.) Checking /proc/mdstat confirms this. |
| 48 |
|
| 49 |
Now this is the odd thing: `systemctl poweroff` works fine! It shuts |
| 50 |
everything down, and turns my workstation off without corrupting the |
| 51 |
RAID array! |
| 52 |
|
| 53 |
So why does `systemctl reboot` not want to work? I'm a little confused. |
| 54 |
|
| 55 |
I also noticed this in the USE flags for systemd: |
| 56 |
- - sysv-utils : Install sysvinit compatibility |
| 57 |
symlinks and manpages for init, telinit, halt, poweroff, reboot, |
| 58 |
runlevel, and shutdown |
| 59 |
|
| 60 |
Should I enable that USE flag? |
| 61 |
|
| 62 |
(By the way, KDE shows the same behaviour. If I shutdown with the K |
| 63 |
Menu, it works. Reboot from the K Menu hangs.) |
| 64 |
|
| 65 |
Dan |
Archives