Fog Not Imaging
-
I have FOG 1.2.0 and when i run the quick image, the prompts all load, but it never begins the imaging process. and fog says that imaging completed successfully.
where do i start?
-
uploading works fine?
-
I only did the initial upload, have not had to run another upload since then, we just keep working of the same image.
Ive noticed another issue this morning where the “boot to HDD” option actually just loops back to the beginning, it never boots to the HDD
-
[quote=“seekerbeta, post: 36864, member: 26173”]I only did the initial upload, have not had to run another upload since then, we just keep working of the same image.
Ive noticed another issue this morning where the “boot to HDD” option actually just loops back to the beginning, it never boots to the HDD[/quote]
Change the settings in your FOG web GUI.
You will want to change the Exit type listed under the FOG Configuration->FOG Settings->FOG Boot Settings->FOG_BOOT_EXIT_TYPE.
-
[quote=“Jaymes Driver, post: 36866, member: 3582”]Change the settings in your FOG web GUI.
You will want to change the Exit type listed under the FOG Configuration->FOG Settings->FOG Boot Settings->FOG_BOOT_EXIT_TYPE.[/quote]
yeah, right after i posted that i searched like i should have, and now that is no longer a problem, but i still have the issue where it says imaging completed, and then reboots, but a 30gb image should take WAY longer than 2seconds
-
what OS is the image?
-
[quote=“Junkhacker, post: 36870, member: 21583”]what OS is the image?[/quote]
Windows 7 PRO 32 bit. ive taken a video and posted to Youtube so that you can see the whole process
[media=youtube]5A33uDF1ZNg[/media]
-
try this [url]http://fogproject.org/forum/threads/quick-format-to-ntfs-with-fog-for-noobs.10349/[/url]
it will guide you through removing the partitions and adding new ones. I believe this could be the cause of the “flyby” you are seeing. -
its a brand new SSD, i dont know if that makes a difference, there is no existing partitions on it.
-
+1,000,000 to Jaymes. putting a partition table in there caused it to recognise and erase and create the ones we needed. machine imaging right now!
-
Glad it was of use
-
Good afternoon,
I have a problem that is the same as the video posted in the thread, but the solution isn’t working for me. Is there anything different with the debug in version 1.2? In the last section I did choose the default for the new partition instead of 10011 since that value was too low for my options
[media=youtube]hLL_5X7uTBI[/media] -
Boot to debug. Run fixparts on hdd.
-
No luck with fixparts. Sounds like you’re leaning towards this being a problem with the partition not matching what is in the image. Would it be worthwhile to create a new image with a smaller partition, and leave part of the hd unallocated?