How come it takes more than a minute to shutdown or reboot the system?

General system Newbie
21

I never try :pray: ( after shutdown com issued)

" It is a ā€˜magicalā€™ key combo you can hit which the kernel will respond to regardless of whatever else it is doing, unless it is completely locked up."

some info here " https://wiki.archlinux.org/title/Keyboard_shortcuts#Kernel

https://www.kernel.org/doc/html/latest/admin-guide/sysrq.html "

22

Thanks!
I thought that the key combo was meant to perform a ā€œsmoothā€ shutdown when there is some sort of system freeze while still in the desktop.
Thanks for the links!
I need to :eyeglasses: :open_book:

23

At least on my computer I could boot from one of two options: EndeavourOS (from external USB disk) or into Windows10 (internal HDD). If both were on the same disk it shouldnā€™t be different.

24

Yes it did do a reboot when I pressed those keys, however when I shutdown or reboot normally (without those keys) then it still takes forever.

25

Just verified this also happens on MATE as well so its not xfce related issue.

26

Just verified this seems to be an issue only on virtualbox, not on actual hardware, so this seems most likely an issue to do with this drivers. Not too sure why its not a problem on Debian based!

27

I donā€™t have this problem and i have never had this problem. My system on bare metal shuts off in 6 seconds. It takes longer for a cold boot. About 3x as long to boot from scratch. I also donā€™t have this issue on vm using vmware. On vmware the shutdown takes 4 seconds to shutdown the installed vm. I can close vmware without shutdown in less time also.

28

Have you tried to disable the systemd services you donā€™t use? It might help a bit eg: systemctl disable cups(if you donā€™t use a printer) etc. you could use ``systemctl --type=service --state=active to see which services are actives and give you an idea of which one you donā€™t actually need!

I used to do that when i was still using systemd distros!
the great community kept me here :smiley:

https://www.tecmint.com/list-all-running-services-under-systemd-in-linux/

29

Virtualbox isnā€™t working properly as far as Iā€™m concerned. I dropped it since the last ISO because of that. Iā€™m strictly using vmware-workstation pro currently because it works.

30

Have you tried switching to TTY1 when this happens? Try pressing Ctrl+Alt+F1 or Alt + F1 when you get this behavior. It should get unstuck and shut down / reboot immediately.

There is a similar issue that affects sddm (especially if hand-off from lightdm is used) that is solved in sddm-git.

31

I am using virtualbox though so I think maybe its virtualbox driver issues not vmwareā€™s issue?

32

The drivers seem to still be installed though cause I can still share clipboard between host and guestOS (which is endeavourOS in this case).

33

I could give it a try on virtualbox next time.

34

Will do check it out, though since it is only happening on VirtualBox and not on actual hardware, typically I use virtualbox for testing purposes, I was afraid this would also happen on actual hardware so that is why I had to check it out.

Thanks for teh suggestion though I will check it out if needed :slight_smile:

36

This isnā€™t going to help, but I was reading about some other Arch distros like Artix, and VoidLinux, that dont use systemd, and this specific issue was called out as a systemd problem. As a result they claim faster startup/shutdown.

If indeed it is so, I hope someone is looking into it for an upstream fix, but I havenā€™t seen anything.

37

I had the same issue since months, a stop job wonā€™t end and 90% of the time shutdown or reboot were stuck during 90 sec.
As a WORKAROUND I just edited the systemd service to wait 10 sec instead of 90.
Since then all is working great.

Here is what I did:

  1. Edit /etc/systemd/system.conf
  2. Uncomment and set DefaultTimeoutStopSec from 90s toā€¦ 10s or whatever

Of course you need to reboot at least once to initiate the change

38

Thanks for the info I will try this out next time :slight_smile:

Because the issue looks like it has something to do with virtualbox, I think a workaround is to install the drivers supplied directly from virtualbox and not depend on the inbuilt drivers instead

39

Lately, itā€™s becoming less and less common for me that it takes several minutes for the computer to shut down.

40

Did this happen on actual hardware or virtualbox?

41

This happens sometimes on my home machine, but I canā€™t remember the last time it happened.