ShredOS wont boot via PXE on Ryzen 5 and newer

[paddymccdrc]

Ive some strange issues with newer laptops and ShredOS and trying to boot via PXE.

A bit of background.... We have ShredOS image running on our PXE server which we use via ethernet cable to boot machines into and run the data destruction service on devices. It then saves reports and logs back onto the server so they are centralised for us to manage.

It works well however we are finding more and more issues with newer machines like Ryzen 5+ or I5-11th Gens for example where it fails to load and we receive the following message:

/kernels/shresos/osshred.... No such file or directory (https://ipxe.org/2d12608e)
Could not boot: no such file or directory (https://ipxe.org/2d12608e)

A workaround we had was to boot via USB stick with the server information and ShredOS config files being pulled in on boot but this is now failing on these newer machines. If you look at the below picture it sets the TFTP server information, waits for the ping from the server then fails.

These machines are all booting via UEFI with no ability to use legacy boot as its not available in BIOS.

Any ideas what this could be or what we could possibly be missing in settings etc?

Look forward to any help

[paddymccdrc]

heres what it looks like when it successfully loads on a machine and pulls in the ShredOS config and customer file from our server

[paddymccdrc]

We have made some progress on this and managed to get these newer ryzen machines to now boot ShredOS via PXE served via TFTP.

The problem were running into is getting ShredOS to load the nwipe_options files, it keeps timing out whch causes ShredOS to load without the config files.

Here is our IPXE setup:

:shredos
kernel tftp://192.168.56.100/kernels/osshred/shredos console=tty3 loglevel=3 shredos_config="tftp:192.168.56.100:/kernels/osshred/:shredos:shredos" shredos_output="tftp:192.168.56.100:/kernels/osshred/pdfs::no password:d" nwipe_options=" --nowait --method=zero --verify=off --noblank "
boot

When it runs on an older machine everything loads successfully as you can see in the image below:

[PartialVolume]

On the system with the network timeout, can you ping 192.168.52.100?

On the same machine, what's the output of ifconfig?

[paddymccdrc]

Ive booted them into tinylinux and attached some pics.

Im able to ping the server IP address fine

[PartialVolume]

No, I meant from ShredOS. Once ShredOS has booted and nwipe appears, ALT F2 to switch to the virtual terminal then type, ifconfig and try the ping. Also type lspci and post the output.

[paddymccdrc]

No, I meant from ShredOS. Once ShredOS has booted and nwipe appears, ALT F2 to switch to the virtual terminal then type, ifconfig and try the ping. Also type lspci and post the output.

Oops sorry i forgot about ALt F2!

Heres the information:

[PartialVolume]

Thanks, So we have the Realtek 8169/8168/8101/8125 ethernet support enabled, however we are missing the AMD IOMMU support.

I can build you an .img or .iso with AMD IOMMU support for you to test, if that's ok?

[PartialVolume]

Also, take a look in the bios and see if you can disable AMD-Vi or IOMMU and try it again. Ultimately though it would be better if you could try the version I'm building this evening. I'll post a link to it in an hour or so.

[PartialVolume]

ShredOS with AMD_IOMMU support.
.img
.iso

[paddymccdrc]

So far so good!

I had the opportunity to test it with a HP DL380 G10 server this evening that wasnt working with the old kernel.

The new bzImage set as kernel has worked and it has pulled in the customer list via TFTP.

Ill get the chance to test it with some newer AMD machines tomorrow