3

edit2: This question keep getting closed with links which point to completely irrelevant posts so giving up on it.

edit: I'm asking how to disable/kill the Stop Job, not change the time to SIGKILL (which apparently isn't working either since 90s is the default).

I have a few Debian 10 systems (Proxmox) which take anywhere from 5 minutes to forever to reboot.

Sometimes I need to drive into the DC and physically hit the power button. The keyboard is always unresponsive at this point. I don't know if USB is already disabled in the reboot process or what. The holdup is always Systemd with "A stop job is running". Today it appears to be the swap partition.

15 minutes to "never" to reboot

Any way to put a kill-switch on the stop jobs? I don't care if swap gets hosed due to a dirty unmount - At this point, I'd rather just fsck -Cf after every reboot and mount swap by hand.

Improve this question
6
  • unix.stackexchange.com/questions/503058/…
    – Artem S. Tashkinov
    Commented May 13, 2022 at 12:00
  • Does this post answer your case in Debian too? - Interactively terminate "A stop job is running" at shutdown
    – dungarian
    Commented May 13, 2022 at 12:00
  • Umm.. not really. Unless I'm missing something, those links don't explain how to kill the Stop Job which is what I'm asking about. It's clearly broken since 90s is the default time until SIGKILL, which apparently doesn't work either.
    – Nstevens
    Commented May 13, 2022 at 14:26
  • @Nstevens Just in case you're missing something... do you know about "Magic SysRq REISUB"? If not, RTFM. If you know, are you saying it didn't work or are you saying it's not your preferred solution?
    – dungarian
    Commented May 13, 2022 at 14:38
  • 1
    How is this question a duplicate? The suggested posts don't provide the answer being asked here...
    – dungarian
    Commented May 15, 2022 at 7:25

0

Reset to default

Browse other questions tagged .