This is now resolved, on checking it appears that the kernel downloaded was the ARM64 instead of 64.
Interesting the ARM kernel gets as far as that on a HP 250 G7…
Being a member of FOG Hangouts will allow you to stay updated about the latest FOG Hangout; the when, the where, and the details. Membership in this group is automatic membership in a mailing list.
Also, I’ve already pulled down the dev-branch and got the error before my initial post
Which version number is shown by the installer script? Just want to make sure we are on the right track here.
As well make sure this is still in a kind of fresh state and
/opt/fog/.fogettings is not created yet. Because if it is then things will behave differently in this particular situation.
Should I delete the previous dev-branch install and download/run it again?
No need to delete. You can re-run the FOG installer as often as you like if it is the same or a later version of what you have installed/run before. Should not cause any trouble.
@Mightmar I assume you hit ENTER before opening the URL to let it do it’s magic DB schema creation/update.
Well, no problem. Just re-run the installer exactly as you did before. This time it doesn’t matter if you really open the web interface URL at the right point because the schema should be updated already.
@NSD_Network_Admin @neodawg Just in case anyone of you is interested in this. The bug was fixed by this commit: https://github.com/FOGProject/fogproject/commit/66fa6f074c4662098ea38b811077f2ad25c09a46#diff-f21fb2470403477fe0c412911d1227f1
I discovered this bug too when updating. My solution was just to create a group of all computers and then update the default AD credentials under Fog Settings. Then I just cleared it and repopulated the fields in Fog Settings. Then used the group of all and modified it for all computers at once. I even used the same password as I was.
My speculation is that the new password encryption measure put in are breaking it, the length when the password is shown is way off of what it should be when its updated correctly.
@astrugatch Please run the following two mysql querys on the command line to see if you can find it in the database:
SELECT * FROM hostMAC WHERE hmMAC LIKE '%aa:bb:cc:dd:ee:ff%'; SELECT * FROM hosts WHERE hostID IN (SELECT hmHostID FROM hostMAC WHERE hmMAC LIKE '%aa:bb:cc:dd:ee:ff%');
Put in the adapters MAC address instead of
I am wondering why you say “Wifi MAC address” at one point. Just a typo?
@Mightmar Did the installer run all the way to the end? Please take a look in the
bin directory where you ran the
installfog.sh script. Find a subdir called
error_logs in there and two log files. Post the last 10 lines of both logs here.
@sudburr Is the partition layout still fine when you see this
blkid: error: /dev/sda4 thing on subsequent tries?
May I ask you to do the following: Let it try to capture a few times more. Every time you save a copy of the
/images/dev/aabbccddeeff/d1.partitions (this aabb… is the MAC address of the host without colons) file to another location for us to compare those afterwards. Whenever you see the
blkid... error you name it
d1.partitions_fail_X (put in numbers instead of X) and if you don’t see the error you name it
What kind of VM do you use? I am wondering if I am able to replicate the issue using the same setup?!