@george1421 I was able to figure it out. After RSYNC’ing the directories you have to export the images off the old server and then on the new server you have to import the images. Tested an image to a laptop and it worked.
Thank you for all the help. All good now.
In case anyone else is experiencing the same issue, I figured this one out.
routeraddress was missing in .fogsettings
cd /opt/fog
vim .fogsettings
enter router/default gateway IP between single quotes
routeraddress='192.168.1.1'
reboot server.
Team,
Seeing this error on our new fog (1.5.10.1622) deployment
Could not mount images folder (bin/fog.upload)
Args Passed:
Reason: mount: mounting 192.168.0.20:/images/dev on /images failed: no route to host
[root@fogserver etc]# sestatus
SELinux status: disabled
[root@fogserver etc]# firewall-cmd --list-all
public (active)
target: default
icmp-block-inversion: no
interfaces: ens33
sources:
services: cockpit dhcpv6-client ssh
ports: 80/tcp 443/tcp 69/udp 111/udp 111/tcp 2049/tcp 49152-65532/udp 2049/udp
protocols:
forward: yes
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
[root@fogserver etc]# ls -alrt /images/
total 4
-rwxrwxr-x. 1 fogproject fogproject 0 Oct 31 12:27 .mntcheck
drwxrwxr-x. 2 fogproject fogproject 30 Oct 31 12:27 postdownloadscripts
drwxrwxr-x 4 fogproject fogproject 61 Oct 31 12:27 .
drwxrwxr-x. 3 fogproject fogproject 58 Oct 31 12:27 dev
dr-xr-xr-x. 21 root root 4096 Nov 4 13:00 ..
[root@fogserver etc]# vim /etc/exports:
/images *(ro,sync,no_wdelay,subtree_check,insecure_locks,all_squash,anonuid=1001,anongid=1001,fsid=0)
/images/dev *(rw,async,no_wdelay,subtree_check,all_squash,anonuid=1001,anongid=1001,fsid=1)
Thoughts on what could be wrong? The client boots to fog so the server client communication is working.
Thanks,
Joe
@sebastian-roth Thanks Sebasian I appreciate the input and had a feeling you would say that. Was worth the ask though! Hats off to ya! Cheers
Is it possible for Fogserver to pull an image live on Windows without having to reboot/boot to pxe? If so can someone link the instructions? Currently we are using a product called Aomei on a USB Stick and it pulls a Windows backup or clones the entire disk live.
@sebastian-roth said in /bin/fog.upload doesn't exist:
mkdir /fogserver/images/dev
chmod 777 /fogserver/images/dev/
touch /fogserver/images/dev/.mntcheck
exportfs -r -v
Thanks for the help on this @Sebastian-Roth this was the fix. I also 777 .mntcheck but not sure if this is/was necessary.
@george1421 Here is the showmount:
[root@fogserver ~]$ showmount -e 127.0.0.1
Export list for 127.0.0.1:
/fogserver/images/dev *
/fogserver/images *
[root@fogserver ~]$
[root@fogserver ~]$ firewall-cmd --list-all
FirewallD is not running
[root@fogserver ~]$
Filesystem is local so NFS is not being used either. Is there any reason why fog.upload is missing or is there a way to create it? We may have to troubleshoot on the client side to see.
Host is on a different subnet but is able to see fogserver from PXE even shows the fogserver version. Fails when checking mounted file system.
Here is fstab:
[root@fogserver ~]$ cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Fri Jan 18 14:32:07 2019
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=d3680351-a819-4c0c-89a1-b057c9d706a6 / ext4 defaults 1 1
UUID=80abf18a-7119-46a7-ac46-422183088f2e /boot ext4 defaults 1 2
UUID=7bac224f-c127-4d8e-8f51-e44aad453bc0 swap swap defaults 0 0
UUID=3a7d35ea-a600-4d0f-b40a-848b54a9bd3e /fogserver ext4 defaults 0 0
UUID=c4bbc7df-8517-4f33-b9a6-374cbd8374da /fog_archives ext4 defaults 0 0
Here are the mounts:
[root@fogserver ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 100G 0 disk
├─sda1 8:1 0 4.1G 0 part /boot
├─sda2 8:2 0 8G 0 part [SWAP]
└─sda3 8:3 0 86G 0 part /
sdb 8:16 0 2T 0 disk
└─sdb1 8:17 0 2T 0 part /fogserver
sdc 8:32 0 4T 0 disk /fog_archives
[root@fogserver ~]$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 85G 51G 30G 64% /
/dev/sda1 4.0G 351M 3.4G 10% /boot
/dev/sdb1 2.0T 1.1T 813G 58% /fogserver
/dev/sdc 4.0T 460G 3.4T 12% /fog_archives
[jkrinsky@fogserver ~]$
@george1421 Hey George, this is a local file system on the fogserver itself. I don’t believe we changed the exports file but there are a few people who access the server so it is possible. The only caveat is this was working a few weeks ago and is now not working. Here is the contents of the exports file:
[root@fogserver etc]$ ls -lrt | grep exports
drwxr-xr-x. 2 root root 4096 Oct 14 2021 exports.d
-rw-r--r--. 1 root root 194 Nov 19 2021 exports
[root@fogserver etc]$ sudo vim exports
/fogserver/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/fogserver/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
Thoughts?
Getting error: Could not verify mount point, check if .mntcheck exists (/bin/fog.upload)
[root@fogserver ~]$ ls -alrt /fogserver/images/
total 116
drwxrwxrwx. 2 fogproject root 4096 Oct 19 2018 T470-Win10
drwxrwxrwx. 2 fogproject root 4096 Jan 22 2019 postdownloadscripts
-rwxrwxrwx. 1 fogproject root 0 Jan 22 2019 .mntcheck
drwxrwxrwx. 2 fogproject root 4096 Jan 22 2019 T480-Win10
Missing fog.upload
[root@fogserver ~]$ ls /bin/ | grep -i fog
[root@fogserver ~]$
Here is the Storage Path:
Thoughts?
@sebastian-roth My apologies for the late response, took an extended weekend. Here is a picture of the Laptop when attempting to create the image. Let me know if you are not able to read this.
Thanks Sebastian,
Here is the /images/dev directory:
[fogserver bin]$ cd /images/dev/
[fogserver dev]$ ls -alrt
total 12
drwxrwxrwx. 4 fog root 4096 Jan 22 2019 …
-rwxrwxrwx. 1 fog root 0 Jan 22 2019 .mntcheck
drwxrwxrwx. 2 fog root 4096 Jan 22 2019 postinitscripts
drwxrwxrwx. 3 fog root 4096 Jan 22 2019 .
[jkrinsky@fogserver dev]$