Bone black NFS root.

Just trying to get NFS root working here, no TFTP boot . . . can anyone spot what I’m missing here ? Onlything I can think of is that I’m trying to boot a kernel that was not set in the second stage uEnv.txt file, but was my understanding that this was controlled via the variable uname_r . . . Beating my head against a wall here trying to get this working :confused: I’ve even expanded some variables into IP’s / fully qualified paths, etc.



loadximage=load mmc 0:1 0x80300000 /boot/vmlinuz-4.1.0-rc8-bone9
loadxfdt=load mmc 0:1 0x815f0000 /boot/dtbs/4.1.0-rc8-bone9/am335x-boneblack.dtb
loadall=run loadximage; run loadxfdt;

netargs=setenv bootargs console=tty0 console=${console} root=/dev/nfs nfsroot=,vers=3 rw ip=
uenvcmd=setenv autoload no; run loadall; run netargs; bootz 0x80300000 - 0x815f0000;

Error I’m getting:

[ 7.623523] bootserver=, rootserver=, rootpath= [ 102.779542] VFS: Unable to mount root fs via NFS, trying floppy. [ 102.786427] VFS: Cannot open root device "nfs" or unknown-block(2,0): error -6 [ 102.794064] Please append a correct "root=" boot option; here are the available partitions: [ 102.802855] b300 15351296 mmcblk0 driver: mmcblk [ 102.808463] b301 1024000 mmcblk0p1 00000000-01 [ 102.814059] b308 3776512 mmcblk1 driver: mmcblk [ 102.819646] b309 98304 mmcblk1p1 00000000-01 [ 102.825242] b30a 3677184 mmcblk1p2 00000000-02 [ 102.830827] b318 2048 mmcblk1boot1 (driver?) [ 102.836423] b310 2048 mmcblk1boot0 (driver?) [ 102.842009] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) [ 102.850703] CPU: 0 PID: 1 Comm: swapper Not tainted 4.1.0-rc8-bone9 #1 [ 102.857557] Hardware name: Generic AM33XX (Flattened Device Tree) [ 102.864001] [<c0012741>] (unwind_backtrace) from [<c0010941>] (show_stack+0x11/0x14) [ 102.872154] [<c0010941>] (show_stack) from [<c05e4d0b>] (panic+0x53/0x168) [ 102.879396] [<c05e4d0b>] (panic) from [<c0953d6d>] (mount_block_root+0xfd/0x198) [ 102.887183] [<c0953d6d>] (mount_block_root) from [<c0953e9f>] (mount_root+0x97/0xb4) [ 102.895329] [<c0953e9f>] (mount_root) from [<c0953f6b>] (prepare_namespace+0xaf/0x100) [ 102.903657] [<c0953f6b>] (prepare_namespace) from [<c0953b13>] (kernel_init_freeable+0x133/0x17c) [ 102.913002] [<c0953b13>] (kernel_init_freeable) from [<c05e3f81>] (kernel_init+0xd/0xa4) [ 102.921515] [<c05e3f81>] (kernel_init) from [<c000e445>] (ret_from_fork+0x11/0x2c) [ 102.929481] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

rootpath= <--- seems suspicious, have tried multiple “cures” but nothing seems to work.

Typo I spotted right after i posted . . .

"rootpath=/home/williame/can-dev" -e and all seems fine - grrrr !


Since I’ve started this topic, and the question is on my mind. Are there any 4.1.x + kernels that do not support nfs root ? I was nearly convinced last night the TI kernels didn’t because the board would immediately go into booting the image from the eMMC, but now, less sure.

I think i had multiple problems. Starting with cough Windows copy / paste :confused:

Also curiously - From the nfs root on the board -

debian@beaglebone:/$ sudo du -h /
663M /

From the nfs server:
william@eee-pc:~$ sudo du -h can-dev
248M can-dev

Was reading last night on this somewhat, but did not really find a definitive answer as to why this happens . . . something about open file descriptors or something but, I don’t know . . .