Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
So I recently got this DNS-320L and followed this tutorial (http://www.nasdestruction.com/tutorial- … 0-dns-325/) to install Debian Squeeze and some other tools on my NAS... however, after doing this and getting everything up and running, I noticed that I lost the NFS support.
When I use the native web interface of the NAS even if I configure the share and enable nfs, it simply will never show as enabled and it just doesn't work.
Do I need to do some additional steps to get it up and running under Debian Squeeze?
Thanks in advance for any help!
Offline
I have the same issue with my Debian chroot: NFS seems to crash after during the boot process
Here is the output of dmesg:
[...]
svc: failed to register lockdv1 RPC service (errno 97).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: unable to find recovery directory /var/lib/nfs/v4recovery
NFSD: starting 90-second grace period
nfsd: last server has exited, flushing export cache
svc: failed to register lockdv1 RPC service (errno 97).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: unable to find recovery directory /var/lib/nfs/v4recovery
NFSD: starting 90-second grace period
I noticed that after a reboot, the NFS shares do work, at least for 60 seconds... It seems something makes the nfs server (maybe during the chroot)
I managed to watch the export list (NFS shares) from another PC with the command "showmount -e nas"
When the NFS server crashes, the /etc/exports file inside the firmware is cleared, which explains why restarting NFS server from the DLink menu does not work.
To successfully restart NFS:
1) in DLINK firmware, disable NFS (clear the /etc/exports file)
2) Restore a backup of the /etc/exports (located at /mnt/root/etc/exports from the chroot)
3) in DLINK firmware, enable NFS
You're done, NFS is back. The only issue is that shares are not visible in the Dlink interface but you can still mount them.
The command "showmount -e nas" confirms the NFS server is running.
Now we have to figure out why the NFS server crash during startup, if the debian chroot is enabled...
Offline
If I switch from Debian chroot to FFP, NFS is back... strange.
Some thoughts:
From the firmware side, RAID is mounted on /mnt/HD/HD_a2
The debian chroot is physically located in /mnt/HD/HD_a2/debian (in my case)
The Debian fun_plug script is also mounting the RAID array (bind) on the Debian chroot (so that the disks are available inside the chroot) in /mnt/HD/HD_a2/debian/mnt/HD/HD_a2
This implies a kind of loop, because the RAID array (which contains the debian chroot) is mounted inside the chroot
/mnt/HD/HD_a2/debian/mnt/HD/HD_a2
/mnt/HD/HD_a2/debian/mnt/HD/HD_a2/debian/mnt/HD/HD_a2
/mnt/HD/HD_a2/debian/mnt/HD/HD_a2/debian/mnt/HD/HD_a2/debian/mnt/HD/HD_a2
and so on...
Offline