@george1421 I’ll be damned, pardon my french.

So I guess I was just not patient enough. You guys were right, the acpi error has nothing to do with this other than distracting it from the real process.

After changing the log to level 7, I noticed at some point it says its resizing right before the acpi errors take over. I realized its not stuck, its just taking a while to proceed bc resizing always takes a little longer when capturing image.

So I just let it sit there and eventually it proceeds on capturing the image. It doesn’t look pretty with all the acpi errors but it still does what it suppose to do.

Thank you @george1421 and @Sebastian-Roth for helping on this.

@george1421 I’ll be damned, pardon my french.

So I guess I was just not patient enough. You guys were right, the acpi error has nothing to do with this other than distracting it from the real process.

After changing the log to level 7, I noticed at some point it says its resizing right before the acpi errors take over. I realized its not stuck, its just taking a while to proceed bc resizing always takes a little longer when capturing image.

So I just let it sit there and eventually it proceeds on capturing the image. It doesn’t look pretty with all the acpi errors but it still does what it suppose to do.

Thank you @george1421 and @Sebastian-Roth for helping on this.

@george1421 Hmm the Web UI is a bit different from what you’re describing. But I do see under FOG Boot Settings > Kernel Log Level = 4. Is that similar to what you’re referring to?

I’m gonna try this then. The laptop I’m having issue with is a Microsoft Surface Laptop 5.

@Sebastian-Roth It just stops there because it won’t proceed one way or another.

Here’s the image of the error I got.

Weird that I’m getting an error when uploading image here but here’s the image with the error: https://postimg.cc/hh4CV40v

Hello,

I was wondering if anyone ran into this issue before or if anyone have any idea how to fix this.

I’m attempting to capture an Image from a Surface Laptop 5 with Windows 11 but during the capture I suddenly get this error over and over again: “ACPI Error: No handler or method for GPE, disabling event”.

I read a couple of articles similar to this issue and use “acpi=off” for the kernel parameter/argument but it just stuck when downloading the bzimage right before it goes to capture and won’t proceed.

Weirdly enough, this is only happen to this specific laptop. Surface Pro seems to work just fine.

My FOG version is 1.5.9.

I’ll take any advice or suggestion to resolve this. Thanks in advance!

@Sebastian-Roth Sorry for the late response. I ended up re-installing everything and its good now. I also changed the permission of the images to executables on the storage nodes, not sure if that helps but its all working now.

Thank you for your help.

@george1421 very sorry for the late response.

yes i have the plugin installed and allocate each storage node to a specific location.

yes during the fog registration, i selected the specific location. so if the target computer is in california office, i selected california.

the california slave storage server is in the california office, and same as the target computer. i even tried on VMs that the server is hosted in the same location. but i would run into the same issue.

when the image is being deployed, it’ll say <texas ip>/images instead of pulling it from california for example.

Hello,

Let’s say I have 2 locations/storage node. Texas location which is the Master Node and California which is the Slave Storage Node, both of them are under the same group and I can see the images synced to the California node. I’ve ran into issue where if I selected California for location during the imaging process, it’ll still pull the image from Texas which is the master node.

On the laptop screen it says it’ll pulling from the <texas_ip>/images and under task management in the web page, it’ll say location California but working with Texas node.

What’s weird is I can see that it’s downloading the inits from the California node. To my understanding, if I’m in California and I select California for the location during imaging, it’ll pull the image from California. Please correct me if I’m wrong on this.

I also check the .fogsettings file and make sure all info are correct.

But have any of you ran into this issue and is there anything I can do to fix this?

Thanks in advanced.

@judzk sorry I just saw this and yes I also see the error.

Glad its working for you now.

I also didn’t use the powershell module.

@jj-fullmer Thanks for that. I actually got it to work

I was using the wrong object.

http://<IP>/fog/host/objectID/edit

Instead it suppose to be

http://<IP>/fog/macaddressassociation/objectID/edit

It works like a charm now.

Thanks for the help though!

Hey guys,

For automation purposes, I’m trying to update host via the API with PUT request. I’ve read the API doc and was able to do a GET request and receive the JSON formatted response.

The issue is when I try to do a PUT request to update the “primac” value and I’m using Postman to send these request at the moment. When I send the request, it returns status “200” and the JSON data of the host but it doesn’t actually update the “primac” value based on the JSON body i provided.

The link is http://<fog ip>/fog/host/hostID/update
I included the 2 tokens in the headers.

JSON body looks like this:

{
“primac”: “01:02:03:04:05”
}

also tried this:

{
host: {
“primac”: “01:02:03:04:05”
}
}

but also not luck. Please let me know if I’m missing anything or if there’s any alternatives.

The other thing is I’m thinking of just write my own API and make changes directly to the SQL server but trying to avoid that.

Thanks in advanced!