[Soekris] NFS root problems

Kyle Brantley kylesb at gmail.com
Mon Jun 13 19:39:05 UTC 2005


Client: 2.6.11.11 (read as: recent enough)
Server: 2.6.10 (read as: recent enough)

Both kernels have NFS 3 AND NFS 4 compiled into the kernel.
/etc/exports as follows:

/mnt/lfs                        192.168.0.0/16(sync,rw,no_root_squash)

All looks good. So I power on my soekris (net4521), and behold:

eth0: DSPCFG accepted after 0 usec.
eth0: link up.
eth0: Setting full-duplex based on negotiated link capability.
eth1: DSPCFG accepted after 0 usec.
Sending DHCP requests .<5>eth0: increased tx threshold, txcfg 0xd0f01004.
., OK
IP-Config: Got DHCP answer from 192.168.0.1, my address is 192.168.0.191
eth1: remaining active for wake-on-lan
IP-Config: Complete:
      device=eth0, addr=192.168.0.191, mask=255.255.255.0, gw=192.168.0.1,
     host=192.168.0.191, domain=l.brantleyonline.com, nis-domain=(none),
     bootserver=192.168.0.1, rootserver=192.168.0.3, rootpath=
Looking up port of RPC 100003/2 on 192.168.0.3
Looking up port of RPC 100005/1 on 192.168.0.3
VFS: Mounted root (nfs filesystem) readonly.
Freeing unused kernel memory: 156k freed
nfs_stat_to_errno: bad nfs status return value: 45
Warning: unable to open an initial console.
nfs_stat_to_errno: bad nfs status return value: 45
nfs_stat_to_errno: bad nfs status return value: 45
nfs_stat_to_errno: bad nfs status return value: 45
nfs_stat_to_errno: bad nfs status return value: 45
Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

Okay. Bad NFS status return value 45.

If I mount it on the server, so basically a loopback NFS share, it
operates fine.

If I mount it on my dev box (not my soekris), I get this fun
situation. I can ls the root mount point, but I can't cd into any
directories, or do ls -lah, as it requires recursing into the
subdirectories.

The thing that REALLY trips me up is that when it's mounted on my dev
box and I attempt to cd into a subdir, I get an *I/O error*. I've doen
all that I can. chmod 777 /mnt/lfs -R, everything, and I can't figure
this out. IRC help stated that I've stumbled across an NFS error that
"doesn't exist." Score one for me.

Which leads me to think: if it's an invalid NFS error, then it's
probably just returning a raw system error code. Kinda like how 13 is
always permission denied, well, what's 45? "LEVEL_TWO_NOT_IN_SYNC" ist
states.

Clues, anyone?



More information about the Soekris-tech mailing list