I thought about writing a script that will scan the /etc/mnttab and run a df of each filesystem in the /etc/mnttab file but unfortunately when it get thru the one that it is having problem with, the script stalls and cannot continue. This is consistent with the kernel not completely starting. What we can see is that it appears the kernel-info response has not been received. Please capture the entire startup sequence, either via screen-scrape or by redirecting the output to a file.
For the time being, am wanting to know how to isolate which mount points are having NFS issues, is there a command that I can run that will report on what mount points is NFS having problems with instead of running df which hangs midway? I believe 'interesting portions' of the terminal output have scrolled off your screen. If I do a df -k, it lists down the filesytem and then stop on when it start getting NFS server error. Reason I said this is because there is about 10-15 NFS mount from this server and the NFS error is not happening on all of them only for some of them. Run as Administrator One of the easiest ways to get around any of the packages not working the problem is to give full administrative access to it.
Code : NFS server not responding still tryingĪm leaning towards a SAN storage issue at the moment. Are you still running into the PvP.net Patcher Kernel has stopped working problem If you are, then try the next solution below. Here are some quick tips to fix PvP.net Patcher Kernel has Stopped Working Issue.
