Linux not shutting down

[CygXanadu]

When I first installed Linux mint 19.3 I was happy that it was shutting down properly, now it stopped doing that, what happened?

[CygXanadu]

Please fix the shutdown issue, it was present with 19.2, now 19.3 has it. It was working fine the first time I installed 19.3 and used a Mirror from the USA to do the first updates that Mirror must have had the shutdown fix, now that Mirror is no longer available. I don't know what Kernel has that fix. I don't want to change kernels as some functions may not work properly or work at all.

[CygXanadu]

Does anyone have shutdown issues with 19.3 and is it on a separate machine?

[Hoser Rob]

You want help, ask your questions properly. Read this: viewtopic.php?f=17&t=83444

[Pjotr]

Do not assume that *your* problem happens on *all* (or most, or many) hardware combinations. For instance, my computers aren't affected.

[JoeFootball]

Does anyone have shutdown issues with 19.3 and is it on a separate machine?

I have a several LM 19.3 installations on a few desktops & laptops. All shutdown without incident.

[karlchen]

Hello, CygXanadu.

When I first installed Linux mint 19.3 I was happy that it was shutting down properly, now it stopped doing that, what happened?

Could you, please, elaborate on which symptoms you notice, since your LM19.3 Cinnamon started to shut down properly no longer?
What does "not shutting down properly" mean in your case?
Does it take very long to shutdown? - Like in: it used to shut down within 7 seconds, now it takes more than 90 seconds?
Does the machine no longer power off at the end of the shutdown procedure?
What else?

Best regards,
Karl

[militiaDei]

Does anyone have shutdown issues with 19.3 and is it on a separate machine?

I have this problem on my laptop which is too short on RAM. Could be the problem, involving the over-usage of swap...
My 2 cents...

[Resistor]

I had this problem on an external SSD.

The problem seemed to be that the installer does not install grub where you tell it to install grub.

The installer says it complied, but apparently it did something else, on its on.
The EFI partition size suggested it was not even looked at.

I fixed it by installing grub to the EFI partition on the external SSD.
I don't recall if I did it from a live session or from one installed on the HDD.

[italia]

My new installation of 19.3 Cinnamon was shutting down properly but now it is hanging during shutdown with a flashing cursor in upper left of black screen. I did go through the suggestions in the "Easy Linux Tips Project: ..." as well as the one to make your Linux Mint run faster, but not sure if those changes (ex. reducing swappiness from 60 to 10) would be causing it to hang during shutdown. My installation is a dual boot Windows XP/19.3 Cinnamon HP Laptop

[CygXanadu]

Hello, CygXanadu.

When I first installed Linux mint 19.3 I was happy that it was shutting down properly, now it stopped doing that, what happened?

Could you, please, elaborate on which symptoms you notice, since your LM19.3 Cinnamon started to shut down properly no longer?
What does "not shutting down properly" mean in your case?
Does it take very long to shutdown? - Like in: it used to shut down within 7 seconds, now it takes more than 90 seconds?
Does the machine no longer power off at the end of the shutdown procedure?
What else?

Best regards,
Karl

It shut down fine when I first installed 19.3, then I had issues with trying to delete software I had to reinstall 19.3
Small mint logo on the monitor when I saw that it shut down properly within seconds(5-7) now it takes forever, I have to manually power it off ( hold the power button).

[Moem]

I have to manually power it off ( hold the power button).

That's a great way to damage your file system. What happens if you open a terminal and enter the following command:

Code: Select all

shutdown -Ph now

[AndyMH]

I have to manually power it off ( hold the power button).

Don't do that! Most of the time you will get away with it but you might trash your filesystem.

If the system locks up and won't shut down type Alt + PrtScn + REISUO (for shutdown) or REISUB (for reboot). Keep the alt key pressed the whole time.

[CygXanadu]

I have to manually power it off ( hold the power button).

That's a great way to damage your file system. What happens if you open a terminal and enter the following command:

Code: Select all

shutdown -Ph now

I don't just shut it down I choose the option then wait 60 seconds before I just hold the power button until it turns off, it powers up fine any other time. I just cannot figure out why it does not shut down properly now when it worked the first time I installed 19.3

[karlchen]

Hello, CygXanadu.

Chances are not bad that the system has logged during (unsuccessful) shutdown what prevented it from shutting down successfully.
The command to check the system journal entries, which were written during the last shutdown is:
journalctl -b -1 -r (the options are dash b minus one dash r)
The command will display the previous session journal, starting from the end to the beginning, a screenful of lines at a time.
So you may have to read several screenful of messages in order to find the error messages, which give a hint, why shutting down did not work.

HTH,
Karl

[CygXanadu]

Hello, CygXanadu.

Chances are not bad that the system has logged during (unsuccessful) shutdown what prevented it from shutting down successfully.
The command to check the system journal entries, which were written during the last shutdown is:
journalctl -b -1 -r (the options are dash b minus one dash r)
The command will display the previous session journal, starting from the end to the beginning, a screenful of lines at a time.
So you may have to read several screenful of messages in order to find the error messages, which give a hint, why shutting down did not work.

HTH,
Karl

There were no error messages! even suspend just makes the screen black and nothing cannot get back into the main home screen, no sign-in screen just black. had to reinstall Mint, and still no proper shut down after all the updates and stuff.

[CygXanadu]

Hello, CygXanadu.

Chances are not bad that the system has logged during (unsuccessful) shutdown what prevented it from shutting down successfully.
The command to check the system journal entries, which were written during the last shutdown is:
journalctl -b -1 -r (the options are dash b minus one dash r)
The command will display the previous session journal, starting from the end to the beginning, a screenful of lines at a time.
So you may have to read several screenful of messages in order to find the error messages, which give a hint, why shutting down did not work.

HTH,
Karl

here is the journalctl

Code: Select all

cygxanadu@cygxanadu-p7-1142:~$ journalctl -b -1 -r
-- Logs begin at Thu 2020-02-20 12:14:14 MST, end at Fri 2020-02-21 22:04:07 MST
Feb 20 14:30:16 cygxanadu-p7-1142 systemd-journald[440]: Journal stopped
Feb 20 14:30:16 cygxanadu-p7-1142 systemd-shutdown[1]: Sending SIGTERM to remain
Feb 20 14:30:16 cygxanadu-p7-1142 systemd-shutdown[1]: Syncing filesystems and b
Feb 20 14:30:16 cygxanadu-p7-1142 kernel: printk: systemd-shutdow: 34 output lin
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Shutting down.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Starting Power-Off...
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Reached target Final Step.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Started Shuts down the "live" prei
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Starting Shuts down the "live" pre
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Reached target Shutdown.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Stopped Remount Root and Kernel Fi
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Reached target Unmount All Filesys
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Deactivated swap /swapfile.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Stopped LVM2 metadata daemon.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Stopping LVM2 metadata daemon...
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Stopped Monitoring of LVM2 mirrors
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped Create Static Device Nodes
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopping Monitoring of LVM2 mirror
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped target Local File Systems 
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Removed slice system-systemd\x2dfs
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped File System Check on /dev/
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Unmounted /boot/efi.
lines 1-23...skipping...
-- Logs begin at Thu 2020-02-20 12:14:14 MST, end at Fri 2020-02-21 22:04:07 MST. --
Feb 20 14:30:16 cygxanadu-p7-1142 systemd-journald[440]: Journal stopped
Feb 20 14:30:16 cygxanadu-p7-1142 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Feb 20 14:30:16 cygxanadu-p7-1142 systemd-shutdown[1]: Syncing filesystems and block devices.
Feb 20 14:30:16 cygxanadu-p7-1142 kernel: printk: systemd-shutdow: 34 output lines suppressed due to ratelimiting
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Shutting down.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Starting Power-Off...
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Reached target Final Step.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Started Shuts down the "live" preinstalled system cleanly.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Starting Shuts down the "live" preinstalled system cleanly...
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Reached target Shutdown.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Stopped Remount Root and Kernel File Systems.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Reached target Unmount All Filesystems.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Deactivated swap /swapfile.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Stopped LVM2 metadata daemon.
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Stopping LVM2 metadata daemon...
Feb 20 14:30:16 cygxanadu-p7-1142 systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped Create Static Device Nodes in /dev.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped target Local File Systems (Pre).
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped File System Check on /dev/disk/by-uuid/C844-D0F0.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Unmounted /boot/efi.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Deactivating swap /swapfile...
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped target Swap.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Unmounted /run/user/1000.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Unmounting /boot/efi...
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Unmounting /run/user/1000...
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped target Local File Systems.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped Create Volatile Files and Directories.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped Network Time Synchronization.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped Load/Save Random Seed.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopping Load/Save Random Seed...
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped Load Kernel Modules.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopping Network Time Synchronization...
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped target Local Encrypted Volumes.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped Apply Kernel Variables.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped target System Initialization.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Closed D-Bus System Message Bus Socket.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Removed slice User and Session Slice.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped target Slices.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Closed ACPID Listen Socket.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Closed CUPS Scheduler.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Closed Syslog Socket.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Closed UUID daemon activation socket.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped target Sockets.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped ACPI Events Check.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped CUPS Scheduler.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped target Paths.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped target Basic System.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopped D-Bus System Message Bus.
Feb 20 14:30:15 cygxanadu-p7-1142 systemd[1]: Stopping D-Bus System Message Bus...
lines 1-57

[karlchen]

Hello, CygXanadu.

Thank you for trying to capture the output of "journalctl -b -1 -r".
Sadly, I have to tell you that 57 lines are not sufficient.

Telling from my own systems, I can tell state that systemd writes between 200 and 300 lines,
+ between the time where it says, systemd-logind[799]: System is powering down.
+ and the final line where it says, systemd-journald[381]: Journal stopped

As a consequence, I cannot find anything in the 57 final lines which give a hint why the system should not power off.

In my previous post I had mentioned a timespan of 90 seconds, because this is the default timeout, which systemd will wait before killing a process which refuses to terminate cleanly.
Waiting for more than 90 seconds while staring at the Mint logo will appear like an eternity.

How long do you really wait before pressing the power button for 5 seconds thus interrupting the power supply?

I suggest next time you notice shutdown takes long, press the ESC key while the Mint Logo is on the screen.
This should make the messages displayed "behind the curtain" visible.
What does systemd tell?
What is the final message which you read?
(If you can, then you might take a picture of this final screen. It might be helpful, provided the messages are readable.)

If you take the time to wait for let us say 3 minutes, does the machine power off itself?

Best regards,
Karl

[CygXanadu]

I have waited for more than 3 mins one time ago it must have been 5+ I know it was long cause I was on my other PC and forgot about it, Mint logo is visible. I tried to D-Ban the HDD there were errors reading the first steps into the HDD could not access the HDD something like that. Are there any manual keys to press that might work.

It just baffles me that it was shutting down the first time fine probably about 10 times, and now when I go to re-install Mint it does not work (I was having issues sorry I cannot elaborate just that Icons were over lapping on the task bar) I'm figuring it might have to something to do with the permanent written block of the boot section IDK.

[CygXanadu]

I have to manually power it off ( hold the power button).

That's a great way to damage your file system. What happens if you open a terminal and enter the following command:

Code: Select all

shutdown -Ph now

That just ends up doing what it was doing when I choose to shutdown.