@peirkern Ok, looks you’re doing this on Windows docker, which means it is using WSL2 as a backend.
https://github.com/libffi/libffi/issues/552
It seems that it doesn’t behave correctly in that environment currently (that specific package that is).
You might run into other problems as well if you’re unlucky.
You can try disabling WSL2 in docker settings and see if that helps.
@peirkern Both the “clock skew” and certificate failures would indicate a problem with your clock/datetime on the docker image, though the echo’d output seems to indicate it’s fine (or close enough anyway).
Still, can’t hurt to doublecheck?
Don’t know if it’s changed since then, but https://forums.fogproject.org/topic/10615/ipxe-booting-possibly-broken-on-os-x-sierra-update/ seems relevant
@fog_newb Some PHP files are already fine as they are, some are not, the database update one is one such that is not fine, hence the error.
@tramirez Try using a different hard drive to deploy to, so we can rule out hardware issues.
@fog_newb Ubuntu 21.10 uses PHP8 by default. PHP 8 has certain breaking changes that FOG isn’t compatible with yet.
So as Wayne said, safer to stick to LTS.
I’ll try and help out the devs with PHP8 support tonight if I find the time, it’s been something on my to do list, but I haven’t gotten around to it yet.
Comment mirrorlist AND uncomment baseurl (and if necessary change the baseurl to the one you want) in /etc/yum.repos.d/remi.repo
@renanrenan While that may be the case, it doesn’t seem related to the image type as this is long before it touches anything related to it.
Presumably you get stuck here: https://github.com/FOGProject/fos/blob/1085652c894e259c88fc069b2a0691099ad18d82/Buildroot/board/FOG/FOS/rootfs_overlay/usr/share/fog/lib/funcs.sh#L431
Are the win7 / win xp machines physical machines different from the w10 machines?
@mightmar RC2 is quite old (even compared to release 1.5.9, never mind the dev branch) Updating might help already.
Other than that, it’s likely an issue with https. Perhaps date/time isn’t configured in BIOS.
Checkout https://forums.fogproject.org/topic/15606/ipxe-boot-issue-boot-php-permission-denied/7 they had a similar issue.
@renanrenan There’s no error in the picture.
Does it hang on the “setting permission” step?
@tom-elliott I haven’t been very active here lately, but I’m willing to help on PHP8 support.
Still setting up an environment at home, but once it’s ready I’ll take a look.
@sebastian-roth I’ve never used this, but as far as I’m aware, old password tools tend to still work even on Windows 10 (provided they’re local accounts and not Microsoft accounts ofc)
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.