How is the multicast task started on the client? Scheduled per host through the Web GUI?

@greezy said in problem ACPI error:

ACPI Exception: AE_NOT_FOUND

What’s between brackets after AE_NOT_FOUND? (screenshot would be helpful)

Also… does it capture/deploy properly regardless of these errors?

FOG version would be nice to know too.

@dirtrunner21 I’d be interested to see if the speed improves any on the latest kernels. I do think it’s some kind of kernel/firmware issue (that being said, the kernel configs seem to already have all recommende options enabled/disabled as needed), although this one in particular isn’t nearly as bad as some others (some reaching only 8mb/s under certain conditions)

Worth checking out an update to FOG 1.5.5 (which will automatically pull latest kernel and binary)

Is this quick deploy? Or from the WebUI interface?

It looks like FOS can’t detect the MAC address for some reason, but since you got this far, it must obviously have one or DHCP would have failed much earlier in the process.

I recall certain SSDs getting inexplicably low speeds.

Here’s the discussion about it on the partclone github page:

https://github.com/Thomas-Tsai/partclone/issues/112

Currently not solved and obviously a pretty big problem if you’re experiencing this.

Only info I’ve found myself is about 32 bit kernels on systems with 4GB+ RAM causing this issue.

Some older topics suggest the DMA is sometimes disabled on SSDs for some reason.

@kAs1m Does this happen on non-VM as well?

What kind of VM software do you use?

Exit types are tricky at best in UEFI, throw in VM as well and it gets even more crazy.

@Dee You can delete old tar files safely.

You have to enter the bin directory after extraction (before ./installfog.sh)

So:

cd Downloads
tar -xzf fog_1.5.5.tar.gz 
cd fog_1.5.5/bin
./installfog.sh

the v parameter for tar stands for ‘Verbose’ and is always optional. (prints more info to screen)

FOG creates backups in /home for every upgrade (both web files and DB backup), so you could clear out those files (or to be safe move them off your server to a storage system somewhere)

Double check your /images/dev folder for stray unfinished capture sessions (the folders will be named to the MAC address of the device in question)

@kAs1m Interesting, I have seen a vast variety of BSOD but this is a first!

Thankfully there is some info online about this which points to hardware/drivers (as the name of the BSOD would imply) (I’ve mostly seen complaints relating to GPUs)

If an older version of Win 10 works on the same device we can only assume that there’s some new or updated driver in the latest Win 10 builds that are causing this to occur on your clients.

What are the models of your clients? Perhaps this is a known problem for those devices.

@kAs1m Did you happen to catch the error code in the BSOD?

Did you use the /generalize switch with sysprep? (I’m assuming you did based on the link you gave)

Does the client reach the OOBE screen? (or do you use an unattend file?)

Did you upgrade your image or did you start with a clean install?

If you started with a clean install and used an unattend file, then there’s probably something going on with the latter. (maybe some options are no longer valid or some new mandatory options are missing)

@Sebastian-Roth https://github.com/FOGProject/fos/pull/22