@Tom-Elliott Alrighty then, I set the BIOS for legacy only and it worked with undionly.kpxe. So all good here.

@Tom-Elliott said in Mellanox ConnectX 3 imaging issues.:

ipxe.kpxe

Hi Tom,
Is there a document some where which explains all of the files in the tftpboot directory and there use case?

I’m having a hard time with this 40Gb system.

@Tom-Elliott Awesome, I’m excited to try it. Thanks Tom, much appreciated!

Hello,

I’m trying to image a system with a 40Gb Mellanox ConnectX 3.

My MPO cable is connected and I can see a light through it and the QSFP.

However I get this message that the link is down and the link status is unknown.

Is it a driver issue?

On my DHCP server, I’m using the supplied file from The Fog Project named undionly.kpxe.

Shall I use a different file?

Attached is a screen shot of my issue.

In short, it simply cycles through this message.

Hello,
I’ve Fog running w/o issue but was curious if some one has a link to more detailed docs regarding all of the different PXE files included with Fog?

I’m currently using undionly.kpxe and while it works for Intel NICs, I’m having a bit of a time in Fog working with the older SolarFlare SFC9020 10Gb fiber based NICs which I have plenty of.

BTW these are great cards.

@Tom-Elliott Hellooooo,
Sooooo, leaving the UUIDs as is I simply decided to use a different machine to create the image. I was using Intel and switched to a SuperMicro and set BIOS booting option to BOTH meaning Legacy + UEFI.

That same image was successfully deployed to that very problem Intel box as well as others. And since it was EXT4, the partition grew and shrunk as needed.

@Tom-Elliott Thank you!

I’m very comfortable with replacing UUID with /dev/sda# and then rebuilding grub to reflect the changes.

However let me redo the file system and hence base system install to use GPT labels rather then msdos labels.

More later and thanks again for the guidance.

@Hongyun I have this exact same error but in my case the UUID not found is my / which is my boot partition. Too bad your post remains unanswered. BTW, if you are still around, are your partition(s) EXT by chance? I’m using Rocky 8.10.

@Tom-Elliott Hellloooo,
Soooo, after using EXT4 on my system that then was captured, and deploying to a different system, I boot into emergency mode due to the boot disks UUID not being found.

Are there any special things that need to be done before capturing a system using EXT4? Like any flags that should be set during the initial image creation before a capture takes place?

I can deploy an XFS based image which does not shrink or expand but it seems as though I cannot deploy an EXT4 based image which shrinks and some how a changing of disk UUIDs?

@Tom-Elliott Thank you once again for a very informative reply. I’ll go ahead and use EXT as my OS file system and report back about expanding/contracting file system deployment in Fog. But I’m sure that it will work as Fog has nothing really to do with filesystem.