Categories

  • 13k Topics
    115k Posts
    Tom ElliottT

    @Strahd At the least I’d suggest downloading an export of your hosts/images:

    From there you can delete the database or rebuidl from scratch by:

    mysql -u root If you have a password on your db I don’t know it but use the -p and you’ll be prompted to enter it.

    DROP DATABASE fog;

    Will delete everything.

    From there, I still highly recommend you delete the /opt/fog/.fogsettings

    Then rerun the installer.

    I’m still going to say use working-1.6 as the testbed.

    I hate that you’re having issues and I assure you I’m unable to replicate the problem you’re currently having which makes trying to fix your specific case impossible of course.

    Hope this helps.

    I’d still (at the least) get a full backup of your DB just in case something goes horribly wrong.

  • Get the latest news on what's happening.
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    V

    @Tom-Elliott said in How to upgrade to FOG 1.6?:

    @Tom-Elliott, Thank you very much for the comprehensive guide. All the necessary files for secure boot were signed correctly when upgrading from 1.5.10.1903 to 1.6.3200 I encountered a few problems, however. I’am now on 1.6.3279.

    1. Secure boot

    I set my dhcp server (FortiGate) to forward DHCP option 67 (set filename) “secureboot/snponly-shimx64.efi”. On my computers that already had an enroll key, so:
    loading snponly-shimx64.efi OK
    loading bzImage OK
    no FOG task -> refind should be loaded -> SECURITY VIOLATION

    I don’t know why, but for some unknown reason the file /var/www/fog/service/ipxe/refind_x64.efi is not loaded and the file refind.efi is loaded, which was not signed, so I signed them additionally and now the whole boot process works as it should, then no more secure boot errors.

    root@fog:/var/www/fog/service/ipxe# sbverify --cert /root/sbkeys/FOG_SB.crt refind_x64.efi Signature verification OK root@fog:/var/www/fog/service/ipxe# sbverify --cert /root/sbkeys/FOG_SB.crt refind.efi warning: data remaining[237128 vs 262592]: gaps between PE/COFF sections? Signature verification failed root@fog:/var/www/fog/service/ipxe# sbsign --key /root/sbkeys/FOG_SB.key --cert /root/sbkeys/FOG_SB.crt --output refind.efi refind.efi warning: data remaining[237128 vs 262592]: gaps between PE/COFF sections? Image was already signed; adding additional signature root@fog:/var/www/fog/service/ipxe# sbverify --cert /root/sbkeys/FOG_SB.crt refind.efi Signature verification OK 2. Web GUI

    In the menuStorage Node-> List All Storagegroups, I see a table with a list for only one row, but I have 12 storage groups created. I can scroll through them using the mouse wheel, but only one row is displayed. Tested in Firefox and Chrome on Windows 11.

    storage_group.png

    In the menuStorage Node -> List All Storagenodes, the same problem as the previous Storage Group.

    3. iPXE menu

    The new item “Enroll Secure Boot Key” did not appear in the iPXE menu, but I had to add it manually. I have FOG 1.6 installed as a clean installation in another virtual machine. Just for testing. In this clean installation, this iPXE menu item was there, but in the version upgraded from 1.5.10 it did not appear. I had some custom items added to the iPXE menu before the upgrade. Maybe that caused the new one not to be added?

  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    L

    @Tom-Elliott Hi, Yes with the proposed fix, it works now.

68

Online

12.7k

Users

17.6k

Topics

156.9k

Posts