error-message when shutting down system, yet shutdown works well
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
error-message when shutting down system, yet shutdown works well
Hi altogether,
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 really fast.
journalctl shows me:
Code:
[...]
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 some process is still using /home.
Now I issued the command
Code:
fuser -mv /home
in order to find out more.
So at the time of shutdown it looks like this:
O.K., now Iīve tried this option, too. But thereīs no difference. The problem remains.
Is there another way of finding out what keeps /home busy so that unmounting fails?
Just so I can understand, when you select Shut Down from the desktop environment menu, does it (i) take its time shutting down but you still see error messages in the logs, or (ii) produce a warning message that something is keeping the system busy? If the latter, which option do you select (keep waiting or force shutdown)?
Ok. I assume you're running Lubuntu or similar. Which version of systemd?
Can you try starting up the system from scratch, log in, wait 5 minutes without doing anything at all, and then log out through the main menu and see if the problem occurs. Thanks.
Can you try starting up the system from scratch, log in, wait 5 minutes without doing anything at all, and then log out through the main menu and see if the problem occurs. Thanks.
O.K., Iīm going to do that now and then report back to you.
So: two entries of pulseaudio!
After that I logged out and issued the same command in a virtual console:
Code:
rosika 1970 F...m pulseaudio
is still running.
It would be interesting to know why there are two instances of pulseaudio running in the first place. And
why keeps the one with PID 1970 running?
Ah, now. I have to admit that I'm no expert on this and was just hoping to see if we could narrow it down to which application or combination of applications was causing the problem by trial and error, i.e. rebooting the computer and starting different "usual" applications and then shutting down to see if the error is generated. It could be pulseaudio. If you shutdown when those double pulseaudio processes are running, do you get the shutdown error?
It could be pulseaudio. If you shutdown when those double pulseaudio processes are running, do you get the shutdown error?
It seems that pulseaudio is the culprit.
Under normal circumstances there are those two pulseaudio-instances running. During the shutdown-process one of them gets cancelled but not the other one. And this one seems to be responsible for still accessing /home.
I tried this method: Before shutting down I identified the pulseaudio-processes with
Code:
ps aux | grep pulseaudio
and the killed both of them with kill .
After that I shut down the system and didnīt get the error-message.
Iīve just looked up my journalctl-log :
And that was after extensive use of the system (about 2 hs). So it seems like we really could norrow it down.
Iīve still got to look at the shutdown-messages in the near future to verify it, but it looks promising.
Thanks. If you don't mind experimenting, try setting autospawn to no (remove the ; comment character at the start of the line), reboot and see if there is any difference.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
