<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[The DDP package file was not found or could not be read]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/30416">@george1421</a> <a href="https://forums.fogproject.org/topic/16448/no-network-interfaces-found-dell-poweredge-r650-intel-e810-xxv" target="_blank" rel="noopener noreferrer nofollow ugc">helped</a> 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 <a href="https://github.com/FOGProject/fos/releases" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/FOGProject/fos/releases</a> but no joy.</p>
<p dir="auto">Server model: AS-3015MR-H8TNR<br />
Board model: 	H13SRD-F<br />
NIC model: AOC-S25GC-i2S / Intel E810-XXVAM2</p>
<p dir="auto">I get the following attempting to capture an image:</p>
<pre><code>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) ]---
</code></pre>
]]></description><link>http://forums.fogproject.org/topic/18087/the-ddp-package-file-was-not-found-or-could-not-be-read</link><generator>RSS for Node</generator><lastBuildDate>Tue, 10 Nov 2026 06:24:33 GMT</lastBuildDate><atom:link href="http://forums.fogproject.org/topic/18087.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 08 Jan 2026 21:47:14 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to The DDP package file was not found or could not be read on Sat, 17 Jan 2026 02:03:53 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/42840">@djgalloway</a> Just to add a bit of detail here. All of the work you did was on the iPXE side, which is great work by the way. The kernel driver I updated was after you select an FOG iPXE menu item that is when bzImage is loaded and run. It relies on kernel parameters that is provided by iPXE to find the root file system. This is technically what you fixed by ensuring that default.ipxe/boot.php from the fog server was being called. At the end of the day, I’m glad you got that working because your setup is definitely an edge case that works well in your environment.</p>
]]></description><link>http://forums.fogproject.org/post/157766</link><guid isPermaLink="true">http://forums.fogproject.org/post/157766</guid><dc:creator><![CDATA[george1421]]></dc:creator><pubDate>Sat, 17 Jan 2026 02:03:53 GMT</pubDate></item><item><title><![CDATA[Reply to The DDP package file was not found or could not be read on Fri, 16 Jan 2026 00:56:37 GMT]]></title><description><![CDATA[<p dir="auto">Here is the working config</p>
<pre><code># detect iPXE
dhcp-userclass=set:ipxe,iPXE
dhcp-match=set:ipxe,175

# FIRST STAGE: UEFI firmware -&gt; iPXE using SNP
dhcp-boot=tag:fog,tag:!ipxe,tag:!maas,snponly.efi,10.20.192.13,10.20.192.13

# SECOND STAGE: iPXE -&gt; FOG (give it the script directly)
dhcp-boot=tag:fog,tag:ipxe,tag:!maas,default.ipxe,10.20.192.13,10.20.192.13
</code></pre>
<p dir="auto">Factory default.ipxe.</p>
<p dir="auto">I think <em>deleting</em> autoexec.ipxe was the missing piece a la <a href="https://forums.fogproject.org/topic/17937/uefi-boot-kernel-panic-unable-to-mount-root-fs-on-dev-ram0/9?_=1768445663029" target="_blank" rel="noopener noreferrer nofollow ugc">https://forums.fogproject.org/topic/17937/uefi-boot-kernel-panic-unable-to-mount-root-fs-on-dev-ram0/9?_=1768445663029</a>?  Unfortunately, I tried so many different things that I am afraid to try to reproduce the failure and not be able to get back to a working state.</p>
<p dir="auto">Regardless, it was not a missing NIC driver as I originally suspected.  Thank you for your help nonetheless.</p>
]]></description><link>http://forums.fogproject.org/post/157760</link><guid isPermaLink="true">http://forums.fogproject.org/post/157760</guid><dc:creator><![CDATA[djgalloway]]></dc:creator><pubDate>Fri, 16 Jan 2026 00:56:37 GMT</pubDate></item><item><title><![CDATA[Reply to The DDP package file was not found or could not be read on Tue, 13 Jan 2026 21:54:09 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/30416">@george1421</a> Today’s findings:</p>
<ul>
<li>autoexec.ipxe is getting loaded by some default somewhere (not because of my dnsmasq entry) and it’s completely ignored.  None of its contents get run.  I confirmed the correct autoexec.ipxe file is actually being loaded by renaming it, attempting a boot, and observing a ‘file not found’ error message.</li>
<li>I pulled bzImage and init.xz directly from the latest release and N-1 <a href="https://github.com/FOGProject/fos/releases" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/FOGProject/fos/releases</a> to ensure compatibility.  No change.</li>
<li>This server’s NIC does not support the native iPXE drivers.  Only snponly.efi works.</li>
</ul>
<p dir="auto">No joy <img src="http://forums.fogproject.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f61e.png?v=7ddmg541643" class="not-responsive emoji emoji-android emoji--disappointed" style="height:23px;width:auto;vertical-align:middle" title=":(" alt="😞" /></p>
]]></description><link>http://forums.fogproject.org/post/157738</link><guid isPermaLink="true">http://forums.fogproject.org/post/157738</guid><dc:creator><![CDATA[djgalloway]]></dc:creator><pubDate>Tue, 13 Jan 2026 21:54:09 GMT</pubDate></item><item><title><![CDATA[Reply to The DDP package file was not found or could not be read on Tue, 13 Jan 2026 00:41:41 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/42840">@djgalloway</a> Well you have a pretty complex environment when you are chain loading other boot loaders. What I would do on a temporary debugging bases, update your dhcp server settings to use the fog server’s IP for dhcp option 66 and ipxe.efi for dhcp option 67. This will use a fog only solution. Something else that might cause the issue is that the linux kernel that is booting, is not the kernel shipped with FOG. Or the opposite, the init.xz image is not a FOG image. The fog developers compress the init.xz image with an uncommon (in regards to linux file systems) compressor, if the booting linux kernel doesn’t have that image decompressor built in you will get that error about unknown block (because its still compressed).</p>
<p dir="auto">It does look from your screen shot that both a bzImage and init.xz is being copied over to the target computer. Another but less likely issue could be that you are not using the custom ipxe.efi boot loader that was shipped with FOG.</p>
]]></description><link>http://forums.fogproject.org/post/157735</link><guid isPermaLink="true">http://forums.fogproject.org/post/157735</guid><dc:creator><![CDATA[george1421]]></dc:creator><pubDate>Tue, 13 Jan 2026 00:41:41 GMT</pubDate></item><item><title><![CDATA[Reply to The DDP package file was not found or could not be read on Mon, 12 Jan 2026 22:36:02 GMT]]></title><description><![CDATA[<p dir="auto">Hiya <a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/30416">@george1421</a>.  First, thanks for your time thus far and thank you for the background/context.  I truly was not aware the way we are using FOG was an edge case so I appreciate the extra help.</p>
<p dir="auto">I can confirm I’ve put the bzImage you provided in place but continue to hit the same screen.  Taking a step back, here is some additional context from my end:</p>
<ul>
<li>This is a new deployment and new environment.</li>
<li>I am using dnsmasq for DNS and DHCP on a server, “soko01” at 10.20.192.11</li>
<li>The rest of the servers of this type are still pointed at a MaaS instance so I have some chain loading going on in dnsmasq to target one server, “trial194” that I am attempting to capture a FOG image from.  The rest are still pointed at MaaS.</li>
<li>MaaS lives on soko02 at 10.20.192.12</li>
<li>FOG lives on soko03 at 10.20.192.13</li>
</ul>
<p dir="auto">Here is my dnsmasq conf</p>
<pre><code>##########################
### maas configuration ###
##########################

dhcp-match=set:pxearch0,option:client-arch,00:00
dhcp-match=set:pxearch7,option:client-arch,00:07
dhcp-match=set:pxearch10,option:client-arch,00:10
dhcp-match=set:pxearch9,option:client-arch,00:09
dhcp-match=set:pxearch8,option:client-arch,00:08
dhcp-match=set:pxearch13,option:client-arch,00:13
dhcp-match=set:pxearch0c,option:client-arch,00:0c
dhcp-match=set:pxearch0e,option:client-arch,00:0e
dhcp-match=set:pxearch1f,option:client-arch,00:1f
dhcp-match=set:pxearch20,option:client-arch,00:20
dhcp-match=set:pxearch11,option:client-arch,00:0b

dhcp-boot=tag:maas,tag:pxearch0,lpxelinux.0,soko02,10.20.192.12
dhcp-boot=tag:maas,tag:pxearch7,bootx64.efi,0.0.0.0,10.20.192.12
dhcp-boot=tag:maas,tag:pxearch10,http://10.20.192.12:5248/images/bootx86.efi,soko02,10.20.192.12
dhcp-boot=tag:maas,tag:pxearch9,bootx64.efi,0.0.0.0,10.20.192.12
dhcp-boot=tag:maas,tag:pxearch8,bootaa64.efi,0.0.0.0,10.20.192.12
dhcp-boot=tag:maas,tag:pxearch13,http://10.20.192.12:5248/images/bootaa64.efi,soko02,10.20.192.12
dhcp-boot=tag:maas,tag:pxearch0c,bootppc64.bin,soko02,10.20.192.12
dhcp-boot=tag:maas,tag:pxearch0e,pxelinux.0,soko02,10.20.192.12
dhcp-boot=tag:maas,tag:pxearch1f,boots390x.bin,soko02,10.20.192.12
dhcp-boot=tag:maas,tag:pxearch20,s390x_partition/maas,soko02,10.20.192.12
dhcp-boot=tag:maas,tag:pxearch11,http://10.20.192.12:5248/images/grubaa64.efi,soko02,10.20.192.12

#########################
### fog configuration ###
#########################

# FOG PXE (soko03 / 10.20.192.13)
# Detect iPXE
dhcp-userclass=set:ipxe,iPXE
dhcp-vendorclass=set:ipxe,iPXE
dhcp-match=set:ipxe,175

# FOG stage 1 (only if NOT already iPXE)
dhcp-boot=tag:fog,tag:!ipxe,tag:pxearch0,undionly.kpxe,soko03,10.20.192.13
dhcp-boot=tag:fog,tag:!ipxe,tag:pxearch0e,undionly.kpxe,soko03,10.20.192.13
dhcp-boot=tag:fog,tag:!ipxe,tag:pxearch7,snponly.efi,10.20.192.13,10.20.192.13
dhcp-boot=tag:fog,tag:!ipxe,tag:pxearch9,snponly.efi,10.20.192.13,10.20.192.13

# iPXE stage: set BOTH bootfile AND next-server
dhcp-boot=tag:fog,tag:ipxe,http://10.20.192.13/fog/service/ipxe/boot.php,soko03,10.20.192.13

# A MaaS-provisioned host
dhcp-host=set:maas,set:front,90:5a:08:77:62:02,10.20.193.193,trial193.front.sepia.ceph.com
# A FOG-provisioned host
dhcp-host=set:fog,set:front,90:5a:08:77:63:36,10.20.193.194,trial194.front.sepia.ceph.com
</code></pre>
<p dir="auto">The autoexec.ipxe file I am serving</p>
<pre><code>root@soko03:/var/www/html/fog/service/ipxe# cat /tftpboot/autoexec.ipxe 
#!ipxe
dhcp
chain http://10.20.192.13/fog/service/ipxe/boot.php || shell
</code></pre>
<p dir="auto">Here is the screen I am getting right before the <code>DDP package</code> error<br />
<img src="/assets/uploads/files/1768257258255-ikvm_capture3.jpg" alt="iKVM_capture3.jpg" class=" img-fluid img-markdown" /></p>
<p dir="auto">Which signals to me that it’s getting the bzImage file okay.  If I load <a href="http://10.20.192.13/fog/service/ipxe/boot.php" target="_blank" rel="noopener noreferrer nofollow ugc">http://10.20.192.13/fog/service/ipxe/boot.php</a>, it looks normal.</p>
<p dir="auto">What should I check next?</p>
]]></description><link>http://forums.fogproject.org/post/157734</link><guid isPermaLink="true">http://forums.fogproject.org/post/157734</guid><dc:creator><![CDATA[djgalloway]]></dc:creator><pubDate>Mon, 12 Jan 2026 22:36:02 GMT</pubDate></item><item><title><![CDATA[Reply to The DDP package file was not found or could not be read on Mon, 12 Jan 2026 22:09:28 GMT]]></title><description><![CDATA[<p dir="auto">As I was connecting the firmware to the kernel I thought to myself, it would be great to see the log files to see what firmware the nic needed. When I looked at the nic’s firmware directory there was only one file to I compiled it into kernel so I just added that file and moved on. While it was compiling I looked at the error again and came to the conclusion that the DPP package error is a bit of a red herring. While its an error that you will eventually have to deal with, it didn’t cause this specific error.</p>
<p dir="auto">The issue is the kernel panic unable to mount the root fs. Initializing the nic comes after the root fs (<a href="http://init.bz" target="_blank" rel="noopener noreferrer nofollow ugc">init.bz</a>) is mounted. Please verify that both bzImage (which is the kernel that is booting) and init.xz is being transferred via ipxe to the target computer. The kernel bzImage is having an issue mounting init.xz (root fs).</p>
<p dir="auto">Now with that said, here is a current kernel with the intel nic firmware included: <a href="https://drive.google.com/file/d/1rISBOUuqAlnV_cq9HZgsFdjfygpB4JLT/view?usp=drive_link" target="_blank" rel="noopener noreferrer nofollow ugc">https://drive.google.com/file/d/1rISBOUuqAlnV_cq9HZgsFdjfygpB4JLT/view?usp=drive_link</a></p>
]]></description><link>http://forums.fogproject.org/post/157733</link><guid isPermaLink="true">http://forums.fogproject.org/post/157733</guid><dc:creator><![CDATA[george1421]]></dc:creator><pubDate>Mon, 12 Jan 2026 22:09:28 GMT</pubDate></item><item><title><![CDATA[Reply to The DDP package file was not found or could not be read on Sat, 10 Jan 2026 15:54:46 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="http://forums.fogproject.org/uid/42840">@djgalloway</a> said in <a href="/post/157716">The DDP package file was not found or could not be read</a>:</p>
<blockquote>
<p dir="auto">The DDP package file was not found or could not be read. Entering Safe Mode</p>
</blockquote>
<p dir="auto">This specific issue is the default fog kernel doesn’t contain the required firmware that is required to communicate with your E810 network adapter.</p>
<p dir="auto">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).</p>
<p dir="auto">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.</p>
]]></description><link>http://forums.fogproject.org/post/157718</link><guid isPermaLink="true">http://forums.fogproject.org/post/157718</guid><dc:creator><![CDATA[george1421]]></dc:creator><pubDate>Sat, 10 Jan 2026 15:54:46 GMT</pubDate></item></channel></rss>