So I figured it out. Capone adds an option to the PXE boot menu, which is great, but my menu is not stock, and the automatic entry it adds was failing. Fix that and it boots fine.

So, it is possible to set Capone to use a different NFS/TFTP/Web server if you want to. The script calls on what is defined in the PXE boot option, not what FOG uses for settings.

[url]http://fogproject.org/wiki/index.php?title=Plugins:_Capone[/url]

Hi,

i found something more:

[QUOTE]
[INDENT=1]yoda wrote:I’ve found a fairly easy way to extract individual files from a partimage image file. These are the steps (Linux):[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]1. create a target image file using dd, e.g.[/INDENT]
[INDENT=1]Code: [URL=‘http://www.partimage.org/forums/viewtopic.php?t=950#’]Select all[/URL][/INDENT]
[INDENT=1]dd if=/dev/zero of=image bs=1024 count=3774771[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]where 3774771 is the number of 1K blocks. You can use “fdisk -l” on the original system to obtain the exact amount. However, I suppose you can obtain the rounded amount from partimage imginfo command and use an overestimated value;[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]2. associate this image with a loopback device, e.g.[/INDENT]
[INDENT=1]Code: [URL=‘http://www.partimage.org/forums/viewtopic.php?t=950#’]Select all[/URL][/INDENT]
[INDENT=1]losetup /dev/loop0 image[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]where loop0 has to be replaced with a higher numbered device (loop1, loop2, etc.) if loop0 is already in use (you can also use the -f option to use the next one available);[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]3. create a mount point, e.g.[/INDENT]
[INDENT=1]Code: [URL=‘http://www.partimage.org/forums/viewtopic.php?t=950#’]Select all[/URL][/INDENT]
[INDENT=1]mkdir mnt[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]4. mount the image from the loopback device, e.g.[/INDENT]
[INDENT=1]Code: [URL=‘http://www.partimage.org/forums/viewtopic.php?t=950#’]Select all[/URL][/INDENT]
[INDENT=1]mount -o ro /dev/loop0 mnt[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]5. and that is! You can now browse the files in the mnt directory.[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]Note that steps 2-4 have to be done as superuser (root).[/INDENT]
[INDENT=1] [/INDENT]
[INDENT=1]Regards,[/INDENT]
[INDENT=1]Rodrigo Ventura[/INDENT]

Hello Yoda

I think there is one step missing, because:

create an empty file connect it to a loop device create mountpoint mount loop device/file to the mountpoint
-> 5) you see an empty filesystem 😉

So between 2) and 4) one has to restore the partimage image to this filesystem… right?[/QUOTE]

Can someone tell if these steps are correct and working?

Greetz X23

and the Award goes to Kevin 😉 thx man

hi andrew, not not done it, but would also be interested in anyone who has considered mechanisms during the image writing to tell the SSD that it is empty again… i.e. knowing/ensuring that FOG sends the required TRIM commands so that the SSD starts wil a full set of erased cells…

Have you first created an image definition in “Image Management”? Once you have done that you can find your host in “Host Management” and associate that image with the host in the “Host Image” option. After that you can upload the actual image from the host.

What Version of Linux are you running and what version of FOG?

Have you updated to the latest FOG kernel? there is a 3.8.8.8 update out now and you can update from the Fog Web Management.

Try changing your partition on Image Management to a “Multiple Partition Image - All Disks (Not Re-sizable)”

I use the “what’s new” link, and there are always plenty of new threads and updates for me. If people ask a question and never come back, I’ve got plenty to work with without trying to chase them down o_O

I’m still tossing this idea around for my FOG server, I’m not exactly convinced on it yet. We kind of want to go the whole “Golden image” route from the sound of things, I prefer just setting up individual images per device (but I only manage 7 different devices so this makes it easier).

Keep us posted on what you come up with I love to see what the community is doing with their fog servers and the mods they put in place!

I prefer to register my machines as well, middle of the year image pushing comes in handy, and end of the year inventory is going to be particularly easy this year.

but I have also thought about using this “bypass host registration” guide… I just can’t decide 🙂

This has been a very handy tool, but it only took me a couple years to realize it. I always created a new file to upload even just an updated copy of an image. It has been nice a couple of times with not knowing how to rearm the SysPrep and being able to redeploy the old image, but for the most part now knowing to rearm SysPrep and needing to update images so often it is awesome to be able to just copy over the existing image. This is good info to have!

Good luck! Sorry for the wall of text.

If you feel like getting in to it, in order to get the boot package to get sent to the right location, you could take a look at the following lines (for example, inside function createInventoryPackage() in functions.include.php):

[php]
$ftp = ftp_connect(getSetting( $conn, “FOG_TFTP_HOST” ));
$ftp_loginres = ftp_login($ftp, getSetting( $conn, “FOG_TFTP_FTP_USERNAME” ), getSetting( $conn, “FOG_TFTP_FTP_PASSWORD” ));
[/php]

If you feel like getting in to a more “correct” way of doing this, I think the issue with getting the boot files pushed to the correct locations is that $conn is (correctly) looking at the master node since that’s where MySQL lives, so the “FOG_TFTP_HOST” information it receives are the master node settings. I [I]think[/I]. I’m not positive on that. I was thinking of switching it so it gets its information from the config.php file located on the service, but there are a [I]lot[/I] of calls to the MySQL based getSetting function. It might take a lot of changes to rework that.

You’re correct about the scope and topology, The problem I was running into, ultimately, is something within my network is preventing the pxelinux.0 from reaching it’s final destination. Part of the pxelinux.0 would be received but the rest kind of just floated in limbo.

I have another topic where I went through troubleshooting steps and eventually, enabling a proxyDHCP service with dnsmasq resolved the issue.

I appreciate your insight on this as well as your understanding of the network!

Topic is here -> [url]http://fogproject.org/forum/threads/tftp-problems.4163/[/url]

Ah, I overlooked the ntfsresize test portions of the script. Try just replacing “$RUN_CHKDSK” on line 391 with “-n -s 10G”.

Ok, thanks for your answer BryceZ. That’s what I’m gonna do now.

I could change the ascii. Thanks for your help.

I’m not using FOG in association with AD. So I can’t help you with this. Maybe you can find some advice in the FOG Wiki or in the forums.