Imaging won’t begin, host going into boot loop

[Wayne Workman]

@PageTown Basically, yeah. Make sure your images copy over.

[PageTown]

@Wayne-Workman Will do.

After am I doing a re-install of Fog over my pre-existing one using the same steps I used to install it originally?

[Wayne Workman]

@PageTown If the installer completed when you first installed, it won’t ask you any questions, it’ll just display the settings that you used when you first installed, and ask you Y/N for installing.

This would be the first step in troubleshooting.

[PageTown]

@Wayne-Workman So do I just go into the fog folder directory and do sudo ./installfog.sh then?

[Wayne Workman]

@PageTown Yup. Let us know what happens.

[Tom Elliott]

I’m confused to what’s happening.

[Wayne Workman]

@Tom-Elliott His FOG server went belly up, so I asked him to rerun the installer and see what happens.

[PageTown]

@Wayne-Workman I re-installed Fog but doing so didn’t solve my problem.

The Fog menu comes up on the host, it let’s me register the host but it won’t image. It makes the iPXE connection, but then reboots.

I looked in task management and verified that an imaging task is created, but it disappears when the host machine fails to begin imaging and reboots itself.

What’s my next step?

[Wayne Workman]

@PageTown What sort of imaging task? Upload or download?

[PageTown]

@Wayne-Workman I am downloading an image to a machine.

I was able to figure out my problem. I was having the same issue as cg2916 in another topic.
I had uploaded an image from a machine that had a 1.5 TB drive and was pushing it to a machine that had a 160GB drive. Even though the image itself was only 4GB or so, the host machines with the smaller drives weren’t taking it.

Thanks for all your help Wayne!

[Junkhacker]

is the image type “Single Disk - Resizable” ? that is the only image type that can deploy images to hard drives of smaller size than the disk of the original source

[A Former User]

Your issue sound similar to one that I had and one that someone else posted on here. Is the hard drive size that you created the image on the exact same size? Also is the image type you are using one that is not resizable? If so, either try shrinking the partition and reupload the image so that way there is about 1-2gb of unallocated space on the drive or simply try imaging a computer with a hard drive that you for sure know is larger (not same, larger) than the one used to make the image. Hope this helps.