Categories

  • Get help with your FOG system.
    FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
    12k Topics
    114k Posts
    W

    Hello!

    I’m currently trying to upgrade our server from running on HDDs to SSDs. We have about 50 computers already running FOG, which I’d say has worked good. I have installed the new SSDs in the server, reinstalled fog, done the standard Debian setup and imported the hosts. I had an issue were I were not even able to capture an image because in became invalid, and didn’t display any date. I fixed this by giving rights to wright and read in the folder.

    The issue is now that I’m neither able to deploy the image nor won’t the computers start if it’s set in bios to start from network (fog). When they start via fog I get to the meny, but then afterwards a black screen with a blue strip at the top saying rEFInd - Initializing, and nothing more. I’m guessing there is a file or something I have missed to move from the “old server” to the new one. (I do still have access to the old files If swap the SSDs for the HDDs). We have tried fully copying the FOG from the old to the new, but there were some issues because of different drive sizes and arrangements.

    Could someone please tell me what I have missed or what could be the issue now. Thank you!
    I’m sorry if I missed to specify something important, feel free to ask for any needed information.

    Thank you so much in advance!

    Kind regards,
    William Moliis

  • Get the latest news on what's happening.
    Security Advisories
    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.
    General Tutorials
    2k Topics
    19k Posts
    K

    @toalalife Hi there! Sorry for the late reply. I’ve been on holiday and I forgot to check up on this. That is interesting. There are a couple of things I can think of to double check/try off the top of my head.

    That particular error happens when iPXE can’t execute the binary, usually because either an architecture mismatch (e.g arm64 on x64) or because secboot fails to verify. Given that disabling secboot fixes it, I’m leaning towards that. (https://ipxe.org/err/2e0080)

    So I would say you should double check that your kernel is signed. If you’ve updated them you’ll have to resign the kernel to ensure it keeps working.

    The other would be to double check that the shim command is being invoked at some point prior to boot.php being chained. There’s a none zero chance that if you’ve updated FOG, it may have overwritten the modified default.ipxe

    Other than that, if you could try and record the boot process I’d be happy to take a look and see if I can spot anything out of the ordinary, I’m also happy to take a look at your kernel or any ipxe scripts etc if you want me to double check if they’re signed or bootable.

    As a final note, I don’t think I see iPXE loading the initrd.xz file there, which contains the ram filesystem that FOG uses on boot. I could be misremembering the boot process (I can’t recall if it’s normal for it to not do that if the bzImage fails to verify, or if it loads it prior to bzImage), but if that’s failing to load it might also be worth checking that out, though it shouldn’t have to be signed!

  • Report bugs, request features, or get the latest progress.
    General Feature Request Bug Reports
    2k Topics
    21k Posts
    M

    Okay - So what killled this installation was the fact a 1.5.9 csv load was imported into my 1.5.10.1698 FOG - this killed a bunch of features and I eded up having to reinstall.

133

Online

12.6k

Users

17.5k

Topics

156.4k

Posts