NFS volume failed to mount
-
@abos_systemax Yes. They have to be in their folders directly under /images (eg /images/W7IMAGE instead of /images/FOGIMAGES/W7IMAGE)
-
@Quazz changing the root path did not solve the issue.
-
@abos_systemax What’s the output of
ls -lah /images ls -lah /images/devAlso, can you try disabling the firewall? (rather than flush it)
-
root@NLBDGASS-X03:/# ls -lah /images total 56K drwxr-xr-x 11 fog root 4.0K Jan 9 13:40 . drwxr-xr-x 25 root root 4.0K Jan 8 17:03 .. drwxr-xr-x 2 fog root 4.0K Dec 23 14:08 M900_v1 drwxrwxrwx 2 fog root 4.0K Jan 8 16:15 dev drwxr-xr-x 2 fog root 16K Jan 8 15:44 lost+found -rwxrwxrwx 1 fog root 0 Jan 9 09:36 .mntcheck drwxr-xr-x 2 fog root 4.0K Jan 8 16:15 postdownloadscripts root@NLBDGASS-X03:/# ls -lah /images/dev total 8.0K drwxrwxrwx 2 fog root 4.0K Jan 8 16:15 . drwxr-xr-x 11 fog root 4.0K Jan 9 13:40 .. -rwxrwxrwx 1 fog root 0 Jan 9 09:37 .mntcheckIPTables has been removed (apt-get remove --purge iptables) and the server has been rebooted, but no change
-
@abos_systemax What’s the name of the image you’re trying to deploy? Also, permissions on
/imagesshould be 777 recursive for troubleshooting purposes. We first want it working, you can change whatever you want after it’s working.You might also try to mount the NFS share manually using debug mode to see what sort of error you get. Instructions on that (and other stuff) are here:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_NFS -
What’s the status of:
sudo ufw status -
Also - you’re adding another drive to the system. Why? Is SDA full? If so, this would cause some pretty major weirdness. Check with this command:
df -hand look for mount points with 99% or 100% usage. -
@Wayne-Workman
The reason why I am using another disk is because we want the images and the server to be separated for replication/backup/restore possibilities.
That is why SDA is only 30GB, and the SDB is 1.2TBRight now I am reïnstalling the server to see why my FOG install seems to be weird; the password etc don’t match, and the FOG client appears to be 1.2.0 instead of 1.3.0 (dunno if that is what it should be). Upgrading the Kernel doesn’t work.
I did first install FOG 1.2.0 by accident; after which I upgraded to 1.3.1, but there might be some configuration issues?
Will post results asap
-
@abos_systemax You might need to check the /var/www/fog folder and the /var/www/html/fog folders.
If my guesses are right, right now they’re both individual folders. This would seem to be the cause of the “I installed 1.3.0 but it still looks like 1.2.0”.
-
@Tom-Elliott
they were indeed! I was wondering where that issue arose from -
@abos_systemax To fix, typically I will find out which holds the current (most likely /var/www/html/fog).
Then I will do:
sudo rm -rf /var/www/fog sudo ln -s /var/www/html/fog /var/www/ -
Trying to hit you on chat with more ideas.
-
@Tom-Elliott Thanks Tom for the quick help;
For the others in this topic: Thanks as well,
The issue has been resolved. Apparently there was a misconfiguration ‘somewhere’ in the server setup.
I installed FOG 1.2.0 and immediately upgraded to 1.3.1, then configured the SDB harddisk and the images (which were copied from another server), chown-ed and grpch-ed the folders, reconfigured the node and MySQL …somewhere some setting went wrong;
I’ve reinstalled the server and started from scratch with Fog 1.3.1, now everything works as intended.
-
@abos_systemax next time please include the bigger story. In this situation, telling us that this was a migration would have caused us to ask different questions.
-
@Wayne-Workman I will. I did not pay much attention to it because I assumed that I installed 1.3… but during our Q&A, i slowly realized that there might be an issue with my initial install, especially when I noticed that the FOG client that loaded was 1.2, not 1.3 (but that skips so darn fast that I noticed only after 3 reboots…)
