Help-could not verify mount point

[batchenr]

Hello,
were using centos 7 with FOG Version: 6971
bzImage Version: 4.13.4
bzImage32 Version: 4.5.0

and had requsted to extend /images mount as it was 78%
so as we have checked the first installtion was mounted on /dev/sdb
without creating any Physical volume\Volume group\Logical volume
so we couldnt extend it -
we had to make a new disk and mount it correctly and create pv vg and lv
and mounted it as XFS (and then i changed it to EXT4 cause i thout this caused the problems)

now, every time we try to pull an image to a new device we get 2 errors :
first : “EXT4-fs (ram0) : couldnt mount as ext3 due to feature incompatibilities”
second:“could not verify mount point, check if .mntcheck exists (/bin/fog.download)”

what do i do ? what did we did worng ?

thanks

[Sebastian Roth]

@batchenr Ok the images are still there. Let me guess, you copied those in the GUI? So you’re only missing a file that FOG uses to check after mounting the filesystem over NFS. Run the following commands and you should be fine:

sudo -i
touch /images/.mntcheck /images/dev/.mntcheck
chown -R fog:root /images

About the warnings in /var/log/messages - I don’t seem to find those fopen/unlink calls in the same lines in the code. So I am wondering which version you have actually installed. On the screenshot it says 6971 but that doesn’t ring a bell for me. I found an old post talking about this version but that’s from March 2016. Can you please tell us how you installed (tar.gz, svn, git) and which version/branch?

By the way - why do you use different kernel versions for 64 bit (bzImage) and 32 bit (bzImage32)??

[Sebastian Roth]

@batchenr The message “EXT4-fs (ram0): couldn’t mount as ext3…” on boot is just a warning and not problematic. It’s got nothing to do with you trying to extend the /images partition! The message has been there for a long time and it’s not new.

But the other message is a problem. I guess something went wrong when you tried to extend/move your /images store! Maybe start by running the following commands and posting the output here: mount and ls -al /images and cat /etc/fstab

[batchenr]

@Sebastian-Roth
Thanks for the fast replay -
the mound seem ok and if we go to images in fog we can see them.

this is the output of the command you asked :

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=1931128k,nr_inodes=482782,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/mapper/centos_fog-root on / type xfs (rw,relatime,attr2,inode64,noquota)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
/dev/mapper/VolGroup01-LogVol01 on /images type ext4 (rw,relatime,data=ordered)
/dev/sda1 on /boot type xfs (rw,relatime,attr2,inode64,noquota)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=388272k,mode=700)

[root@FOG ~]# ls -al /images
total 92
drwxrwxrwx  20 fog  fog   4096 Dec 21 14:17 .
dr-xr-xr-x. 21 root root  4096 Dec  4 15:03 ..
drwxr-xr-x   2 fog  root  4096 Dec  4 13:54 DellOptiplex7040
drwxrwxrwx   3 fog  root  4096 Dec  4 13:54 dev
drwxr-xr-x   2 fog  root  4096 Dec  4 13:59 GBB75MD3H
drwxr-xr-x   2 fog  root  4096 Dec  4 14:01 GIGABYTEB85MD2V
drwxr-xr-x   2 fog  root  4096 Dec  4 14:01 GIGABYTEG41MTS2PT
drwxr-xr-x   2 fog  root  4096 Dec  4 14:03 GigaByteGAH61MS2PV_Win7prosp1_181115
drwxr-xr-x   2 fog  root  4096 Dec  4 14:05 HPCompaq6000
drwxr-xr-x   2 fog  root  4096 Dec  4 14:06 HPCompaq8200Elite
drwxr-xr-x   2 fog  root  4096 Dec  4 14:08 HP_CompaqPro6200
drwxr-xr-x   2 fog  root  4096 Dec  4 14:08 HPPro3500
drwxr-xr-x   2 fog  root  4096 Dec  4 14:08 HPPro3500v3
drwxr-xr-x   2 fog  root  4096 Dec  4 14:10 HPPro3500v5
drwxr-xr-x   2 fog  root  4096 Dec  4 14:13 HPProDesk400G2
drwxr-xr-x   2 fog  root  4096 Dec  4 14:14 LenovoThinkCentreM58
drwxr-xr-x   2 fog  root  4096 Dec  4 14:16 LenovoThinkCentreM72eM71e
drwxr-xr-x   2 fog  root 16384 Dec  4 14:16 lost+found
drwxr-xr-x   2 fog  root  4096 Dec  4 14:16 postdownloadscripts
drwxr-xr-x   2 fog  root  4096 Dec  4 14:16 TestVM

[root@FOG ~]# cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Tue Mar 29 07:55:54 2016
#
# 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
#
/dev/mapper/centos_fog-root /                       xfs     defaults        0 0
UUID=0937e4a8-70ed-429e-b9c2-104c7a441eb6 /boot                   xfs     defaults        0 0
/dev/mapper/centos_fog-swap swap                    swap    defaults        0 0
/dev/VolGroup01/LogVol01  /images                                   ext4    defaults        0 0

[batchenr]

@sebastian-roth
pluse i get all this errors in /var/log/messages

Dec 21 16:44:23 FOG FOGImageReplicator: PHP Warning:  fopen(): Filename cannot be empty in /var/www/html/fog/lib/service/fogservice.class.php on line 82
Dec 21 16:44:23 FOG FOGImageReplicator: PHP Warning:  unlink(//): Is a directory in /var/www/html/fog/lib/service/fogservice.class.php on line 90
Dec 21 16:44:23 FOG FOGImageReplicator: PHP Warning:  fopen(//): failed to open stream: Is a directory in /var/www/html/fog/lib/service/fogservice.class.php on line 91
Dec 21 16:44:23 FOG FOGImageReplicator: PHP Warning:  fopen(): Filename cannot be empty in /var/www/html/fog/lib/service/fogservice.class.php on line 82
Dec 21 16:44:23 FOG FOGImageReplicator: PHP Warning:  fwrite() expects parameter 1 to be resource, boolean given in /var/www/html/fog/lib/service/fogservice.class.php on line 92
Dec 21 16:44:23 FOG FOGImageReplicator: PHP Warning:  fopen(): Filename cannot be empty in /var/www/html/fog/lib/service/fogservice.class.php on line 82
Dec 21 16:44:23 FOG FOGImageReplicator: PHP Warning:  fclose() expects parameter 1 to be resource, boolean given in /var/www/html/fog/lib/service/fogservice.class.php on line 93

[Sebastian Roth]

@batchenr Ok the images are still there. Let me guess, you copied those in the GUI? So you’re only missing a file that FOG uses to check after mounting the filesystem over NFS. Run the following commands and you should be fine:

sudo -i
touch /images/.mntcheck /images/dev/.mntcheck
chown -R fog:root /images

About the warnings in /var/log/messages - I don’t seem to find those fopen/unlink calls in the same lines in the code. So I am wondering which version you have actually installed. On the screenshot it says 6971 but that doesn’t ring a bell for me. I found an old post talking about this version but that’s from March 2016. Can you please tell us how you installed (tar.gz, svn, git) and which version/branch?

By the way - why do you use different kernel versions for 64 bit (bzImage) and 32 bit (bzImage32)??

[batchenr]

@sebastian-roth
IT SOLVED IT!!
i dont know what i did worng with the copy, i moved all files in /images/* to some other dir
and then after adding new disk moved it back… what did i do worng ? (copy throw linux not GUI)

about all other qustion - i didnt install this fop it has installed by somone else long time ago
i only beed requsted to extend the disk

anyway THANK YOU!! saved me

[Sebastian Roth]

@batchenr Good to hear you are up and running again. Though you might have used the GUI but just as well things can go wrong when you copy on the console. Using cp /images/* /target-dir/ does not copy hidden files (files starting with a dot - like .mntcheck) because Linux bash does not include those hidden files when using the * glob. It’s as simple as that.

[A Former User]

Just hopping on the bandwagon: creating .mntcheck fixed my issue, too.

sudo -i
touch /images/.mntcheck /images/dev/.mntcheck
chown -R fog:root /images

When I copied the images from our old FOG server to the new FOG server, I followed the lftp directions on this page:

https://wiki.fogproject.org/wiki/index.php?title=Migrate_images_manually

Is there any reason not to add the .mntcheck commands to the above page?

[tkrusterholz]

For anyone with this issue in 2023 and beyond, the user is now “fogproject”
So the final command should be:

chown -R fogproject:root /images