Reboot Freeze

[MRL_LMint]

Been on mint 20.1 for a little over a month now. Been an ok experience so far. Keeping an open mind coming from windows and trying to not make comparisons has helped me. I read quite a bit before taking the plunge and that message was consistent and clear. Linux ain't windows. Regardless, yesterday I ran into a problem rebooting. The system hard froze during the shutdown at the circular LM graphic. No keystrokes or mouse movements remedied that. I have to use the power button to reboot. Had no program obviously running at the time of selecting reboot. I did have the Timeshift USB stick in a USB port but I don't think that would stop a reboot. Looking for some thoughts on where and how to determine what may have happened. Thanks for looking.

[SMG]

Had no program obviously running at the time of selecting reboot. I did have the Timeshift USB stick in a USB port but I don't think that would stop a reboot.

Do you only run Timeshift on-demand or do you have it run on a schedule?

In order to reboot, the system has to shutdown. It does not power completely down, but the operating system shuts down and restarts. So if a process was not done, then the system would be delayed in shutting down which would in turn delay the boot.

Was that the only time it happened or has it happened more than once?
Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz
Click </> from the mini toolbar above the textbox where you type your reply and then place your cursor between the code markers and paste the results of the command between the code markers [code]Results[/code]. This will let us know how Mint sees your hardware.

[MRL_LMint]

Runs on a schedule and had already completed the daily much earlier in the day. This was the first time that has happened.

[SMG]

Sometimes these issues and/or the fixes for them are related to hardware. That's why I asked for your system information. Section 5 of READ: How To Get Help! explains the data we need to be able to help you. Please provide that system data.

[MRL_LMint]

As requested...

Code: Select all

System:    Kernel: 5.4.0-72-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.8.6 wm: muffin 4.8.1 
           dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:   Type: Desktop Mobo: Gigabyte model: Z68X-UD3H-B3 serial: <filter> BIOS: Award v: F12 date: 03/20/2012 
CPU:       Topology: Quad Core model: Intel Core i5-2500K bits: 64 type: MCP arch: Sandy Bridge rev: 7 L2 cache: 6144 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 26478 
           Speed: 1907 MHz min/max: 1600/4500 MHz Core speeds (MHz): 1: 1628 2: 1613 3: 1612 4: 1605 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Gigabyte driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0112 
           Device-2: NVIDIA GF104 [GeForce GTX 460 OEM] driver: nvidia v: 390.141 bus ID: 01:00.0 chip ID: 10de:0e24 
           Display: x11 server: X.Org 1.20.9 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa 
           resolution: 1600x1200~75Hz 
           OpenGL: renderer: GeForce GTX 460/PCIe/SSE2 v: 4.6.0 NVIDIA 390.141 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:1c20 
           Device-2: NVIDIA GF104 High Definition Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0beb 
           Sound Server: ALSA v: k5.4.0-72-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: kernel 
           port: de00 bus ID: 07:00.0 chip ID: 10ec:8168 
           IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 961.34 GiB used: 58.16 GiB (6.0%) 
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB speed: 6.0 Gb/s serial: <filter> rev: 4B6Q 
           scheme: MBR 
           ID-2: /dev/sdb vendor: Western Digital model: WD5000AACS-00G8B1 size: 465.76 GiB speed: 3.0 Gb/s serial: <filter> 
           rev: 4C05 scheme: MBR 
           ID-3: /dev/sdc type: USB vendor: SanDisk model: Cruzer Fit size: 29.82 GiB serial: <filter> rev: 1.26 scheme: MBR 
Partition: ID-1: / size: 46.68 GiB used: 14.47 GiB (31.0%) fs: ext4 dev: /dev/sdb1 
           ID-2: /home size: 51.24 GiB used: 18.08 GiB (35.3%) fs: ext4 dev: /dev/sdb5 
Sensors:   System Temperatures: cpu: 34.0 C mobo: N/A gpu: nvidia temp: 38 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 25% 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http://packages.linuxmint.com ulyssa main upstream import backport #id:linuxmint_main
           2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
           3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
           4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
           5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
           6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:      Processes: 233 Uptime: 9m Memory: 7.69 GiB used: 1.73 GiB (22.5%) Init: systemd v: 245 runlevel: 5 Compilers: 
           gcc: 9.3.0 alt: 9 Shell: bash v: 5.0.17 running in: gnome-terminal inxi: 3.0.38

[SMG]

Nothing in the data jumps out at me as a possible concern.

When the system is shutting down and you see the LM Logo on the screen, you can press the Escape key to remove the logo and see the shutdown messages. Should this happen again, I suggest taking a photograph of where the system seems to get stuck (no new messages on the screen). Sometimes, messages show up on the screen after the log has shut down (because of timing issues--how fast certain things happen), so we can not always get the info from the log.

You can also get the log info, to see if it might have info letting us know what is happening, by running the following command in a terminal on your next boot after the freeze.
journalctl -rb -1 | nc termbin.com 9999
That command prints the journal log information of the prior boot cycle (the one which you stopped with the power button) in reverse order (so the reason for the freeze should be near the top) and sends it to termbin. It will return with a url address that you should post should you want us to help you analyze it.