could not mount images folder (/bin/fog.upload)

  • @Trev-lchs what would be the best way to rerun the installer?

  • @Trev-lchs Hi George do you think that might reset other things that we had to change since the install?

  • Moderator

    @Trev-lchs ok lets rerun the fog installer to see if it rebuilds the /images/dev directory.

  • no not at all, it used to work brilliantly, those images were all uploaded before with no issues, the only thing that has happened is the updates and the work around that i have already posted?

  • Moderator

    @Trev-lchs Well right there is your problem. Your /images directory isn’t complete on the fog server. You are missing the /images/dev and its files. How did you install the FOG server? Did you do something special when creating the /images directory?

  • @george1421

    root@fog-03:~# ls -la /images
    total 40
    drwxrwxrwx 10 fogproject root 4096 Nov  5 12:58 .
    drwxr-xr-x 26 root       root 4096 Nov 14 06:49 ..
    drwxrwxrwx  2 fogproject root 4096 Dec  9  2016 5730Exams
    drwxrwxrwx  2 fogproject root 4096 Aug  2  2018 8300Win10SW
    drwxrwxrwx  2 root       root 4096 Nov  5 10:38 EliteDesk800G2
    drwxrwxrwx  2 root       root 4096 Oct 17 08:53 HPProDeskG400G5
    drwxrwxrwx  2 fogproject root 4096 Dec  9  2016 Kitchen
    drwxrwxrwx  2 root       root 4096 Nov  4 12:16 LenovoV130-15IKB
    -rwxrwxrwx  1 fogproject root    0 Dec  1  2016 .mntcheck
    drwxrwxrwx  2 fogproject root 4096 Dec  9  2016 PresLaptops
    drwxrwxrwx  2 root       root 4096 Oct 16 14:36 winbasic-testws
  • Moderator

    @Trev-lchs Ok on the fog server ls -la /images

  • Senior Developer

    @Trev-lchs On your FOG server console please run these commands and post output here:

    ls -al /images

  • @george1421 login as: root
    root@’s password:
    [Thu Dec 19 root@fogclient ~]# mkdir /images
    [Thu Dec 19 root@fogclient ~]# mount -o nolock,proto=tcp,rsize=32768,wsize=32768,intr,noatime “” /images
    mount: mounting on /images failed: No such file or directory
    [Thu Dec 19 root@fogclient ~]#

  • @george1421 Thanks George, just going though everything, I will be a while with the results as i have to be in a meeting at 13:00

  • Moderator

    @Trev-lchs I’ve added some additional comments to my previous post.

  • yes the PC is on the same subnet as fog.

  • Moderator

    Is the target (pxe booting) computer on the same IP subnet as the fog server? The question is around if there are any screening routers or firewalls between the two devices.

    We may need to setup a debug deploy test. This is where you schedule a capture but before hitting the schedule task button you tick the debug checkbox. Then schedule the task. PXE boot the target computer and it will boot into the debug console. You will have several screens of text you need to clear by pressing the enter key. Eventually you will be dropped to a linux command prompt. This is the FOS Linux debug environment. At this point we need to key in a few commands.

    The first will be a ping to see if the target computer and ping the fog server by its IP address.

    These next steps are optional but will help with copy and pasting into the debug console. These next few steps will allow you to connect to the target computer using putty or ssh. From putty or ssh you can paste in the mount command exactly without having to key it in. These commands need to be executed on the target computer not the FOG server.

    Setting up a remote debugging session to FOS Linux.

    1. At the FOS Linux command prompt key in ip addr show and get the IP address of the target computer.
    2. Give the root user a known password with passwd This will be a one time password so make it simple like hello
    3. From a putty or ssh session connect to the target computer using the IP address collected in step 1.
    4. Login as root with the password you set in step 2

    From there lets issue these two commands. The first will create the /images directory on the target computer and the second will map the share on the fog server to the target computer’s mount point.

    1. mkdir /images
    2. mount -o nolock,proto=tcp,rsize=32768,wsize=32768,intr,noatime "" /images

    That should connect the directory. If it connects without error issue this command and post the results (note you can copy and paste from putty)

    ls -la /images

  • @george1421

    root@fog-03:~# showmount -e
    Export list for
    /images/dev *
    /images     *
    root@fog-03:~# ip addr show
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host
           valid_lft forever preferred_lft forever
    2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
        link/ether 00:21:5a:d1:d2:20 brd ff:ff:ff:ff:ff:ff
        inet brd scope global enp3s0
           valid_lft forever preferred_lft forever
        inet6 fe80::221:5aff:fed1:d220/64 scope link
           valid_lft forever preferred_lft forever
    3: enp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
        link/ether 00:21:5a:d1:d2:1e brd ff:ff:ff:ff:ff:ff
  • Moderator

    @Trev-lchs Its probably not the ubuntu enemy post. That would deal with database issues. This appears to be an nfs issue.

    What is the output of showmount -e also ip addr show

    Edit: OK looking at previous posts I see the showmount command being issued. So lets try something else (in next post)

  • @Sebastian-Roth this one

    I think i would have followed those instructions, could this be the issue?

  • @Sebastian-Roth I seem to remember that fog stopped working after an unbuntu update, the webpage would not work and system locked up when rebooted as they could not get the ipex file i seem to remember a thread call Unbuntu updates the ememy of fog

  • @Sebastian-Roth i mean 10 or less at once, not more.

  • @Sebastian-Roth to 10 or more PCs please see the attached picture of the errorfogerror2.jpg