Re: [Ltib] Problems with tftpnfsbooting RDB-8377E board

[Mike Goins]

I went through something similar and noticed that the ethernet device
I was using for nfs was also set to dhcp in the boot process.  I
modified the system device settings in --config to not use dhcp.
"Sending discover.." looks like the dchp client.




On Wed, Jul 8, 2009 at 6:30 PM, B.J. Buchalter<address@hidden> wrote:
> Hi Folks,
>
> I have been trying to boot my RDB-8377e board with a newly built kernel and
> root file system using the TFTP for the kernel/bootimage and NFS for the
> root filesystem (built with LTIB).
>
> This appears to work OK until the very end of the boot process where I get
> the following:
>
> => run tftpnfsboot
> ...
> IP-Config: Complete:
>     device=eth0, addr=10.0.1.231, mask=255.255.255.0, gw=10.0.1.1,
>     host=PowerQUICC, domain=, nis-domain=(none),
>     bootserver=10.0.1.42, rootserver=10.0.1.42, rootpath=
> Looking up port of RPC 100003/2 on 10.0.1.42
> PHY: e0024520:02 - Link is Up - 100/Full
> Looking up port of RPC 100005/1 on 10.0.1.42
> VFS: Mounted root (nfs filesystem).
> Freeing unused kernel memory: 168k init
> Mounting /proc and /sys
> Starting the hotplug events dispatcher udevd
> Synthesizing initial hotplug events
> Setting the hostname to mpc837xe-rdb
> Mounting filesystems
> mount: proc already mounted
> rootfs / rootfs rw 0 0
> /dev/root / nfs
> rw,vers=2,rsize=4096,wsize=4096,hard,nolock,proto=udp,timeo=11,retrans=2,sec=sys,addr=10.0.1.42
> 0 0
> proc /proc proc rw 0 0
> /sys /sys sysfs rw 0 0
> tmpfs /dev tmpfs rw,mode=755 0 0
> devpts /dev/pts devpts rw,mode=600 0 0
> rwfs /mnt/rwfs tmpfs rw,size=512k 0 0
> mount: can't find / in /etc/fstab or /etc/mtab
> It appears that your root file system was not cleanly shutdown.
> Please wait while checking /dev/nfs
> fsck 1.34 (25-Jul-2003)
> fsck.ext2: No such file or directory while trying to open /dev/nfs
> /dev/nfs:
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
>    e2fsck -b 8193 <device>
>
> File system check completed.
> mount: can't find / in /etc/fstab or /etc/mtab
> mount: devpts already mounted or /dev/pts busy
> mount: sysfs already mounted or /sys busy
> Running sysctl
> Setting up networking on loopback device:
> Setting up networking on eth0:
> udhcpc (v1.11.2) started
> Sending discover...
> nfs: server 10.0.1.42 not responding, still trying
> nfs: server 10.0.1.42 not responding, still trying
> nfs: server 10.0.1.42 not responding, still trying
> nfs: server 10.0.1.42 not responding, still trying
> nfs: server 10.0.1.42 not responding, still trying
> nfs: server 10.0.1.42 not responding, still trying
> nfs: server 10.0.1.42 not responding, still trying
> nfs: server 10.0.1.42 not responding, still trying
> nfs: server 10.0.1.42 not responding, still trying
> nfs: server 10.0.1.42 not responding, still trying
>
> =====
>
> At which point the console more or less hangs (e.g. <control>-C will receive
> a ^C response on the serial port, but there is no meaningful interaction).
> The board does not respond to pings at this point.
> I have verified that the NFS server does indeed provide service to the board
> at the assigned IP address. I can download an image from the NFS server via
> uBoot on the board, and the NFS server does allow me to mount the root
> filesystem.
>
> Does anyone have any advice on how to proceed or things to look for?
>
> Thanks!
>
> B.J. Buchalter
> Metric Halo
> http://www.mhlabs.com
>
>
>
>
>
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib
>