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.

@Tom-Elliott Thanks Tom, super appreciate the reply.

Rather then focus on XFS because to me that’s more of a file system best left to backending an NFS share for global access, I can always create an EXT2, EXT3 or EXT4 based OS and deploy that.

However my question would be; Can a non LVM EXT based file system be resized smaller and larger when being deployed?

Or should the EXT file system be under an LVM topology for resizing?

I’m not tied to XFS for a workstation OS by any means.

I’ve found and read the following link below and feel that I should not be encountering the issues stated.

However I am using XFS with no LVM containers of sorts on my source image so could that be an issue?

There is a blurb about using ext2, ext3, ext4 where XFS is not mentioned but that’s under the section Multiple Partition Image - Single Disk (Not Resizable).

https://docs.fogproject.org/en/latest/management/web/images/#image-type

Hello,
I’m noticing something odd in terms of capturing and deploying images.

I’m capturing and deploying Linux in this case.

While things are working, I wanted to bring this up in the event that I don’t understand how Fog is supposed to work.

I’ve gone with Fog defaults in terms of;
Image Type = Single Disk - Resizable
Partition = Everything

However I’ve captured a system having a 450GB drive with a 450GB partition having 100GB used.

When I deploy that very image to a different system having a 400GB drive, I get the error that the source drive is larger then the target drive and cannot continue.

Conversely when I take that same captured image and deploy it to a system with 1TB drive, it creates a 450GB partition leaving roughly 50% of the drive not partitioned.

Am I misunderstanding how Fog works?

Hey there Tom and many thanks for the reply.

I’m curios about something as I didn’t really customize anything other then adding network storage.

In terms of plugins, I do see a section under Fog System Settings > Plugin System but it’s not enabled. So is that what you mean by the hoststatus plugin as being part of that suite?

However I’ll go ahead and edit referenced PHP file.

Does this setting mean that it’s default and if by chance I do include Windows into my Fog imaging, then it could be seen as Windows which i would like?

I did a little cursory reading on my issue and it seems that Fog mistook my Linux boxes to be Windows, although one system that I registered was seen properly as Linux.

I’ve more systems to register and will update this thread.