Posts made by Wolfbane8653

[url]http://www.fogproject.org/wiki/index.php/WorkingDevices[/url]

Page updated thank guys!

86 machines listed working with 1.x.x

Please read wiki!
[url]http://www.fogproject.org/wiki/index.php/Tftp_timeout[/url]…

[quote=“purpleturtle99, post: 32413, member: 23775”]Thanks Jaymes, No I have changed the boot file name yet. I upgrade via the following instructions:
[url]http://www.fogproject.org/wiki/index.php/Upgrade_to_1.0.0[/url]

Can you please advise how to change this file? As I have now tried another laptop that was work on 0.32 and I receive PXE-T01, PXE-E3B and PXE-M0F[/quote]

…added to Upgrade page
[SIZE=6][B][FONT=sans-serif][SIZE=24px][COLOR=#000000]Change your DHCP Option 67[/COLOR][/SIZE][/FONT][/B][/SIZE]

[LIST=1]
[*]Go to your DHCP server and change your Option 67 to undionly.kpxe
[/LIST]

1.) This could be a registry error or possibly a driver issue. Some refurbishing companies are notorious for swapping a motherboard out with a “compatible” board. Yes the CPU and everything seems to be fine but the video card may be a different version (not talking model but version of BIOS on the video card).

2.) If you contact your Microsoft vendor and give them all your single licenses they will combine them up and give you a volume license for as many single licenses that you have. This will negate all the single licenses but now you have a useful volume license. Then, you can just load the volume license on the image and not worry.

Usually you use the Http interface to change these but I’m sure someone here can help you out with telnet or a administrative software.

POKE (Jaymes)

By chance do you have Cisco switches or PowerData switches?

You may need to “enable Portfast (fast link)” and “disable STP” on the swithes as the opposite settings will cause issues wth iPXE(fog v1.x.x) where PXE(fog v0.32) will work without issues.

[FONT=sans-serif][COLOR=#000000]✓Firewall[/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000]✓AV[/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000][FONT=sans-serif][COLOR=#000000]✓Rogue DHCP[/COLOR][/FONT][/COLOR][/FONT]
Are you running any filtering software/Harware for turrents or anything of that sort?
Throwing this out there but your not using a wifi connection for the fog server are you?
Are you using a static IP on the fog server?

IF all fails connect the fog server and the client (tftp client) to the same switch.

OK so…

[FONT=sans-serif][COLOR=#000000]✓Firewall[/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000]✓AV[/COLOR][/FONT]

[FONT=sans-serif][COLOR=#000000]Now how about…Do you have a rogue or misconfigured secondary DHCP server?[URL=‘http://blogs.technet.com/cfs-filesystemfile.ashx/__key/telligent-evolution-components-attachments/01-4333-00-00-03-26-09-62/RogueChecker.zip’] Here[/URL] is the Rogue Checker I use. [/COLOR][/FONT]

What firewall and Antivirus are you running?

No your database will be fine. As long as you just reinstall.

[quote=“Mike M, post: 31275, member: 24694”][B]Yes we do have STP enabled on the switches.[/B][/quote]

Here is your probable issue.

If you could, please disable STP on the switch(es) between the fog server and the client. Then try a network boot using undionly.kpxe as your option 67.

Can you tell us what your switches are?

It is possible that portfast is disabled or STP is enabled on your network gear.

When trying to update btsync I receive the following error.

Setting up btsync (1.3.1-1) …
insserv: warning: script ‘S20FOGMulticastManager’ missing LSB tags and overrides
insserv: warning: script ‘S20FOGScheduler’ missing LSB tags and overrides
insserv: warning: script ‘S20FOGImageReplicator’ missing LSB tags and overrides
insserv: warning: script ‘FOGScheduler’ missing LSB tags and overrides
insserv: warning: script ‘FOGImageReplicator’ missing LSB tags and overrides
insserv: warning: script ‘FOGMulticastManager’ missing LSB tags and overrides

This is a Debian fog storage node.

[quote=“jdorst, post: 30787, member: 814”]I am guessing that the bandwidth graph for the nodes are tied to the Disk Info issue?. Fantastic work so far guys![/quote]

No, this bug does not relate to the “bandwidth” issue. If you are having a bamdwidth issue please , make a new thread.

[quote=“Robbie McHugh, post: 30762, member: 24192”]Hi Wolfbane,

Version installed was from main download section, not sure how to find my exact revision but will have a look in a min :)[/quote]

That means you are on the release of v1.1.1. The node problem is a gui/mysql bug. This is just a cosmetic bug and will not effect the storage node functionality. This show be fixed in the next release. It may not be fixed in the next revision.

Tom is currently working on this. Do you know the revision of 1.1.1 you are on ?

It is also now in the wiki under the How-to-guides–>[url]http://www.fogproject.org/wiki/index.php/Not_passing_PXE,_or_ProxyDHCP...NO_PROBLEM_Cisco[/url]

I’m curious…If you change Fog Configuration–>FOG Settings–>General Settings–>FOG_LEGACY_FLAG_IN_GUI tick this option. Then go to Image Management–> Select your image --> change image settings and set the Deployment Method to partImage instead of partClone.

Then upload with the bad sectors and deploy on the new HD.

What happens? Will this actually work?

Using my nodes the fastest speed I got out of 30 dc7800 was 2.61 GB/min on part clone(fog 1.x.x). I have a 1GB fiber backbone with 1GB Netgear Switches.

I noticed that IDE hard drives operate much slower. SATA, SATA II. and SATA III all operate a also different speeds. I would say that yes the speed of cloning is VERY dependent on the hardware.

As a quick update I have added this into the wiki “How-To-Guides”
[url]http://www.fogproject.org/wiki/index.php/Windows_Storage_Node[/url]