@sebastian-roth Ok - thank you - that works! ( I actually did see mention of this but did not quite follow through on testing it)
ipxe boot issues with https enabled (I enabled https on the old server and it all went wrong).
Ran into this issue again with new server this morning – looked at the system time of the pc, date was way off – corrected and booted fine…I gather system time + UEFI + https ipxe is crucial?
Regardless, I appreciate the quick replies!
Hello all,
Cannot seem to find this info, hence the post.
Issue with my old FOG server prompted me to “kill” it and create a new one.
Before I did kill it, I copied the images off to a network share.
So now I am attempting to “hard copy” the images back into the new server image dir - and of course the WEB UI under IMAGES does not see them.
Any direction on steps to accomplish a migration this way?
@x23piracy How are you fogging your Win10 machines?
I can create a fresh image and deploy to Bios in Legacy mode but then I can’t use the embedded key.
All my attempts at UEFI capture/deploy fail.
We are a Dell shop – would love to know how you are accomplishing this.
@Tom-Elliott
777 should be cut and dry-- I’m the first to suspect error to be mine.
I am more than willing to do a fully documented build if you like. I have a shiny new Compellent with some top end ESXI hosts at my disposal- installation from OS to Fog takes no time at all.
My build in my isolated home lab worked completely 1st try- building in our domain environment added a few extra mods as expected but I was not expecting these errors.
On build #4
Did not create a user - logged in and installed all as root
Build#5
created my standard non-admin user to log into and install all using su.
Both of these builds resulted in root:root permissions until corrected.
@junkhacker
(i create an ‘foguser’ but not ‘fog’)
Update - I rebuilt the server from the ground up again to ensure I did not miss anything.
I did.
This was still required:
[root@FOG /]# chown -R fog images/
But there was another posting with nfs-server references that I used as well
I needed to start the nfs server:
[root@FOG /]# systemctl status nfs-server
[root@FOG /]# systemctl start nfs-server
[root@FOG /]# systemctl enable nfs-server
Working great so far
So I believe I solved this - your chmod is exactly right - I was chewing on the /images permissions owner last nght, got into the office and looked at it with fresh eyes…simple problem, simple solution.
[root@FOG /]# ls -la images/
total 0
drwxrwxrwx. 4 root root 61 Mar 8 18:04 .
dr-xr-xr-x. 20 root root 284 Mar 8 17:33 ..
drwxrwxrwx. 3 root root 46 Mar 8 18:02 dev
-rwxrwxrwx. 1 root root 0 Mar 8 18:00 .mntcheck
drwxrwxrwx. 2 root root 30 Mar 8 17:33 postdownloadscripts
[root@FOG /]# chown -R fog images/
[root@FOG /]# ls -la images/
total 0
drwxrwxrwx. 4 fog root 61 Mar 8 18:04 .
dr-xr-xr-x. 20 root root 284 Mar 8 17:33 ..
drwxrwxrwx. 3 fog root 46 Mar 8 18:02 dev
-rwxrwxrwx. 1 fog root 0 Mar 8 18:00 .mntcheck
drwxrwxrwx. 2 fog root 30 Mar 8 17:33 postdownloadscripts
[root@FOG /]#
I then bounced my test client and it picked up its capture task immediately as it did in my test lab. (Test lab in esxi server hosting fog to a pc on same vlan hosting test client in vmware workstation worked 1st try. Implementing this in a Windows Domain environment was still easy with the exception of this one speedbump)
To be utterly complete I will still need to Deploy a Captured image.
This solution is painfully obvious I admit, Your tutorial is excellent- however I might suggest for those following it to spec this albeit obvious permissions update might be included as optional for this error only?
Hi Wayne, thank you for the prompt response - PDQ said you guys were helpful !
So this is my 4th build from the ground up - didn’t bother adjusting swap or boot (i’m not worried about space) – error is identical through.
As per your post-config timing options, I have tried with and without --the error remains.
My config will not allow the Client to upload its Capture image to the /image dir.
Fun fact- the fog dashboard clearly shows the Storage Node Disk Usage at 1TB.
[root@FOG ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/cl-root 20G 5.4G 15G 27% /
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 84K 3.9G 1% /dev/shm
tmpfs 3.9G 8.9M 3.9G 1% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sda1 1014M 227M 788M 23% /boot
/dev/mapper/cl-images 1021G 33M 1021G 1% /images
tmpfs 783M 16K 783M 1% /run/user/42
tmpfs 783M 8.0K 783M 1% /run/user/0
userx@127.0.0.1:/cygdrive/C/Users/userx/X2GO~1/S-ROOT~2/spool 225G 140G 85G 63% /tmp/.x2go-root/spool/C-root-50-1489040562_stDXFCE_dp32
[root@FOG ~]#
[root@FOG ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1T 0 disk
├─sda1 8:1 0 1G 0 part /boot
└─sda2 8:2 0 1T 0 part
├─cl-root 253:0 0 20G 0 lvm /
├─cl-swap 253:1 0 7.9G 0 lvm [SWAP]
└─cl-images 253:2 0 1021.1G 0 lvm /images
sr0 11:0 1 7.7G 0 rom
[root@FOG ~]#
I am more than willing to rebuild the entire OS/FOG from the ground up with snapshots of EVERY phase to help solve this.
Mod edited to use code boxes.
I have followed the tutorial here:
https://wiki.fogproject.org/wiki/index.php?title=CentOS_7
to the letter…3 times.
I keep receiving the same error:
reason: mount: mounting 192.168.x.x:/images/dev/ on /images failed: operation not supported
So to me it appears that there needs to be a permssions change on the /image partition.
chmod -R 777 is applied.
I did have success when I logged in as fog, created a images dir under fogs home and cp -rf the /images contents to it.
however, i only have 20GB available, not the TB I partitioned for the /images.
I think i can “hack & slash” to fix this but I’m hoping there is a simple clean solution.