Need more information. What type of Image? NTFS Resizeable I’m guessing?

If so your filesystem must be 100% tiptop or you will get lost files during the NTFS partition resize, delete and recreation.

This is outside of FOG’s control and is down to the badness of NTFS.

Always chkdsk /x 😄 multiple times, reboot in between.

I have a similar issue, but it doesn’t seem to be related to the OS install. I get the black screen with blinking cursor after the fog menu. If I change bios and boot directly to the HD and skip the fog boot screen the pc boots fine. Of course this is not a solution for us as we have over 360 pcs that we need to be able to image or reimage monthly or quarterly (student lab). This setup was working fine on Thursday of last week, but on Monday all 360 pcs only boot to flashing cursor. Ideas?

I have used the feature in the past without issues, it just seems once we pushed out SP1 to win 7 we started to see this issue.
The rebooting instead of logout doesn’t bother me, but the fact that it does not register activty does.

I put in a bug at:
[url]http://fogproject.org/forum/threads/auto-log-out-restarting-even-during-activity.1136/[/url]

Awesome, Keep this thread updated with your progress

through the webUI, add new images and select the type, name, and storage location to match what they were. Doing this tells the FOG database about the images, but doesn’t actually touch the contents of /images/ on the FOG server.

You need to make sure the type and location match the files in /images/ though or you’ll have problems.

I suggest in the future you use VirtualBox as a test bed so you can avoid similar issues in the future with your production systems.

[url]https://www.coolacid.net/articles/39-latest/134-restore-a-partimage-backup-to-loopback[/url]

did you try “sudo”?

My apologies, the error is “can’t have partition outside the disk”. I found a possible solution here: [url]http://www.edugeek.net/forums/o-s-deployment/61956-fog-client-error-cant-have-partition-outside-disk.html[/url]

I’m going to run DBAN and wipe the drive and then try to image again.

Have you checked the DHCP scope to make sure its populating the default gateway? I had this problem when I setup a new scope in a rush for my VMware vlan.

Perfect. That’s exactly what I needed! Pretty sure I missed the step to change the framework to 2.0. Everything else I’ve done, so that makes sense. Thanks again Chad!

[quote=“astrouga, post: 4790, member: 907”]I’ve updated the link again. This is the original 3.4 kernel I created a month or so back:

[url]http://www.filedropper.com/bzimage34[/url]

click on the “Download This File” image link after the “URL:” and “Embed:” text boxes.

astrouga[/quote]

Hey,

I don’t suppose you could upload the 3.4 Kitchen Sink Kernel to a filehost that doesn’t charge you to download could you?

Thanks
Dan

try compatibility check option or debug mode. See if you can get more info on where it’s failing.

Yeah. I didn’t realize choakem had resurrected a 7 month old thread. Thanks for updating the WIKI though!

Yeah, I’ve technically got my kernel edited to include the SCSI drivers, but I agree - it would’ve been easier to just switch to IDE before loading the OS.

don’t delete image. just upload over the old one

monkey see, monkey do.

Follow the instructions for modifying the init and the pxe menu. It’s basically a copy + paste, change the mode to whatever you want to call the new mode. Then go into the init file, modify the fog script to recognize your new mode, do what you need it to do, which is basically hard code the answers for OS/Image and removed all questions except for the name.

If you are afraid of tanking your production fog server, then use virtualbox/vmware to setup a new fog server and client and you can do that there.

The great thing about open source and free software is you paid nothing to get it and can modify it to meet your unique needs.