> I suspect some kind of timing problem, where the network interface hasn't > come up yet at the time the portmap request is made. What does your nfsroot > kernel option look like? What happens if you add ",port=2049" to the > end of > your nfsroot kernel option? That's my kernel line (and it's exactly the same for all kernel versions I used): root=/dev/nfs rw nfsroot=137.226.167.241:/srv/nfs/cluster2 ip=137.226.167.242::137.226.167.225:255.255.255.224:cluster2:eth0:off nfsrootdebug (I know that nfsrootdebug isn't available in older kernels but it doesn't matter...) With ",port=2049" I get this from linux-2.6.29.4: [ 252.932407] IP-Config: Complete: [ 252.932476] device=eth0, addr=137.226.167.242, mask=255.255.255.224, gw=137.226.167.225, [ 252.932680] host=cluster2, domain=, nis-domain=(none), [ 252.932794] bootserver=255.255.255.255, rootserver=137.226.167.241, rootpath= [ 252.933230] Root-NFS: nfsroot=/srv/nfs/cluster2,port=2049 [ 252.933523] NFS: nfs mount opts='udp,port=2049,nolock,addr=137.226.167.241' [ 252.933583] NFS: parsing nfs mount option 'udp' [ 252.933621] NFS: parsing nfs mount option 'port=2049' [ 252.933675] NFS: parsing nfs mount option 'nolock' [ 252.933722] NFS: parsing nfs mount option 'addr=137.226.167.241' [ 252.933787] NFS: MNTPATH: '/srv/nfs/cluster2' [ 252.933823] NFS: sending MNT request for 137.226.167.241:/srv/nfs/cluster2 [ 254.038874] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx [ 254.059251] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 288.023684] NFS: failed to create MNT RPC client, status=-60 [ 288.023793] NFS: unable to mount server 137.226.167.241, error -60 [ 288.023929] VFS: Unable to mount root fs via NFS, trying floppy. [ 288.024092] VFS: Insert root floppy and press ENTER So the result is the same as before... In the past I also tried higher "timeo" and I think higher "retrans" values but also without a positive effect... -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
