Could Not Mount Image
-
I am unable to get an image to upload. I’ve tried this from two machines and I get the same results.
I’m running on CentOS 7
Version: 6132
bzImage Version: 4.4.0
bzImage32 Version: 4.4.0All it says is:
An error has been detected!
Could not mount images folder (/bin/fog.upload)
Computer will reboot in 1 minute.The host register just fine. I’ve attached a screenshot of the error and the task that is running
![1_1454023576157_image1.JPG](Uploading 100%) ![0_1454023576157_Capture.PNG](Uploading 100%)
-
As you’re in debug, I’m going to guess you’re current working directory (found with
pwd
) is in /images on the client machine.Run:
cd fog
You should be good.
-
@Tom-Elliott
I run that from the machine connecting to the FOG server? -
@bberrelez Yes.
-
@Wayne-Workman
Tried that. Nothing happened. -
@bberrelez Teamveiwer maybe?
Hit me on chat. -
@Tom-Elliott said:
Teamveiwer
That would be awesome! Thanks! I could do a teamviewer session. Are you just wanting to see the management console or are you wanting to actually get on the linux box?
-
I ran into this before too. Check that nfs-server is running by running:
systemctl status nfs-server
If it’s not, you can manually start it with:
systemctl start nfs-server
This enables the service to start automatically on next boot, but it should already be enabled…
systemctl enable nfs-server
Which brings me to telling you to follow this guide on delaying the FOG services to fix the problem:
https://wiki.fogproject.org/wiki/index.php/Fedora_21_Server#Set_the_FOG_services_to_start_30_seconds_after_bootI needed to also add “systemctl start FOGPingHosts” to the rc.local on my CentOS 7 installation.
Two commands you can use to easily see what is/isn’t running on your CentOS 7 installation are:
pstree
&
systemctl list-units --type=service
-
Hello – I’m having a similar issue. I don’t want to hijack the thread, but I have checked to make sure the NFS server service has been started, and it has. If I boot into debug mode and check the current working directory, I am in the root directory – there seems to be no /images path. Again, not sure if it’s related, but I’m having the same problem.
-
Also ensure that all of the FOG services are running by entering:
systemctl list-units --type=service
You should see see all five Fog services in my screenshot as loaded, active, and running:
Another issue I’ve seen is the nfs-server service will show that it is running, but will be inactive and exited. Also double check that isn’t the case, because it will at a glance look as though it is loaded when you check status.
To verify the Images directory exists, try the following:
cd cd /images ls
You should be within the directory and able to see at least a directory called dev and postdownloadscripts.
-
@jgurka, here is a list of my running services. A few are stopped; do you suppose these are crucial processes?
-
It looks like you’re on CentOS 6 – I was assuming you were on 7 earlier. Is this the latest trunk build of FOG, btw?
I don’t think the stopped FOG services are crucial for what your problem is, but I’d start them back up anyway:
service FOGPingHosts start service FOGSnapinReplicator start
It looks like you have the IPv6 firewall still enabled…this might potentially be causing the problem? I’d go ahead and disable it:
service ip6tables stop chkconfig ip6tables off
Try it again and see if it made any difference.
-
@Vasahond said:
I am in the root directory – there seems to be no /images path.
Really? If that’s the case, that’s almost surely the problem. Can you please post the output of
find / | grep /dev/.mntcheck
Also, what output/errors do you get when you re-run the installer? You’ve also not specifically stated what version of FOG you’re using, we need this information as well.
-
Vasahond’s running services output seems to show it as existing and being mounted via NFS:
Configured NFS mountpoints: /images /images/dev Active NFS mountpoints: /images /images/dev
-
@jgurka Yeah I saw that, but the directory could still be missing. I’m most concerned with him not seeing a
/images
directory on his server.As a test, I just created a directory called
/image
and exported it in/etc/exports
, and restarted rpcbind and nfs-server and saw that NFS was running fine, I then deleted the/image
directory and then again checked NFS… still running fine. You’ll also hopefully understand that I have been bitten many times by making assumptions about things. No telling what the guy has copy/pasted into his server trying to get it to work. -
I definitely get where you’re coming from.
You can try running this to see whether or not /images actually exists:
[ -d /images ] && echo 'Directory Found' || echo 'Directory /images not found'
You should see "Directory Found’ if it does in fact exist.
-
@jgurka People like @george1421 suggest to put the images in /opt/fog/images, which is why I suggested searching for /dev/.mntcheck
-
Hello, i think i’ve got the same problem except i made modification on the web interface :
i didnt want the “images” directory be at the root (/images)
then i copy the images directory into /home/images.Then i modify the image path on the web interface, i thought it would modify the export file also but it seems not.
then i had to modify manualy the export file. Now it works fine.
Could it be the problem ? -
The images directory needs to have full r/w/x permissions in order for FOG to use it – did you make sure to change the permissions when you created the new directory and copied the contents of the old /images?
To check the directory permissions, run the following:
cd /home ls -la #You want permissions on the new images directory to be drwxrwxrwx and also on sub-directories
To enable full r/w/x permissions on the folder, run the following:
chmod -R 777 /home/images #-R will run it recursively to apply the permission changes to sub-directories as well as the top directory
-
I tried this and still nothing. I did find that I had an incorrect path list on the the image path under Storage management. I created a directory here: /home/fog/Images, applied the appropriate permissions and corrected the path under the storage management.
Still have the same message appearing.
Could not mount images folder (/bin/fog.upload)