Results 1 to 4 of 4

Thread: Hanging at [Systemd: OK] Reached Target Shutdown

  1. #1
    Join Date
    Oct 2014
    Location
    Switzerland
    Posts
    415

    Default Hanging at [Systemd: OK] Reached Target Shutdown

    Hello,
    I recently upgraded to LEAP 15.1. (Fresh install) Everything has gone smoothly but it seems that sometimes that during reboot/shutdown sequence the laptop is stuck at
    Code:
    [OK] Reached Target Shutdown
    I tried the folllowing:
    uncomment/modify
    Code:
    /etc/systemd/system.conf
    DefaultTimeoutStopSec=3s
    
    modifying to include "acpi=force" in
    Code:
    /etc/default/grub
    GRUB_CMDLINE_LINUX_DEFAULT="splash=silent quiet mitigations=auto acpi=force"
    mkinitrd
    The latter changed from being stuck during shutdown to being slow/stuck for less than 1 minute.

    It seems to happen to 2 of my Lenovo laptops + my student's laptop and only on LEAP 15.1, but not on LEAP 15.0

    Are there some suggestions for this?
    Thanks

  2. #2
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,983

    Default AW: Hanging at [Systemd: OK] Reached Target Shutdown

    If you installed without lvm (Logical Volume Manager), disable:
    Code:
    systemctl disable lvm2-monitor.service
    Code:
    systemctl stop lvm2-monitor.service
    Reboot.

  3. #3
    Join Date
    Oct 2014
    Location
    Switzerland
    Posts
    415

    Default Re: Hanging at [Systemd: OK] Reached Target Shutdown

    Perfect!
    Thank you.
    I've also reverted changes to acpi=force and timeout

    and I can confirm that disabling and stopping lvm2-monitor worked perfectly.

  4. #4
    Join Date
    Aug 2008
    Location
    Brazil
    Posts
    2,908

    Default Re: AW: Hanging at [Systemd: OK] Reached Target Shutdown

    Quote Originally Posted by Sauerland View Post
    If you installed without lvm (Logical Volume Manager), disable:
    Code:
    systemctl disable lvm2-monitor.service
    Code:
    systemctl stop lvm2-monitor.service
    Reboot.
    Many thanks, Sauerland! I had this same issue with a desktop that I use as a media center and this fixed it. Curiously, this problem only happened with this box, but not on three other upgraded to 15.1, one of them with very similar hardware. Go figure...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •