I have the same problem. I just did a new lenny installation using this entries in fstab:
kueppers:/home /home nfs rw,noatime,nosuid 0 0 kueppers:/var/mail /var/mail nfs rw,nosuid,noac,actimeo=0 0 0 kueppers:/usr/local /usr/local nfs ro,noatime,actimeo=900 0 0 My /etc/network/interfaces look like this: auto lo eth0 iface lo inet loopback iface eth0 inet static address 134.95.9.150 netmask 255.255.255.0 broadcast 134.95.9.255 gateway 134.95.9.254 In /etc/default/rcS I have ASYNCMOUNTNFS=no With etch, this works fine, in lenny the NFS mount will not happen at boot time. When I do mount -a after I logged in, everything is fine. The error messages are: eth0 is not ready. . . eth0 becomes ready . . mount.nfs: Mount to NFS Server 'kueppers' failed. System Error. No route to host. IMO it's because my NIC needs some seconds to autonegotiate with the switch or to become fully enabled. So the mount request if done before the NIC can really send packages to the network. I have the same problem on different hardware. Why did this not happend with etch? I had following workarounds 1) add option bg to the NFS mount in /etc/fstab 2) add a "sleep 3" in /etc/network/ifup.d/mountnfs I think both is suboptimal and should be fixed in the initscripts. ii initscripts 2.86.ds1-61 ii linux-image-2.6-686 2.6.26+15 -- regards Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
