Downgrading isn’t exactly supported from 1.x.x to 0.32. While you “could” do it by removing the current installation of FOG and the database system, export the hosts list and reimport to your “new” downgraded install, I’d first like to see if we can get this for you.

I’ve now created and deployed a few images using 13.10 with 1.1.0. It is working very well. Thank you, everyone–for your help!

Now, I need to start a new thread about another problem… 🙂

Yes all of this worked I can cd /images create a folder as the user fog and double check by going to images folder and seeing the test folder.

Sorry for the late reply, got crazy busy on Friday. Anyway, I think it may be a problem when I try to pxe boot the machine, that’s when the error comes up and not much more information is provided :(.

[quote=“JeffT, post: 28742, member: 24415”]Changing it to undionly.kpxe.INTEL worked! Tested it with booting to the OS and to the FOG server.

Thanks for the help![/quote]
Glad I could help.

Sorry, I forgot to reply.
Upload works fine with the normal windows installation.
Now, i’ll look for the problem of downloading old image.

[quote=“number_one, post: 28796, member: 24434”]Tom, do you mean the documentation shown as the installer runs? Maybe I’m missing something but I don’t see much except for a changelog included with the installer files. If you mean inline documentation within the installer then I didn’t pay enough attention while it was running. Sorry about the venting; just haven’t had any experience with FOG yet and am eager to get things up and running.[/quote]

I meant the inline installer, that’s why it’s there.

No upgrade, it’s a fresh install

[quote=“Tom Elliott, post: 28467, member: 7271”]Which undionly.kpxe file are you running?[/quote]

here is the tail of the error.log

Cannot adopt OID in UCD-SNMP-MIB: laErrMessage ::= { laEntry 101 }
Cannot adopt OID in UCD-SNMP-MIB: laErrorFlag ::= { laEntry 100 }
Cannot adopt OID in UCD-SNMP-MIB: laLoadFloat ::= { laEntry 6 }
Cannot adopt OID in UCD-SNMP-MIB: laLoadInt ::= { laEntry 5 }
Cannot adopt OID in UCD-SNMP-MIB: laConfig ::= { laEntry 4 }
Cannot adopt OID in UCD-SNMP-MIB: laLoad ::= { laEntry 3 }
Cannot adopt OID in UCD-SNMP-MIB: laNames ::= { laEntry 2 }
Cannot adopt OID in UCD-SNMP-MIB: laIndex ::= { laEntry 1 }
[Fri May 30 13:22:37.131054 2014] [mpm_prefork:notice] [pid 1702] AH00163: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4 configured – resuming normal operations
[Fri May 30 13:22:37.131117 2014] [core:notice] [pid 1702] AH00094: Command line: ‘/usr/sbin/apache2’
How do you tell what version of the undionly.kpxe file you have?
Yes I have searched the forum and the wiki also did the steps from kernel Issues url and no change.

[quote=“Tom Elliott, post: 28707, member: 7271”]It’s always the same file size?[/quote]

It was giving me different file sizes when I tried different Kernels. I was using .32 and just updated to 1.0.1. Now the Kernels are downloading but I can’t boot to the NIC. Did a setting get changed when I updated? Also, I noticed there is a new tftpboot folder and the old one was renamed to tftpboot.prev

That node is the master storage node.

[quote=“Todd Humphries, post: 28684, member: 24418”]Jaymes, that was it! I deployed using the advanced ‘Download - Debug’ task and then ran fdisk to create an empty FAT32 partition. I then continued the download process and the image download started normally.

I’ve been using v.32 for several years and never had to create a partition prior to pushing out an image. Now I know. Thanks for the help.[/quote]

Hahaha, I was using a windows 95 disc letting it format a partition then yanking the disc… I knew there had to be a better way, in man all you are loading with the pxe is basically a slimmed down linux cli. Glad I could help someone!

[quote=“Mark Carrara, post: 28662, member: 1363”]I have downloaded Ubuntu 13.04 and will load it today. I’m sure with the help on this forum I will get moved to the new version of FOG.

I thought I remember reading about removing some of the unused/unneeded services from FOG. I am a firm believer in software doing one thing and doing it great and not dong a dozen things well. On our network I have many servers that only do one thing like DHCP, print manger, single app server. I feel it is better for optimization and troubleshooting then having one server do multiple things.[/quote]

I agree with you there!

And you are correct, you can slim fog down from anything you don’t use. If you look at the installer script before you run it, you can even remove the calls there to prevent them from being installed.

However, most of what is installed with fog is required. The only thing that is really optional would be the DHCP sever and that is why there is a question about using FOG as the DHCP. If you don’t want/need it you tell it no and it will still install happily.

If you remove services you need to accommodate them by providing the services else where. But that would involve a custom set up and that would fall outside of the bounds of our support. Of course we will try our best to get you running, I would prefer if you install fog as it is intended and get it working, then you can play with it further from there if you wish.

Got it, thanks!

Does the FOG server have access to the internet? If not, this is the reason for your slowness and it is already documented in the forums.

Thank you! Thank you! Thank you!

[quote=“RoweAdmin, post: 28562, member: 23772”]I made the mistake of thinking there was a problem when only 1 client was connected and stuck on the Please Wait screen. After starting the second client, everything worked great.

We are seeing speeds of 2Gb/s and more through an old Linksys/Cisco 16 port gigabit switch with 11 clients.[/quote]

This is the nature of Multicast, it sends the same stream of data to ALL machines on the list and if one falls out the process will stall and fail. You need all machines to stay in constant contact with your FOG server during imaging. Multicast waits until each client reaches the “checkpoint” before sending any more data. This is typically sower than unicast because it will decompress the image at the server to send out, rather than waiting until it reaches its destination and expanding.

I enabled the “Is Master Node” option on my new Storage Node and it works ! 🙂

Any chance you could point me in the right direction as i can’t find where to make those changes at all .

Cool,

I also, hopefully, fixed the image replicator as well to have, basically the same information.