Categories

  • 12k Topics
    114k Posts
    D

    @george1421 helped build a custom kernel for me in the past and I’m wondering if I’ve hit a similar situation. This is a newer Supermicro platform. I pulled the latest bzImage and init.xz from https://github.com/FOGProject/fos/releases but no joy.

    Server model: AS-3015MR-H8TNR
    Board model: H13SRD-F
    NIC model: AOC-S25GC-i2S / Intel E810-XXVAM2

    I get the following attempting to capture an image:

    ice 0000:01:00.0: The DDP package file was not found or could not be read. Entering Safe Mode ice 0000:01:00.0: Fail during requesting FW: -2 ice 0000:01:00.1: The DDP package file was not found or could not be read. Entering Safe Mode ice 0000:01:00.1: Fail during requesting FW: -2 hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19) Kernel panic - not syncing: VFS: Unable to mount root fs on "/dev/ram0" or unknown-block(1,0) Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on "/dev/ram0" or unknown-block(1,0) ]---
  • 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
    K

    @Florent Thanks Florent. Hopefully it does!

    The issues I’ve listed here do seem to only affect older models of Dell, however UEFI (despite having the word unified in the name) varies wildly by vendor, and even within Vendors, so I wouldn’t be surprised to learn there are similar or different issues affecting newer Dells or even non-Dell machines.

    That said, based on my experience at work. I can’t say I’ve seen too many machines have the number of bizarre issues as I have seen with the older Dell PCs we have.

    As with all things, I’d suggest testing it on some of the machines common in your fleet of computers and seeing what works and what doesn’t.

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

    @Tom-Elliott Really for the purposes of user tracking. It is helpful for us to keep track of who is deploying and capturing. This is purely for transparency and accountability. I can instruct my team to always register devices they are imaging but I cannot force it.

    EDIT: Is there a way to force full reg prior to image deployment? Like a prereq for deployment.

111

Online

12.5k

Users

17.5k

Topics

156.1k

Posts