Hi, to follow jacs hint I will create a new thread for NFS with jacs modified firmware. My problem is that after installing the alternative firmware annd downloading the extrafs modules tgz and using the script that is in the announcement thread I got the following: insmod: cannot insert `/harddisk/volume_3/data/extra/modules/fs/nfsd/nfsd.ko': Unknown symbol in module (-1): No such file or directory dmesg gives: nfsd: Unknown symbol posix_acl_from_xattr nfsd: Unknown symbol posix_acl_to_xattr nfsd: Unknown symbol posix_acl_valid nfsd: Unknown symbol nfsacl_decode nfsd: Unknown symbol posix_acl_alloc nfsd: Unknown symbol nfsacl_encode nfsd: Unknown symbol posix_acl_from_mode What went wrong ?
Did you try my tarball? I have to say I don't use it myself because NFS is so slow but I did test it once. ===Jac
Hi jac, yes, I tried your tarball but the executables in .../sbin are missing, and the nfsd prints the messages in dmesg. Any hints ??
NFS on NAS200 Hello, I am having the same problems, I would like to enable NFS version 3 over TCP on the NAS200 as then I can use it as a datastore for ESX 3.5. $ insmod nfsd.ko Using nfsd.ko insmod: cannot insert `nfsd.ko': Unknown symbol in module (-1): No such file or directory dmesg nfsd: Unknown symbol posix_acl_from_xattr nfsd: Unknown symbol posix_acl_to_xattr nfsd: Unknown symbol lockd_up nfsd: Unknown symbol posix_acl_valid nfsd: Unknown symbol nfsacl_decode nfsd: Unknown symbol export_op_default nfsd: Unknown symbol lockd_down nfsd: Unknown symbol find_exported_dentry nfsd: Unknown symbol posix_acl_alloc nfsd: Unknown symbol nfsacl_encode nfsd: Unknown symbol posix_acl_from_mode nfsd: Unknown symbol nlmsvc_ops Can anyone please help? Thanks, Jan
You should try: $ modprobe nfsd Instead of insmod... modprobe will resolve dependancies and load the required modules.
modprobe is not supported by the NAS200. The problem is that the module dependencies aren't part of the file system so modprobe has nothing to go by. I compiled NFS into the kernel as modules but the modules aren't part of the file system. For Jac0 they are already available (see the Jac0 thread) but it looks like I'll have to put different modules online for Jac2 because the kernel config is different so the symbol table doesn't match. I'll try to make the necessary modules available some time this week. Sorry for the inconvenience and thanks in advance for your patience. ===Jac
The NFS file system modules (and some other ones such as ISO9660) for the Jac2a firmware are now available from my website at http://www.goudsm.it/nas200/extrafsmodules_jac2a.tar.gz. Note, these are only the kernel modules, the NFS daemon binaries aren't included and I don't currently have them (I misplaced them somewhere); if someone can put these online somewhere, that would be cool... ===Jac
Jac, Were you (or anybody else) ever able to track down the NFS daemon binaries? They've proven to be surprisingly difficult to find. Thanks! - Jerfo
I probably stored them on my old Linux machine which has started gathering dust since I bought my new notebook last August. I'll see if I can dig it up next weekend. As for the NFS binaries... Basically to build the binaries for software such as NFS, Dropbear, net tools and some other stuff, I went through the TinyGentoo page to set up an i386-based toolkit and chroot, and then Emerged the packages into an empty directory. Then I simply uploaded the binaries to the NAS200 and tried them out to see if they worked, and I was lucky :grin:... ===Jac
I succesfully built unfsd (the userspace nfs server) and portmap for nasi200 using some quick dirty hacks in the source codes of tcpwrappers, portmap and unsfd. I accidently deleted the source when I was cleaning my homedir but still got the binaries. If jac2b uses the same uclibc version as nasi200 it should work there too since it runs in userspace only. If not, it was only an hour work so have fun hacking Binaries can be found on http://lars.opdenkamp.eu/unfsd.tar.bz2
Thanks. I'm usually a Fedora user, but I'll see if I can run through that process to build the binaries myself. Here's a silly question for you: since root is mounted read-only, where should these executables reside? - Jerfo
Unfortunately it's not TOTALLY straightforward... but as long as you understand the purpose of each of the commands you will know which ones to skip and which ones to change. Sorry I don't have time to write an easy list of instructions... Silly answer to a silly question: this is a NAS so you got tons of disk space to put anything you want. All you need to do is change the access rights so the files become executable, and write a script in rc.d. There's a script in the Jac0 thread if I remember correctly. ===Jac
