Posts made by astrouga

Seems like the “FOG_DISABLE_CHKDSK” setting in .32 is not set correctly. It is set to 1 by default, and according to the information, that should mean that chkdsk will not run. However the behavior is opposite, at least in some limited testing. When you run a Quick Image, and this value is set to 1, chkdsk runs. Chkdsk does not run if you change the value to 0.

There are several short-hand php if-then logic statements in /var/www/fog/management/includes/tasks.confirm.include.php that deal with this.
[CODE]$other .= (" chkdsk=" . ($core->getGlobalSetting(“FOG_DISABLE_CHKDSK”) == “1” ? ‘0’ : ‘1’));[/CODE]

And I noticed it in the fog script when I was looking at the init image file:
[CODE]if [ “$chkdsk” == “0” ]
then
RUN_CHKDSK=“-x”;
fi[/CODE]

More information on this thread: [url]http://fogproject.org/forum/threads/skipping-chkdsk.925/[/url]

Thanks,
astrouga

[quote=“dvlsg, post: 4938, member: 1186”]Yeah. I tend to swap between disables/enables as well as if/not-if and my own code gets thrown off like that all the time. I completely understand, haha.

Easy fix though! Might want to report it as a bug, as well.[/quote]
Good idea. I’ll do that. I think Blackout is re-writing that portion of the code in .33 anyway, but I’ll go ahead and do it.

Cheers,

astrouga

Yeah, perhaps they whole “DISABLE”/“ENABLE” thing got him confused. I think it would be easier for most people to go edit the php for the FOG SETTINGS page and change the FOG_DISABLE_CHKDSK to FOG_ENABLE_CHKDSK. I’m not near my computer now, otherwise I’d insert the code and filename here. Tomorrow I guess.

astrouga

Thanks for testing that out quickly.

That is what I figured after looking at the code. There is a shorthand php if-then that seems to determine it. Let us know if your get to test it on another host.

astrouga

Sure. From a cmd window on your windows clients, type one of the following to add a firewall exception.
[CODE]to open ping from a single ip:
netsh advfirewall firewall add rule name=“Networking - Echo Request (ICMPv4-In)” remoteip=xxx.xxx.xxx.xxx,Localsubnet protocol=icmpv4:8,any dir=in action=allow

for a subnet:
netsh advfirewall firewall add rule name=“Networking - Echo Request (ICMPv4-In)” remoteip=xxx.xxx.xxx.1-xxx.xxx.xxx.255,Localsubnet protocol=icmpv4:8,any dir=in action=allow[/CODE]

Obviously, you’ll need to replace the “xxx” 's with your numbers. Hopefully I didn’t introduce any typos there.

astrouga

[quote=“don miyagi, post: 4900, member: 1564”]Thanks a lot for all of your help. I went ahead and installed 10.4 LTS on one of many hp dx7500 I have to see what module it uses for the network adapter. I ran the following command in terminal: lshw -C networking

I haven’t tried creating the custom kernel at this point. I have remastersys loaded on my system. Should I do a backup of the system or should a backup of the current fog kernel be sufficient?[/quote]

I’m not sure what you are asking here. You don’t need to worry about where you build the kernel. You don’t have to mess around with your existing fog kernel, unless you want all of your systems to use the new one. Then you could just:
“mv bzImage bzImage.default”
Then you could just move your new kernel over to that directory and test it out.

–astrouga.

Has anyone tried setting “FOG_DISABLE_CHKDSK = 0” to see if chkdsk runs? I just finished a couple of quickimage tasks with the setting on “0” and it did not run a chkdsk. Of course, I didn’t try it with “1”.

astrouga

I have to ask, why would you want to go to XP? Application compatibility?

astrouga

[quote=“Kevin, post: 4871, member: 3”]
astrouga, what are you using the modify the file. I tend to use gedit to modify my files but init is to big to open. Are you using something else like Vi?[/quote]

I’m using the “by hand” method in the link dvlsg mentioned:
[url]http://www.fogproject.org/wiki/index.php/Modifying_the_Init_Image[/url]

BTW, I realized a long time ago that it takes mere minutes to do a complete reinstall of a fog sever (minus images and such). So I just take a spare system set it up with ubuntu and the latest version of fog. Whenever I want to test a system, I just take my fog server offline and bring the test one up. I don’t have to worry about whacking my working server that way and I don’t have to go to the trouble of backing it all up.

astrouga

[quote=“Kevin, post: 4876, member: 3”]Interesting, never knew that existed Thanks[/quote]
I didn’t either. It seems it might not work though.

astrouga

[quote=“don miyagi, post: 4878, member: 1564”]I’ve been able to upload images from two other computers and I’m 99.9% sure it has to do with the nic drivers and the kernel. Is there a way I can include certain nic drivers? Do I have to create a custom kernel? Is there such a thing as a definitive guide to that process?
[/quote]

I’ve commited myself to making a 3.4.5 kernel tomorrow, so I’ll post a note when I’ve got something working.

astrouga

Yeah, I’m not sure about the multiple chkdsk thing either. I have been told to do it though by the developers before, so I just run it twice now.
The BIOS setting sounds OK. I was worried about RAID. Dells seems to come with RAID turned on and I’ve had problems with that.
The mysql password is not an issue. It is fine to create that as long as you make sure you configure fog to use the password. I actually set a password for mysql. Think of it this way, if you can see any information about hosts or images, etc in the web gui, fog knows your mysql password because it is pulling all that info from mysql tables.
I’ll try to create a 3.4.5 kernel in the morning and post the link to this thread. Just “watch” this thread so you get a notice when it is posted.
astrouga

[quote=“gballane, post: 3954, member: 1226”]I just wanted to see if anyone had a chance to T/S this? Getting anxious due to deadlines![/quote]
Sorry I missed these posts. I’ve only seen this issue when I am trying to dump a partition to a drive that is smaller than the partition. For example, if I imaged an 80 GB partition and tried to put that image on a 60 GB drive, I would get that error.

The trick to make all of you images work on all of your machines (well at least part of the trick) is to shrink your windows partition before you image it. Then you can extend it when you install. My images all “extend” via a vbscript after the imaging process is complete and sysprep is running.

astrouga.

[quote=“rakarn, post: 4739, member: 921”]Any way I can get this kernel everytime i go to your link it doesnt give me anything to download, no link just a page asking me to signin or upload?[/quote]
Sorry about the dead link. I didn’t know there was a time limit to the post. I have reloaded it.

You can build your own kernel. It is fairly simple actually until you start trying to include your own drivers. The process is pretty simple:
Download the kernel
copy in config file from fog
make oldconfig
make ARCH=i386 bzImage
copy the new bzImage to the tftpboot/fog/kernel folder and point you host to it.
done!

This guide should be helpful:
[url]http://www.fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel[/url]
If you use xconfig, you can actually look to see if your particular nic drivers included or not.

astrouga

Yeah, perhaps. I’ve just given up on the “single disk” for now. I’m going to test out the latest .33 beta trunk tomorrow. Looks like the NTFS resizable option is a work in progress though:

[url]http://freeghost.svn.sourceforge.net/viewvc/freeghost/trunk/?view=log[/url]

Cheers,

astrouga

Hmm…not familiar with that error. Also, I’m not familiar with the HP system you are working on.
Did you run defrag and run chkdsk a few times on the drive before you tried to image it?
Anything unusual about the disk? How is the drive configured in the BIOS?
Also, what are those partitions like?

You mentioned that .26 supposedly worked. Have you tried using an older kernel with host?

astrouga

I was digging around in the init image, trying to track down the “chkdsk” variable that seems to control this and eventually discovered that is is trying to get this setting from the web management! So, try this:

Other Information --> Fog Settings --> General Settings --> FOG_DISABLE_CHKDSK =1.

1 skips chkdsk, 0 runs it. Mine was set to 1 already. It seems that this is an “experimental feature” in .32.
Let me know if that works for you. If not, I’ll go back into the init image. I think I know what to adjust now.

–astrouga

I’d stick with “Multiple Partition.”

To try the custom kernel, you want to save the bzImage34 file to /tftpboot/fog/kernel. Make sure the perms are like the bzImage file that is there already. Now, in the fog web interface, go to:

“Host Management” -->“List all hosts” --> click on the host you are trying to image --> find the “Host kernel” option.

You’ll need to specify the custom kernel here. If your custom kernel is named “bzImage34”, then you’d enter:

“/fog/kernel/bzImage34”

in the text box and update it. Then you can try pulling an image.

Again, let us know if you need more help.

–astrouga

Ah, I see. I don’t use the quick image much.

Modifying the init image is not a big deal. Just make a backup copy of the file before you start.

I just took a quick peek. There is a fog file in /bin with a “RUN_CHKDSK” setting and some conditions. I’ll see if I can modify it and get it to never do a checkdisk. Give me a day to take a look. I won’t have a chance to try it today.

astrouga