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.

That was it! .mntcheck was missing from /images/dev. Thank you!

[quote=“cr31, post: 33511, member: 25150”]Was this a New HDD?
I came accross this when we purchased a pallet full of refurbished machines, and got the same message…because the HD wasn’t initialised.
I removed the drive, put it into an external caddy, used disk management to initialise the disk, put disk back into PC, re-tried with Fog, and it worked!
Alternatively you can use Diskpart or similar

i may be off the mark here, but just check[/quote]

it is definitely initialized - it’s currently got XP on it. Also, it imaged fine with the 0.32 fog server when I spun it back up. The issue is somewhere in the update, unfortunately 😕

I ran [FONT=Consolas]sudo service tftpd-hpa restart. Worked like a charm. Thanks a bunch everyone. That one sure had me going. [/FONT]

Just what I thought. Thank you and the rest of the forum staff for your awesome support!

Thanks for the information. I’ll check the settings in the BIOS and then test.

Okay, I’ll give that a try as a final attempt of using fog. I have a server ready to go with Server 2008r2 on it to get WDS setup since I’ve had nothing but problems with FOG/Linux since the day I started using it. All of everyone’s help is deeply appreciated.

Ok I was able to delete them when I use Google Chrome but not IE! I still have the issue that some status are Queued and some say N/A!