error-message when shutting down system, yet shutdown works well
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
when shutting down my system I use the terminal-command shutdown -H -P +0 or poweroff. For me that´s a good way of achieving that goal
and it works well.
I changed my grub-config from
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="noplymouth"
in order to get
screen output of the logs.
An here I saw an entry reading "failed unmounting /home" (in red). After that came some more messages which all were O.K. Everything else was in green with an "O.K." in front.
I don´t know why I get this message because the shutdown works well. In fact it shuts down so fast that it´s virtually impossible to read
the rest of the messages.
Any ideas what might be the cause of the "failed unmounting /home"-message?
Journalctl says:
Apr 05 18:16:19 rosika-Lenovo-H520e umount[25556]: umount: /home: das Ziel wird gerade benutzt.
Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/28BC-DAFC...
Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1...
Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: home.mount: Mount process exited, code=exited status=32 Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Failed unmounting /home
So basically a process seems to be running which prevents unmounting.
Further info:
Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Failed with result 'exit-code'
P.S.:
my system: Linux/Lubuntu 18.04.2 LTS, 64 bit
shutdown
asked Apr 6 at 11:23
RosikaRosika
18711
|
show 3 more comments
when shutting down my system I use the terminal-command shutdown -H -P +0 or poweroff. For me that´s a good way of achieving that goal
and it works well.
I changed my grub-config from
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="noplymouth"
in order to get
screen output of the logs.
An here I saw an entry reading "failed unmounting /home" (in red). After that came some more messages which all were O.K. Everything else was in green with an "O.K." in front.
I don´t know why I get this message because the shutdown works well. In fact it shuts down so fast that it´s virtually impossible to read
the rest of the messages.
Any ideas what might be the cause of the "failed unmounting /home"-message?
Journalctl says:
Apr 05 18:16:19 rosika-Lenovo-H520e umount[25556]: umount: /home: das Ziel wird gerade benutzt.
Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/28BC-DAFC...
Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1...
Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: home.mount: Mount process exited, code=exited status=32 Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Failed unmounting /home
So basically a process seems to be running which prevents unmounting.
Further info:
Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Failed with result 'exit-code'
P.S.:
my system: Linux/Lubuntu 18.04.2 LTS, 64 bit
shutdown
asked Apr 6 at 11:23
RosikaRosika
18711
please include relevant parts ofjournalctlinto the question and it is a bug. You get this if there is a service using /home/ that was not stopped before the shutdown started. Example: github.com/systemd/systemd/issues/6956 Identify the service that was not stopped and file a bug report :)
– Rinzwind
Apr 6 at 11:30
Tnx. Journalctl says:Apr 05 18:16:19 rosika-Lenovo-H520e umount[25556]: umount: /home: das Ziel wird gerade benutzt. Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/28BC-DAFC... Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1... Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: home.mount: Mount process exited, code=exited status=32 Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Failed unmounting /homeSo basically a process seems to be running which prevents unmounting. But I´m bit at a loss here.
– Rosika
Apr 6 at 11:52
>> Identify the service that was not stopped and file a bug report...... Not sure how to do that.
– Rosika
Apr 6 at 11:55
I found:Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Failed with result 'exit-code'.Could that be the culprit?
– Rosika
Apr 6 at 12:04
edit it into the question please. and yes.
– Rinzwind
Apr 6 at 12:46
|
show 3 more comments
when shutting down my system I use the terminal-command shutdown -H -P +0 or poweroff. For me that´s a good way of achieving that goal
and it works well.
I changed my grub-config from
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="noplymouth"
in order to get
screen output of the logs.
An here I saw an entry reading "failed unmounting /home" (in red). After that came some more messages which all were O.K. Everything else was in green with an "O.K." in front.
I don´t know why I get this message because the shutdown works well. In fact it shuts down so fast that it´s virtually impossible to read
the rest of the messages.
Any ideas what might be the cause of the "failed unmounting /home"-message?
Journalctl says:
Apr 05 18:16:19 rosika-Lenovo-H520e umount[25556]: umount: /home: das Ziel wird gerade benutzt.
Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/28BC-DAFC...
Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1...
Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: home.mount: Mount process exited, code=exited status=32 Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Failed unmounting /home
So basically a process seems to be running which prevents unmounting.
Further info:
Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Failed with result 'exit-code'
P.S.:
my system: Linux/Lubuntu 18.04.2 LTS, 64 bit
shutdown
asked Apr 6 at 11:23
RosikaRosika
18711
when shutting down my system I use the terminal-command shutdown -H -P +0 or poweroff. For me that´s a good way of achieving that goal
and it works well.
I changed my grub-config from
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="noplymouth"
in order to get
screen output of the logs.
An here I saw an entry reading "failed unmounting /home" (in red). After that came some more messages which all were O.K. Everything else was in green with an "O.K." in front.
I don´t know why I get this message because the shutdown works well. In fact it shuts down so fast that it´s virtually impossible to read
the rest of the messages.
Any ideas what might be the cause of the "failed unmounting /home"-message?
Journalctl says:
Apr 05 18:16:19 rosika-Lenovo-H520e umount[25556]: umount: /home: das Ziel wird gerade benutzt.
Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/28BC-DAFC...
Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1...
Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: home.mount: Mount process exited, code=exited status=32 Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Failed unmounting /home
So basically a process seems to be running which prevents unmounting.
Further info:
Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Failed with result 'exit-code'
P.S.:
my system: Linux/Lubuntu 18.04.2 LTS, 64 bit
shutdown
shutdown
asked Apr 6 at 11:23
RosikaRosika
18711
asked Apr 6 at 11:23
RosikaRosika
18711
edited Apr 6 at 13:24
Rosika
asked Apr 6 at 11:23
RosikaRosika
18711
asked Apr 6 at 11:23
RosikaRosika
18711
asked Apr 6 at 11:23
RosikaRosika
18711
18711
please include relevant parts ofjournalctlinto the question and it is a bug. You get this if there is a service using /home/ that was not stopped before the shutdown started. Example: github.com/systemd/systemd/issues/6956 Identify the service that was not stopped and file a bug report :)
– Rinzwind
Apr 6 at 11:30
Tnx. Journalctl says:Apr 05 18:16:19 rosika-Lenovo-H520e umount[25556]: umount: /home: das Ziel wird gerade benutzt. Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/28BC-DAFC... Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1... Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: home.mount: Mount process exited, code=exited status=32 Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Failed unmounting /homeSo basically a process seems to be running which prevents unmounting. But I´m bit at a loss here.
– Rosika
Apr 6 at 11:52
>> Identify the service that was not stopped and file a bug report...... Not sure how to do that.
– Rosika
Apr 6 at 11:55
I found:Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Failed with result 'exit-code'.Could that be the culprit?
– Rosika
Apr 6 at 12:04
edit it into the question please. and yes.
– Rinzwind
Apr 6 at 12:46
|
show 3 more comments
please include relevant parts ofjournalctlinto the question and it is a bug. You get this if there is a service using /home/ that was not stopped before the shutdown started. Example: github.com/systemd/systemd/issues/6956 Identify the service that was not stopped and file a bug report :)
– Rinzwind
Apr 6 at 11:30
Tnx. Journalctl says:Apr 05 18:16:19 rosika-Lenovo-H520e umount[25556]: umount: /home: das Ziel wird gerade benutzt. Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/28BC-DAFC... Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1... Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: home.mount: Mount process exited, code=exited status=32 Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Failed unmounting /homeSo basically a process seems to be running which prevents unmounting. But I´m bit at a loss here.
– Rosika
Apr 6 at 11:52
>> Identify the service that was not stopped and file a bug report...... Not sure how to do that.
– Rosika
Apr 6 at 11:55
I found:Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Failed with result 'exit-code'.Could that be the culprit?
– Rosika
Apr 6 at 12:04
edit it into the question please. and yes.
– Rinzwind
Apr 6 at 12:46
please include relevant parts of
journalctl into the question and it is a bug. You get this if there is a service using /home/ that was not stopped before the shutdown started. Example: github.com/systemd/systemd/issues/6956 Identify the service that was not stopped and file a bug report :)– Rinzwind
Apr 6 at 11:30
please include relevant parts of
journalctl into the question and it is a bug. You get this if there is a service using /home/ that was not stopped before the shutdown started. Example: github.com/systemd/systemd/issues/6956 Identify the service that was not stopped and file a bug report :)– Rinzwind
Apr 6 at 11:30
Tnx. Journalctl says:
Apr 05 18:16:19 rosika-Lenovo-H520e umount[25556]: umount: /home: das Ziel wird gerade benutzt. Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/28BC-DAFC... Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1... Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: home.mount: Mount process exited, code=exited status=32 Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Failed unmounting /home So basically a process seems to be running which prevents unmounting. But I´m bit at a loss here.– Rosika
Apr 6 at 11:52
Tnx. Journalctl says:
Apr 05 18:16:19 rosika-Lenovo-H520e umount[25556]: umount: /home: das Ziel wird gerade benutzt. Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/28BC-DAFC... Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1... Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: home.mount: Mount process exited, code=exited status=32 Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Failed unmounting /home So basically a process seems to be running which prevents unmounting. But I´m bit at a loss here.– Rosika
Apr 6 at 11:52
>> Identify the service that was not stopped and file a bug report...... Not sure how to do that.
– Rosika
Apr 6 at 11:55
>> Identify the service that was not stopped and file a bug report...... Not sure how to do that.
– Rosika
Apr 6 at 11:55
I found:
Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Failed with result 'exit-code'. Could that be the culprit?– Rosika
Apr 6 at 12:04
I found:
Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Failed with result 'exit-code'. Could that be the culprit?– Rosika
Apr 6 at 12:04
edit it into the question please. and yes.
– Rinzwind
Apr 6 at 12:46
edit it into the question please. and yes.
– Rinzwind
Apr 6 at 12:46
|
show 3 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1131650%2ferror-message-when-shutting-down-system-yet-shutdown-works-well%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1131650%2ferror-message-when-shutting-down-system-yet-shutdown-works-well%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
please include relevant parts of
journalctlinto the question and it is a bug. You get this if there is a service using /home/ that was not stopped before the shutdown started. Example: github.com/systemd/systemd/issues/6956 Identify the service that was not stopped and file a bug report :)– Rinzwind
Apr 6 at 11:30
Tnx. Journalctl says:
Apr 05 18:16:19 rosika-Lenovo-H520e umount[25556]: umount: /home: das Ziel wird gerade benutzt. Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/28BC-DAFC... Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Unmounting /media/rosika/f14a27c2-0b49-4607-94ea-2e56bbf76fe1... Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: home.mount: Mount process exited, code=exited status=32 Apr 05 18:16:19 rosika-Lenovo-H520e systemd[1]: Failed unmounting /homeSo basically a process seems to be running which prevents unmounting. But I´m bit at a loss here.– Rosika
Apr 6 at 11:52
>> Identify the service that was not stopped and file a bug report...... Not sure how to do that.
– Rosika
Apr 6 at 11:55
I found:
Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE Apr 05 18:16:17 rosika-Lenovo-H520e systemd[1552]: xfce4-notifyd.service: Failed with result 'exit-code'.Could that be the culprit?– Rosika
Apr 6 at 12:04
edit it into the question please. and yes.
– Rinzwind
Apr 6 at 12:46