Chromium Image Issues after Updating Server

[Tom Elliott]

Init’s are now uploaded.

If you aren’t willing to jump to the working branch, please run:

wget --no-check-certificate -O /var/www/fog/service/ipxe/init.xz https://fogproject.org/inits/init.xz
wget --no-check-certificate -O /var/www/fog/service/ipxe/init_32.xz https://fogproject.org/inits/init_32.xz

This should get you the latest init’s with the changes @Sebastian-Roth has suggested.

[rstockham23]

Attached is a photo of the error that we’re still getting even after doing a fresh install of the latest version of FOG. I still can’t Capture a Chromium image without getting an error. Same FOG server works just fine with Windows images, etc, but not with Chromium.

[Quazz]

@rstockham23 Can you post a screenshot of the image settings?

Are there any special settings for this host? (eg kernel arguments and the like)

[Sebastian Roth]

@rstockham23 Sorry but the important information is not on the picture. Usually there is a message in the blue partclone screen which should give is more hints on what’s wrong. When scheduling the task you can set the checkbox for debug and after the error happens you’ll get to a command shell. There you can check the mentioned log file: cat /var/log/partclone.log