Posts made by astrouga

That is good news. I’m going to build a Kitchen-Sink 34 kernel as well. Hopefully I’ll get a chance this week.

Without knowing more, it is difficult to identify the problem. You can try the 3.4 kernel I built. It might work for you, if it is a driver issue. It solved some issues for me. Click on the “Download this file” button:

[url]http://www.filedropper.com/bzimage34[/url]

Also, others in the forum generally recommend updating your BIOS or checking the settings there. Have you done that?

Excellent. I just wanted to get some feedback since I had offered it up to a few others. Cheers.

falko:

Any luck with that kernel?

What OS are you trying to image/deploy? What is the image type?
Please verify that you have successfully pulled an image from one of these.

Also, can you clarify – It sounds like when you PXE boot your system, it just goes to a black screen, nothing happens. Is that right? Does it even attempt to PXE and if so, how far does it get in the process when it stops?

Can you get to the PXE boot menu in fog?

[quote=“krow, post: 3768, member: 1206”]thanx for your answer, I felt like no one can help me for a while :). actually I have the [SIZE=13px][FONT=Ubuntu][COLOR=#333333]Kernel - 3.3.3 Core, do you think that an older kernel can work ?? i’ll also try update the bios. many thanx [/COLOR][/FONT][/SIZE][/quote]

An older kernel might work. Also, I just compiled a 3.4 kernel. You could give it a try and let me know if it works or not. Click “Download this file” here:
[url]http://www.filedropper.com/bzimage34[/url]

Also, what is the manufacturer and model of your hard drive?

I have UEFI systems. I can take a look at this and see if I can duplicate it. However, can you tell me the make/model of your systems and the make/model of the disk drives you having this issue with?

This is kernel 3.4 with the addition of the latest NIC driver, though I think it just recompiled the driver itself. Still, it solved my issues. You should be able to use it for all of you machines. Test it out though and let us know. It would be great to know make/model with successes or failures.

You know how to specify a kernel for a host, right? If not, I am sure it is in the wiki or forum somewhere. Otherwise, ask and I’ll look.

I can see how one would go about doing this. It would be as easy as queueing up a couple of tasks in the WEBUI, if you are willing to figure out how to alter the pages to allow you to schedule a dban job. It isn’t that hard. Otherwise, you could manually queue them. You’d need to start a dban job on each client and then after it started, queue up a quick host registration job. This would be as simple as creating two files for each client.

I don’t have dban setup yet, but you’d need to create a file to start the dban process named after the mac address of the nic of the client you want to wipe. Put them in a folder like /var/tmp/local/dbanfiles. Then create a file for the systems to do the quickreg part. Save those in /var/tmp/local/quickreg. Copy the appropriate “dbanfiles” for the systems that you want to run dban on to /tftpboot/pxelinux.cfg. After those dban starts on those clients, copy your “quickreg” files for those systems over to /tftpboot/pxelinux.cfg. When the systems are done wiping and reboot, they will do a quickreg, assuming your machines are set to pxeboot first in the boot order.

Example, I have one machine with mac address 01-00-26-88-77-bb-aa:
My files would look like:
more /var/tmp/local/dbanfiles/01-00-26-88-77-bb-aa
[code]
DEFAULT fog
LABEL dbanwipe
KERNEL /fog/kernel/dban_image_filename
APPEND proper_dban_info_here
[/code]
(use your KERNEL and APPEND options…I don’t know what they are for dban)
If you reboot that client and PXE boot it, it will auto wipe.
more /var/tmp/local/quickreg/01-00-26-88-77-bb-aa
[code]
DEFAULT fog
LABEL quickreg
KERNEL fog/kernel/bzImage
APPEND initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp d
ns= mode=autoreg web=XXX.XXX.XXX.XXX/fog/ loglevel=4
[/code]
To start things off for my client, I copy my dban file:
[code]
sudo cp /var/tmp/local/dbanfiles/01-00-26-88-77-bb-aa /tftpboot/pxelinux.cfg/01-00-26-88-77-bb-aa
[/code]
After dban starts, I copy the other file:
[code]
sudo cp /var/tmp/local/quickreg/01-00-26-88-77-bb-aa /tftpboot/pxelinux.cfg/01-00-26-88-77-bb-aa
[/code]

[LEFT][COLOR=#555555][SIZE=2][FONT=Tahoma][COLOR=#141414]You could probably write a script to create these files easily by pulling the mac addresses for your clients from the MYSQL db. I’d look into it, but that would take more time than I have right now. I’ll add it to my todo list, but please don’t wait for it. :)[/COLOR][/FONT][/SIZE][/COLOR][/LEFT]

I’d search the forums for your particular problem(s). If don’t find anything, just post the particular issue here and someone will likely help. If it looks like a bug, or something you think the developers can help with, I’d post it in the bug section of the forum:

[url]http://fogproject.org/forum/forums/bug-reports.17/[/url]

I have a bunch of these ST250LT007 Seagate drives (the same Momentus line of drives, but with no encyption) and they work just fine. However, 4K advanced format drives are not supported in FOG yet. You’d have to use FOG .33 (beta still) to image those drives. That is what I am using now and it is working. The beta is not “feature complete” yet, but 4K drive imaging works.

I’d recommend downloading the beta release to a spare system and doing a few image tests. You could report your success/failures to this forum post:

[url]http://fogproject.org/forum/threads/bugs-in-fog-0-33.631/page-4#post-3691[/url]

If you need help getting the latest beta release down, just let me know.

A lot of people have had trouble with the single partition resizable option and windows 7. Honestly, I’ve never gotten it to work. I’ve been testing the .33 beta code and it didn’t work for me there either. The developers are looking into it though.

You can use the link above. I didn’t have a better way to upload the file. You want to click on the download link that says “Download this file”.

Regarding your questions, the clients all use a 32-bit init.gz prodived by FOG. It doesn’t matter what your OS/arch is. I built the bzImage file on a 64-bit Ubuntu 12.04 system using the FOG .33 beta core.config file. I had to specify a 32-bit kernel for output because I was building on a 64-bit system. Hope I said all the correctly.

Just give it a try. The worst case is you are out 10 minutes of real time – the time it takes to download, assign the kernel to your client,and start the upload/download. Plus, if it doesn’t work I’ll try to build you one that does. Just be sure to let us know if it solved your issue for you or not.

I’ve not tried doing anything with FOG and virtual machines. I suspect you are right that it has to do with the VM setup. Have you tried using a different image setting? What happens when do “multiple partition image - single disk (not resizeable)”?

Also, there is a small doc on fog and VM here:

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

Keep us updated if you get it working.

Have you tried setting the image type to “multiple partition image - single disk (not resizeable)”? This usually works for everything.

See if you get this. I’ve never used filedropper, but it didn’t require an account.

[url]http://www.filedropper.com/bzimage34[/url]

Yes, my image uploads/downloads would get to about 50% and then start to slow to a crawl. Now imaging speed is steady. What is the upload file size limit? I just tried to add a file, but get an unspecified error.

Mostly, this worked for me. However, I missed the note at the bottom, which was critical.
[url]http://www.fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel[/url]
I’m reinstalling FOG today and rebuilding the 3.4 kernel. I’ll take notes and post.

Eric High:

Are you interested in trying the 3.4 kernel I built last week? Let me know if this link works or not:
[url]http://www.filedropper.com/bzimage34[/url]

Falko:

I built one last week. I used the FOG .33 core.config file. If you want it still, I’ll upload it and you can give it a try. I built it to try to resolve some speed issues with the network card in my Optiplex 990s.

Let me know.

Have you tried using a different kernel for those? I think you can still see kernel options via FOG. Try: WebUI > Other Information > Kernel Updates >Published Kernels

Also, a long shot, but people often report machines work after they update the BIOS.