Hi,

My previous slack (14.1) configured to support an ARM board to mount its root file system from slack via nfs. It's been working fine. After I upgraded to 14.2, the same client cannot mount root file system from the new slack no longer. However, when I test normal (non-rootfs) mounting from another PC linux, the mounting works normally.

What I did to configure my slack server involves:
1. add entry to /etc/exports
/home/nfs/arm-rootfs 10.86.0.0/255.255.0.0(ro,no_root_squash,no_all_squash,no_subtree_check)
2. /etc/rc.d/rc.nfsd restart

Below is error messages I got from the ARM client in it's booting time:

----------
[ 3.090000] IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.86.11.135
[ 3.090000] IP-Config: Complete:
[ 3.095000] device=eth0, addr=10.86.11.135, mask=255.255.255.0, gw=10.86.11.254,
[ 3.100000] host=10.86.11.135, domain=ap.bm.net, nis-domain=(none),
[ 3.105000] bootserver=0.0.0.0, rootserver=10.86.201.53, rootpath=
[ 3.115000] Root-NFS: nfsroot=/home/nfs/ffc3-rootfs
[ 3.120000] NFS: nfs mount opts='vers=2,udp,rsize=4096,wsize=4096,nolock,addr=10.86.201.53'
[ 3.125000] NFS: parsing nfs mount option 'vers=2'
[ 3.130000] NFS: parsing nfs mount option 'udp'
[ 3.135000] NFS: parsing nfs mount option 'rsize=4096'
[ 3.140000] NFS: parsing nfs mount option 'wsize=4096'
[ 3.145000] NFS: parsing nfs mount option 'nolock'
[ 3.150000] NFS: parsing nfs mount option 'addr=10.86.201.53'
[ 3.155000] NFS: MNTPATH: '/home/nfs/ffc3-rootfs'
[ 3.160000] NFS: sending MNT request for 10.86.201.53:/home/nfs/ffc3-rootfs
[ 3.175000] NFS: MNT request succeeded
[ 3.185000] VFS: Unable to mount root fs via NFS, trying floppy.
[ 3.185000] VFS: Cannot open root device "nfs" or unknown-block(2,0)
[ 3.190000] Please append a correct "root=" boot option; here are the available partitions:
[ 3.195000] 1f00 1024 mtdblock0 (driver?)
[ 3.200000] 1f01 2048 mtdblock1 (driver?)
[ 3.205000] 1f02 4096 mtdblock2 (driver?)
[ 3.210000] 1f03 1041408 mtdblock3 (driver?)
[ 3.215000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
------

And, /var/log/messages outputs while the client is booting:
-----
May 8 12:45:16 clockwork rpcbind[10443]: connect from 10.86.11.135 to getport/addr(mountd)
May 8 12:45:16 clockwork rpc.mountd[10433]: authenticated mount request from 10.86.11.135:784 for /home/nfs/ffc3-rootfs (/home/nfs/ffc3-rootfs)
May 8 12:45:16 clockwork rpcbind[10444]: connect from 10.86.11.135 to getport/addr(nfs)
------

Could anyone please help me? Thanks in advance.

-woody

Hi,

It certainly does work - here I have several diskless machines pxe booting with root/swap/home all over nfs.

[ 3.185000] VFS: Unable to mount root fs via NFS, trying floppy.
[ 3.185000] VFS: Cannot open root device "nfs" or unknown-block(2,0)

What's your kernel cmdline and what's your booting fstab?

and is
1. add entry to /etc/exports
/home/nfs/arm-rootfs

but
nfsroot=/home/nfs/ffc3-rootfs

just a leftover from testing?

Kernel cmdline:
nfsroot=10.86.201.53:/home/nfs/ffc3-rootfs ip=dhcp console=ttySAC0 vt.global_cursor_default=0 s3c_wdt.tmr_atboot=0 s3c_wdt.tmr_margin=30"

/home/nfs/arm-rootfs is I changed in the posting, but the actual name is /home/nfs/ffc3-rootfs

Please note: the same client machine can boot into a slack 14.1 but cannot to 14.2.

Thank you for your help!