@george1421 Yup that did it! It was a combination of the Fog server’s firewall as well as my trying to connect to the web interface using the imaging network’s IP instead of the business network IP. Once I disabled the firewall again and tried the other IP I was able to finally reach the web interface.

Thanks for the help!

Update: I just went back through and checked all the places where the fog password is set and somehow the tftp settings in the Web interface was a different password. I set it to the same password that was in /opt/fog/.fogsettings.

Now I’m trying to capture the image again. Hopefully that’s all it was. I’ll give another update if it was successful or not.

I decided to go ahead and start all over with CentOS7 instead of Fedora this time. I setup the server as well as Fog the same exact way. This time I didn’t run into any issues with the Fog server’s firewall like I did on the Fedora server. And I was able to successfully capture an image from my test laptop with no errors.

I’m running another test right now with deploying the image to the laptop to make sure there’s no issues there, but it looks like switching to CentOS worked for me.

I know the most recent wiki on installing fog on Fedora is specifically for Fedora 25 so maybe a lot has changed between Fedora 25 and Fedora 28 that the same instructions won’t work, but I’m just guessing.

Looks like I needed to be a little more patient or do just a little more research. I read a post that explained that this is a known issue and it will sometimes get stuck on “Saving original partition table…” but will eventually move past it after about 5 minutes or so. Sure enough, my capture process continued after a little while. Good to know.

YOU GUYS ARE AMAZING!

Both the capture and deploy tasks completed successfully! Thank you all so much for your help! Now I can have our staging team start using Fog for our equipment with RAID.

Thanks again!

@george1421 It looks like that did it! It’s currently capturing the image. I’ll keep an eye on it to make sure it completes without any errors. Then I’ll try and deploy the image back to the tablet to make sure that works as well.

@Sebastian-Roth Yeah I was thinking the same thing. So now that tablet is booting reliably every time. I’ve moved to another one and it’s getting the errors again. This is totally a tablet-related issue and not a Fog related one.

Ok I don’t know what happened, but after I exited BIOS settings this time on the tablet, it booted into Fog and started a capture task. I have no idea why. I didn’t change any of the settings. I’ll have to play with it some more.

@Sebastian-Roth It’s the same model, but not the exact same tablet I got working before.

I tried changing the host settings back to bzimage and init.xz and I got the same error.

These tablets do not have the option to enable/disable secure boot in BIOS setup.

I’ll see if we still have the original tablet that we got working to see if it’s also getting the errors.

EDIT: Nope. It’s impossible to find the original tablet. It was added back to the stock of all the others and I didn’t get the serial# from it.

@Sebastian-Roth The first thing I checked was that I had Host Kernel set to bzImage32 and Host Init set to init_32.xz since that was the last thing we were missing when we got it working last.

I followed your instructions of moving the original files and getting the latest ones, but I’m still getting the same Exec format error.

@Zerpie Ok I don’t know what happened in the last couple weeks, but it’s not working anymore. I’m back to getting the following errors when trying to capture an image from these tablets.

bzImage32... ok
Could not select: Exec format error (http://ipxe.org/2e008081)
Could not boot: Exec format error (http://ipxe.org/2e008081)
Could not boot: Exec format error (http://ipxe.org/2e008081)

I haven’t made any changes to Fog since I got this working originally. I told my team that it was working and they could move forward with using Fog to image these tablets. Once they got around to it they brought it to my attention that it wasn’t working.

I also don’t know if I need to start a new thread since I already marked this one as solved.

Capture and deploy completed successfully! Looks like the problem is solved. Thanks for all your help, guys!

@george1421 It looks like that did it! It’s currently capturing the image. I’ll keep an eye on it to make sure it completes without any errors. Then I’ll try and deploy the image back to the tablet to make sure that works as well.

@Sebastian-Roth Alright, that got me a bit further. It looked like it was actually going to start capturing, but I got “An error has been detected!”

* Could not mount /dev/mmcblk2p3 (/bin/fog.upload->beginUpload)
Args Passed:
Reason: The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache refused to mount.
Failed to mount '/dev/mmcblk2p3' : Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option.

I allowed the tablet to boot into Windows and did a full shutdown using the command Shutdown -f -s -t 0. Then I booted it back up and now when it tries to boot over ipv4 it immediately skips over it and tries ipv6 before booting back into Windows.

Ok I still had debug earlyprintk=efi loglevel=7 set in the Host Kernel Arguments so I cleared that out and tried again. I didn’t get the wall of text this time, just the Kernel panic. Here’s everything I see.

Starting init: /sbin/init exists but couldn't execute it (error -8)
Starting init: /bin/sh exists but couldn't execute it (error -8)
Kernel panic - not syncing: No working init found.  Try passing init= option to kernel.  See Linux Documentation/admin-guide/init.rst for guidance.
Kernel Offset: disabled
---[ end Kernel panic - not syncing: No working init found.  Try passing init= option to kernel.  See Linux Documentation/admin-guide/init.rst for guidance.

@Sebastian-Roth Yup. I got these errors at some point before and posted about it earlier in the thread.

Ok I could have sworn I tried it with bzimage32 set for Host Kernel earlier today, but I just tried it now and I got a little further. It gave me a whole page of text and it looked like it was going to work but then it stopped and I see these lines at the bottom.

Kernel panic - not syncing: No working init found.  Try passing init= option to kernel.  See Linux Documentation/admin-guide/init.rst for guidance.
Kernel Offset: disabled
---[ end Kernel panic - not syncing: No working init found.  Try passing init= option to kernel.  See Linux Documentation/admin-guide/init.rst for guidance.