@jc35
mount /dev/sda1 /mnt
mount --bind /sys /mnt/sys
mount --bind /proc /mnt/proc
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts

chroot /mnt ./usr/sbin/grub-install /dev/sda

@Wayne-Workman said:

Do you have FOG 1.2.0 working? It can do all these things already.
Yes we have FOG 1.2.0 working.

Why do you want bash commands for those things?

We need to automate some actions. We use glpi and rabbit mq.
when we put a machine discarded with glpi, rabbit mq send to fog " a wipe and imaging and delete a machine."

@Arrowhead-IT
Thank you very much.

@Wayne-Workman
thank you very much.

@jc35
mount /dev/sda1 /mnt
mount --bind /sys /mnt/sys
mount --bind /proc /mnt/proc
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts

chroot /mnt ./usr/sbin/grub-install /dev/sda

Hi,

@sebastian-roth said in Ubuntu Image with both - UEFI and Legacy support:

@jc35 said in Ubuntu Image with both - UEFI and Legacy support:

Can we use chroot in a script?

Sure you can. But I suggest you try it out in a FOS debug session first for easier debugging. I think you need to bind mount special filesystems like /dev and maybe also /proc and /sys for grub-install to properly work in this chroot environment. Just use your favorit search engine to find hints on this topic on the web.

It’s works fine.
Thanks you very much.

@sebastian-roth said in Ubuntu Image with both - UEFI and Legacy support:

@jc35 What I mean is mount the root partition of your Ubuntu system (that you deployed) and use chroot to switch into that system…

Can we use chroot in a script?

@sebastian-roth said in Ubuntu Image with both - UEFI and Legacy support:

@jc35 said in Ubuntu Image with both - UEFI and Legacy support:

The solution is grub-install, but is not include in FOS.
How to put grub-install on FOS ?

So far I have not succeeded, I have compiled GRUB on my pc, then I try to copy the files to the FOS, but dependency problem. We would have to figure out how to compile GRUB in STATIC and copy into FOS.

Well then you use FOS to chroot into the Ubuntu install after imaging and run grub-install there.
With chroot, this requires manual intervention unfortunately, I would like to do it automatically in the postinstall scripts.

Hi,
I have create a ubuntu image to boot in legacy and uefi mode, it works fine in virtualbox.
But when I upload the image on FOG. When I deploy this image on a legacy computer, it dosen’t boot, but boot on uefi computer.
The solution is grub-install, but is not include in FOS.
How to put grub-install on FOS ?

@george1421 said in problem boot ipxe with usb nic after update FOG 1.5.8 -> 1.5.9:

@Sebastian-Roth Just circling back on this.

I took 3 of the dell systems here that have thunderbolt/usb-c ports and use the WD15 (mainly), WD19 and the Dell usb-c to ethernet adapter.

I downloaded the ipxe.efi from the github site: https://github.com/FOGProject/fogproject/blob/master/packages/tftp/ipxe.efi and installed it on my production 1.5.7 server. I confirmed the iPXE build number is [g4bd0].

It works with usbc->ethernet dongle.

I was able to pxe boot into the FOG iPXE menu with a Dell 7400, 7389, 3520 laptops with the WD15 and usb-c to ethernet dongle. The 7389 pxe booted with the WD19 dock OK. I did not test the others.

I can confirm that the version if ipxe.efi from FOG 1.5.7 is [990f4]. So as far as I can tell there is no impact of updating from 1.5.7 to 1.5.9 on network booting.

Thanks you very much.

@Sebastian-Roth said in problem boot ipxe with usb nic after update FOG 1.5.8 -> 1.5.9:

As we don’t know much about the NIC you use (beyond it being USB) we can’t say which change in the iPXE code could cause the new behaviour. So let’s see if we can gather some more information. Can you post the exact USB NIC model you have. Best if you have USB IDs at hand.
As well you might try George’s suggestion on using snponly.efi instead of ipxe.efi just to see if that makes a difference with those USB NICs.

Docks dell wd15,wd19
Dongle dell usb-c -> network

on Linux with “lsusb”
ID : 0bda:8153

@Sebastian-Roth said in problem boot ipxe with usb nic after update FOG 1.5.8 -> 1.5.9:

@Sebastian-Roth said in problem boot ipxe with usb nic after update FOG 1.5.8 -> 1.5.9:

For how long does it sit there waiting? Does it proceed at all?

• About 3 minutes.
• After it boot on a hard disk.

Would you mind answering those questions?

I had already answered these 2 previous questions.

As well I wonder if your switch is setup with spanning tree? What happens if you connect a dumb mini switch in between?

• Spanning tree is configured between switches only, but not between the client and FOG.
• We can’t to that. We do not have access to the switches.

@george1421 said in problem boot ipxe with usb nic after update FOG 1.5.8 -> 1.5.9:

@jc35 said in problem boot ipxe with usb nic after update FOG 1.5.8 -> 1.5.9:

While waiting to find a solution, we have put back the “/ tftpboot” folder and the “/ var / www / fog / service / ipxe” folder from version 1.5.8, and it works.

Lets have you rerun the fog installer for 1.5.9 this will restore your system to 1.5.9 version. Then put back just the /tftpboot directory. See if this combination works OK. I feel your fix to put back /tftpboot fixed the problem.

I restore “/var/www/fog/service/ipxe” from 1.5.9 backup.
“/tfptboot” from 1.5.8 And I reboot the server. It works.

@Sebastian-Roth said in problem boot ipxe with usb nic after update FOG 1.5.8 -> 1.5.9:

@jc35 For how long does it sit there waiting? Does it proceed at all?

About 3 minutes, and it boot on a hard disk.

I’d suggest you download the ipxe.efi file we released with FOG 1.5.8 from github to see if that really makes a difference.

Rename the current file /tftpboot/ipxe.efi to have a backup copy of it and then put the file downloaded above in place. See if it’s doing the same thing using that iPXE binary.

While waiting to find a solution, we have put back the “/ tftpboot” folder and the “/ var / www / fog / service / ipxe” folder from version 1.5.8, and it works.