Latest Development FOG
-
gone will be the days of temps/trainees uploading images when they should be downloading images…
… that was a nice day to come in to… “what’s happened to all the images???” -
[quote=“Timelord83, post: 30968, member: 10119”] for some reason its not expanding properly after the image. if you go into my computer it shows a 23.86 GB hard drive that is almost full but if i don into computer management / disk management it shows that
is a 295 GB partition… i am completely lost and i’ve already imaged 50 machines and am a day behind, how can i fix this issue without re-imaging?[/quote]This may be a little late but if you prefer a method that doesn’t involve manually extending partitions on each computer I recommend using a script and running diskpart with the /s switch to call a text file containing the following:
select disk 0
select partition ([I]Partitionnumber)[/I]
extendJust replace [I]partitionnumber[/I] with the correct number and run this on each and you should be all set.
-
SVN 1973 released.
With this comes functional postdownloadscripts within /images directory.
What this file does:
Just for documentative purposes.
It is a sh script with means it must start with:
[code]#!/bin/sh[/code]You place all the scripts you need to run after imaging is complete.
The way you call these scripts is by “sourcing” to them so they run in the current shell. So if you installed in earlier revisions the documentation may be out of date.
The Calls to the file would work in:
[code]. ${postdownpath}scriptname[/code]Notice the period and space before the ${postdownpath} is called.
${postdownpath} is the literal name, don’t replace with your path unless you know exactly what you’re doing.
If you have folders within the ${postdownpath} (which is set to /images/postdownloadscripts) you simply start the scriptname with the folder and forward slashes as needed. For example:
. ${postdownpath}mycustomfolder/mycustomscriptnameThat should do it.
-
SVN 1991 released.
Many more changes. Namely for Image and ImageManagementPage.
Installer fixes where if you’re on a server but use a different sql server, you can store the server IP in the .fogsettings file under snmysqlhost as is done with nodes.
Upgrades from SVN will no longer request if you’ve set the password at install as it should be stored in the .fogsettings file as well. As it now works properly, you don’t need to verify every single time, just on the initial install. It will still ask you to check for schema update.
Image ON SERVER is now received by FTP. So if the image exists and you know it does, it will not fail out of the page or report ls errors in the error log. It will just not display the proper size. This can also serve as a means to let you know if the username and password are correct for the ftp side of things. I’ve also fixed it so it will display the page even if the node is not correct or not within a group.
-
SVN 1993 fixes the broken hwinfo information.
SVN 1992 just hopes for better session handling.
-
1999 released.
Adds the hfsp parameter to the init. So if you format a disk in hfsp it can now image this. I don’t know if it will actually work, but it’s there just in case.
Fixes FOG Client page if you’re not logged in.
-
SVN 2021 released.
With this comes more additions to hopeful resizing of linux partitions. I’ve not fixed the partition table’s yet, but the resizable parts themselves are resized and properly set. They’re also restored and expanded properly. Again this is only on resizable partitions (ext[234]). The extended location is still at it’s original location, so for that I’m sorry. It’s still, very much, a work in progress.
-
Have you had any reports of looping boots after tasks? I’ve seen this a couple of times on new PCs we’ve switched to our new fog server today.
I will try to update to the latest and try again but got a ton of other things to do since it’s nearly the end of the school year.
-
[quote=“VincentJ, post: 32482, member: 8935”]Have you had any reports of looping boots after tasks? I’ve seen this a couple of times on new PCs we’ve switched to our new fog server today.
I will try to update to the latest and try again but got a ton of other things to do since it’s nearly the end of the school year.[/quote]
Going on a limb here, you’re testing via VM or physical systems?
-
I have seen it on virtualbox VMs, but today it was on new i5 systems. Same model system works perfectly on other PCs but some seem to boot loop.
I wasn’t doing the new PC installs, but the guy who was wouldn’t know how to muck things up too much so for the moment we’ve switched back while I troubleshoot.
-
SVN 2033 released.
This is a huge change in Linux/Windows Resizable Imaging techniques all thanks to Fractal13 of the forums. If you can give him many likes as I couldn’t have done what has now been accomplished.
First I’d like to note (and feel free to add if needed fractal), UUID’s of the swap partition are now stored and reset properly with this. Resizable imaging works in the truest form that it “resizes” all partitions including extended partitions. Uploads no longer store the swap partition on linux disks either, just the UUID is stored. This should help minimize the Code needed. There are some fixed size partitions, but that shouldn’t be a worry as I highly doubt anyone’s still got 8 GB hard drives in any of their systems anymore.
Second I’m in the process of testing the Windows Only systems. However Fractal has tested this with Multiboot systems as well. So Multiboot systems are also able to be resized as well. These have not been tested or even known to work with GPT disks. So please be cognizant of that as GPT Resizable Multiboot or plain-jane Linux systems is probably not going to work.
-
Woo hoo! Good News Everyone! (Professor Farnsworth flash backs)
-
[ATTACH=full]1131[/ATTACH]
Figured I would put up the real thing. lol
[url=“/_imported_xf_attachments/1/1131_vhyfxm.jpg?:”]vhyfxm.jpg[/url]
-
Hello, So after my earlier ugh… which i managed to google the issue to before the reply but i do appreciate it. I have a new issue… I run ubuntu 13.10 in a VM on Fusion 6.0.X and i have an issue where at random while doing a full registration it will say its unable to register blah blah… no error given just says it can’t and flys through spitting out all the system data and restarts. Normally i just run it again. but today a system did it… and hung up on end where is says sending to host… and just scrolled black for over 15 minutes before i force restarted it. well it turns out it started to make a host on the fog server but now I cannot remove the host it gives me this error when i try to delete it.
[FONT=Ubuntu][COLOR=#555555]FOG DEBUG: Host: Database Load Failed: ID: 0, Error: Operation field not set: ID[/COLOR][/FONT]
[FONT=Ubuntu][COLOR=#555555]any ideas? i need the host removed so i can re-add it… i tried to manually edit at least the mac in but its not working at all. and its just the one host thats having issues i can edit any of the other 150+ hosts without issue.[/COLOR][/FONT]
-
is there a reason you’re not upgrading to a newer version? because that bug sounds familiar, and if it’s what i think it is, was fixed a long time ago. at this point you’ll have to edit the database to fix the problem though.
-
[quote=“Junkhacker, post: 32684, member: 21583”]is there a reason you’re not upgrading to a newer version? because that bug sounds familiar, and if it’s what i think it is, was fixed a long time ago. at this point you’ll have to edit the database to fix the problem though.[/quote]
I guess I am a little lost… I am running a brand new install of fog on a 13.10 ubuntu install… I was under the impression that 13.10 was still the way to go…
-
a newer version of fog
you mentioned you “have an older version of fog” in a prior post and you were running 0.33b
fog 1.1.2 is out now -
[quote=“Junkhacker, post: 32701, member: 21583”]a newer version of fog
you mentioned you “have an older version of fog” in a prior post and you were running 0.33b
fog 1.1.2 is out now[/quote] Ahh no, since I work in VM’s i built a new fog server on sunday. Not sure to tell what revision i am running though… how can i check? either way its up to date as of sunday around 10pm EST -
when logged into the fog webgui, the version number is listed at the top of the page, in the fog “cloud”
-
It looks something like this…
[ATTACH=full]1155[/ATTACH][url=“/_imported_xf_attachments/1/1155_fog_cloud.png?:”]fog_cloud.png[/url]
