PXE Timeout is set by the Boot Menu which means it’s already booted. In your case, it’s failing before it gets that far.

You can play around with the files and build your own undionly to fix this, but I’d recommend having port fast, or if you can, disabling STP all together.

how do the c:\fog.log files compare between the working ones and non-working ones? you will need to recover these logs within 2 minutes or so after startup, as that is when the hostnamechanger service makes it’s request and the logs are quickly overwritten

[quote=“dwit, post: 31433, member: 24311”]HI,

I’ve done a fresh install of fog 1.1.1 with node, I’m trying to upload an new image. It run fine except the image stay in the /image/dev folder and stay with a generic name.

I try to chmod -R 777 * the images folder but it doesn’t change …
I’m running on ubuntu and FOG 1.1.1.

Any idea ?

thanks in advance ,[/quote]

Try this
[code]
sudo chmod -R 0777 /images[/code] and give it a go. also there is an update out please download and install FOG 1.1.2 some major bug fixes and improvements have been implemented.

No other idea or a way to debug this ?

No problem, have fun!

I read your post to my System Admin and she knew exactly what you were talking about. Thanks for your help! It’s working!

this problem would not occur if you sysprepped the image prior to uploading it. there is a new feature for windows 8 and 8.1 in the svn revision for deploying without sysprep. if you’d like to update to the latest svn, you can test the new feature and provide feedback on how well it is working.

Nope. I removed them from the task management tab and the hosts/groups tabs.

I have just found that if I manually add the devices and fill in the info and then create a new task, I am able to image a single device. I will try multicast next. This looks like it will be my workaround for this issue.

If multicast don’t work, then i’ll just do the last four individually.

Justin

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.