Anybody have a how to delay the network shutdown upon reboot? Ever since 13.1 I have not been able to reboot my systems because the network goes down before the nfs mounts are unmounted causing the system to wait forever trying to unmount them.
Doing a umount to the shares before hand allows the system to reboot nearly instantaneously.
deanjo13 wrote:
>
> Anybody have a how to delay the network shutdown upon reboot? Ever
> since 13.1 I have not been able to reboot my systems because the network
> goes down before the nfs mounts are unmounted causing the system to wait
> forever trying to unmount them.
>
> Doing a umount to the shares before hand allows the system to reboot
> nearly instantaneously.
>
>
If we are dealing with fstab entries try the solution provided here :-
https://bugs.archlinux.org/task/32955
–
Version 3.10.2
openSUSE 13.1 (Bottle) (x86_64) 64-bit
Kernel Linux 3.11.6-4-desktop
Where are my penguins :- https://features.opensuse.org/316767
You should probably file a bug report.
I use “autofs” for NFS mounts, and I am not having that problem (not yet).
Tried _netdev and that doesn’t help the issue.
I am only running 13.1 occasionaly at the moment, but yesterday I had the same experience. I had to switch the system of hardwarewise. But 10 mins later I shutdown the system and hadn’t the problem. Reading your post it seems that it (like mine as an afterthought) only experience this with a reboot. Can you conform that you also do not have it at a shutdown? (this to have a better bug description when someone of us go to bugzilla).
I find this strange because IMHO a reboot and a shutdown are exectly the same, only difference is a signal too the BIOS at the end to either switch off or do a boot. The whole Linux system shutdown should run exactly the same in both caces (again IMHO).
In my case, shutdown hangs as well. In both shutdown and reboot I’m left hanging with this:
http://img440.imageshack.us/img440/3589/jgcd.jpg
I had the same issues with 12.3 when trying to use SystemD, switching it to sysvinit cured the issue.
Well, strange. I only had this yesterday in that reboot (seeing your picture, I am almost sure I had the same). Could be a timing problem (which may hamper finding the excact problem). In any case IMHO it worthwhile to file a bug here: openSUSE:Submitting bug reports - openSUSE
The same username/password as that for the Forums should work there.
Please report the bug number here in the thread when you are finished, so interested people (like me) can trace what happens and eventauly can add comments to it.
Same issue was reported against 12.3. I have really given up on submitting bugs to openSUSE as pretty much everyone I have submitted over the last 4 years has been ignored.
FWIW, similar thread here with workarounds mentioned
Unfortunately none of those worked either. Think it’s just going to be easier to either revert to 12.3 or hack sysvinit back into 13.1.
On 2013-12-30 05:36, deanjo13 wrote:
> or hack sysvinit back into 13.1.
That’s impossible.
You really have to submit the bugzilla and hope. Other people having the same issue here should then
add a “me too” (the more, the merrier). If nobody answers, then go to the factory mail list and nag
the devs in there to pay attention (tell them the issue was reported in another bugzilla some many
months/years ago). Most of them do not read the forum.
Yes, I also have many bugzillas reported an no response in years. But it can not be said that I
did not contribute my duty. 
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Elessar))
Screenshot you attached later does not show network being stopped. How did you perform diagnostic? Do you have any detailed logs from shutdown that can help to find the root cause? What are bug numbers?
I just tried a reboot and it jung (until I swotched it off). This is my screenshot (a bit different):
http://hcvv.home.xs4all.nl/NFS-h.JPG
It stops Postfix.
It stops the NTP deamon.
It stops DNS client (if I interprete this correct).
It can be seen that the network interface enp0s5 is stopped now.
Then it tries to unmount /home/wij, which is NFS mounted.
After several minutes it says that it unmounted /home/wij. Then three more lines which are a not very understandable to me, but show that the system is still busy doing NFS things.
Then it hangs forever.
Hope thgis helps in understanding the problem.
Yes, your screenshot indeed clearly shows that first network is stopped and then NFS client. Could you please
Make output of “systemctl dump” and “journalctl -b -1” available.
You can delete /var/log/journal to save disk space; you will need to reboot.
I will try to follow your recipe and report back.
For the record: I repeat that shutdown in my case works as lightning. I tried to see on the screen what the sequence is in that case, but the only thing I can see that there is much more before the screen gets dark because of the shutdown.
Booted thsystem and did Ctrl-Alt-F!. Loged in as root.
/var/log/journal did not exist, created it.
Used shutdown -h now. Observation: NO HUNG!
This gives
systemctl dump
Unkown operation dump"
Can not find the dump command in the systemctl man page.
??? System is 13.1 and yesterday I did a YaST Online update.
Apparently it had been moved into systemd-analyze (you may need to install it separately, do not remember). system wiki needs update.
This 13.1 system I am using for this is a testsystem, thus I can meddle around without problems.
Indeed
systemd-analyze dump
works (15000 lines of output).
The frustrating thing now is that I can not recreate the hung. Even from the KDE session, a reboot runs flawless>:)
Thus making the output you want is not an easy process. Maybe I will do some trials until I get it happening.
Could you compress it and make available (dropbox or similar)? I’m afraid it is too long for susepaste or probably even pastebin.
Yes, that is one reason why bugs sometimes are left open for a long time - as soon as you try to debug it, it does not happen. No debug information - no fixes 
I have no problem hosting that file on a website of my own ready for download for some time. So that will not be a problem.
But I guess It is all of no use until I can recreate the problem. I did a few reboots allready, but in vain until now