Posts made by fmslick

@george1421 Yes I have it working, now I am working on moving the files off my fog server and on to a file server. I like to do things the hard way anyhow you make a point on the type-o lol.
Thank you

@george1421 said in Booting ISO issue / Mount /dev/cdrom:

I’m looking at this as a puzzle, so I’m only speculating on how this could be done.

1. On the fog server create the following file path /images/iso/dell1950
2. Extract the contents of the cdrom to the fog server file path you just created in step 1
3. Copy the following files from /images/iso/dell1950/isolinux to /var/www/html/fog/service/ipxe
4. This last part is to create a fog iPXE menu to boot this kernel.

Menu Item: iso.dell1950
Description: Dell 1950 something cdrom
Parameters:
kernel SA.1 initrd=SA.2 ramdisk_size=400000 Stage3_type=cdrom DEBUG=0 quiet BUILD=955 vmalloc=256M share_type=nfs share_location=<fog_server_ip>:/images/iso/dell1950e share_script=drm_files/apply_bundles.sh share_opts=nolock selinux=0
imgfetch SA.2
boot || goto MENU

Menu Show with: Registered Hosts

Well that is a start, it will boot and start to run but skips over starting the drm_files/apply_bundles.sh

EDIT:
I found the issue, there was a type’o of “delle” in your line " share_location=<fog_server_ip>:/images/iso/dell1950e " … I fixed the type’o and now I have Permission denied but got that fixed… thanks for the help m8

@Wayne-Workman Think

@Wayne-Workman All the servers I am testing with are Dell 1950 III , do you have a link to where I can read up on? (if you don’t mind and think you)

@Wayne-Workman 50 is the test, I plan on making this work with other servers and + this is a good way for me to get my hands on a few thing I don’t know and up my skills

Thinks guys and yeah I know in a way it would be some what “easier” to just run off of a CD but I have about 50 some odd servers I need to run this ISO on and just burning CD’s will not work.

@Wayne-Workman said in Booting ISO issue / Mount /dev/cdrom:

You’re most likely going to need to do this differently. Look through this article - there are several examples: https://wiki.fogproject.org/wiki/index.php?title=Include_any_ISO_in_the_FOG_Bootmenu

As I was doing some googling I did find this and was going to give it a try!

@george1421 said in Booting ISO issue / Mount /dev/cdrom:

I agree with Wayne.

What is going on is the iso image kernel has it hard coded to connect to the physical cdrom (which doesn’t exist because the kernel was pxe booted). You will need to unpack the iso image and then look for the syslinux config files.

I’m in the process of downloading the liniso.iso for the 1950 to see what the iso image looks unpacked.

Yep I see that now and Here is a link to the ISO I have , I hop it will help?!

@george1421 said in Booting ISO issue / Mount /dev/cdrom:

Your task may be somewhat difficult with this image. It may be easier to just boot from cdrom and forget about pxe booting this iso image.

But if you want to keep working on it. There is a folder on that iso image called isolinux. In there is the syslinux.cfg file. That will give you different options to boot this iso image. You will need the SA.1 (kernel) and SA.2 (initrd) from that directory and place them in the /var/www/html/fog/service/ipxe directory on the fog server.

The next bits you will need to work out for the fog menu to send the right commands to the kernel to boot. We can get you started on that, but the heavy lifting will be up to you.

Below is an excerpt from that syslinux.cfg file that looks promising. Booting the kernel and inits are only part of the issue, you also need access to the other files and scripts on that cdrom. It appears you can extract that iso to a NFS share and provide the kernel with a path to the nfs share.

 Modify this if dtk files are on a nfs share.
# the mount command will become...
# mount -t $share_type -o $share_opts $share_location /opt/dell/toolkit/systems/
label network-nfs
	kernel SA.1
	append initrd=SA.2 ramdisk_size=##RAMDISK_SIZE##  Stage3_type=cdrom DEBUG=0 quiet BUILD=955 vmalloc=256M share_type=nfs share_location=<ip address>:/path/to/share share_script=<name/relative path to script to execute> share_opts=nolock selinux=0

As well here is syslinux.cfg

default 1
prompt 1
timeout 100
display message.txt

label 1
	kernel SA.1
	append initrd=SA.2 root=/dev/ram0 rw DEBUG=0 share_type=cdrom loglevel=1 BUILD=955 init=/init selinux=0 edd=off share_script=drm_files/apply_bundles.sh

label 2 
        kernel SA.1
        append initrd=SA.2 root=/dev/ram0 rw DEBUG=9 share_type=cdrom loglevel=1 BUILD=955 force_mediacheck=1 init=/init selinux=0 edd=off

# Modify this if dtk files are on a nfs share.
# the mount command will become...
# mount -t $share_type -o $share_opts $share_location /opt/dell/toolkit/systems/
label network-nfs
	kernel SA.1
	append initrd=SA.2 ramdisk_size=##RAMDISK_SIZE##  Stage3_type=cdrom DEBUG=0 quiet BUILD=955 vmalloc=256M share_type=nfs share_location=<ip address>:/path/to/share share_script=<name/relative path to script to execute> share_opts=nolock selinux=0

label debug
	kernel SA.1
	append initrd=SA.2 ramdisk_size=##RAMDISK_SIZE##  Stage3_type=cdrom BUILD=955 vmalloc=256M DEBUG=9 share_type=cdrom selinux=0

# Modify this if dtk files are on a smbfs share.
# the mount command will be.....
# mount -t $share_type -o $share_opts //$share_location /opt/dell/toolkit/systems/
label network-smbfs
	kernel SA.1
	append initrd=SA.2 ramdisk_size=##RAMDISK_SIZE##  Stage3_type=cdrom BUILD=955 vmalloc=256M DEBUG=9 share_type=smbfs share_location=//<ip address>/sharename share_script=<name/relative path to script to execute> share_opts=<share options eg username, password, or domain> selinux=0

label network-tftp
	kernel SA.1
	append initrd=SA.2 ramdisk_size=##RAMDISK_SIZE##  Stage3_type=cdrom BUILD=955 vmalloc=256M DEBUG=9 share_type=tftp share_location=<share dir> share_script=<name/relative path to script to execute> tftp_ip=<ip address of tftp server> selinux=0


#label mediacheck
#	kernel SA.1
#	append initrd=SA.2 ramdisk_size=##RAMDISK_SIZE##  Stage3_type=cdrom BUILD=955 DEBUG=0 quiet dsa_force_mediacheck=1

# Modify this if dtk files are on modified dtk CD.
# the mount command will be....
# mount /dev/cdroms/cdrom0 /opt/dell/toolkit/systems/
label cdrom
	kernel SA.1
	append initrd=SA.2 ramdisk_size=##RAMDISK_SIZE##  Stage3_type=cdrom BUILD=955 vmalloc=256M DEBUG=0 mem=15G quiet share_type=cdrom share_script=<name/relative path to script to execute> selinux=0

label 3
    localboot 0x80


# This file could be modified to suite your network configuration.
# The variables share_type, share_location and share_script are available
# an environment variables in the root shell. These variables are used
# to mount the share containing all the dtk components.

# Choose and modify network-nfs if you have a network share where you have
# dtk files.

# Choose and modify network-smbfs if you have a network share where you have
# dtk files. Pleaes note  the syntax differenc b/w nfs and smbfs for
# the share_location.

# Choose and modify cdrom if you have the dtk files on the cdrom itself

# After modifying the required section please set the default(the first
# line in this file)to this section.

Think you for the info and I hope with your help we can get this working in a few days or sooner, I will be looking in on this post everyday and report back what I have done and how far I have got.

Hey guys, (Tom & Junkhacker)

So I am having an issue finding some info, I have my .iso added to the menu and it will pull/push the .iso into RAM but after the iso starts running I get a “Mount /dev/cdrom” error. Would anyone link me info on how to fix this or a work around / whatever you wanna call it lol, or what am I doing wrong/missing and/or how you would go about fixing this.

.iso added to the main menu as fog.ddu (Dell Update Utility)

initrd http://${fog-ip}/iso/dell-1950_update-utility.ISO
chain memdisk iso raw

Error I am getting

Thanks

Thanks! Tom

@Sebastian-Roth said:

Why is this posted under ‘FOG Problems’? If I get what you mean I reckon this is a feature request, right? Otherwise you need to explain what you are really up to.

My bad. I just got back on the new forums and did’t see there is a new place for “feature request”, If you feel the need to move it than do so! Thanks

---

@george1421 said:

With the new pxeMenu table in the trunk version of FOG (i.e. pre1.3.0) one could write a perl/python/php/bash script to pump this directory ISO information directly into that table with some careful scripting. This is totally possible. Then just automate the process with a cron task

hmmmm, sounds a bit EZ but I suck at code lol

Hey guys long time no see lol

I was wanting to know if there is a way to get the boot menu to auto fill a list of .iso file’s from a folder?

Advanced Menu – ISO – auto list

&& I think this would be hell to work out in code in the menu (at less I think?)

Side note:
Hey Tom & Junk hacker how have you guys been?

[B]/var/log/httpd/error_log (for centos/redhat as this is your OS)[/B]
[QUOTE]
[Sat Mar 14 15:24:57 2015] [
error] [client 192.168.1.10] Directory index forbidden by Options directive: /var/www/html/

[Sat Mar 14 15:24:57 2015] [error] [client 192.168.1.10] File does not exist: /var/www/html/favicon.ico
[Sat Mar 14 17:13:58 2015] [error] [client 192.168.1.226] PHP Warning: Unknown: open(/var/lib/php/session/sess_6cusenfpb1njs94ltebbv5c3c3, O_RDWR) failed: No space left on device (28) in Unknown on line 0
[Sat Mar 14 17:13:58 2015] [error] [client 192.168.1.226] PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php/session) in Unknown on line 0
[Sat Mar 14 17:14:14 2015] [error] [client 192.168.1.226] PHP Warning: Unknown: open(/var/lib/php/session/sess_j0njdq3916hi8hl1onl3khetk2, O_RDWR) failed: No space left on device (28) in Unknown on line 0
[Sat Mar 14 17:14:14 2015] [error] [client 192.168.1.226] PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php/session) in Unknown on line 0
[Sat Mar 14 17:14:30 2015] [error] [client 192.168.1.226] PHP Warning: Unknown: open(/var/lib/php/session/sess_ahbnsdfcu9co8me4pl0l63ib57, O_RDWR) failed: No space left on device (28) in Unknown on line 0
[Sat Mar 14 17:14:30 2015] [error] [client 192.168.1.226] PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php/session) in Unknown on line 0
[Sat Mar 14 17:33:31 2015] [error] [client 192.168.1.10] Directory index forbidden by Options directive: /var/www/html/
[Sat Mar 14 17:33:32 2015] [error] [client 192.168.1.10] File does not exist: /var/www/html/favicon.ico
[Sat Mar 14 17:33:39 2015] [error] [client 192.168.1.10] PHP Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0, referer: [url]http://192.168.1.202/fog/management/index.php[/url]
[Sat Mar 14 17:33:39 2015] [error] [client 192.168.1.10] PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php/session) in Unknown on line 0, referer: [url]http://192.168.1.202/fog/management/index.php[/url]
[Sat Mar 14 17:33:45 2015] [error] [client 192.168.1.10] PHP Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0, referer: [url]http://192.168.1.202/fog/management/index.php[/url]
[Sat Mar 14 17:33:45 2015] [error] [client 192.168.1.10] PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php/session) in Unknown on line 0, referer: [url]http://192.168.1.202/fog/management/index.php[/url]

[U][Sat Mar 14 17:33:47 2015] [error] [client 192.168.1.10] PHP Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0, referer: [url]http://192.168.1.202/fog/management/index.php[/url][/U]

[Sat Mar 14 17:33:47 2015] [error] [client 192.168.1.10] PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/php/session) in Unknown on line 0, referer: [url]http://192.168.1.202/fog/management/index.php[/url]
[[Sat Mar 14 18:09:42 2015] [notice] caught SIGTERM, shutting down
[Sat Mar 14 18:12:13 2015] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Mar 14 18:12:13 2015] [notice] Digest: generating secret for digest authentication …
[Sat Mar 14 18:12:13 2015] [notice] Digest: done
[Sat Mar 14 18:12:14 2015] [error] [client 192.168.1.10] Directory index forbidden by Options directive: /var/www/html/
[Sat Mar 14 18:12:14 2015] [notice] Apache/2.2.15 (Unix) DAV/2 PHP/5.3.3 configured – resuming normal operations

[U][Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::mysqli(): (HY000/2002): Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (2) in /var/www/html/fog/lib/db/MySQL.class.php on line 64[/U]

[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::select_db(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 165
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::query(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 89
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: MySQL::sqlerror(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 180
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: array_key_exists() expects parameter 2 to be array, null given in /var/www/html/fog/lib/db/MySQL.class.php on line 150
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::mysqli(): (HY000/2002): Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (2) in /var/www/html/fog/lib/db/MySQL.class.php on line 64
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::select_db(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 165
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::query(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 89
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: MySQL::sqlerror(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 180
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: array_key_exists() expects parameter 2 to be array, null given in /var/www/html/fog/lib/db/MySQL.class.php on line 150
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::escape_string(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 247
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::escape_string(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 247
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::query(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 89
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: MySQL::sqlerror(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 180
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::escape_string(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 247
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::escape_string(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 247
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::query(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 89
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: MySQL::sqlerror(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 180
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::escape_string(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php on line 247
[Sat Mar 14 18:12:57 2015] [error] [client 192.168.1.10] PHP Warning: mysqli::escape_string(): Couldn’t fetch mysqli in /var/www/html/fog/lib/db/MySQL.class.php

[/QUOTE]

Some MySQL errors so I try to restart / start the MySQL server and see if it will run or not an well lets just say its a fail :oops:
[CODE][root@fog0 mapper]# service mysqld start
Timeout error occurred trying to start MySQL Daemon.
Starting mysqld: [FAILED]
[/CODE]

[QUOTE][B]TOM: [/B]But it sounds to me more like a space issue, not a problem with the database.[/QUOTE]

Yeah I am thinking you are right on the money there sir!

[QUOTE][B]TOM: [/B]From ssh can you run: " df -h "[/QUOTE]

[CODE][root@fog0 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_fog0-lv_root
50G 50G 0 100% /
tmpfs 947M 0 947M 0% /dev/shm
/dev/sda1 477M 44M 408M 10% /boot
/dev/mapper/vg_fog0-lv_home
240G 60M 228G 1% /home
[/CODE]

[QUOTE][B]TOM: [/B]I think it’s space due to how CentOS sets up the environment. The / partition is usually setup with a maximum of 50GB, so if the sda1 disk is less than that it’ll likely be less than that as well. It set’s up, in a default install, an LVM, one for / and one for /home. /home usually get’s the rest of the space the disk has available. When fog installs, it creates the directory /images which falls under the / volume[B].[/B][/QUOTE]
I see what you mean and I guess i’ll have to move that if i’m going to image big drives, would you say “/home/fog/images” would be a good place?

---

so there would seem there is more going on then just the space issue! , What is the next move Tom?

Hey how have you guys been?

[B]INFO[/B]
Old Dell computer with p4 proc / 2GB RAM / 300GB HDD / CentOS minimal 6.6 32bit FOG: v1.2.0

So just as it said up there^ I pulled (upload) a image from a computer on my network and then after it was down the login for the web GUI would not let me login o_O so I got into SSH and reset the password for the CentOS user “FOG” back to “password” an well yeah you guessed it, that was a no go as well So I got out of GC (Google Chrome) and try-out IE (Internet Explorer) & FF (FireFox) [B][COLOR=#ff0000]N[/COLOR][COLOR=#00ff00]O[/COLOR][COLOR=#993366]P[/COLOR][COLOR=#ff00ff]E [/COLOR][/B][COLOR=#000000]still dead in the water.[/COLOR]
[COLOR=#000000] I rebooted the server seeing to as it has been up for some time an after reboot the Apache server didn’t want to start at boot or that is what it seemed like so back to SSH and run the command “service httpd start” and it spit this out at me … [/COLOR]
[QUOTE]
[root@fog0 ~]# service httpd start
Starting httpd: httpd: apr_sockaddr_info_get() failed for fog0
httpd: Could not reliably determine the server’s fully qualified domain name, using 127.0.0.1 for ServerName
[ OK ]
[/QUOTE]

so ok ok that’s cool :rolleyes: BUT after going back over to GC and hitting up [url]http://IPADDRESS/fog[/url] I get his with ([B]Database Schema Installer / Updater[/B]) that fails at “INSERT INTO”
[CODE]INSERT INTO fog.globalSettings(settingKey, settingDesc, settingValue, settingCategory)
values(‘FOG_ADVANCED_MENU_LOGIN’,‘This setting enforces a login parameter to get into the advanced menu.’,‘0’,‘FOG Boot Settings’)
FOG Project: Chuck Syperski, Jian Zhang, Peter Gilchrist & Tom Elliott FOG Client/Prep link: FOG Client/FOG Prep[/CODE] [B][I]…::[URL=‘http://fmslick.com/files/Database_Schema_Installer_Updater.txt’]insert text document here[/URL]::… [/I][/B]so now I am at a lost for word’s and before going on what do you guys think the issue could be or what happen??

I’ll post log files if you need them just tell what logs and location however I have a feeling my config file is missing the MySQL password I don’t know why I just do…

Where is the new location of the config file that holds that info?

[quote=“pravinkumar, post: 43416, member: 28885”]its may be helpful once see this…[url]http://fogproject.org/forum/threads/pxe-boot-problems-after-install-fog-1-0-0-on-ubuntu-dhcp-server.10478/[/url][/quote]

Thanks man but its not a PXE boot problem or DHCP server issue seeing to as I am not using FOG’s for DHCP & I’m not running Ubuntu (EWW & WTF lol)

[quote=“Junkhacker, post: 42325, member: 21583”]i found some instructions for setting up that version of backtrace for network booting over a mounted NFS volume using pxelinux. the instructions should be a good clue on what you could do with ipxe [url]http://www.gtkdb.de/index_7_1786.html[/url][/quote]

Cool and thanks ill look into that right now and get back to you on that.

Note… google translate is going to help here! --> [url]http://www.gtkdb.de/index_7_1786.html[/url] lolololz

Sorry for dul-post…

[quote=“Tom Elliott, post: 42322, member: 7271”]
You got the same error if you change the clonezilla to BT5R3-GNOME-32.iso and boot from that menu as you got using the “real” BT5R3-GNOME-32.iso?[/quote]

Nope. If I rename the “real” clonezilla to BT5R3-GNOME-32.iso it works so it is not the name if that was the point in that test?!

[quote=“Tom Elliott, post: 42322, member: 7271”]From what I’m gathering, it’s not a filesize issue. Rather the way the iso’s are being booted. You could add a pause or prompt to the menu to have it wait for your entry on failure.[/quote]

How do I add a pause or prompt to the menu to have it wait for entry on failure?

[quote=“Tom Elliott, post: 42322, member: 7271”]
You got the same error if you change the clonezilla to BT5R3-GNOME-32.iso and boot from that menu as you got using the “real” BT5R3-GNOME-32.iso?[/quote]

… Hold on let me try that real fast…

(Do note I dum down the names for testing to see if I can get it to work this is why they are not the same in the menu as posted up there…)

What they are on my server.
[IMG]http://i.imgur.com/o7IpT4U.png[/IMG]

[quote=“Junkhacker, post: 42303, member: 21583”]the biggest issue with names that people have is that they forget that Linux filenames and paths are case sensitive[/quote]

Thanks Junkhacker for the info and yes Linux is case sensitive, however I don’t think this is the issue I am having here do to I was thinking that the name’s I had for the ISO file may have been the issue so this is why I renamed the “BT5R3-GNOME-32.iso” to “[FONT=Consolas]clonezilla[/FONT]” and the REAL [FONT=Consolas]clonezilla ISO to “[/FONT][FONT=Consolas]clonezilla_.iso[/FONT][FONT=Consolas]” seeing to as I know the real [/FONT][FONT=Consolas]clonezilla.iso file would boot via from Fog and over my network but the rename however failed. So I try to use other ISO’z but they to fail, this [/FONT][FONT=Consolas]led me to believe that it is maybe a file size issue?!?!o_O[/FONT]

Hey guys

Alright so I have my Fog server running on a old Dell computer with p4 pox / 2GB RAM / 300GB HDD / CentOS minimal 6.6 32bit FOG: v1.2.0 I just started editing the boot menu to addon some .ISO files to boot from an some are seen and same are not, like “clonezilla-live-2.3.1-18-i686-pae.iso” is seen and will load but if I try to use “BT5R3-GNOME-32.iso” I see an error flash for 0.1 sec saying something like file can not be found, I was reading on HERE (the forum) that some times the name can be an issue with this so I made a test ISO by using clonezilla got it to boot and then renamed the ISO file BT5R3 to clonezilla so I never moved the ISO’s or anything like that BUT it was a fail still the same error… Is there a set size the ISO file can be or something along them lines?

My boot menu (I know it could be better)
[CODE]:MENU
menu
item --gap – ---------------- iPXE boot menu ----------------
item clonezilla-live clonezilla-live-2.3.1-18
item BT5R3-GNOME BT5R3-GNOME-32
item shell ipxe shell
item return return to previous menu
choose --default WIN7PE64BIT --timeout 5000 target && goto ${target}

:clonezilla-live
initrd http://${fog-ip}/iso/clonezilla-live-2.3.1-18-i686-pae.iso
chain memdisk iso raw ||
goto MENU

:BT5R3-GNOME
initrd http://${fog-ip}/iso/BT5R3-GNOME-32.iso
chain memdisk iso raw ||
goto MENU

:ipxedemo
chain http://boot.ipxe.org/demo/boot.php ||
goto MENU

:shell
shell ||
goto MENU

:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU

autoboot[/CODE]

I didn’t test this with physical hardware it was just something I seen when I was testing FOG in VM’s before moving to physical hardware and thanks for the addon there that now I know it will do the same on physical hardware.

I know this is a old thread but I have found out if the VM has no OS on the hard drive it will just loop over and over on the countdown.