Ipxe Network Boot Of Rescue Cd

javamarket

I would appreciate anyone sharing their menu configuration who has had success in using iPxe to http boot (perhaps sanboot?) the newer Rescue CD iso image since it is in isohybrid format. I've spent a few days trying both pxelinux & iPxe and haven't managed a successful result.

Many thanks,

Mark

shortkut

Hey Mark, I'm actually in the process of figuring all this out myself. So far, using an NFS share w/iPXE I can get it to boot semi-properly. I say semi-properly because for whatever reason, the only thing that is missing is the nameserver (DNS). Not sure why, it gets all the other DHCP info, but leaves out the DNS.

Here's the iPXE code I'm using:

kernel http://10.1.10.2/pxe64/Linux/BDRescue/boot/kernel.x86_64-efi netboot=nfs nfsroot=10.1.10.2:/Linux/BDRescue root=/dev/nfs real_root=/dev/nfs loop=/rescue/livecd.squashfs looptype=squashfs udev cdroot ip=dhcp ro

initrd http://10.1.10.2/pxe64/Linux/BDRescue/boot/initfs.x86_64-efi

boot

If you run into the same DNS issue and are able to resolve it, please let me know!!

P.S. - I haven't yet been able to get it to work booting directly to the ISO with either chaining, or sanbooting.

javamarket

Hey Mark, I'm actually in the process of figuring all this out myself. So far, using an NFS share w/iPXE I can get it to boot semi-properly. I say semi-properly because for whatever reason, the only thing that is missing is the nameserver (DNS). Not sure why, it gets all the other DHCP info, but leaves out the DNS.

Here's the iPXE code I'm using:

kernel http://10.1.10.2/pxe64/Linux/BDRescue/boot/kernel.x86_64-efi netboot=nfs nfsroot=10.1.10.2:/Linux/BDRescue root=/dev/nfs real_root=/dev/nfs loop=/rescue/livecd.squashfs looptype=squashfs udev cdroot ip=dhcp ro

initrd http://10.1.10.2/pxe64/Linux/BDRescue/boot/initfs.x86_64-efi

boot

If you run into the same DNS issue and are able to resolve it, please let me know!!

P.S. - I haven't yet been able to get it to work booting directly to the ISO with either chaining, or sanbooting.

Thanks for your post @shortkut, it was quite helpful. I can also confirm your experience with no DNS. Even trying to add it to the parameters as dns=x.x.x.x failed.

As a workaround, I was able to use the following to renew the dhcp once at the desktop. Not optimal but until we find something more graceful this seems to work:

Use

nmcli con

to get your ID, (likely eth0), then you can

sudo nmcli con down id eth0

and finally use the GUI to connect once more.