FOG won't complete when reimaging a computer.
-
We are using FOG 0.32. It has been working great for at least 2 years. All of a sudden it just stopped finishing imaging at the end of July 2016. I have tried to figured out what the problem is but have been unable to do so. I’d really like to use this for a little while longer before building a new FOG server. So, I’m hoping to figure out the problem. It doesn’t seem to get to any certain percentage and quit to restart. It is pretty random at where it’ll stop and restart. I can occasionally get some presysprep images to finish but even that is random. None of my sysprepped images will finish at all. Any help is greatly appreciated.
-
Sounds like either a hardware failure, or a full HDD. You can check freespace on the partitions with
df -h
It could also be something simple as a patch cable, or as bad as a flaky switch port.You should move to 1.3.0 RC, on a new server. If you need to move over those old images, we can help with that. I wouldn’t really advise upgrading from 0.32 unless you’re on a modern linux OS, using a server without hardware issues. If you’re not on a modern OS, the upgrade will surely fail. I’d also not recommend upgrading the OS - it never goes well with fog. Until you get the issues solved, I wouldn’t do anything to that old server besides make a copy of the images and hosts to somewhere else.
-
said in FOG won't complete when reimaging a computer.:
it just stopped finishing imaging
Can you explain exactly what “it just stopped finishing imaging” means?
I see two possible interpretations of this
- FOG fails to completely send the image to the target computer
- FOG does complete sending the image to the target, but the OOBE process now fails to complete leaving a broken install.
Which one is it?
-
Just meaning while in the process of doing a reimage(progress bar and percentage going across the screen in the blue, gray, and red screen) it will just stop and restart. Then after it restarts, the computer says Boot selection failed because of a required device is in accessible.
I also noticed today that I have a couple of computers that seem to be stuck trying to reimage even though they are not in active tasks. I wondered if that could possibly part of the problem?
The OOBE process failing, can you tell me more about that and how to check and fix it?
I don’t think it is out of space. I even deleted some images earlier today. Thanks so much for the replies!
We definitely do hope to get a new FOG server going soon. We hoped to use this one a bit longer.
-
@rghawk said in FOG won't complete when reimaging a computer.:
Just meaning while in the process of doing a reimage(progress bar and percentage going across the screen in the blue, gray, and red screen) it will just stop and restart. Then after it restarts, the computer says Boot selection failed because of a required device is in accessible.
Just to be clear you are talking about the partclone (or what ever FOG 0.30 used) screen that is transferring the image from the FOG server to the target computer. At this point OOBE or windows setup program has not started.
So this might point to the fog server since you are saying that all target computers are doing the same. Check to see if you are out of space on the fog server storage disk or if you have a corrupt storage volume.
