UEFI won boot tools via fog menu.
-
@Quazz the files are being exported via nfs server of Ubuntu
/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0) /images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1) /images2 *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=2) /images2/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=3) /var/www/html/bootimgs *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure) /opt/bootimgs *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)``` -
@dureal99d They need to have fsid assigned at the very least to work properly as far as I know.
-
-
@dureal99d said in UEFI won boot tools via fog menu.:
i see add
@Quazz I shall add fsid= to the export and shall report back
-
-
@Quazz said in UEFI won boot tools via fog menu.:
showmount -e 127.0.0.1
dureal99d@dureal99d-Precision-WorkStation-T5400:~$ sudo exportfs -a exportfs: /etc/exports [5]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/var/www/html/bootimgs". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x exportfs: /etc/exports [6]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/opt/bootimgs". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x exportfs: duplicated export entries: exportfs: *:/opt/bootimgs exportfs: *:/opt/bootimgs dureal99d@dureal99d-Precision-WorkStation-T5400:~$ showmount -e 127.0.0.1 Export list for 127.0.0.1: /opt/bootimgs * /images2/dev * /images2 * /images/dev * /images * -
@dureal99d You’ll need to add subtree_check as well, otherwise any folders underneath it won’t be accessible.
-
dureal99d@dureal99d-Precision-WorkStation-T5400:~$ sudo exportfs -a exportfs: duplicated export entries: exportfs: *:/opt/bootimgs exportfs: *:/opt/bootimgs dureal99d@dureal99d-Precision-WorkStation-T5400:~$ showmount -e 127.0.0.1 Export list for 127.0.0.1: /opt/bootimgs * /images2/dev * /images2 * /images/dev * /images * dureal99d@dureal99d-Precision-WorkStation-T5400:~$ ``` Does this look right? /images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0) /images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1) /images2 *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=2) /images2/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=3) /var/www/html/bootimgs *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=4) /opt/bootimgs *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=5) -
@dureal99d It’s trying to export /opt/bootimgs twice.
Is it a symbolic link or something?
Either way, it should probably work now, might need to restart NFS service, though.
-
-
@dureal99d Looking at my own boot items, I do not appear to have a trailing slash. Try removing that from your boot options.
If it still has issues after that, see if you can manually mount that NFS location.
You can base yourself on https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_NFS replace paths where necessary.
-
@Quazz Keep in mind in bios boot mode these options work just fine, the issue exist in uefi mode.
also, what is a trailing slash?
-
@dureal99d It’s a forward slash / at the end of the url.
I don’t know why it would work in BIOS mode, honestly. Or perhaps why not in UEFI. Secure Boot is off on the target device, right?
-
@Quazz said in UEFI won boot tools via fog menu.:
know why it would work in BIOS mode
yes I am also at a loss, that is also what I find strange, I see no reason I can upload and download an image but not boot these isos in uefi mode. its crazy to me. but ive read uefi is pretty pick about stuff so who knows?
-
@dureal99d You should use subtree_check, not no_subtree_check.
-
@dureal99d ISO’s can be created to run in only “BIOS” mode. This means, while UEFI is backwards compatible from a support perspective, the ISO’s have no idea how to use UEFI. BIOS expects certain things to run. You must remember BIOS booting has been around, essentially, since the beginning of personal computers. UEFI is relatively new so simply saying “UEFI is supposed to be backwards compatible” doesn’t mean much. EFI has been around for quite some time, but only recently has it been in “major” use.
-
@Tom-Elliott Ok I’m going to try that now
also i tried this config and its getting farther than before by loads
initrd http://${fog-ip}/bootimgs/16.04.1_64/casper/initrd.lz chain http://${fog-ip}/bootimgs/16.04.1_64/casper/vmlinuz.efi initrd=initrd.lz root=http://${fog-ip}/bootimgs/16.04.1_64/casper/squashfs ip=dhcp – || read void boot || goto MENU``` -
@dureal99d The post I’m linking here.
You are missing the initrd= statement. You will likely need to add: initrd=initrd.lz (or the respective initrd filename) to each of your menu entries.
-
@dureal99d Try to use fetch=http://${fog-ip}/bootimgs/16.04.1_64/casper/squashfs instead of root=
-
@Tom-Elliott said in UEFI won boot tools via fog menu.:
@dureal99d ISO’s can be created to run in only “BIOS” mode. This means, while UEFI is backwards compatible from a support perspective, the ISO’s have no idea how to use UEFI. BIOS expects certain things to run. You must remember BIOS booting has been around, essentially, since the beginning of personal computers. UEFI is relatively new so simply saying “UEFI is supposed to be backwards compatible” doesn’t mean much. EFI has been around for quite some time, but only recently has it been in “major” use.
I understand.
