June 4, 201412 yr I've exhausted hours on google, and its just not working. At all. I can get it to manually mount .. sometimes. But if you're a Mac user, you'll know this doesnt work. As with every boot you'll have to create the folders in /Volumes/ all over again and its not something that can be easily automated. Here is what I've done so far: - This guide fixes illustrates a fix to the /volumes/ creations problem, and a fix. Except, the folders are very unresponsive and they dont show anywhere (desktop, sidebar) unless you manually try to activate them, which often means running the automount command manually ... like every 2-3 hours. - Manually mounting using 'http://www.bresink.com/osx/NFSManager.html' is great! it works, its fast, its on the desktop, its everywhere and I get 100mb read/write easy .. every single time. Its just the volumes dont survive reboots. - Automatically mounting using the same tool (NFS Manager) says that I (the admin user) do not have access to /local/default is restricted and broken in Mavericks .. and that I should upgrade to another OS or downgrade. Which is not an option for me. Why arent I using SMB or AFP? - SMB2 and CIF is basically broken on mac and with the new service pack, its even more so. Finder hangs every time I try to mount anything and results in me having to restart my array to make it responsive again. - AFP is horrible, slow reads/writes, creates like 3-4 types of useless folders everywhere .appledouble..etc) What I hope to accomplish So what I learned so far, is that I need to run an Active directory .. somewhere .. that way I can auto mount everything, and everyone will be happy. So far, from what I've seen, this can only be done on Windows Server (is this true? can I not run an active directory on unraid? sorry if that sounds stupid). Not even sure if this is the best thing to do, but any help or guidance would be really appreciated. Thanks, I am running unraid v6b5a, but the problem existed even on latest stable build.
June 4, 201412 yr I can't say much for your NFS problems. I don't use it. It surprises me though that you're still having problems with samba. My system has been running, mounting etc. great with no problems. I'm using Mavericks and unRaid 5.0.5 though. Perhaps these problems are only in version 6?
June 4, 201412 yr Author Perhaps these problems are only in version 6? I think you may be right, I cant downgrade now. Will have to wait for the new beta perhaps? Because I remember reading that Unraid 6 is using a 'new' version of Samba, so that could be it. I had less issues before on 5 for Samba, thats for sure. But this is a beta software, so this is to be expected. I just thought I could make NFS work.
June 4, 201412 yr i connect to unraid via samba, but i have a server that shares a couple zfs pools via nfs ... i connect to these shares using a script. it is manual, but i believe you can automate via launchd and choosing a mount point other than in /Volumes (so that you dont need to sudo). Or you could make your user have write permissions on /Volumes and make mount not to ask for a password when called via sudo (man sudo then run visudo). if [ ! -d "/Volumes/skynet/staging" ]; then sudo mkdir -p /Volumes/skynet/staging fi if [ ! -d "/Volumes/skynet/cache" ]; then sudo mkdir -p /Volumes/skynet/cache fi if [ ! -d "/Volumes/skynet/backup" ]; then sudo mkdir -p /Volumes/skynet/backup fi if [ ! -d "/Volumes/skynet/storage" ]; then sudo mkdir -p /Volumes/skynet/storage fi if [ ! -d "/Volumes/skynet/home" ]; then sudo mkdir -p /Volumes/skynet/home fi sudo mount -t nfs -o resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=32768 skynet:/mnt/staging /Volumes/skynet/staging sudo mount -t nfs -o resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=32768 skynet:/mnt/cache /Volumes/skynet/cache sudo mount -t nfs -o resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=32768 skynet:/mnt/backup /Volumes/skynet/backup sudo mount -t nfs -o resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=32768 skynet:/mnt/storage /Volumes/skynet/storage
Archived
This topic is now archived and is closed to further replies.