Today I just learned that systemctl --force --force reboot is a command. We had a computer we remotely connected to which got permission errors and bus errors when we tried to reboot it normally. For some reason the mentioned command did actually manage to shutdown the computer bit did not manage to reboot it correctly.
I wonder what the double --force flag actually accomplishes and what possibly could hinder a regular reboot in this scenario.
I’d never use it on a production server due to the implications of data loss associated with such a command.
You could say this is the same as sysreq trigger b where everything is ignored and just reboot with ignorance.
You can force the kernel to terminate all processes and amount all filesystems
deleted by creator
This is very valid but in our case we dont really store any important data on the computer. We make digital timetable signs for bus stops and train stations, the computers we build and put inside are just a base image we flash onto the disk and set hostname and IP on. Then they all connect and set themselves up via our servers and pull any displayed data from our actual main servers.
In this case its sad that it didnt actually restart, that means our client has to drive out and deassemble the entire sign. But it seems to be a failing disk so it had to be replaced either way.
As long as it’s not writing to disks, you’re probably safe. This is a good method to avoid getting a remote device stuck too.