@Sebastian-Roth Hi, Yep and it was very helpful for me, just execute the last command after coming back to the snapshot and all is good now :-).
Thanks a lot to Tom Elliot for this post.
Have a nive day
Thanks a lot for your answsers, i will try your advices and come back soon.
Edit : Just tried to modify my /etc/exports file but got the same error again. But i go back to “before update state” why my snapshot and see that before update values in /etc/exports was /media/administrateur/images and /media/administrateur/images/dev like you say @Sebastian-Roth.
That means that update to 1.5.7 modify my configuration in some ways in this files but not only because if i change it after update it not works.
Have a good day.
Well i follow a tutorial on the forum to add a another disk on my Vm for all the images because i have many to manage in the school network i handle. So all the images is on this disk.
That’s the results of commands
So /dev/sdb is the images disks and it is mount on /media/administrateur/images, that’s the way it’s configured in the storage node in the GUI and before the update to 1.5.7 it worked good.
In the .fogsettings the “storageLocation” was /images before the update so i let it. Update changes fogproject si i move it to fog in this file.
I have a snapshot before the update so ichecked many things on files and GUI before and after update and tried to configure same things on same place but i d’ont know i must forget a thing …
Please excuse me if my english is not perfect …
I have update my FOG Server (Ubuntu) 126.96.36.199 to 1.5.7, all seems to go well except when i try to download image on a host i have a mount error
I have test many things i seen on many topics of this forum like this one https://forums.fogproject.org/topic/9823/mounting-images-dev-on-images-failed-permissions-denied :
Wayne Workman Mar 30, 2017, 3:41 AM
Make sure NFS is running with:
systemctl status nfs-server
Set the ownership of the images directory to user fog and group root like this:
chown -R fog:root /images
Then try again.
Also, see what this says:
Also check the .mntcheck files
Before upgrade the user in fogsettings and GUI was Fog, upgrade changed it in Fogproject then i changed it again in Fog but got the same error again.
My server has a separated disk for images but seems ok because the mounting looks good in fstab, and Fog server recognize images and space on “Storage Node disk Usage” in dashboard.
The problem is i think localise in this part of the error message "storage=10.149.20.64:/media/type=down but can’t say why appear.
Thanks again, it’s ok on both Vms and 3050 with “REFIND_EFI” Bios Exit Type.
We can pass this post in resolve state.
Have a good day.
Thanks for the answer, i alreadey try to change it to “Grub”.
I will try other options.
I am using FOG since few years and i have a recent problem.
I am actually preparing W10 systems for my school, have to use GPT partition to work well with new processors.
I have just migrate to 188.8.131.52 to avoid problems with UEFI. I am able to capture and download images without problems on physical or Vms. But if i configure UEFI to boot to NIC ipv4 first and if no FOG task configured for the host i got this message :
Seems FOG can’t link the boot to the disk system.
I have configure my DHCP server to use ipxe.efi file like it is describe on the link i see on few topics here.
And seems it’s ok because FOG is able to launch well tasks.
I have this problem on both Vms and physical computers (tests on Optiplex 3050). I have correctly configure the bios i think.
I want to try other kernels but not sure it works better.
Hi FOG Community,
I do have fix my error 4xx issue but got a new one this morning :-) :
The symptoms not exactly the same when i try to reach the GUI, the browser is serching a while then respond a “504 Gateway Timeout” Error.
And it get the screenshot message on the client pxe boot.
After fixing my “Http 4xx error client” with “ALTER USER” command i was able to capture images and server seemed fixed but this morning it seems not that well.