I just resolv my problem. I changed my IP Address in the /opt/fog/.fogsettings , it was the wrong IP as we changed it previously.

Did not realize a /tftpboot.old file would be created with the upgrade

Issue Resolved.

The final resolution to this issue was related to additional Storage Nodes. There were two extra storage nodes that must have been created a few years ago for testing. Neither one of them was the Master Node. Once I deleted those two nodes the error about not being able to find a suitable storage node disappeared and everything started working.

Thanks for all of the help.

Thank you, I was able to get it. TFTP is not enabled by default in Windows 7. We aren’t using our Fog server for DHCP, so I just had to enable tftp and it worked.

[quote=“TylerC, post: 30792, member: 2655”]You figure this out yet. I have this same thing going on right now and I really need to deploy some images. I’m wishing I would have never upgraded from .32 I now understand why some older sysadmins are like never upgrade anything! lol[/quote]

I’ve finally figured it out. Both the source and target disks have 500GB but not exactly the same number of blocks (source is a bit larger), So I’ve made the partition layout so it’s the same number of blocks than the smallest disk and now it’s working even without creating any partition on the destination.

[quote=“Tom Elliott, post: 31204, member: 7271”]Going to go out on a limb and ask, Does the host have an image assigned to it?[/quote]
Yes, a lot of image… but maybe I can remove /var/www/fog and re-run install script ?

edit : it’s ok with my method : solved !

I’m going to go out on a limb and take a guess that you also assigned an imageID and told the system to image after registration was complete?

There is/was a known bug with this and I’ve fixed it in SVN.

To fix this in the meantime, you’ll likely need to remove it manually from the database.

Something like:
[code]delete from hosts where hostID=‘0’;[/code]

Guys, one more thing.

I created that VM with only 20gb, which is not enough for the “images”. I then add another VDH, mounted and give permissions. But when i try to used, changing the settings on the FOG GUI (Storage Management), i get a permission error, when i try to Download an “image”.

What kind of permission i still need?

I have problems with fog 1.1.1 working correctly if the GUID of the computer is not displayed. Fog 1.1.1 is ok if the GUID is displayed, however if it sees FFFFFF …etc it says not for us.

I’m going to run western digital diagnostics on the hard drive, hopefully, if it is corruption on the drive then a reload with another drive will remedy this issue.

I figured as much, thanks for the reply though.

No I doesn’t ask for me for what delimiter. And I didn’t realize I was supposed to set that up during the process

init.xz

[code]cd /var/www/fog/service/ipxe
xz -d init.xz
mkdir tmp
mount -o loop init tmp
#EDIT YOUR FILE SPECIFICALLY tmp/bin/fog.man.reg
cd /var/www/fog/service/ipxe
xz -C crc32 -9 -c < init > init.xz[/code]

If it’s only linked to Chrome : [url]http://news.softpedia.com/news/Chrome-34-Seeks-to-Save-All-Your-Passwords-436693.shtml[/url] (added screenshot about that flag but can’t test if it works right now)

But, I’m under the same Chrome and going to the FOG 0.32 right now and the problem isn’t here.
Homepage password is saved but it’s doesn’t overwrite node account or password.

[ATTACH]1057[/ATTACH]
(sorry my browser is in french)

[url=“/_imported_xf_attachments/1/1057_Sans titre.jpg?:”]Sans titre.jpg[/url]

FYI
I upgraded fromFOG 1.1.1 -> FOG svn 1910 and got same problem, Updater never finish.
Installation stopped on Database Schema Installer / Updater

Server reboot did not help it goes to Database Schema Installer / Updater again…
Running Ubuntu 10.04.3 LTS

After that I installed FOG 1.1.1 ant thet installation went trough.

[url=“/_imported_xf_attachments/1/1054_foginstall.log.txt?:”]foginstall.log.txt[/url][url=“/_imported_xf_attachments/1/1055_daemon.log.txt?:”]daemon.log.txt[/url]

[quote=“adam lawler, post: 30853, member: 21019”]Similar to this thread
[url]http://fogproject.org/forum/threads/tftp-boot-fails-the-selected-boot-device-failed-after-upgrading-to-fog-1-1.10878/[/url]

I am unable to get 5 desktops to boot to the fog menu. i get PXE-M0F: Exiting Intel Boot Agent. now these desktops all have DP43TF motherboards, so intel nics. I have no issues with the VM i have with an intel nic, and no issue with my realtek desktops (weird that intel if the issue).

Again, PXE works fine for most boards and some other intel nics. I have the latest bios on these boards. any ideas?[/quote]

Do other DP43TFs boot to your other machines? If not, it’s the drivers in the kernel. you need to update your kernel to support the drivers for that specific model of nic.

If other DP43TFs boot fine, try moving the machines, sometimes switch gear can affect if the boot file will reach its destination.

There’s ways to assign different .pxe boots to different clients. Sadly my google-fu is lacking right now but bringing VLANs into it is kind of a mess.

Hey Mark,
The only QoS policies we have in place are for VoIP phones so I don’t think that should have any effect.

I’m actually doing my testing on the core. I noticed the issue offsite in another building and then came back to the office to test at the source. Yep - the server and clients are both on the core switch. This switch does the routing between vlans. As soon as the clients move out of the server vlan, multicast suffers.

I might have to look into the Iperf tests - it sounds like a neat tool. All other traffic seems okay though - I can copy files from PCs around the network and still get gigabit speeds.

Thanks for the thoughts! At this point the issue is only slowing me down a little bit - we’re just unicasting everything at the moment so it’s not a major problem, just something I’d like to try to fix.

Edit: forgot the IOS version, it is 12.2(17r)S4

I figured out the problem and that was the hosts table with all the MAC addresses was jacked so I created a new one and it now working fine. I appreciate you for helping me and i never thought of checking if the task was generated that way.