Re: NFS boot - could not open /.tftp_tmp_path

[Sascha Hauer <s.hauer@pengutronix.de>]

On Fri, Aug 10, 2018 at 08:08:04AM +0200, Sam Ravnborg wrote:
> Hi Ulrich.
> > > Hi Ulrich
> > >> > Then when I try to boot from nfs I get the following output:
> > >> >
> > >> > barebox: boot nfs://192.168.86.201/nfsboot/arm9/
> > >> 
> > >> you already have the slash separating the host part of the URL and the
> > >> path part, but you missed the slash that is needed at the beginning of
> > >> the absolute path:
> > >> 
> > >>   boot nfs://192.168.86.201//nfsboot/arm9/
> > >> 
> > >> (with a two slashes) should hopefully do the trick.
> > >
> > > Hmm, no luck:
> > > barebox:/ boot nfs://192.168.86.201//nfsboot/arm9/
> > > eth0: DHCP client bound to address 192.168.86.20
> > > T T T T T T T T T T T T T T could not open /.tftp_tmp_path/zImage-at91sam9263ekt
> > >
> > > barebox:/ boot nfs://192.168.86.201//nfsboot/arm9
> > > eth0: DHCP client bound to address 192.168.86.20
> > > T T T T T T T T T T T T T T could not open /.tftp_tmp_path/zImage-at91sam9263ekt
> > >
> > > I will try to add some debugging and see whats going on.
> > 
> > Do you see anything of interest in the server's log?
> 
> 
> I got it working, using a slighly different approach.
> 
> I now have:
> 
> barebox: cat /env/init/automount
> #!/bin/sh
> 
> mkdir -p /mnt/nfs
> automount -d /mnt/nfs 'ifup -a && mount -t nfs 192.168.86.201:/nfsboot/arm9 /mnt/nfs'
> 
> barebox: cat /env/boot/nfs
> #!/bin/sh
> 
> nfsdir="/mnt/nfs"
> 
> global.bootm.image="${nfsdir}/boot/zImage"
> 
> nfsroot="192.168.86.201:/nfsboot/arm9"
> 
> global.linux.bootargs.base="rw rootwait init=/usr/bin/system-init.sh"
> global.linux.bootargs.dyn.root="root=/dev/nfs nfsroot=${nfsroot},v3,tcp"
> 
> 
> Then I can nfsboot my kernel using "boot nfs"
> 
> The solution has my NFS server IP IP hardcoded as the NFS server IP
> is not the same as the DHCP IP, so no way to find it automagically.
> 
> In the linux kernel I also selected NFS + NFS boot to make it work.
> 
> With the above I have something that do what I need - good!
> 
> Thanks for the help/hints.

Nevertheless I would be interested why the original approach did not
work since that would be the preferred one.

Do you have bootloader spec enabled in barebox and do you also have a
bootloader spec config file on the root NFS?

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox