The DDP package file was not found or could not be read

[djgalloway]

@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) ]---

[george1421]

@djgalloway said in The DDP package file was not found or could not be read:

The DDP package file was not found or could not be read. Entering Safe Mode

This specific issue is the default fog kernel doesn’t contain the required firmware that is required to communicate with your E810 network adapter.

If I built a custom fog kernel for you in the past you already know this, but for the folks that find this post in the future… The fog developers in an effort to make a super fast imaging engine designed it using the 90/10 rule in that they will build a kernel for 90% of the deployments (which mean desktop computers) and leaving the rest for one-off builds. The supermicro servers or servers in general are in a different class than desktop/workstation computers. The desktop/workstation computers are pretty much the same even from different vendors. So the 90% rule has almost all of the hardware drivers built into the kernel. Servers class computers on the other hand have specialty components to aid in redundancy, performance, or monitoring (that other 10%) that are not typically found in the workstation class computers. Natively supporting that remaining 10% means almost doubling the size of the FOS engine kernel as well as having an impact on imaging speed. That is why the native FOS kernel doesn’t have every hardware driver built in. In your case the Intel E810 is a server class network adapter with QSFP28 ports (not something typically found in a workstation class computer).

With that said, I’m sure either the FOG kernel developers or I can create a one-off kernel for you. I will need to resetup my development environment because I just built a new linux server and haven’t move the files over from my old server, so it may take me a day or so to be in the position to create a current kernel with the required firmware built in for the nic.