I’m looking for the unicast log files but i didn’t find anything in /var/log/fog ?
Oh nice! So I’ll update my server and I let you know if it fix the problem, maybe it could help someone in the futur.
Thank’s for everything @Quazz
@Andorfyn Latest git version is 1.3-RC8, so maybe not
It’s peculiar behavior, it definitely shouldn’t be happening in such a standard situation. It might have just been a fluke, a recapture on the latest and testing might confirm that.
I thought I had the latest version actually ^^’.
It’s the default Windows recovery partition which show you that screen :
@Andorfyn Probably want to update your FOG to the latest, might resolve the issue on its own.
Can you tell me more about the recovery partition? Is it just the default Windows recovery or something specific such as HP recovery?
OS of FOG server : Debian Jessie 8.5
Version of FOG : Running Version 8479 (1.2 version Trunk)
Image : Windows 10 single disk (resizable)
Tell me if you need more information.
@Andorfyn Hard to say without knowing the details. Answers can vary widely depending on your image, FOG version and such.
Andorfyn last edited by Andorfyn
Okay no problem! I already solved my issue, I had : “Target partition size(470MB) is smaller than source (471MB). Use option -C to disable size checking(Dangerous)”.
So I’ve decide to delete this Recovery partition which is useless for me. But why there is 1mb different beetween those ?
Thank’s again @Quazz ;- )
@Andorfyn Unfortunately, no such logs exist on the FOG server currently. There was some talk at one point of maybe looking into it, but if an error is encountered during capture it should display it on the screen.
Could you try watching it carefully as it tries to capture an image and perhaps take a picture when you see an error? Or could you tell us more about the problems you’re experiencing?
Info we might need:
OS of FOG Server (including version number, eg Ubuntu 14.04)
Version of FOG (eg 1.2 or 1.3-RC8 or svn 5949)
Thank’s for your reply.
Actually there is nothing interesting in the scheduler log. What i’m looking for is a log is the result of an imaging. Because I’ve some trouble when I want to capture a device. (Sorry for my humble English :'D).
I don’t believe there’s logs for unicast, unless you schedule them as a task, in which case they end up in the task scheduler log file.