@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.

@george1421

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

@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

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.