AH that is different!
[url]http://www.fogproject.org/wiki/index.php/Windows_Storage_Node[/url]
BUT this is only as a storage node NOT the primary but. You can make this the PRIMARY in the Storage management group.
AH that is different!
[url]http://www.fogproject.org/wiki/index.php/Windows_Storage_Node[/url]
BUT this is only as a storage node NOT the primary but. You can make this the PRIMARY in the Storage management group.
Is still exactly the same!
[CODE]/images[/CODE]
If you are willing to run both why not use the new server as the primary and install the storage node to the old server. This way this hardware is still usable.
To be honest I found earlier this past summer it was easier just to start over from scratch but new developments have really helped the situation to upgrading from 0.32 to 1.x.x
I would suggest to use the export and imports for hosts, then download the old images to the appropriate machines and re-upload to the new server. Also, verify that your environment is correct for iPXE boots. [url]http://www.fogproject.org/wiki/index.php/IPXE[/url].
With the images you could also try to push them over to the new server with ftp to the correct location but you will need to check the legacy images in Fog settings. Also, you will need to correct the permissions on those folders. Images created in 0.32 were created with partimage and now with 0.33b+ 1.x.x we use partclone.
Edit: corrected partimage and partclone part sorry for the mix up.
Its just not 100% easy to upgrade from 0.32 to 1.x.x.
[url]http://www.fogproject.org/wiki/index.php/Upgrade_to_1.0.0[/url]
[url]http://www.fogproject.org/wiki/index.php/Upgrade_to_trunk[/url]
1.2.0 is the stable published release. This was put out in June. If you could update to trunk it will help to narrow down some issues. Please update using the wiki link below.
[url]http://fogproject.org/wiki/index.php/Upgrade_to_trunk[/url]
[quote=“zingaro, post: 39868, member: 26873”]
2. with some pc with SSD installed , fog reboot after start menu display … !!, if remove SSD disk fog start correctly !!!, “standard disk i have not problem”
[/quote]
I think he means that the machine boots to the Fog Menu waits the MENU_TIMEOUT (5 seconds by default) and then when it goes to boot to the OS it kicks back to the Fog Menu. Is this correct?
If so you will need to change Fog Configuration --> FOG Settings --> Fog Boot Settings --> FOG_Boot_Exit_Type to Sanboot, GRUB or EXIT. The setting it is set to now may not be working for your SSD’s.
Can you download the file using a windows computer?
Change undionly.kpxe to default.ipxe in the command in this wiki help.
[url]http://fogproject.org/wiki/index.php/Tftp_timeout…#0.33_and_1.x.x[/url]
As developers run across improvements they often send word to others that there are some tweaks you can do to increase performance of FOG. To help spread it a little better I’m putting this out in the open and if any other GENERAL tweaks can be applied please post them here.
[url]http://fogproject.org/wiki/index.php/Installation[/url]
To be clear. TFTP is a bit buggy in Ubuntu 14.xx but some have corrected this by editing a start up script.
[url]http://fogproject.org/wiki/index.php/Ubuntu_14.04[/url] (includes 14.04.1 & 14.10)
We updated the wiki about a month ago to reflect these settings on Cisco, Dlink, and other smart network switches.
Have you tried changing your “Image Type” to “Multiple Partition Image - ALL Disks (Non-resizable)” ?
Andrew,
I have updated this page with some info I hope this helps.
[url]http://fogproject.org/wiki/index.php/Deploying_your_Image_a_group_of_clients[/url]
I purchase threw a reseller and they say exacly the same thing. But some drives are different models and the “same size”.
Really check.
I was imaging this summer in a lab of 24 and 20 would image without issue but then 4 would crap out. This was my exact issue.
Easy…
Host Management --> List Hosts --> [Select Host] -->Basic Tasks --> Advanced --> Download-Debug
Then boot the host. i can’t remember all the commands but “fog” will continue on the way to the imaging process. You can then figure out step by step exactly where you fail. If it fails during the partition allocation it will point you to the size of the hard drive.
For example:
Not all 80gb harddrives are 80gb some are 78.1, 79.8, etc. If the “master” upload was 79.8gb and the host to download to is 78.1gb then you need to tweak your “master” upload partition sizes.
This is what we call multicast. I will fix the wiki link but unfortunately i use unicast. You can still use unicast on multiple computers but they just don’t all image exactly at the same time.
[url]http://fogproject.org/wiki/index.php/Multicasting[/url]
Have you tried using the debug mode?
Listing updated. Thank your for notes and posting.
At time index 1:20 you get the wonderful error code!
Error 0x040ee119
Read thru the last few pages. This is most likely due to something not right in your environment.
[url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/#post-27304[/url]
Also check your network switches.
[url]http://fogproject.org/wiki/index.php/IPXE[/url]
I have updated a few of the wiki pages(with Tom’s help) to explain more in-depth of what each plugin does and will help you with. Here are the links below. If there is any other information that can be added please post or edit it yourself if you have wiki rights.
[url]http://fogproject.org/wiki/index.php/FOGUserGuide#FOG_Plugins[/url]
[url]http://fogproject.org/wiki/index.php/Plugins[/url]
sudburr,
The “Scrary slider” will not change the size of your current images. Nor will it override the global settings. This is image specific. NEW uploaded images should be affected by this new feature.
Other members were worried about compression for particular images in the past. This will simply give Fog users more control over their image sizes. Lower compression equals faster uploads but more network traffic.