Quantcast
Channel: iPXE discussion forum - All Forums
Viewing all 1484 articles
Browse latest View live

Ipxe sanhook

$
0
0
Hi. I want to use two diff servers for using for diskless stations. My script contains
...
set-rootpath iscsi....
sanhook --drive 0x81 iqn....
sanboot ${root-path}

But when i boot, i cant see my drive, only after starting manually iscsi-initiator? What the matter? I want to mount it foreground for users, not them manually start iscsi-initiator

DHCP offer and timeout

$
0
0
Hello everyone,

Is it possible to boot to the hard drive after having received a DHCP offer without any parameters? (only the IP @)
The goal would be, if the DHCP server does not provide requested information for the iPXE to boot correctly, it would default to the local Linux.

Here is the error I am getting.
FATAL: INT18: BOOT FAILURE


Many thanks for your help,
Regards,
Bruno.

HP server exit iPXE boot from disk red screen with illegal opcode error

iPXE not working as expected.

$
0
0
Hello Everyone,

We have an iPXE server that has worked for us for years (in a network of 1000's of hosts and vendors) and never had issues, till we upgraded proxmox to version 5. Now we are unable to boot over the network for automated installs, for any guests on the proxmox cluster.

I searched the forum here and found a few people with similar issues but no work arounds or fixes reported, sorry if i missed one.

it complains there is no such file (undionly.kpxe).

Is there a solution to correct this?

I'm a bit surprised there is a problem as about 100% of our other PXE clients are using Intel's implementation of PXE, I see proxmox using iPXE roms, yet our iPXE server and they don't seem to get along

Any Idea , Suggestions would be appreciated,

Thanks,

I didn't find the right solution from the internet.

References:https://forum.proxmox.com/threads/ipxe-not-working-as-expected.37287/

installation video

iscsi sanhook/sanboot fail

$
0
0
I have tried to follow the win7 guide to install win10 on a iscsi disk
but I keep stuck at service unavailable response.
so i used Wireshare on the server capture packages between the target and initiator.
it seem both debian and Windows 10 initiator will skip the Security Negotiation as i do not set chap for both target and initiator but ipxe does not do that.

attached:Wireshark captured packages

loading initrd.img is failed and auto reboot on iPXE

$
0
0
Hi Friends,

iPXE.iso is used in the VM, the VM is pending at loading initrd.img, no ok, then auto reboot after a while, repeat it again and again.

Any suggestion is appreciated.

Thanks.

iPXE as PXE servers discover tool

$
0
0
Hi all

I have discovered iPXE today, so I'm quite new here.. :-)

Very often I have a need to discover PXE servers within the LAN.
I mean I need to know :
* is pxe server coming via DHCP options 60, 66-67 and what these options are
* is pxe server coming via local network (pxe and client are on the same network)
* is pxe server coming via ipHelpers

So, in short, I need a way to simulate a PXE request and analyze the answer.
So far I have discovered, that booting a computer from ipxi.iso and performing:
dhcp
config => proxyDHCP
gives me that information (at least in case, that DHCP, PXE Server and client are within the same subnet).

However this doesn't work on UEFI computer.

May I ask how can I accomplish that? Probably a properly deployed/configured Virtualbox VM with iPXE on it will do the tricks, that I need.

So that I could a have simple , small , solution, that will do the diagnostic for UEFI and BIOS machines.

Thank you in advanced and best regards

2Pint Software Signed IPXE

$
0
0
In my quest to get a signed IPXE going for my small PC business (I Have an extensive PXE boot environment), I stumped across the signed IPXE boat loader from 2Pint Software.

Looks like they baked in some mechanism to use their custom 2PXE server, but this thing is a signed snponly.efi IPXE file. After letting it timeout I was able to ctrl-B to a command prompt and have it grab my IPXE config file and do IPXE things with it.

Their server software is not really what I wanted, but this shows you can sign an IPXE file. Anyone played with this? I wasn't able to track any output to see what it wanted from the server to get it to load my IPXE config files. But, it's a secure boot IPXE, shows it can be done.

pending at loading initrd.img

$
0
0
Hi Friends,

iPXE iso is used in one server, the server boots and is pending at loading initrd.img, auto reboot after a while, repeat it again.

Any suggestion is appreciated.

UEFI sanboot local drive

$
0
0
Hello,

With QEMU, I'm trying to boot directly on a local drive from iPXE with an UEFI binary but I always get the error:
Code:
iPXE> sanboot -n -d 0x80
Booting from SAN device 0x80
Boot from SAN device 0x80 failed: No such device (http://ipxe.org/2c222087)

I compile iPXE from source with
Code:
make bin-x86_64-efi/ipxe.efi

When I try with a bios version, it works fine. I'm probably missing something but I can't see what.

Any idea on how to do it ?

Inside Security (insert)

$
0
0
Hello Everyone,

At one time, I had a decent setup done - which was lost due to a major server crash (yeah - no backups - I know...#1 rule; always have good backups).

I had iBoot, Linux live environments, Linux Utilities, Storagecraft, Windows installers (not to iscsi - never could get that working - but to local storage), Windows "ERD" images (Utilities), etc. all network bootable and usable on almost any hardware (yes there are always those few systems that - well they just suck).

I had that all running in a PXE environment (not iPXE), and it was something I put together almost a decade ago, which at the time worked great. It's been so long, that I do not recall how I created this.

Now, the one image I "need" to get functioning ASAP is Insert v1.3.6 - which, is a ... "pain" to get running via network boot (PXE). When I first did this, it took me about a week or so to finally succeed. I'm already in this about a week - and still stuck. Insert is based on Knoppix - which should not be this hard to get to network boot. You've got vmlinuz, and miniroot.gz - piece of cake right? Eh, no (insert minion gif here... lol). I can get it to a certain point (boots via image) but when it looks for the cdrom (scans /dev/sd?##) it comes up empty and drops to a limited shell.

Now times have changed (iPXE vs PXE) since I've done this last, and there's more functionality. So, I've been looking at the work and examples here - which are pretty awesome. I've been trying quite a few different approaches to getting Insert up and running - all of which still fail. I would like to get everything running via iPXE, but will not shy away from PXE if it is the only option.

Any assistance/ideas will be much appreciated.

Created ipxelinux.0 file:
make bin/undionly.kpxe EMBED=../../imbedded.ipxe
install -v -m 0644 -g root -o root bin/undionly.kpxe ../../ipxelinux.0

Here is my imbedded.ipxe file:
****************************************************************
#!ipxe
set base-ftp-ip ftp://###.###.###.4
set base-http-ip http://###.###.###.4
set base-iscsi-ip ###.###.###.6
set base-nfs-ip ###.###.###.4:
set base-nfs-dir /var/lib/tftpboot/boot_images
set base-url boot_images
set base-iso-dir boot_images/iso
set base-iqn iqn.2017-11.nnnn-iscsitrgt.nnnn.local
set base-iscsi iscsi:${iscsi-server}::::${base-iqn}
set initiator-iqn ${base-iqn}:${mac}

dhcp
chain http://###.###.###.4/menu.ipxe
****************************************************************
Here is my menu.ipxe (the insert boot function), I'm using direct IP addresses just to
alleviate any possible issues with using variables. Once it's functioning, I'll change to
the variables:
****************************************************************
:insert136
echo Booting Insert 1.3.6
sanboot --keep --no-describe --drive 0x81 http://###.###.###.4/boot_images/iso/UTI...-1.3.6.iso || goto failed ##STILL FAILED

## Failed Attempts - or some combination/variation of the following:
#sanboot --keep --no-describe --drive 0x81 http://###.###.###.4/boot_images/iso/UTI...-1.3.6.iso || goto failed

#sanhook --keep --no-describe --drive 0x81 http://###.###.###.4/boot_images/iso/UTI...-1.3.6.iso || goto failed
#sanboot

## Also tried below kernel entries with http://###.###.###.4/boot_images/insert1.3.6/vmlinuz

#KERNEL boot_images/insert1.3.6/vmlinuz
#APPEND nfsdir=###.###.###.4:/var/lib/tftpboot/boot_images/insert1.3.6/cdrom/ nodhcp lang=en ramdisk=1000000 init=/etc/init apm=power-off nomce vga=normal
#initrd insert1.3.6/miniroot.gz

#KERNEL boot_images/insert1.3.6/vmlinuz
#append nfsdir=###.###.###.4:/var/lib/tftpboot/boot_images/insert1.3.6/cdrom nodhcp lnag=en ramdisk_size=1000000 init=/etc/init apm=power-off nomce vga=normal initrd=insert1.3.6/miniroot.gz BOOT_IMAGE=insert
****************************************************************

iPXE fails if DPDK enabled

$
0
0
Hi,

I am using Mirantis OpenStack 9.2. If DPDK is enabled, the vm’s iPXE boot fails with the following message:
link for the screenshot
Thanks in advance for the help.
Rafael

Menu login with encrypted password

$
0
0
I am using "login" and "iseq" to password protect a certain part of ipxe. Is there a way of using an encrypted password in a string? Currently i use:

login || goto start
iseq ${username} admin || goto menu-os
iseq ${password} admin || goto menu-os

And those strings are clear text. Looking for something like "grub-crypt".

Another way to chainload iPXE from iPXE

$
0
0
Hello all!

I tried to use iPXE with DHCP Server that not support classes (MikroTik ROS) with following config:

make bin/undionly.kpxe EMBED=loadlkrn.ipxe

loadlkrn.ipxe contents:
Code:
#!ipxe

dhcp
kernel ipxe.lkrn initrd=boot.ipxe
initrd boot.ipxe
boot

Then booting using "undionly.kpxe" as boot file name I got this error:
[Image: h8nl8a]

If I boot using pxelinux.0 with this config:
Code:
menu title PXE Boot Menu

label Load iPXE SuperBoot Menu
       menu label Load iPXE SuperBoot Menu
       kernel /ipxe.lkrn
       initrd boot.ipxe
, iPXE was loaded successfully.

All files (undionly.kpxe, ipxe.lkrn, boot.ipxe) are in the Boot TFTP root.

What do I do incorrectly in the first option of loading and what decision will be true to use only iPXE?

Minimal iPXE build

$
0
0
Hi !

I needed to build a iPXE EFI loader and everything works quite well so far.
There's an embedded script using the many possibilities of iPXE (thanks for that!).
But this loader is meant to be distributed across a large number of (similar) devices, so I started to look at reducing the generated binary size (starting from ~950KiB)

I found that building secure-boot enabled reduces the size to ~500KiB.
With further features tweaking (through config/local/*.h), I made this a little bit smaller, but it still included a lot of drivers I don't need.
I found no official way to specify a list of drivers, so I started to dig the Makefile a little bit and came with the solution of adding DRIVERS_ipxe=intel on the make invocation (as I only need a specific Intel driver).

Final size is 134KiB and still works as expected.

Do you feel like this technique is safe and future-proof or am I missing something to specify a list of drivers?

Thanks Smile

sanboot reboots the pc if i use something else than 0x80

$
0
0
Hi,
im attemping to make the iPXE boot from iSCSI target and if fails, to boot from a iSCSI attached virtual DVD.

This is petty much it

Code:
#!ipxe
set server-ip 192.168.88.254
set target-name iqn.2006-03.com.kernsafe:Shivan-PC.VhdDisk0
set dvd-target iqn.2006-03.com.kernsafe:Shivan-PC.VirtualCD0

dhcp
set keep-san 1
sanboot iscsi:${server-ip}::::${target-name} || sanboot --drive 0x81 iscsi:${server-ip}::::${dvd-target}

The idea is to first attempt to boot from the iscsi hdd, if fails (because is a new disk and its empty), to boot from the virtual iscsi dvd to install the O.S.

But as soon as the sanboot --drive 0x81 is executed the pc reboots, no matter if is a real pc or virtualbox.

The only way that it boots the dvd image is using 0x80 for it, and hook the iscsi hdd to 0x81

Code:
#!ipxe
set server-ip 192.168.88.254
set target-name iqn.2006-03.com.kernsafe:Shivan-PC.VhdDisk0
set dvd-target iqn.2006-03.com.kernsafe:Shivan-PC.VirtualCD0

dhcp
set keep-san 1
sanboot iscsi:${server-ip}::::${target-name} || goto start

:start
set keep-san 0
sanunhook
set keep-san 1
sanhook --drive 0x81 iscsi:${server-ip}::::${target-name}
sanboot --drive 0x80 iscsi:${server-ip}::::${dvd-target}

But then the windows installer does not work, it says it cant install on that drive because the hardware may not be able to boot from it.

Server Variables Not Resolving Reliably

$
0
0
I am booting a Hyper-V guest using Tiny PXE Server.

My iPXE script starts

Code:
#!ipxe
set BootServer http://${dhcp-server}

However, BootServer and dhcp-server do not working later in the script, I always receive could not boot image, file not found.

Code:
initrd ${BootServer}/boot/BCD
initrd ${BootServer}/boot/boot.sdi
initrd ${BootServer}/sources/boot.wim

If i hard code the ip in the following then it boots fine.

Code:
initrd http://10.0.1.62/boot/BCD
initrd http://10.0.1.62/boot/boot.sdi
initrd http://10.0.1.62/sources/boot.wim

I am using a menu, and so to check the variable I use it in the Menu Title and it displays the correct http://10.0.1.62

Why are these variables not working??

iPXE 1.0.0+ (30f9)

TFTP Block Size

$
0
0
So I am total novice when it comes to iPXE having only discovered it recently, however I have noticed that the boot performance is not great, from a gen 2 Hyper-V guest (gen 2 being UEFI).

The performance out of the box is similarly poor, when using SCCM + WDS to PXE boot a gen 2 Hyper-V guest, but was dramatically improved when changing the RamDiskTFTPBlockSize and RamDiskTFTPWindowSize.

[Image: TFTPSettings.PNG]

I have no idea if these settings apply to iPXE efi or not, can anyone enlighten me? Or do they relate to the TFTP server (Tiny PXE Server in my case)?

http://ccmexec.com/2016/09/tweaking-pxe-...ager-1606/

Thanks.

wimboot - sccm tsbootshell.exe

$
0
0
Hi There,

So I am using wimboot with a boot image created on our SCCM environment, and this boots successfully using wimboot within ipxe from either a traditional BIOS environment or a UEFI environment.

the boot image itself has all the required drivers for the hardware I am using, so nics and disks are present and I can see these by doing an ipconfig or diskpart

it seems that tsbootshell.exe is having a bit of a problem in that smsts is logging multiple entries for boot wim. from the UI, it appears to hang on a dialogue for initialising hardware devices.. and then eventually prompts to restart with a "Unable to read task sequence configuration disk" this is usually attributed to missing drivers from the boot wim.

the smsts.log is reporting the following:
<![LOG[ConvertBootToLogicalPath failed to convert 'MULTI(0)DISK(0)RDISK(1)PARTITION(1)\SOURCES\BOOT.WIM (0x80070003)

I'm happy with the boot image because if I chainload the WDS/SCCM and have this image served up by TFTP, this runs successfully.

Any ideas as to what could be the cause?

Regards

Muzz

how to install Solaris11.3 on ipxe

$
0
0
#!ipxe
set boot-url http://${next-server}
set base ${boot-url}/Oracle/sol-11_3-text-x86/
kernel ${base}/platform/i86pc/kernel/amd64/unix kernel/unix -v -install -B install_media=${base},install_boot=${base}/boot
module ${base}/platform/i86pc/amd64/boot_archive
imgstat
boot || goto



so I had to pre-unzip the image(boot_archive) before having ipxe load it.

but~~~~~

[Image: 6b6d8241ly1flpo8zzktqj218c0hwgoe.jpg]
[Image: 6b6d8241ly1flpo902642j20l00mowka.jpg]
[Image: 6b6d8241ly1flpo900oduj20l00mowka.jpg]
[Image: 6b6d8241ly1flpo8zy9j4j20k40bwaaq.jpg]
Viewing all 1484 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>