@UWPVIOLATOR When preparing the release I started a list of changes but soon figured that it’s pretty much all bug fixes and that I can’t add much value generating a manual list. Please take a look at the commit log between 1.5.8 and 1.5.9 to find out what has been changed: https://github.com/FOGProject/fogproject/compare/1.5.8...1.5.9
Lets have you a few things.
Upgrade to FOS Linux 5.6.18 and test.
What is the hardware ID of this network adapter (as seen in the device manager in windows)?
From the fog iPXE menu did you run the hardware compatibility test? What was the results?
From what it looks like the kernel is running fine, but getting hung up updating the database. If it was a network issue it should have errored out before this point. If we can’t find the root of the issue you may need to schedule a debug deployment and then single step through the deployment until we can see a traceable error.
I assume all other systems deploy fine, its just this specific model that has an issue?
@choppaholic26 said in Image replication failing due to syntax error?:
Will running a new install script do an in-place upgrade without breaking anything?
That’s what we try to achieve. But as you know there can always be special cases. So we cannot promise an upgrade with no issues. Make sure you have a backup copy of your database and the images any you can re-build a FOG server in no time.
Don’t get me wrong, I am not saying upgrades don’t work very well. I just can give you an assurance! In most cases (no manual modifications, mostly standard settings) the upgrade runs through without any hickup whatsoever. And even if you bump into an issue we are here to help you. So don’t worry about it. Take a backup copy and go for it.