Topics created by JJ Fullmer

In the end I am maintaining a separate image, I was able to get management to let us buy a separate surface go 4 for maintaining the 4k disk image.
I found that bhyve based VMs can be set to 4k blocks but it was cumbersome to get it to boot to fog to capture the image at the end. And when that image was deployed, it did not expand on the surface go.

@JJ-Fullmer I think I have determined this is a problem in an internal process with the api. Gonna try to narrow it down some more.

@Sebastian-Roth Just an FYI, I ran into this again on different hardware. An HP Z2 G4 Workstation did the same thing.
There may have been more to it though, still troubleshooting a bit. My failsafe in the postdownload script to have it still join the domain through the unattend file was injected into the file, but the computer did not join the domain through that method, there may have been a different reason for that though.

Point being, there could be other hardware that weirdly doesn’t get all the variables. I sadly can’t super test on this hardware as I discovered it when imaging a production machine that I can’t take out of production for testing. But I can probably find a chance to get the fos level device info or something.

@jj-fullmer said in Secure Boot Support for Windows 11:
“As long as your CPU supports TPM 1.2 you can do a clean install of windows 11, you just can’t in-place upgrade (without a registry change).”

Is it possible to share the registry change? Unless something even better has changed, I am thinking of in-place windows 10 21H2 to 11 in a dual-boot ubuntu environment. I figure this would stop me from having to reinstall Ubuntu (or grub repair).

@sebastian-roth Well yes I see that now. It just felt like a familiar problem from whenever I change kernels. Should have just restarted and tried again before assuming something was broken though.

@tom-elliott said in API Return object for scheduledtask is malformed (has a tiny typo):

@tom-elliott Added a little tiny bit.

Thank you,

That tiny bit that allowed non-unique names for tasks and scheduled tasks did the trick!

@sebastian-roth I have not, it seems to have just been that one time.

@JJ-Fullmer said in Surface Go 2 (microsoft surface usb-c ethernet adapter) won't boot bzImage on fog 1.5.9.2 and Getting database update errors:

I will update my install shortly and re-image one of the machines. Will this also change my kernel? Will I need to remake that change for the surface ethernet adapter?

You will need to re-download the 5.6.18 kernel.

Ok, after lots of digging in the code and @JJ-Fullmer database we seem to have found out what happend. Turned out some of his PowerShell code messed things up by deleting the primary MAC address of some hosts and the fog-client did its share to kind of reset some of the hosts’ information and make them pending.

The PowerShell code is fixed already and I will work on adding some checks to hopefully not mess as much up with the fog-client as we did here.

Initially we thought the snapin hash problems were at fault but the evidence collected points to this being a coincidence.

@JJ-Fullmer It’s good you bring this point up. We get posts in the forums every now and then but it’s very hard to estimate how often this really happens in the wild as we have no numbers of rEFInd working properly.

Adding more options is a good idea either way as it doesn’t hurt us and might help people.

Personally having used grub2 to PXE boot I will get onto that and see what’s the best way to add this to FOG.

@Sebastian-Roth OK. I just didn’t wait long enough sorry to rattle your cage. Thanks for the help it did the hash just waited a while and it’s working now.

@JJ-Fullmer Ok, I just prepared a first one to test for you - download 1_bzImage and put in /var/www/html/fog/service/ipxe. Then edit this host’s settings and set this kernel as Host Kernel and see what you get.

I used a fairly recent kernel version 4.19.13 and so we might even see different behaviour than when we tested some months ago.

I had the same issue with T540p’s, a git pull and the 1.5.0-RC-10 resolved this for me also.

@george1421 It is a HP Prodesk 400 Mini G3 MFR part# 2RN27UT#ABA
The nvme was manually added, not something that comes with it.
But the Intel Optane setting was new to me, and this wasn’t my first prodesk 400 mini g3. But they did just change the mfr part # for this configuration and stop sending out the old one, so it’s probably related to this.

From what I read briefly about the intel optane feature, it’s a part of the 7th gen intel core cpus chipset or requires it or something like that.

@jj-fullmer said in USB ethernet adapter mac(s) for imaging multiple hosts. (Universal Imaging Nics) (Wired Nic for All Wireless Devices):

current host or get a host by a given uuid, mac, or hostname.

You should fork the fog-community-scripts repository and add this stuff to it. Just label it the powershell cli or something, give it some snazzy name.

For the Python project, I’m calling it fog-cli.

@JJ-Fullmer Don’t worry about this duplicate post. It was just a lucky guess of mine that this could be connected. As well it’s good that you brought up this issue again as I would have forgotten about it. Checking the CentOS repo now I see a new package being available since 13th of June - search for rpcbind here.

@Quazz The files “d1.original.partitions”, “d1.original.fstypes”, “d1.fixed_size_partitions”, “d1.original.swapuuids” are all there. The system tries to load “d1.partitions” which is missing.

So I tried “cp d1.original.partitions d1.partitions” and it works! Even with NVME drives!

This solved it for me, thank everyone!

First, I think app armor was blocking the fog update, so I disabled all of apparmor, but it still didn’t work and I got the same error about apparmor in the logs still. So I dug deeper and disabled it further and/or removed it.

Then, it still didn’t work, so I looked at the logs some more. I made sure apache was working and fixed a few things there. I also made sure mysql was working.

I tried a lot of other things, but I think this mysql upgrade with my root user and root password is what was really needed. I had to do the mysql update manually with my own command instead:

sudo mysql_upgrade -u root -p

Then, I re-ran the fog update and it worked. If that doesn’t work for anyone else, let me know and I can give you more details on other things I did to fix it. It is all working now. Thank you! Fog is awesome!

BOTTOM LINE = Follow the errors in the logs. I did sudo journalctl -xe a lot and also tail -n 20 /var/log/mysql/error.log to see what was going on.