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.

Thank you, that’s helpful for my understanding of a few things. My guess was that the FOS was booting and then trying to load the system ssd drive, and crapping out there. I will get a further look at it tomorrow at the office. It’s odd that shortname is there, this was a new ssd pulled out about 3 weeks ago as far as i know and for sure only has had rocky9 workstation installed on it. I had rebuilt the fog server from scratch earlier this week on a new vm just to make sure I was starting from fresh after screwing around with building my own init.xz and bzImage - after struggling for a while with what I thought was a different IPXE problem, when it turns out it was a bug in the switch firmware that was turning the network port off on some reboots unless it was set to 1g b(from 10gb).

I can recreate the server, and reinstall the OS on the workstation on the driver after i delete all the partitions just to get things as simple as possible. Thanks again.

This is as the fos kernel boots, shortly after the bzImage and init.xz have downloaded and the boot process had started. Before it, there’s a screen or two of the boot process though it’s a bit too quick to give details but I’m not seeing anything that stands out in the bits I get to read

@george1421

Thanks George,

Rocky 9 is the OS.
This was with the default bzImage and init.xz that the system installed, as well I downloaded a couple a version of each from the kernel and initrd sections in the Fog Configuration. I could be just missing something obvious, I just found it odd that the 1 system I’ve chosen to use as my image source, turns out to be unbootable with fog. I’ve had very limited experience with Fog in the past, and it just worked - that was at home on my 4 pc home lab.

I was unable to find a .config file from the fog kernels so I wasn’t sure if AHCI was loading as a module or not and wondering if that was a problem… You don’t want me mashing about trying to build a kernel.

Wrong screen cap attached - editing message:

Is this possibly an issue with AHCI not being built into the kernel? That seems unlikely but is my latest hole i’m running down