Change the kernel back to just plain jane bzImage.64.

As you’re not deploying to the point where it even downloads that, my suspicion is in the boot parameters.

To test this is going to be difficult and I may just request a remote session if at all possible where I can connect and tweak a few file on your fog server.

Hello Elliott!

thanks for the reply, after many attempts I decided to install it again to a new virtual machine with 'ubuntu 14:04 LTS.

I installed the new version fog '1.2.0 and reconfigured with the footsteps of my previous posts.

I’ve tested and everything works perfectly including the / mnt / imagensfog the virtual disk that is where I have the images of the OS.

I exported the ‘cvs the old machine with 143’ hosts made ​​the link to the images of the OS already had, and everything works OK now.

from the old machine do not know where the problem lay not know if it would be for version 12 ‘ubuntu even if it was for doing the installation over some old version of’ DB fog or even problems in version 'fog 1.1 .2.

what I am sure is that FTP works in the old machine. because I can access the fog machine via FTP (Fillezila) client with user credentials’ fog
created when you install the 'ubuntu. I can edit, create pictures from the / mnt / imagensfog and / mnt / imagensfog / dev

How it works now I think we can now close the POST, the posts that I put the changes that are needed to mount another hard work.

Thank you for everything

\ GF

Thanks all I was on the right path but now i’ve got it working just right thanks for the help!
Incase it helps anyone else here is the FirstLogin Commands i use to auto activate windows 7 OS and Microsoft office 2010 using sysprep

[CODE] <FirstLogonCommands>
<SynchronousCommand wcm:action=“add”>
<CommandLine>cscript /b c:\windows\system32\slmgr.vbs /ato</CommandLine>
<Order>1</Order>
<RequiresUserInput>false</RequiresUserInput>
<Description>Act OS</Description>
</SynchronousCommand>
<SynchronousCommand wcm:action=“add”>
<Order>2</Order>
<CommandLine>cscript “C:\Program Files (x86)\Microsoft Office\Office14\ospp.vbs” /act</CommandLine>
<RequiresUserInput>false</RequiresUserInput>
<Description>Act Offfice</Description>
</SynchronousCommand>
<SynchronousCommand wcm:action=“add”>
<CommandLine>sc config “FOG Service” start= auto</CommandLine>
<Order>4</Order>
<Description>Change FOG service from delay to Automatic</Description>
</SynchronousCommand>
<SynchronousCommand wcm:action=“add”>
<CommandLine>timeout 20</CommandLine>
<Description>Pause for 20 seconds</Description>
<Order>3</Order>
</SynchronousCommand>
<SynchronousCommand wcm:action=“add”>
<Order>5</Order>
<Description>Enable the fog service</Description>
<CommandLine>net start “FOG Service”</CommandLine>
</SynchronousCommand>
</FirstLogonCommands>[/CODE]

thank you very much!!!

For the future, you may want to edit the .fogsettings file so that this doesn’t happen down the road as well.

Try this
You know what username you used?

Do you know what type you entered it as?

FOG Uses MD5 encryption to the passwords to set the password. This way there’s kind of a level of security making cracking your passwords that much more difficult.

Try this:
[code]mysql -u root [ -p #only if you have a password for your database ] fog
select * from users WHERE uName=‘<YOURUSERNAMEHERE>’;
update users set uType=‘0’ where uName=‘<YOURUSERNAMEHERE>’;
update users set uPass=MD5(‘<YOURNEWPASSWORDHERE>’) WHERE uName=‘<YOURUSERNAMEHERE>’:[/code]

Hopefully everything will work properly and you’ll be able to sign into your FOG system.

if you can boot the system with a live cd you may be able to gain access to the /var/lib/mysql folder. While this isn’t the best means to backup your database systems, it will work to at least get your hosts and image definitions back. If you can copy the entire contents of this folder you’ll be much better off.

Your Active Directory password needs to be encrypted through the FOG Crypt download from the client page. This, most likely, is the issue you’re seeing where it can’t join to domain.

The 10.10.1.50 fog user and password need to work as well to be able to see the size information. This node also needs to have the Config.class.php file updated to point at your main fog server’s IP/Database and fogstorage username and password to connect and read its information.

The FTP to the 10.10.1.50 is likely incorrect at the moment which would be why you’re not getting any information on the images page.

I can’t make a video, I had downgrade to 0.32 because I use FOG just for Dell OptiPlex GX520 at this time…

I think it’s “undionly.kpxe” is bad for this models 😞

Thanks for ypur help.

What was the actual root cause of this problem? I’ve just run into it after upgrading a 0.32 system to 1.1.2. The system is in production so I’d rather not upgrade to SVN unless it is absolutely necessary.

[COLOR=#ff0000]EDIT - FIXED (kindof)[/COLOR]
[COLOR=#000000]In my case this turned out to be one of my “antique” images which was referring to an imageNFSGroupID which no longer exists. Correcting that problem fixed the white screen issue for me. [/COLOR]

[COLOR=#000000]N.B. I’m including the SQL (below) which fixed my problem, but I’m doing this mostly as a reminder to myself. Use it at your own risk!!![/COLOR]

[CODE]
$ mysql -u root -p
Enter password: *************
mysql> use fog;
mysql> SELECT ngID,ngName FROm nfsGroups;
±-----±--------+
| ngID | ngName |
±-----±--------+
| 1 | default |
±-----±--------+

mysql> SELECT ngmID,ngmGroupID FROM nfsGroupMembers;
±------±-----------+
| ngmID | ngmGroupID |
±------±-----------+
| 1 | 1 |
±------±-----------+

mysql> SELECT imageID, imageName, imageNFSGroupID FROM images WHERE imageNFSGroupID!=1;
±--------±-----------------------------------------±----------------+
| 47 | RHL6x64PIMS50GBTest | 3|
±--------±-----------------------------------------±----------------+

mysql> UPDATE images SET imageNFSGroupID=1 WHERE imageID=47;
[/CODE]

Thank you for the replies.

Thanks for the explanation Lee. Sounds like the Location plugin along with the TFTP from Node option is what we want. I hope to put this into production later today.

Thanks again!

-MRCUR

Dear Tom,

here the print of the fog ipxe Directory. This is a Print of my main fog. This is what i did before:

renamed the folowing in the FoG configuration => it worked
FOG_TFTP_PXE_KERNEL => bzImage32
FOG_PXE_BOOT_IMAGE => init_32.xz renamed it back to bzImage and init.xz => dont worked renamed bzImage to bzImage.old and init.xz to init.old.xz cp bzImage32 bzImage (same with the init_32.xz) deleted the .old files
=> Worked again

if i install a new kernel FoG names it “bzImage” automaticly no matter which one it is 32- or 64-bit.
But if install the 64-bit Kernel it dont work.

Greetings

Andy

[url=“/_imported_xf_attachments/1/1178_FoG ipxe.png?:”]FoG ipxe.png[/url]

Hi,

found it 😉 will fix it and send you the new file

[IMG]http://i.imgur.com/lpiKB7s.png[/IMG]

Regards X23

I figured it out. We had inf files on our server that we used to install printers via batch files. I tried to use those same inf. For some reason they did not work. I reinstalled the exe that installed the inf files on the local machine. Pointing fog to these clean installs of INF files worked.

Gentlemen we have lift OFFFFFFFFFF.
I have finally booted to my fog server successfully. In the end it was the line: dhcp-range=10.0.0.10,proxy which I had to change to the ip address of my server.

Soooooo to help others
here is a quick breakdown of my set up and by no means perfect but hey it works
Ububtu 1204 LTS
Fog 1.1.0
Cisco WAG120N switch with DHCP enabled to provide IP address in the same subnet as your server(just in case)
DNSMASQ installed and configured as per link (DNSMASQ doesn’t provided DHCP it inform the client’s computer where to find the fog server)
[url]http://fogproject.org/wiki/index.ph...with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]

I had to change the following in the /etc/dnsmasq/ltsp.conf
dhcp-boot=undionly.kpxe,fog,IP.Add.of.yurserver
and
dhcp-range=IP.ADD.OF.yurserver,proxy

Thanks to LifeHacker, Jaymes and Tom Elliott

Do you see the iPXE setup screen appear? It should, since you were able to deploy an image earlier, but can you confirm that you see it saying something like (N.B. This is for a system without a task scheduled)
[CODE]
net0: 52:54:00:27:7a:dd using virtio-net on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 52:54:00:27:7a:dd)… ok
net0: 192.168.222.102/255.255.255.0 gw 192.168.222.1
Next server: 192.168.222.100
Filename: undionly.kpxe
tftp://192.168.222.100/undionly.kpxe… ok
PXE->EB: !PXE at 9C3B:06D0, entry point at 9C3B:030C
UNDI code segment 9C3B:076C, data segment 9CB2:2CD8 (624-638kB)
UNDI device is PCI 00:03.0, type DIX+802.3
624kB free base memory after PXE unload
iPXE initialising devices…ok

iPXE 1.0.0+ (8a380) – Open Source Network Boot Firmware – http://ipxe.org
Menures: NFS FTP HTTP HTTPS iSCSI DNS TFTP VLAN AoE bzImage ELF MBOOT PXE PXEXT
Configuring (net0 52:54:00:27:7a:dd)… ok
/default.ipxe… ok
http://192.168.222.100/fog/service/ipxe/boot.php… ok

http://192.168.222.100/fog/service/ipxe/bg.png… ok
[/CODE]
Depending on how much or little of this you see we might be able to narrow down where the problem is.