3

A message like this one is often shown on shutdown:

"A stop job is running ..." (nfs mount)

This apparently even happens when the NFS server did not go away. But even if the connection to the NFS server was lost, systemd is effectively preventing the system from shutting down. It is not possible anymore to ssh into the system and it's not possible to switch to another tty either. Hitting Ctrl + Alt + F2 does switch to a black screen with a cursor, but there's no login prompt. The user is forced to reboot the system forcefully, risking data corruption on those filesystems that are still mounted.

How can the tty console login be enabled at that time during the shutdown process?
It should be possible to log in as root and do umount -l or whatever might be necessary to allow the system to continue the shutdown process normally.

(This question is not about NFS, it's just a common example. An NFS mount does actually hang by design if the server went away. This question is about the fact that while this "stop job" is blocking the shutdown process, it is not possible to log in and enter commands to take care of the situation.)

  • Haven't encountered this with systemd yet, but have seen it with sysvinit scripts. Does typing Control-C kill the job that's hung? – Mark Plotnick Jul 8 '16 at 2:05
  • @MarkPlotnick: Tried all kinds of shortcuts, pretty sure Ctrl + C was one of them and it didn't do anything. The person sitting in front of the computer should be able to get a shell and stop such a process, whether systemd or sysv. – basic6 Jul 15 '16 at 14:48
  • A related question is unix.stackexchange.com/questions/310737 . – JdeBP Jan 25 at 17:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.