I have a development board connected over ethernet such that my desktop is 10.0.0.1 and my dev board is 10.0.0.3.
The remote device is set to boot from an NFS share and the kernel is told as so:
console=ttyO0,115200n8 root=/dev/nfs rw nfsroot=10.0.0.1:/home/nick/Dev/git-rootfs ip=10.0.0.3:::::eth0,nfsvers=3
I booted my desktop this morning after applying updates before shutting down last night and tried to start it all up this morning. Sadly my board hangs with the following:
[ 108.951477] VFS: Unable to mount root fs via NFS, trying floppy.
[ 108.958831] VFS: Cannot open root device "nfs" or unknown-block(2,0)
[ 108.965606] Please append a correct "root=" boot option; here are the available partitions:
[ 108.996002] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
I've checked that /etc/export hasn't been broken which reads as follows:
but I did notice that if I try and mount the nfs share locally it also fails:
[nick@slimtop tftpboot]$ sudo mount -v 10.0.0.1:/home/nick/Dev/git-rootfs /media/
mount.nfs: timeout set for Thu Jul 5 11:06:59 2012
mount.nfs: trying text-based options 'vers=4,addr=10.0.0.1,clientaddr=10.0.0.1'
mount.nfs: mount(2): Permission denied
I can make this work by issuing:
sudo mount -v -o vers=3 10.0.0.1:/home/nick/Dev/git-rootfs /media/
But I have no idea on how to do the same to the kernel - I thought specifying the version with nfsvers would work but I can't find a changelog for the nfs-utils that would explain what's broken/changed.