Hi,

I have exactly the same problem. I have just reinstalled my fog on Ubuntu 10.04 and im having nothing but grief. Fails at 0% on a GX620 and on a 380 it fails at 4%.

I have checked all mysql settings and they are correct. I have checked my storage node settings and they are correct.

I thought moving it to Ubuntu 10.04 would work.

check out this video of mine

[media=youtube]IqvBbV0CqwA[/media]

HELP ME PLEASE, ANY ONE FIXED IT?? UPLOADING IMAGES WORKS FINE

I thought so as well but it happened. I try to get new machines under waranty. I have to try

I am not sure why it was discontinued but the developers are shooting to bring it back in the next release. You can run a report in SCCM to get hostnames and MACS or the free SoftPerfect Network Scanner can also generate .csv’s for you if your shop does not use SCCM.

My guess is that it’s having an issue with the hidden dos partition in the beginning. I’ve had trouble with OEM partitions and Fog, and checking the forums, it looks like other have too.

Have you had any luck with another image that’s less complex? If a plain vanilla image works captures and deploys ok, then you at least know Fog is set right and working. From there you could try adding an additional partition, capture/deploy, repeat, until you reach a problem and try to troubleshoot from there.

Other thing I could think of to try if you really need that image with the hidden partitions is to do a RAW image type. I’ve not tried it myself as I don’t have the storage space for such a thing, but I’m wondering if that’d at least get you going for the time being. It’d be a large image file and take a bit longer to capture and deploy, though.

Anybody else had better luck with multiple partition setups?

If you can mount the drive into another machine running linux, you can probably get to the /images folder and copy your image files.

For the image definitions, host records, and hardware inventory, you’ll have to locate the fog database files. You need to look on the internet/mysql website about how to restore a database from the data files. On the old drive, the data files will be on /var/lib/mysql/ and you may need all of the files or just the ones in the “fog” subfolder. I’m not sure.

If you need help setting up a backup process once you get your FOG server back up, just ask.

If one machine still boots to PXE and run something like a hardware inventory, then I wouldn’t think it is the TFTP password. Schedule a hardware inventory task for a machine in the 192.168.10.x network and make sure that works.

If that works. Try to schedule a task for a machine in the 192.168.12.x network. Schedule it through the web interface, then check the /tftpboot/pxelinux.cfg/ folder for a task file matching your machine (01-mac-address-of-machine). If you get a file in that folder, paste the contents into this thread (use code tags).

Hi All. I never posted the fix for TFTP open timeout.

navigate to /etc

then type in

sudo nano rc.local

then your password.

next, add this one line before the end:

/bin/sleep 30 && /etc/init.d/tftpd-hpa restart

hit ctrl + o

hit enter

then ctrl + x to exit.

I can also confirm that HP 8100’s and 8200’s work with the latest kernel out of the box.

Please start a new thread with your issue. Reference existing threads if needed. Your issues are different enough to warrant its own thread.

I fixed my problem. I had the IP address pointing to the wrong place. D’oh. Noobie mistake.

Thanks MLX,
I’ll mention the requirements to others - 🙂

I quick Google search for “Throttle Linux network connection” came up with this result - even if Fog can’t throttle, if you can slow down the speed of the server’s NIC it should accomplish the same result. You also might ask whoever the network is outsourced to if some form of QoS can be setup (so it can run at full speed unless someone else needs it).
[url]http://superuser.com/questions/66574/how-to-throttle-bandwidth-on-a-linux-network-interface[/url]

not without heavy modifications to the code. When uploading or deploying images, NFS is used to to access the image files.

The # is the prompt indicator. If I told you to run a command in windows like c:>ipconfig /release, would you type the c:>? o_O

Actually it was pretty straightforward to get working on FC17 -

Follow instructions found in other posts for Fedora Core 16 (Remove php-gettext from the install file, fix the NFS-server start so it won’t break the install process) Replace &$tmp with $tmp Start the NFS-server / enable the nfs-server

I just successfully re-imaged a computer 😄

OK, I’m an idiot, I’d somehow overwritten the ramdisk image with the kernel, turning off quiet produced an error that made that clear (unreadable ramdisk image, essentially).

Now I can load the kernel, but I eventually just end up at a command prompt. If I type “acronis” there, it does some stuff (something with network interfaces then enumerating my drives) but then just dumps me back to the prompt. Do I need to run it from a graphical environment? Is there any way to automate whatever the solution to getting it to run is?

[quote=“pjcard, post: 8665, member: 2528”]This discussion is about booting hirens over the network, russed, I think you’re talking about something else.[/quote]
Maybe you’re right, but as I stated at the start of my post, I had something to say about booting Hiren’s boot CD from it’s ISO image file and running its menus and programs.
I only had the hope that this can be useful for someone.

run chkdsk /f 😄
defrag
seatools for dos maybe?

Use proxyDHCP so you don’t have to worry about what the DHCP server config looks like.

Incase anyone else has this problem - It seems to have resolved it self.

The image I mention above was never sysprepped. I sysprepped it, uploaded it as multiple partition - single disk, and it worked fine multicast. After that I noticed the hidden partition shrunk from 500mb to 100mb. I figured I’d try uploading it as NTFS resizable - and go figure, it works fine multicast now.

Odd

hahaha thanks for the award. I checked the cabling and switching, things seem fine. I had to reboot the machine for some OS updates to take effect and that ended up fixing the issue for now. I’m still curious as to why it was happening. I will definitely poke around in syslog like you suggested next time.