Adding Hirens 15.2 boot cd to the boot menu
-
@Wayne-Workman
There’s only one file in there -
The whole directory /casper/… just isn’t there, and its not explained in the wiki how they get there.
It just say’s extract the hirens boot cd to the directory /fog/iso/15.04_64I’m not shure to wich file i should point in the hirens iso to make it boot.
-
@goempie the “boot” folder in that picture you posted looks promising… look around in there… Maybe you’ll find the files you need to point to…
-
kernel http://${fog-ip}${path}/casper/vmlinuz.efi || read void <---- there is nog casper/vmlinuz.efi in the iso that i extracted?
initrd http://${fog-ip}${path}/casper/initrd.lz || read voidThese two things are your kernel and your init.
so fog-ip is auto-filled in with your FOG IP. The path is set in the boot entry, it’s this line:
set path /fog/iso/15.04_64So your path would be /fog/iso/15.04_64
Put that all together and you have a web URL:
x.x.x.x/fog/iso/15.04_64/casper/vmlinuz.efi
Where x.x.x.x is your fog server IP, of course.
What the iPXE boot script is trying to do is load the kernel and init via HTTP, through a web request basically.
So… it may be that the mounted directory cannot be read by Apache due to permissions or placement, or it could be that the files listed there just aren’t where they should be.
Either way, you need to sort that out, or figure out how to do it via NFS fully. In the wiki link below, you’ll find an example in the “Parted Magic - Older” area. Not sure if a Linux kernel will work with Hirens though! Probably not!
-
@Wayne-Workman
This is the file structure of the hirens boot cd.
And I can reach it through a browser. -
@Wayne-Workman
yes i’m using nfs mounting, i extracted the iso to the directory as it say’s in the wiki.I just don’t get where this is pointing to:
kernel http://${fog-ip}${path}/casper/vmlinuz.efi || read void <---- there is nog casper/vmlinuz.efi in the iso that i extracted?
initrd http://${fog-ip}${path}/casper/initrd.lz || read void -
@goempie So, let’s look at where you are?
You got to the boot menu, and the FOG background image is displayed. So at this point, you’ve successfully gotten a boot ROM via TFTP, it loaded correctly, and now that ROM is following specific instructions for the Hirens boot entry.
“File not found” seems pretty obvious, right? Some way or another the files the boot menu item is requesting are simply not available. This could be that… permissions are not set right, or the files simply are not there (in the wrong directory or typo in path or filenames. Linux is CASE SENSITIVE).
Look over your boot menu entry again, and look over where your files are on the fog server again. Make sure everything is jiving. Check permissions on those files as well.
Are you using NFS mounting at all for this? Yes you are, I just looked at what Tom posted. Did you export the
/var/www/fog/iso/15.04_64directory via NFS? If not, it wouldn’t exist I guess! -
@Tom-Elliott
I’m following the wiki, otherwise I have no idea what i’m doing
-
When I add the above in my menu then i get this
-
Ok, I guess we better test and then update the wiki on this stuff: https://wiki.fogproject.org/wiki/index.php/Include_any_ISO_in_the_FOG_Bootmenu#Hirens_15.04
-
I dont’ know what you’re doing.
From what I can tell, there is no function called “start”.
There’s no function called “return”
My guess, you need:
:MENU menu item --gap – ---------------- iPXE boot menu ---------------- item ubuntu15.04_64 Boot Ubuntu 15.04 item return return to previous menu :ubuntu15.04_64 set path /fog/iso/15.04_64 set nfs_path /var/www/fog/iso/15.04_64 kernel http://${fog-ip}${path}/casper/vmlinuz.efi || read void initrd http://${fog-ip}${path}/casper/initrd.lz || read void imgargs vmlinuz.efi root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:${nfs_path} ip=dhcp splash quiet – || read void boot || goto MENU :return params param mac0 ${net0/mac} param arch ${arch} isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootmeOf course we would need to see exactly what your system is showing via the browser.
