[*** ] A stop job is running

[Zelator57]

Since upgrading to 17.3, shutdown often, but not always, seems to go on indefinitely, and when I hit a key I see:

Code:

[*** ] A stop job is running for /media/suewin (7min 39s / 9min 7s)

Alt+SysRq+B gets me back to the login, where I can shut down successfully.

/media/suewin is on a Windows 10 box, which has been shut down by the time I shut down Maui. It is quite probable that I have a Dolphin tab for it, open if not with focus, at the time of shutdown.

The fstab entry for /media/suewin is:

Code:

//desktop-92taib0/Sues_Documents /media/suewin cifs username=andrew,password=******,iocharset=utf8,sec=ntlm,_netdev  0  0

The only reference I can find to this specific type of problem is on a Debian bug report. The solution given there is:

Code:

/home/mythtv /home/mythtv nfs x- systemd.requires=network.target,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=1min 0 0

The poster is unsure which part of this does the job, he thinks it is "systemd.required=network.target".

As trial and error testing would require frequent coordinated startups and shutdowns of two computers at opposite ends of the house I would prefer to be fairly sure of what I am doing before I start. I would appreciate an expert opinion.

[kdemeoz]

I can't give any advice, only offer my solidarity with you -- you're not alone with this. For me also, ever since 17.03 only, attempted shutdowns of my Tower also sometimes hang for very long periods, also with "A stop job is running for...". Even when the big lags don't actually occur, pretty much every shutdown is accompanied by a large tract of fast-scrolling text on-screen. It's ugly & disconcerting, but not otherwise apparently problematic. Those stop-job delays though; they're seriously annoying.