Giles,

If you tested the mount externally and it works this probably wouldnt be a
NFS issue. Just on a guess form experience and what you've posted. the
kernel is loading, but the rootfs isnt. Your debug messages seems to nearly
confirm this. So if you can add the line mentioned on my blog post to
inittab ( which is copied from Roberts guide ), perhaps you'll get more
information as to what is exactly happening.

Good luck, ill be on later today. Bed time for me.


On Wed, Jul 30, 2014 at 12:26 AM, Giles Godart-Brown <[email protected]
> wrote:

> Thanks for the sugestion William, I'll try that once I can get it
> successfully mounting the file system using the suggestions below/above
>
> Giles
>
>
> On Wednesday, 30 July 2014 06:38:17 UTC+1, William Hermans wrote:
>
>> Would be much easier to just use:
>>
>> cd ~/rootfs/
>> sudo tar -zcvf ~/rootfs.tar.gz .
>>
>> To compress and then.
>> sudo tar xzvf ~/rootfs.tar.gz -C /media/rootfs/
>>
>> To target a rootfs.
>>
>>
>> On Tue, Jul 29, 2014 at 7:05 PM, John Syn <[email protected]> wrote:
>>
>>>
>>>  From: Giles Godart-Brown <[email protected]>
>>> Reply-To: "[email protected]" <[email protected]>
>>> Date: Tuesday, July 29, 2014 at 2:26 PM
>>> To: "[email protected]" <[email protected]>
>>>
>>> Subject: [beagleboard] unable to boot Beaglebone Black from NFS
>>>
>>> I've seen many posts about how to boot a Beaglebone black via an NFS
>>> mounted root partition, but none seem to work with the latest version.
>>> I started by creating an NFS mount on my Ubuntu PC and successfully
>>> mounting it from the Beaglebone when booted from an SD image of the latest
>>> version dated 2013.06.20
>>> <https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.xz>
>>>  from
>>> the Beaglebone site. All the commands below were done as root.;
>>> uname -a
>>> Linux beaglebone 3.8.13-bone50 ....
>>> Then test the mount with;
>>> mount -o nfsvers=3 192.168.10.118:/home/bone /mnt/nfs
>>> Next I copied the entire filesystem to the nfs mount with
>>> cp -axv /. /mnt/nfs/.
>>>
>>> I’m not sure this is going to work because you are attempting to copy
>>> dynamic files and folders. Rather insert the SDCard into your host and do
>>> the following:
>>> sudo rsync -avz /mnt/rootfs/ /home/<userid>/targetNFS/
>>>
>>>
>>> I've edited the fstab on the nfs (/home/bone/etc/fstab) to add
>>> /dev/nfs / nfs defaults 0  0
>>> and correctly edited /home/bone/etc/network/interface to reflect the
>>> correct IP address etc.
>>> Next I edited the uEnv.txt on the SD card to add
>>> serverip=192.168.10.118
>>> ipaddr=192.168.10.47
>>> hostname=MH_bbb
>>> netmask=255.255.255.0
>>> gateway=192.168.10.1
>>> nfsdevice=eth0:off
>>> nfsopts=vers=3
>>> rootpath=/home/bone
>>> and changed the mmcargs line to;
>>> mcargs=setenv bootargs console=tty0 console=${console} ${optargs}
>>> ${cape_disable} ${cape_enable} ${kms_force_mode} ip=${ipaddr}:${serverip}:${
>>> gateway}:${netmask}:${hostname}:${nfsdevice} root=/dev/nfs rw
>>> nfsroot=${serverip}:${rootpath},${nfsopts}  ${systemd}
>>> The Bone starts to boot and I can ping it on the correct IP address, but
>>> the display never shows anything and it doesn't let me ssh to it.
>>> Can anyone let me know what I've missed?
>>> Thanks
>>>
>>> This is my complete uEnv.txt:
>>>
>>> ==============================
>>> client_ip=10.100.116.105
>>> server_ip=10.100.116.73
>>> gw_ip=10.100.116.1
>>> root_dir=/home/<userid>/targetNFS
>>> ==============================
>>>
>>> Replace <userid> with your own desktop login id and replace client_ip,
>>> server_ip and gw_ip addresses as required.
>>>
>>>
>>>
>>>
>>>
>>>  --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>  --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to