Switching NAS servers
-
@szecca1 said:
I am getting a “failed to mount NFS volume” error
Double Check your NFS path in the storage node settings.
-
@Wayne-Workman There is no NFS setting in the storage node settings. Just IP address unless that setting is somewhere else
-
@szecca1 said:
@Wayne-Workman There is no NFS setting in the storage node settings. Just IP address unless that setting is somewhere else
Sorry, it’s called Image Path. Also, you’ll need a newer version of FOG Trunk to get the FTP Path field too.
You can use github to do that, or wait for Source Forge to get svn working again.
-
@Wayne-Workman Ok I was wondering why my svn wasn’t working. I am going to update using git right now and let you know how that goes. And thank you, no need to apologize at all.
I appreciate all the help!
-
It fails with this error. And I checked the file path and it should be good. I didn’t have to change that as that was the same for both synology boxes.
-
@szecca1 Can’t skip steps
https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk#GitAnd you’re supposed to change /some/local/folder to a folder where you want your git repository stored.
-
@Wayne-Workman haha yea I was hoping to just change the IP address and it would work. But I just updated the GIT and still getting the same issue.
-
@Wayne-Workman I feel like I am back to the beginning where you guys helped me fix this a few months ago. I still am getting the same error or fatal error failed to mount NFS volume. I followed some things on the wiki page but maybe I am missing something. Any thoughts? I have a feeling it has to do with the fact that the .mntcheck is not on the new synology box but I can’t figure out how to get it there.
-
@szecca1 the .mntcheck file is just a blank file. FOG merely checks that it exists - hence the name mntcheck. If FOG can see a file named that, then FOG knows that NFS has been mounted correctly.
To create this file, just issue the touch command in the images and dev directories.
touch .mntcheck -
@Wayne-Workman I did that and that file is not showing up on my Synology server. I am not sure if this is what is causing my issue but I am still getting that error message. I am not sure what I did wrong
-
@szecca1 I don’t think the mntcheck files are the issue. If FOG couldn’t find them, it’d say it couldn’t find them. Your problem happens before the check - it fails during mounting.
I’d ensure that your /images directory on the new synology box is being shared via NFS with 777 permissions on it.
-
@Wayne-Workman I just did that and still getting the same error message. Maybe it still thinks I am trying to give the old Synology box those rights? Is there a way to check if in Linux, the IP address is the right Synology box?
-
@Wayne-Workman Should I delete the storage node and start over?
-
@Wayne-Workman https://wiki.fogproject.org/wiki/index.php/NAS_Storage_Node
Or should I follow these instructions?
-
@szecca1 said:
@Wayne-Workman https://wiki.fogproject.org/wiki/index.php/NAS_Storage_Node
Or should I follow these instructions?
Those instructions have been made somewhat obsolete with the new FTP Path feature.
I’d say run through the troubleshooting found here to see what your issue with NFS is:
https://wiki.fogproject.org/wiki/index.php/Troubleshoot_NFSI’d pay special attention to the testing NFS bits at the top.
-
@Wayne-Workman Good morning, I just tried doing what you sent me and I created the text file but when I boot my machine it just boots to windows. Theres no options on the screen like the instructions say there should be
-
@Wayne-Workman Ok I got in but when I follow these instructions:
Next, we will mount to FOG’s remote image directories like this:mount -o nolock,proto=tcp,rsize=32768,intr,noatime $storage /images
mount -o nolock,proto=tcp,rsize=32768,intr,noatime 10.0.0.3:/images/dev/ /images/devI am getting an error " mount: mounting 10.1.0.227:/volume1/FOG/Images/dev/ on /images failed: invalid argument
-
@szecca1 Did you create the local /image and /image/dev folders?
-
@Wayne-Workman Yes I followed those commands, it didnt say that it did but it didnt give an error message when I typed those commands
-
@szecca1 I just reviewed the commands and changed one of them. Can you look at that and try again?
