That’s because it first send sigterm, then sigkill. Then it gives up and let the kernel handle it…
Happens on my BTRFS disk’s unmount. If the kernel is currently busy handling some heavy btrfs command (like a 4tb scrub), systemd cannot stop it with sigkill.
So when it eventually gives up, you also need to wait for the kernel to finally stop the operation and actually disconnect the disk.
Step 2: press the power button 5 or 10 seconds while contemplating why you decided to do a quick restart instead of keeping the session and do something actually productive
…
???
That’s because it first send
sigterm, thensigkill. Then it gives up and let the kernel handle it…Happens on my BTRFS disk’s unmount. If the kernel is currently busy handling some heavy btrfs command (like a 4tb scrub), systemd cannot stop it with sigkill.
So when it eventually gives up, you also need to wait for the kernel to finally stop the operation and actually disconnect the disk.
Shieeet
In those cases there’s an easy solution.
Step 1: sigh
Step 2: press the power button 5 or 10 seconds while contemplating why you decided to do a quick restart instead of keeping the session and do something actually productive
I recommend starting with SysRq+E before that, there’s a chance it gets whatever the shutdown was waiting for. And if that fails… REISUB my beloved.
RSEIUB. Raising skinny elephants is utterly boring.