FOG can capture an image, but can't then deploy it.



  • So at my work I was asked to set up a fog server so we could create an oobe image/oobe images for our clients. I set up as basic of a fog server as you can and got it working quite well. We had to migrate the fog server onto a new hypervisor due to changes in our network, so I made a new fog server. It’s running on a Proxmox hypervisor currently on a Centos7 VM. The fog server is NOT functioning as a DHCP server. I set the actual server to be 8GiB, then there is another 100GiB drive mounted in /images/dev as an ext4 file system.
    I can capture images no problem, everything looked quite promising, however when I went to deploy an image it gave me the error

    Init Version: 20190714
    Image store corrupt, unable to locate MBR, no file found (MBRFileName)
         Args Passed: /images/dev/UEFI/Generic-W10-UEFI 1 tmpMBR
         Variable set to: /images/dev/UEFI/Generic-W10-UEFI/d1.mbr
         tmpMBR Variable set to: /images/dev/UEFI/Generic-W10-UEFI/d1.mbr
    

    I’ve searched the forums for this issue and found several people who have had the issue, unfortunately none of the fixes for them worked for this case.

    As far as what I’ve troubleshooted so far, I have tried:

    • Verifying that /images have permissions via sudo chmod -R 777 /images and sudo chown -R fogproject:root /images
    • Verified that both /images and /images/dev have .mntcheck inside them
    • Testing that ftp is working via the documentation on the FOG wiki page here.
    • Verifying that the captured images actually went to the correct directory.
    • Verifying that d1.mbr exists and has data in the file.

    The Computer I captured an image from only had a single disk with 4 partitions on the disk. It was captured using Partclone Gzip, Single Disk - Resizable.

    I’m not entirely sure what I’ve done wrong, but if someone could help me figure out what it’d be greatly appreciated.


  • Moderator

    @dmathews If you are going to start over, once the linux server is built. Create the /images directory by hand and then create the mappping of /dev/sdb1 to /images THEN install FOG. It will create everything correctly then and no changes will need to be made to FOG because the disk was added at the OS layer.



  • @george1421

    Ooooh, okay. I see. I figured it had something to do with the second hard drive but I definitely didn’t know for sure. I think i’ll just blow the server away and reinstall it with these details in mind. I only had 2 PCs imaged anyway. I’ll read through those links and if on reinstall it fixes the problem (which from that bit of info I feel it will) I’ll go ahead and mark it as the accepted answer. Thank you for that information, it makes a lot of sense.


  • Moderator

    @dmathews The bit longer answer is…

    The target images are stored in /images not /images/dev. The /images/dev directory is only used during image capture. Once capture is done the images are moved to /images directory.

    During an image capture the disk contents are written to /images/dev/<mac_name> at the end of image capture FOG moves the images to /images/<image_name> The /images and /images/dev directories need to be on the same partition. If they are when FOG “moves” the files from /images/dev/<mac_name> to /images/<image_name> it uses the mv command which if the files are on the same partition only updates the file location table. If they are on different partitions then the data must actually be moved between the partitions.

    I do have a few tutorials on moving your images off the root partition I can reference.
    https://forums.fogproject.org/topic/11048/moving-fog-s-images-files-off-the-root-partition-2017-edition
    https://forums.fogproject.org/topic/10450/adding-additional-image-storage-space-to-fog-server


  • Moderator

    @dmathews Ok the short/quick answer is (assuming you are just starting out and have nothing to loose) mount /dev/sdb1 to /images and then rerun the fog installer.



  • @george1421

    Absolutely, I look forward to learning what I did (or didn’t) do. 🙂


  • Moderator

    @dmathews I have to step out for a minute, but we need to talk about your config. I see something already. The /images/dev needs some attention.



  • @george1421

    lsblk returned

    NAME     MAJ:MIN     RM     SIZE     RO     TYPE     MOUNTPOINT
    sda      8:0         0      8G       0      disk
    sda1     8:1         0      8G       0      part     /
    sdb      8:16        0      100G     0      disk     /images/dev
    sr0      11:0        1      4M       0      rom
    

    df -h returned

    Filesystem        Size     Used     Avail     Use%     Mounted on
    devtmpfs          896M        0      896M       0%     /dev
    tmpfs             919M        0      919M       0%     /dev/shm
    tmpfs             919M      17M      903M       2%     /run
    tmpfs             919M        0      919M       0%     /sys/fs/cgroup
    /dev/sda1         8.0G     3.3G      4.8G      41%     /
    tmpfs             184M        0      184M       0%     /run/user/1001
    /dev/sdb           99G      31G       63G      33%     /images/dev
    

    showmount -e 127.0.0.1 returned

    /images/dev *
    /images     *
    

    storage config
    Capture.PNG


  • Moderator

    @dmathews said in FOG can capture an image, but can't then deploy it.:

    You have said a few things that confuse me a bit so lets start out with the output of these commands executed on the FOG server.

    lsblk

    df -h

    showmount -e 127.0.0.1

    Also paste in a screen shot of your storage node configuration for this server, probably called default from the FOG web ui.


Log in to reply
 

305
Online

7.4k
Users

14.5k
Topics

136.5k
Posts