That did the trick. Thank you. Was so use to seeing installation finished that it was finished. But did realize it seemed to grab the kernels and client wayyy faster than normal. Iāll make sure to keep that in mind next time.
Posts made by Adam.E
-
RE: PC Rebooting during Fog startup image process. (Build 4248)
-
RE: PC Rebooting during Fog startup image process. (Build 4248)
Ok, Iāll do that. Iāll let you know. Thanks!
-
PC Rebooting during Fog startup image process. (Build 4248)
I just did an SVN up to update things before making an image. After the computer grabs an IP through PXE it gets to the bzImage deal and then reboots. I tried it on another machine to make sure it wasnāt just the computer but did the same on the other machine too. Just a heads up.
-
RE: IPXE - Could Not Start Download issue
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.
-
RE: IPXE - Could Not Start Download issue
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. -
RE: IPXE - Could Not Start Download issue
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.
-
RE: IPXE - Could Not Start Download issue
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]
-
RE: IPXE - Could Not Start Download issue
Alright sounds good. Iāll give that a try. Thank you for your help. Iāll let you know when Iām done.
-
RE: IPXE - Could Not Start Download issue
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
-
RE: IPXE - Could Not Start Download issue
I installed 1.2.0 today. I used the SVN command to get all of the latest and greatest stuff.
[url]https://svn.code.sf.net/p/freeghost/code/tags/1.2.0/[/url]That error that I mentioned above is coming from the client machine during boot up into PXE.
Unless I need to grab the tar.gz file from Sourceforge instead?
[url]http://sourceforge.net/projects/freeghost/files/[/url]Thanks!
-
IPXE - Could Not Start Download issue
Hello,
I have used Fog in the past with CentOS 6.5 and worked amazingly. Definitely saved me a ton of time. Well I was having issues with our network storage and nobody had answers. So my answer was to make a RAID 5 in a new Linux box!
Well now Iām upgraded to CentOS 7 and know there were some issues with the install. I got through that and seems everything is working well.
I set everything up on Fogās end and now Iām trying to upload an image of a machine to it. When in boot it gives me an error (Could not start download: Operation not supported ([url]http://ipxe.org/3c092003[/url]). Not sure what the deal is with that. I am on the latest Fog version also. Any ideas what might be causing this? Thanks! -
RE: Fog with NAS issues
Nvm, still canāt figure this thing out. About to just go buy parts and RAID 5 my linux machine itself. I know I can get the storage node to work locally. But I just canāt figure out this NAS deal.
Maybe itās because it NEEDS a username and password? Not sure how specific NFS is but I know it doesnāt ask for it there when I want to mount the nas. I can mount it just fine with CIFS. Infact when I mount it as a CIFS and add that as a node on fog it even gives me the available space pie chart and all. But all in all we need NFS for all of this to work client side.Hereās what I currently did:
-
On the Imation DataGuard T5R (IP: 192.168.2.201) I made a /Images share out there. This NAS is kind of goofy so it could full well be the NAS. The NAS isnāt on the Active Directory but the computers are. So even though I donāt have the NAS on the AD I still needed to add my username and pass to it as a user and it let me in. So thinking that way I added fog as a user also to see if that could rule it out.
-
My /etc/exports say:
[CODE]/fogimages *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure,fsid=1,)
/fogimages/dev *(rw,sync,no_wdelay,no_root_squash,insecure,fsid=2,)
[/CODE]
I also added the .mntcheck files in these folders. I never did āTouchā those files so that will be next on the list.
-
My NAS line in /etc/fstab looks like this:
[QUOTE]192.168.2.201:/Images /fogimages nfs defaults 0 0
[/QUOTE] -
When I was done with all of that I made sure I did the exportfs command and even restarted services.
-
When I try to mount again I still get this:
[CODE]mount -t nfs 192.168.2.201:/Images /fogimages
mount.nfs: access denied by server while mounting 192.168.2.201:/Images
[/CODE]
I have tried doing all of this in Fog itself too. [IMG]http://fogproject.org/forum/gyazo.com/8948a37556ff51c00f362e942e4c0538[/IMG]
I have tried different variations of the Image Path also. Some forums have mentioned that some NAS systems donāt grab the share correctly. So try to find a more direct path. So I tried /Nas1/Images <-- (Logical Drive/ImageFolder). Nadda. Next I logged into the NAS through SSH and found an even more absolute path. Tried that and still nothing. This is going to haunt me, haha. [IMG]http://gyazo.com/8cf806729d6dbcfcbe45edc7d23deaaa[/IMG]
I know I can get this working with Clonezilla but I really love the way Fog is laid out. Clonezilla I need to always go to the machine and follow the 15 steps and make sure I even have the correct paths. Fog, you just do it once and after that you click a button to start anything you want. Itās super nice.
So if anybody has some ideas that maybe I am missing or if Iām SOL with this NAS possibly let me know! Thank you. : )
-
-
RE: Fog with NAS issues
Nevermind. Apparently I was supposed to know that the option āUnix/Linuxā meant it was NFS in the NAS. Haha. Iāll research some more on how to get it working though. You can delete this thread if you wish.
-
RE: Fog with NAS issues
Sorry. I forgot to add in that I am running on CentOS 6.5 also.
-
Fog with NAS issues
I know this was brought up a few times even wtihin this forum but most never really had a clear cut way to make this work. I have the Imation DataGuard T5R that I was going to try and use with Fog. I noticed that this NAS doesnāt have NFS capabilities either. Am I pretty much S.O.L. without the NFS service on the NAS?
I was able to connect just fine mounting as CIFS. Fog even sees the folder and give sme a pie chart and everything but when starting the image upload it definitely wants NFS.
Iām sorta of noobie at Linux. I can get around pretty good but Iāll try whatever you have suggests for! Thank you
-
RE: Can not create deployment tasks
I ran into a lot of the problems. Since itās only an imaging server I literally opened up TCP/UPD 0:65535 ports and disabled Selinux. Everything works great now.
-
RE: Can not create deployment tasks
I have something very similar too. Mine is the other way around. The creation process completes on the client end but then displays [I][SIZE=16px][FONT=Ubuntu][COLOR=#ff0000]FOGFTP: Failed to connect. Host: xx.xx.xx.xx, Error: Undefined index: conn[/COLOR][/FONT][/SIZE][/I][I][SIZE=16px][COLOR=#000000]. [/COLOR][/SIZE][/I]I figured whatever answer you may get will fix my problem as well.