Posts made by Junkhacker

none of those if you’re using fog 1.0+
[url]http://fogproject.org/forum/threads/fog-0-33b-edit-pxe-menu.10403/#post-26420[/url]
there is a memdisk file located in <fog-web-root>/service/ipxe/memdisk

Blatantly copied from Tom’s signature:

Basics: Please provide:
FOG Version (e.g. FOG 0.32, FOG 0.33, FOG 0.01, 1.0.0, 1.0.1, SVN build)
OS Version (e.g. CentOS 6.5, Ubuntu 12.04, Redhat 6.5)

Have you checked your apache error logs? Can you provide information from these logs?
Debian based Location (normally)
/var/log/apache2/error.log
Redhat based Location (normally)
/var/log/httpd/error_log

Have you searched the forums for your issue yet?
Have you checked the wiki yet?
Kernel Issues: [url]http://fogproject.org/wiki/index.php/FAQ[/url]

is the image type set to partimage or partclone?
if it is an image from prior to 1.0 it should be set to partimage, 1.0+ uses partclone

i meant the options in the Image Management page

what operating system and image type are you using in your image?

you said this worked before on 0.32
do you mean this computer specifically? have you tried other computers?

sorry to come down on you, it’s just hard enough to keep up without double postings.

well, it kind of was, but the proper etiquette would be to either ask for the thread to be moved, or to post in your thread about how you have moved the conversation to a new thread.

well, a google search for your error leads to info about kernel driver errors. so it may be your kernel

no, those errors you’re getting are after ipxe has done it’s job.

it looks like your network is not configured correctly. also, you might try updating your kernel

i’m not familiar with webmin. but if it can make a full database backup, i don’t see why it wouldn’t work. you may also want to backup the files in the root of your web folder, just in case.

the svn trunk is the repository of pre-release code. it is the “bleeding-edge” of the software, and is not considered final release quality, generally. however, it does contain bug-fixes, updates, and features not included in the official releases. in general, it is not recommended to use the developmental versions in production environments. however, your system isn’t working right now anyway.
updating to the svn trunk version may fix your problem, i can’t be certain. It is also vital that you backup your server’s data before you update, as the code is not officially supported, and may contain bad bugs we haven’t found yet.
[url]http://www.fogproject.org/wiki/index.php/SVN[/url]

those apache errors all look like report page errors, and are unrelated to the boot problem you are having.
reports are not functioning properly, mostly due to files inadvertently left in from previous versions of the reports. tom has that mostly fixed already and will be working properly in the next official release.

[url]http://www.fogproject.org/wiki/index.php/SVN[/url]

i’m still trying to look into what could be causing the problem. maybe make a backup of your server and try the latest svn trunk. i suspect that something has an invalid value in your mysql database, with regard to either hosts or tasks, but i can’t be certain.

check that your passwords are all set and correct
the password in the webgui must match the password set for the linux user “fog”
check both the [FONT=arial][COLOR=#262626]FOG_TFTP_FTP_PASSWORD in Fog Configuration -> fog settings, and t[/COLOR][/FONT][FONT=arial][COLOR=#262626]he Storage Management -> NODE -> fog password.[/COLOR][/FONT]

all new images uploaded are partclone. partimage is download only, and is included for legacy reasons.

is there a reason you created a new thread instead of continuing the other one you started with the same statement?
[url]http://fogproject.org/forum/threads/host-wont-boot-in-pxe.10582/[/url]

i agree that being able to specify groups during registration would be useful. for example, last week i had student workers registering 3 labs of computers in fog that should all be grouped differently, and they would have been able to add them to the appropriate groups instead of having to sort them out later. though, i would put it in as part of “full” registration instead of quick.