mfsbsd icon indicating copy to clipboard operation
mfsbsd copied to clipboard

Published 20 hours ago • verified publisher icon mmatuska

mfsbsd img file not working in UEFI mode

Open Gitrrrr opened this issue 5 years ago • 8 comments

UEFI_Mfsbsd mfsbsd boot is not working in UEFI mode. it is working fine for me in legacy mode using memdisk. ipxe file

kernel http://$server/cobbler/ks_mirror/$distro/boot/loader.efi initrd http://$server/cobbler/ks_mirror/$distro/boot/mfsbsd-amd64.img boot Note i tried this (mmatuska/mfsbsd#100) but not worked for me.

Gitrrrr avatar Jun 23 '20 14:06 Gitrrrr

ipxe file

kernel http://$server/cobbler/ks_mirror/$distro/boot/loader.efi initrd http://$server/cobbler/ks_mirror/$distro/boot/mfsbsd-amd64.img boot

This is probably not the correct way to boot mfsBSD via iPXE. You should run sanboot http://$server/cobbler/ks_mirror/$distro/boot/mfsbsd-amd64.img

because the sanboot command is designed for fetching hdd and iso images.

Anyway, loader.efi is not a kernel. If you want to use it, you probably should run chain loader.efi in your ipxe file.

and then loader.efi would fetch and load the kernel and mfsroot. But only with NFS.

victor-sudakov avatar Dec 25 '20 10:12 victor-sudakov

@victor-sudakov Thanks for correcting me.

Gitrrrr avatar Dec 25 '20 11:12 Gitrrrr

@Gitrrrr look

The way it should work (though it does not):

  1. Create an msfBSD tar image cd mfsbsd && make tar
  2. tar -x -C /tftpboot -f mfsbsd-12.2-RELEASE-p1-amd64.tar
  3. make /tftpboot available over TFTP and over NFS
  4. cp /boot/loader.efi /tftpboot/
  5. Configure your DHCP server to provide next-server and root-path as 192.168.1.1:/tftpboot and "loader.efi" as bootfile.

loader.efi will be fetched to the host by the PXE boot, and should do the rest of the job. However in my case, it loads the kernel, tries to load mfsroot and then freezes, and then reboots in a minute or so. Or maybe it's not loader.efi that freezes, but "/mfsroot" and several seconds of rotating "/" is the last thing I can see.

IMG_20201226_143220

victor-sudakov avatar Dec 26 '20 07:12 victor-sudakov

Can you please tell me how to enable some debug output to see what's happening after the "/mfsroot" message?

victor-sudakov avatar Dec 28 '20 03:12 victor-sudakov

I know it is old issue, but if someone find it useful, I have successfully booted mfsbsd-se-13.2-RELEASE-amd64.img using: sanboot --no-describe mfsbsd-se-13.2-RELEASE-amd64.img on R720xd via UEFI iPXE boot.

tuxj avatar Nov 05 '23 02:11 tuxj

@tuxjz could you be able to share the working config?

gopiio avatar Jan 12 '24 10:01 gopiio

Can you please elaborate on what part of config you are interested in? We use custom build iPXE, booted from TFTP, then load menu from HTTPS and then it is only sanboot with no-describe option as mentioned above: sanboot --no-describe mfsbsd-se-13.2-RELEASE-amd64.img

tuxj avatar Jan 15 '24 17:01 tuxj

Can you please elaborate on what part of config you are interested in? We use custom build iPXE, booted from TFTP, then load menu from HTTPS and then it is only sanboot with no-describe option as mentioned above: sanboot --no-describe mfsbsd-se-13.2-RELEASE-amd64.img

Thanks @tuxjz . Finally, I managed to get it to work. I am not using ipxe. I was totally stuck on it. My PXE server is based on debian. I was using dnsmasq for DHCP and TFTP. My issue was I couldn't find a way to pass the dhcp-option root-path. In order to get it working, I had to disable dnsmasq and went with isc-dhcp-server, tftpd server and loaded loader.efi.....it worked!!! mfsbsd image worked out of the box, without any customization.

gopiio avatar Jan 25 '24 15:01 gopiio