nfs storage server 2008 R2 not responding for a while after powering on


hi all

have 2 windows servers 2008 r2 enterprise configured nfs storage server in (active/passive) replication cluster.
nfs storage mounted on linux servers.
every time power on environment, find nfs become not responding(from linux servers side) several minutes , responding(the services on nfs servers , running , there isn't errors in event viewer)
attitude keeps repeating while (may hour or two) , after works fine.
happens after power on environment.

ideas might cause this?

additional information:

  • the physical storage sas configured raid 5.
  • powering on sequence:
  1. power on physical storage
  2. power on windows nfs servers
  3. power on linux servers

thanks help.

hi ramy adly,

thanks post.

please install update below see if issue still exists:

update server nfs drivers per url below:
  http://support.microsoft.com/kb/2222746

update rpc drivers:
 http://support.microsoft.com/kb/983574

nfs server not responding great error message, meaning error message isn’t totally ambiguous  nfs client can no longer communicate nfs server.

you may following check:

  1. ping netapp filer ip , dns name or short name.
  2. on netapp filer, try ping nfs client(s).
  3. confirm ip configuration on nfs client , servers correct
  4. confirm correct nfs version enabled
  5. check nfs options on netapp filer correct

please refer article below more details

http://seriousbirder.com/blogs/common-nfs-error-messages-and-troubleshooting-tips/

please note: since web site not hosted microsoft, link may change without notice. microsoft not guarantee accuracy of information.

best regards,

mary dong


please remember mark replies answers if , unmark them if provide no help. if have feedback technet subscriber support, contact tnmff@microsoft.com.



Windows Server  >  File Services and Storage



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file