Hi!

I've configured nfs and it works. I can mount remote drives etc.
But when I reboot the client, I get errors. Here's from my boot.log:

Sep 30 02:49:07 portege7200 ifup: tulip device does not seem to be present, delaying eth0 initialization.
Sep 30 02:49:13 portege7200 mount: mount: RPC: Port mapper failure - RPC: Unable to send
Sep 30 02:49:07 portege7200 network: Bringing up interface eth0: failed
Sep 30 02:49:13 portege7200 mount: mount: RPC: Port mapper failure - RPC: Unable to send
Sep 30 02:49:13 portege7200 last message repeated 3 times
Sep 30 02:49:13 portege7200 netfs: Mounting NFS filesystems: failed
Sep 30 02:49:15 portege7200 netfs: Mounting other filesystems: succeeded
Sep 30 02:49:18 portege7200 apmd: apmd startup succeeded
Sep 30 02:49:19 portege7200 autofs: automount startup succeeded
Sep 30 02:49:24 portege7200 xinetd: xinetd startup succeeded
Sep 30 02:49:26 portege7200 lpd: lpd startup succeeded
Sep 30 02:49:27 portege7200 nfs: Starting NFS services: succeeded
Sep 30 02:49:27 portege7200 nfs: rpc.rquotad startup succeeded
Sep 30 02:49:27 portege7200 nfs: rpc.mountd startup succeeded
Sep 30 02:49:28 portege7200 nfs: rpc.nfsd startup succeeded

It seems that mount is trying to mount drives before nfs services are running and that's why it's failing? after it boots, I can manually mount the nfs systems listed in fstab.

How can I avoid these errors, and get the fs to mount on boot?
Also, what is tulip and portmapper? why can't they bring up eth0 (after it boots, my network connections are working fine?!)

thanks for any feedback,
jonathan.

mounting nfs and init eth0 is failing most likely because tulip is failing.

tulip is the network card, also it is most likely eth0 and if you find the problem with it everything will probably work

look at the output of

lsmod

and

dmesg

and see if you actually have a tulip driver loaded when it's working

if it's a tulip card then I think you need to look at /etc/modules.conf

it should have the following

alias eth0 tulip

if it's a different card then replace tulip with the right module name




what distro are you using?

This seems to be a bit of wonkiness, on, let me guess... RedHat's part? of the order of its SysV scripts. It makes sense that they might have hatcheted the order for your runlevel. RedHat personal probably puts mounting of the local drives (and hence the network drives, all it looks at is fstab), ahead of network initialization in the init order. I've read some of your other posts; I don't usually suggest fiddling like this, but you might be interested.

See what numeric value network is given as opposed to nfs in /etc/rc.d/rc3.d.. or rc5.d if your an X person, they're all symbolic links to /etc/rc.d/init.d, and the lower the number, the earlier it runs. S is start, K is kill. Fiddling with that can create issues, but its easy to put back the way it was.

Cheers,

Finegan