Most likely these are partially (or fully captured that were unable to move) capture images hanging out in /images/dev

@irishfoguser Hi, generally speaking you’re better off using Resizable image. If this for some reason doesn’t work (fails to deploy), then trying the other options is recommended.

For your situation, it sounds like Resizable Image will do the trick. So I recommend picking an image, setting it to resizable, recapture, deploy and see if it works for you.

1.3 is able to resize the correct partition for you before Windows even boots for the first time.

@AlexPDX Rule of thumb is to create a new thread, since the OP in this case was using a very old version, and you are likely using FOG 1.5.8

That said, quick fix is:

sed -i 's#/usr/bin/php env #/usr/bin/env php #g' /usr/lib/systemd/system/FOGSnapinReplicator.service
systemctl daemon-reload
systemctl start FOGSnapinReplicator

To be fair, it’s been a longstanding recommendation that the FOG server should be running nothing but the FOG server for a reason.

Apparentally, to prevent Windows search from breaking after copying the profile over, all you have to do is delete

AppData\Local\Microsoft\Windows\UsrClass.dat

Windows will create one on login.

@TomBagley Considering you have to enter tftp server address, it is likely you have another DHCP server on your network (likely your modem), which might be interfering.

I’m guessing you launch a batch script which launches a msiexec and then closes rather than waiting

Adjust accordingly.

It’s /var/www/fog/service/ipxe (singular service)

@lebrun78 You could try a different disk boot command. You can choose these globally, per group or per host I believe. Default is Sanboot if I’m not mistaken.

There’s different options because different hardware handles it differrently, annoyingly enough.

What error are you getting?

set username foglogin
set password foglogin
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

Try using that, changing the set username and set password parts to your own webgui login info

SecureBoot must be disabled for EFI

New to Centos 8/Stream is that modules can have “streams” (different versions of the same package)

For example, the default stream for PHP is 7.2.

However, PHP7.3 and PHP7.4 are also available.

To get a list of the versions:

dnf module info php | awk 'BEGIN{FS=" "} $1~/Stream/ {print $3}'

This means we can swap the versions to 7.4 as such:

dnf module reset php -y
dnf module enable php:7.4 -y
dnf update -y

Would it be worth it to add this to the install script?

@dinesh Can I ask what exactly you were hoping for here?

Not only do you give very little information, you also seem to assume that we know everything the Linux kernel supports. We don’t. We are not involved with developing the Linux kernel, we only use it as part of FOS.

There are hundreds (if not thousands) different kinds of M.2 Samsung SSDs, nevermind new ones coming out constantly.

There are thousands (if not tens of thousands) different kinds of Toshba Hard Drives, with new ones still coming out.

There are tons of different ways to connect them. They could be behind software raid, hardware raid, connected to some PCIE board, basic SATA connector, SAS connector, U.2 connector, etc

It’s unreasonable to assume we can just know what will work and what will not.

Just try, it either works or not.

Unfortunately, not only partclone was updated, but a ton of the logic in handling partitions/disks was changed as well to be more flexible, fewer bugs, etc

Older partclone versions would indeed be unable to deploy newer partclone images, there is nothing that can be done to change that.

You can try using the 1.5.9 init (and 1.5.9 kernel bzImage) on those storage nodes, though, like George said. I don’t know if it will work, but if it does it should help you out.

@dinesh This patch only added additional support, it didn’t remove anything that was working previously.

If you encounter other devices that don’t work you can mention them here of course so we can investigate.

@juntacadaveres Well, it’s pretty clear, boot in recovery mode and fsck -fy it.

@gutter Microsoft actually provides an executable that tries to convert MBR to GPT

https://www.tenforums.com/tutorials/81502-convert-windows-10-legacy-bios-uefi-without-data-loss.html

Your mileage may vary; I’ve used it only once (still works fine to this day), but I’m not sure it’s going to be exactly the same as a clean GPT install, that would still be your best bet imo.

In VBOX you can create an image in EFI, turn off the VM, switch off EFI, boot to PXE in legacy, capture the image and now you have an EFI image ready to go.

Key aspect to remember is that the mode PXE boots in is irrelevant to the image.

@seppim If you load it over http like in the example it should be quite fast. I use the same method, works fine.

@wayne-workman I just did the same today (easy to swap from 8 to Stream) to test it out and see how different it really is.

Most packages got fairly minor updates (eg it runs the same Kernel, just a newer security release), interestingily, httpd got downgraded.

Still, only minor point differences in packages as far as I can tell. I don’t foresee any issues with it.

Of course we have no idea how it will evolve over time.

@baessens I’m going to take a guess, but is the disk a “dynamic virtual disk” by any chance?