IPXE - Could Not Start Download issue
-
Alright, I’ll give that a shot.
-
This post is deleted! -
Well I don’t need the bleeding edge release or anything. I’m just wondering why I’m getting the “Could not start download: Operation not supported” on the client machine I want to image. If the bleed edge server fixes that I’ll do this right now
-
I would say try the latest and greatest. You may have to uncheck the FOG_NEW_CLIENT after upgrading, but other than that all should work perfectly.
-
Alright sounds good. I’ll give that a try. Thank you for your help. I’ll let you know when I’m done.
-
Ok so I figured with this since I been going ham on the previous one I’d start fresh. Im on a fresh install of CentOS, did all of the updates and such. Went to the link and started setting up/installing everything. Even got BTSync up and working I believe :).
I start the install of Fog and towards the end of the install I get this.
[CODE] Press [Enter] key when database is updated/installed.- Setting up storage…OK
- Setting up and starting NFS Server… * Configuring Fresh Clam…mkdir: can not create directory ‘/opt/fog/clamav’: No such file or directory
chmod: cannot access ‘/opt/fog/clamav’: No such file or directory
Failed!
[/CODE]
-
I know what’s wrong don’t mind me being an imbecile
-
2917 should fix this sorry
-
You guys are being tricksters now I see! I set everything up and got the image info set and ready to go. Turn on the computer I want to image and nothing. Didnt even find anything. I was so use to just click enter enter enter enter during Fog install that now you have DHCP set to y/N instead of Y/n. Haha. Rerunning this so I have the DHCP service and will let you know if that other issue goes away.
-
Getting SOOOOO close! So on the client machine it’s went through some of the load up process within the iPXE. It hangs up at the FOG ASCII screen though with a blinking cursor.
I could always start fresh again if I need to. -
Is this while the system is attempting to boot, or are you trying to perform a task?
-
I set up on the server side to perform an upload task. Booted up the client machine and it hangs on the FOG screen. I thought maybe there were some sort of permission issues to the /image folder so changed the permissions but that didn’t do anything.
-
[QUOTE]Booted up the client machine and it hangs on the FOG screen.[/QUOTE]
Hard to say without having more details. Could you send a screenshot or describe a little more? Do you get the Boot Menu if there is no task scheduled? Are you able to perform the registration from this menu? What exactly do you see right before it ‘hangs’? e.g. ‘Checking Operating System’ or ‘bzImage’ or ‘iPXE’ or …?
-
We narrowed what the issue was. On current SVN versions we are not specifying the version number of fog in the init. This displays when the banner is displayed and this was where the issue was/is occurring. The reason for the banner to be stuck is his system would boot and everything just fine. However the os layer is being assigned an ip outside of the fog dhcp controller. For example if his network main has a dhcp server handing out IPs in the 172.16 range while the fog dhcp is handling 10.x.x.x range, boot up would get the 10.x.x.x range but the init would get ip in 172.16.x.x range.
