Rusk Crashed after a "hard node reboot" by the VPS supplier

[Rikkie82]

Describe the bug
Noticed already a couple of times my node gets stuck with the server gets a forced reboot by the supplier.
Only way a got around it and got it working was a full node reset (ruskreset) which then triggers a full re-sync, specially when fast-sync is not available (yet).
But would be better if after a forced reboot rusk would recover normally.

To Reproduce
force reboot your node
login to console and try to start rusk or fetch the status.

Expected behaviour
Node recovers itself after a hardware issue when hardware is restarted and doesn't get corrupt

Logs/Screenshot

Platform
Vultr node according to specs

Additional context

[Rikkie82]

looks like first Rusk service start is in middle of node reboot, afterwards it goes into a loop:

Oct 10 03:36:47 Dusk-Nocturne-Node-RG1 systemd[1]: rusk.service: Scheduled restart job, restart counter is at 1.
Oct 10 03:36:47 Dusk-Nocturne-Node-RG1 systemd[1]: Stopped DUSK Rusk.
Oct 10 03:36:47 Dusk-Nocturne-Node-RG1 systemd[1]: rusk.service: Consumed 20.768s CPU time.
Oct 10 03:36:47 Dusk-Nocturne-Node-RG1 systemd[1]: Starting DUSK Rusk...
Oct 10 03:37:07 Dusk-Nocturne-Node-RG1 systemd[1]: rusk.service: Control process exited, code=exited, status=1/FAILURE
Oct 10 03:37:07 Dusk-Nocturne-Node-RG1 systemd[1]: rusk.service: Failed with result 'exit-code'.
Oct 10 03:37:07 Dusk-Nocturne-Node-RG1 systemd[1]: Failed to start DUSK Rusk.
Oct 10 03:37:07 Dusk-Nocturne-Node-RG1 systemd[1]: rusk.service: Consumed 20.673s CPU time.
Oct 10 03:37:17 Dusk-Nocturne-Node-RG1 systemd[1]: rusk.service: Scheduled restart job, restart counter is at 2.
Oct 10 03:37:17 Dusk-Nocturne-Node-RG1 systemd[1]: Stopped DUSK Rusk.
Oct 10 03:37:17 Dusk-Nocturne-Node-RG1 systemd[1]: rusk.service: Consumed 20.673s CPU time.
Oct 10 03:37:17 Dusk-Nocturne-Node-RG1 systemd[1]: Starting DUSK Rusk...