Fully automated UEFI-based O/S installation (Debian 10)
-
@robpomeroy said in Fully automated UEFI-based O/S installation (Debian 10):
But grubx64.efi seems to have some hard-coded files it looks for, so I’m not sure where else to place them.
Also be aware there are different flavors of grub. There is grubx64.efi and grubnetx64.efi depending on the distro where you get them from some distros don’t add networking support to grubx64.efi so it can only reference local storage.
You can pxe boot with grub in the case of grub (grubnetx64.efi) from ubuntu’s repo on your tftp server create a grub directory
mkdir -p /tftpboot/gruband place your grub.cfg file in there. That is hard coded into the grub binary as you noted. -
This post is deleted! -
@george1421 - I took a lot of inspiration from that whole post of yours; you’ve clearly done a lot of work in this area, so thank you for that. In my approach, I wanted to achieve this using the lightweight network installer for Debian, rather than a Live CD/
filesystem.squashfsapproach.So this:
kernel tftp://${fog-ip}/os/debian/Server10.7/linux initrd tftp://${fog-ip}/os/debian/Server10.7/initrd.gz imgargs linux auto=true url=http://${fog-ip}/os/autoinstall/debian-10/preseed.cfg hostname=debian-10 domain=local interface=auto vga=788 noprompt --- quiet boot || goto MENU…is closer to what I’d hope to achieve. I did try an approach along these lines, but without any success, hence resorting to the
grubmethod. I’ll give it another try - thanks! -
@robpomeroy said in Fully automated UEFI-based O/S installation (Debian 10):
I did try an approach along these lines, but without any success,
What were your results? Did you confirm that you can download the preseed file with a standard browser?
-
@robpomeroy With the exception of testing the preceed file these instructions work as advertized: https://forums.fogproject.org/post/140720
-
@george1421 said in Fully automated UEFI-based O/S installation (Debian 10):
@robpomeroy With the exception of testing the preceed file these instructions work as advertized: https://forums.fogproject.org/post/140720
On UEFI? I’ll try that now! Thanks.
-
kernel tftp://${fog-ip}/os/debian/Server10.7/linux initrd tftp://${fog-ip}/os/debian/Server10.7/initrd.gzHave you tried leaning on IPXE’s HTTP support here rather than TFTP? I’m just wondering if that would make it cleaner (keeping all installer files in one location under the web root).
-
@robpomeroy Yes I have use tftp, http/https, nfs. The use of tftp was a conscious decision to keep the instructions consistent throughout the article. One of the issues is the http document root varies depending on the linux distribution.
From a performance standpoint for the kernel and the initrd tftp transfer is fast enough, for the live boot OS’ its better to use http transfer because the squashfs files are usually several hundred MB in size.
Actually looking at the tutorial for debian 10 server, the files are shared with the pxe booting computer over NFS, so the only thing transferred via tftp is just the kernel and init.
imgargs linux root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:/images/os/debian/Server10.7/ locale=en_US.UTF-8 keyboard-configuration/layoutcode=us quiet splash ip=dhcp rwI guess the point here is there is no bad way to go about it. Whatever works for your environment is the right choice. FOG just give you the options to use whatever you need to get the job done.
-
@george1421 - Thanks George. My problem is understanding all the options!
Following your latest instructions unfortunately results in a kernel panic (presumably initram related?). The kernel and init disk both transferred correctly via TFTP. Incompatibility with UEFI perhaps?
-
@robpomeroy Switch the VM to bios and try it (just to test). I was having that issue with efi on proxmox. I thought it was just being proxmox being silly. Maybe not.
The error is basically the kernel doesn’t understand the format of the virtual disk drive (initrd).
-
@george1421 It’s a physical server (Dell T40) that literally cannot boot BIOS-based OSes, I’m afraid. It has no internal legacy boot capability. I was amazed, but then I haven’t worked with physical hardware in a while.
-
@robpomeroy Ok so next plan I was going to try is to grab FOG’s bzImage from
/var/www/html/fog/service/ipxeThat is EFI capable I was thinking about sliding that in and replacing the “linux” kernel just to see if it would init the disk. Let me see what I can do on vmware I should be able to duplicate the error I was seeing in my home lab. -
@george1421 - okay, thanks George.
This boots beautifully though:
kernel tftp://${fog-ip}/grubx64.efi boot || goto MENUIs there no way to squirt additional parameters into that Grub EFI loader?
Sorry - I figured that this might be simple. I should know better by now!
-
@robpomeroy Well I have a workable solution.
kernel tftp://${fog-ip}/os/debian/Server10.7/linux loglevel=7 initrd=initrd.gz root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:/images/os/debian/Server10.7/ locale=en_US.UTF-8 keyboard-configuration/layoutcode=us quiet splash ip=dhcp rw imgfetch tftp://${fog-ip}/os/debian/Server10.7/initrd.gz boot || goto MENUAfter several itterations of try this, crash that… I found that the image args was missing this
initrd=initrd.gz. Understand I did not push the installer past configuring the keyboard. But the kernel now boots. You will probably need to add in the link to the preseed fileauto=true url=http://${fog-ip}/os/autoinstall/debian-10/preseed.cfgand anything else you want configured via image args. -
@george1421 George, firstly thanks again for the all the work you’ve put into this!
This steered me in exactly the right direction. The following are the parameters I used for a completely automated netboot install (no Live ISO required). This is the point I was hoping to get to. Brilliant.
kernel tftp://${fog-ip}/debian-installer/amd64/linux auto=true url=http://${fog-ip}/os/autoinstall/debian-10/preseed.cfg interface=auto hostname=debian-10 domain=local initrd=initrd.gz vga=788 noprompt quiet imgfetch tftp://${fog-ip}/debian-installer/amd64/initrd.gz boot || goto MENUSo this removes the need to mess around with
grub.cfgor boot to an intermediate (grub) menu. All you need are thenetboot.tar.gzfiles and apreseed.cfg. Next I’ll try doing this all via HTTP (rather than TFTP), to avoid polluting/tftpboot. I’m mindful that I would like to make the backup and restoration of FOG itself as straightforward as possible.I know I’ve said this a few times in this thread (!) but once more: thank you. If I can help by writing up a wiki page for this process, do point me in the right direction.
-
Yep, HTTP worked perfectly too, which means I could put the three required files in a single location under the web root. FOG menu parameters:
kernel http://${fog-ip}/os/autoinstall/debian-10/debian-installer/amd64/linux auto=true url=http://${fog-ip}/os/autoinstall/debian-10/preseed.cfg interface=auto hostname=debian-10 domain=local initrd=initrd.gz vga=788 noprompt quiet imgfetch http://${fog-ip}/os/autoinstall/debian-10/debian-installer/amd64/initrd.gz boot || goto MENUThis is clean & efficient. I like it. Probably not as quick as using a Live image, but I’m doing this over a fast internet connection and it’s a minimal install. So the whole thing is done in ten minutes or so.
Again, I’m more than willing to write this up somewhere if useful for others.
-
@robpomeroy said in Fully automated UEFI-based O/S installation (Debian 10):
three required
*the required
-
@robpomeroy said in Fully automated UEFI-based O/S installation (Debian 10):
I’m more than willing to write this up somewhere if useful for others
Tutorials in the tutorial forum section is always appreciated. No one knows the entire IT picture so your work covers areas where others have not been. That is kind of why I started that huge tutorial on network booting, to give others a platform to start their projects with.
-
@george1421 Done.
