@Tom-Elliott

Ok thanks @Tom-Elliott - that helped me. I had a script that was failing and trying to find logs for it was difficult to get a location that it could write to, that I could find after the deployment, and i couldn’t see if it was erroring or whatever… running in deploy debug was really helpful. Thanks.

@Tom-Elliott said in what makes an image, call for a fog.postdownload script?:

deploy based imaging tasks runs postdownload.

And if they don’t run for some images, how would i debug?
I installed the OS, booted the host, registered it, imaged it… but I can’t get it if I try to deploy back to the same or another host to run the postdownload script and I’m struggling to understand why. Thanks @Tom-Elliott

Sorry - I should’ve mentioned - Rocky9 client and server for the most part. Updated to latest versions.

Thanks

Is there something that makes an image, when deployed, call for the fog.postdownload script to run?

I have some that do run them and others that don’t but it’s not my server so I’m not sure what was done to make it work that way. Thanks

Biggest thing I found from this for future searches of answers…

F*CK UEFI. Legacy FTW.

@gribbler Move to the new building is over, had a chance today to try and get our proxmox server back online, but alas a drive was dead so I used a different server, and what may have been key is a different workstation to try to boot. I had to use the newer built ipxe.efi as pxe boots, hands off to ipxe and then it just can’t do anything. Gets an IP address but can’t see shit.

I was able to get FOG working without much hassle, I do have workstations with LVMs with XFS on them which seems to be a problem for FOG . It did say I could try to not do it as a resizable image but that I assume would then be the same size as the drive? Much too big. In doing some digging I found an option is to boot off a live CD, use partclone and I was able to clone the /home and / partitions which I can import into FOG. Further thoughts I had on the way home was that I must try to just image a partition and see if that works, and a few other ways I could try to skin the cat so to speak… It seems like I have a few directions I could head, so any advice you have that would be appreciated and might save me some trial and error.

I am pretty sure there was something up with that workstation I was trying before, I will try to image it again sometime next week I hope.

Thank you to @george1421 @JJ-Fullmer @Tom-Elliott for your guidance. It is really appreciated.

@gribbler Thanks to @JJ-Fullmer and @Tom-Elliott for some direction.

We’ve just moved buildings over the weekend and I’ve not had a chance to get the proxmox servers back online, gotta get people working was the first priority. I will have a look in the next couple days and for sure no later than early next week.

Thanks again.

Bump for some love…

@gribbler I’ve rebuilt the workstation a couple times, once with defaults for the system drive and the other with manually settings ext3 partitioning, and still getting the same failure.

I’m stumped as to why this system is not booting. I’ll see if I can steal a system from someone else and try theirs, it might be something odd about the hardware.

@george1421 Thanks again for your reply.

I rebuilt the server, though I need to use an updated ipxe.efi to support the network card (Marvell AQC107).

This gets me to the exact same place I was with the kernel panic.

Just to be clear - is my assumption correct? it seems like in the ipxe boot process, the fog kernel is crashing when trying to mount the local host OS drive. I have to step away for a few hours and perhaps not get back to it until tomorrow.

thanks.