@wayne-workman Absolutely. As soon as I can I will.

@george1421 Pffft…i’m there with ya brother.

Is there a way to turn a FOG image in a recovery thumb drive I can send to outer offices when they have a hard drive crash?

@george1421 Pffft…i’m there with ya brother.

@george1421 said in Errors Before Image:

@dpotesta50 Ok so then the firmware doesn’t address the issue. Then do what Tom recommended. In the host management page for that computer, there is a field called kernel parameters. Place noapci in that field, save and then pxe boot that computer again.

But again, these are just warning message and do not, will not impact imaging.

No Kernel parameters. I see Kernel Arguments and Host Kernel under NEW HOSTS

@george1421 BIOS updated. Same errors.

@tom-elliott said in Errors Before Image:

@dpotesta50 as they appear to be acpi errors I might suggest turning it off for that machine with the appropriate kernel arts? I think it’s just noapci

Do I literally just type “noapci” from a command window?

@george1421 Hey George
I’ll check to see if there is a BIOS update for the hardware. I have no idea how to do a kernal update.

BzImage Verision: 4.13.4

Hey All
I’ve been getting these lines of errors before the image starts to pull for a couple of weeks now. The image loads perfectly fine, but I’d like to know what changed for these errors to appear.

@sudburr No clue how to do that.

@wayne-workman That’s actually a friggin’ genius idea. Too bad I didn’t do that at first. There’s no way I’m rebuilding this thing again. I needed outside help getting FOG configured.