BigMan99211, You need to adjust apache to look for php before html, or remove the html file as you described above. This is not a bug.
That “This works!” page is a default created by apache as a courtesy to check on localhost to make sure your folder is accessible. I theory we could add a “remove index.html if exists” line, but for those of us that use our FOG servers as web servers (internal or external) this could cause a HUGE headache if your index.html went missing.
The way multicast works, it waits for EVERY machine in the group to reach the same point in the upload, everyone will hang until ALL of the units have checked in.
This is probably a setting in your switches that may be flagging or causing issues with the traffic.
What kind of switches do you use? Are they managed switches? I’m not too versed in Multicast troubleshooting, however I did get it working in my environment.
If you have proxyDHCP set up, can you try doing a multicast on a basic hub and see if you can image them, if not try a basic router with dhcp functions, then we can rule out multicast as a problem at the server.
You could try :
[code]
chown -R fog:root /tftpboot[/code]
Could be a possibility that the rights aren’t correct on the folder.
vmlinuz is just an “executable” of the linux kernel, for lack of a better way to describe it.
In that case, give it a go! Since you aren’t needing anything specific from the IT department, and everything is housed on machines you manage, set up a shared space, save your image there and find the right syntax to get it to load via the “USB FOG Server”.
When you set up Ubuntu did you create a user named FOG?
Are you able to Register the machine as a Host in the Web GUI? (sorry silly question just want to verify)
Maybe I misunderstood, your last post only touched base on how many times you installed FOG, there weren’t any issues posted.
[quote=“Valden, post: 22694, member: 21858”]Does it works only on the usb key ? Is it possible to put a network path to the initrd ?[/quote]
only one way to find out!
It depends on your network, if it is ANYTHING like my network (I work in education), it will be troublesome. We make every user authenticate, if you do not authenticate you only get public rights. So you need to understand your network environment.
From what I gather you are a student correct? I do not allow my students open space to store files and information on my server… you will need to check with your local IT department to find a place to put your files for access, possibly even create a special user and password.
THAT BEING SAID. I have written scripts in the past to authenticate to a network storage drive on windows, so the task is possible, it’s just a matter of learning to write a script that can authenticate itself to a user, whose home directory is the storage space of the iso image.
I would use something like
[code]
append iso initrd=10.x.x.x/path/to/FILENAME.iso
[/code]
where 10.x.x.x is the IP address of the server, you may have to syntax it another way to get it to see the server too, this is only an example, and not a working one.
I understand you are frustrated, but trust me, if we can get a good clean install to work from, FOG will be your best friend.
You did the right thing in choosing Ubuntu, i feel it is the best for user friendliness. I have set up servers on CentOS with a fair share of problems, and OpenSuse is pretty much impossible at the moment (the pieces are there to an extent but they don’t work together, and every time I get close I crash my VM -.-).
Don’t have doubts, Ubuntu has gone through a lot of changes from 10.04 on, they change the look and feel from Gnome to Unity and that messed a LOT of things up, since then it has been in “patch mode” (that’s what I call it when users have to solve their own problems because of changes made to an OS).
I just wanted to make sure you weren’t on a troublesome revision. 13.04 is stable enough of a release you shouldn’t have issues because of OS problems, so we can write that off, for now.
Normally, after I have figured out the issues with the fog installer, I nuke my fog install and run it again. You never know where it hung last, if is finished setting up the user properly, etc.
You can manually install the services and configure them, but I only recommend this for advanced comfortable users.
At this point (since there is nothing on the server), wipe it, fresh install Ubuntu, install FOG.
[quote=“Ubuntu_newby, post: 22668, member: 22075”]I have tried it, same result.No errors btw.
My Ubuntu computer is not online all the time,only when I’m trying Fog or something else. The services are therefore (re-)started when booting the computer.
Gr, Jos[/quote]
Be carful with your expectations there… There are some versions of Ubuntu that have problems with upstart jobs. Mainly the TFTP service being started before an ip address has been assigned to the machine.
What revision of Ubuntu did you use?
You can look into gPXE, you can set it up so the disc looks for your FOG server information, I used it as a troubleshooting step when trying to find the issue with my network.
There are USB bootable version of gPXE so you can give that a shot if you want. However, I may be misunderstanding you. This will allow you a USB bootable to FIND your FOG server already set up.
If what you are asking is for a “mobile” FOG server on a USB drive, unfortunately I have no suggestions for you, I have not looked into this.
Welcome to FOG!!! I will paste this information here for you, but the thread can be located here in the future: [url]http://fogproject.org/forum/threads/setting-up-and-building-udpcast-failed.4548[/url]
Log into the FOG Server as root and go to your installation folder.
Something like:
[code]
cd /opt/fog_0.32
[/code]
Then cd into the packages folder
[code]
cd packages
[/code]
Then run these commands:
[code]
wget [URL]https://svn.code.sf.net/p/freeghost/code/trunk/packages/udpcast-20120424.tar.gz[/URL]
rm -f udpcast-20071228.tar.gz
sed -i ‘s/udpcastout=“udpcast-20071228”/udpcastout=“udpcast-20120424”/’ …/lib/common/config.sh
sed -i ‘s/udpcastsrc=“…/packages/udpcast-20071228.tar.gz”/udpcastsrc=“…/packages/udpcast-20120424.tar.gz”/’ …/lib/common/config.sh
cd …/bin
./installfog.sh
[/code]
You MAY want to delete the /opt/fog folder for a clean install. (or rename it)
Awesome, glad you got a workaround figured out! Sounds like the issue may have been the card itself, did you try the Kitchen Sink kernel with the original hardware? now that you have them imaged you can tinker with em to figure out what the real issue was 
I still find it odd that one would image and the others wouldn’t 
I would have recommend a different kernel otherwise O.o
SOMETHING else to think about, Tom Elliot here on the forums works hard to keep 0.33b up and working, he also makes custom kernels, you can take a look at his kernel, they tend to work for most hardware
his kernel is here -> [URL=‘https://mastacontrola.com/fogboot/kernel/bzImageCORE’]https://mastacontrola.com/fogboot/kernel/bzImage[/URL]
just back up your old bzImage before giving it a whirl.
You will want to look into the FOG 0.33b version, we are working to get multiboot imaging working.
No problem Juston, I live here from 8am to 3pm weekdays 
I just try to share what I have learned so far. I implemented FOG about a year ago as an imaging solution for the summer, luckily I played long before the summer and got all the bugs ironed out or I would have been up the creek without a paddle.
If that doesn’t fix it let us know and we will try some different steps.
I know it seems silly but check the BIOS settings, I know you said there is “nothing” different between them, but there is obviously something.
Have you tried imaging the other hard drives (from the custom boxes) in the one working unit to rule out any problems with the drive?
It seems to me like the custom boxes may need a BIOS update to see your PXE server properly, I only say this as I had a similar situation happen with some Tangent C105 units. They will image on WDS all day long but won’t talk to FOG, installed the BIOS update and imaging went off without a hitch. Yes I had 3 or 4 that WOULD image to FOG without any updates but the other 25 REFUSED.
Since you have some working units, we can kinda put the FOG server on the back burner as the main issue. It has to be something specific with the units.
HOWEVER, Another option is to install the DNSmasq service, it acts as a proxydhcp server during boot and helps to resolve some issues with PXE booting. This can SOMETIMES help with troublesome BIOS set ups.
You could try the second link I posted you, it covers specifically adding a second hard drive rather than replacing.
[url]http://fogproject.org/forum/threads/how-to-add-a-second-hard-drive-to-fog-server.4383/[/url]
I only posted this information so you could give it a shot. I personally haven’t ventured into increasing my drive space, or adding another drive.
You alternatively could use the Web GUI after you mount and format the new drive to add a storage node. It all depends on how you want to set it up.
I posted these here in case I misunderstood what you were trying to convey (which I did )