same problem here

I found the same when launching systemrescue-11.02-amd64.iso through Ventoy version 1.0.99. This issue didn't happen when launching systemrescue-11.01-amd64.iso through the same ventoy version.

I was wondering whether this issue had to do with SystemRescue itself and had nothing to do with Ventoy, so I created a bootable USB with SystemRescue version 11.01 and then with SystemRescue version 11.02. I downloaded systemrescue-11.01-amd64.iso and systemrescue-11.02-amd64.iso from https://sourceforge.net/p/systemrescuecd/activity/ . I could start systemrescue-11.01-amd64.iso (Experiment 1) and systemrescue-11.02-amd64.iso (Experiment 2) without any error, so it seems this issue has to do with Ventoy itself.

Experiment 1: Bootable thumb drive using SystemRescue 11.01

I created a bootable thumb drive with System Rescue 11.01 using the command below (note that I'm not using ventoy):

sudo wipefs -a /dev/sdf
sudo dd if=/home/rodrigo/Downloads/systemrescue-11.01-amd64.iso of=/dev/sdf status=progress

I plugged the thumb drive into my laptop and I turned it on. The SystemRescue menu was shown and I selected "Boot SystemRescue using default options". The shell [root@systemrescue ~]# was shown and no error showed up.

Experiment 2: Bootable thumb drive using SystemRescue 11.02

I created a bootable thumb drive with System Rescue 11.02 using the command below (note that I'm not using ventoy):

sudo wipefs -a /dev/sdf
sudo dd if=/home/rodrigo/Downloads/systemrescue-11.02-amd64.iso of=/dev/sdf status=progress

I plugged the thumb drive into my laptop and I turned it on. The SystemRescue menu was shown and I selected "Boot SystemRescue using default options". The shell [root@systemrescue ~]# was shown and no error showed up.

@rodrigomorales1 The cause is always Ventoy, by design. There is nothing to dwell on here.

SystemRescue is built on archiso, and there was an issue with booting Arch Linux before (#2825). The error messages in the screenshots in that issue look very similar to the error messages with SystemRescue.

xzcat fails, not easy to debug since the keyboard does not work

Confirming this issue persists with SystemRescue 11.03, released today.

Why wouldn't it? It's Ventoy that needs to be fixed, not SystemRescue.

The issue is critical. How to fix it?

If it is critical for you, I suggest that you use some other tool.

How to fix it? Examine how Ventoy handles archiso images and what has changed.

Easy2Boot uses grubfm to boot via UEFI and that works, If you want to use Ventoy, then a workaround is to add the grubfm_multiarch.iso to your Ventoy USB drive and boot to that and then select the Systemrescue iso,
This works best using an MBR Ventoy drive not a GPT Ventoy drive (with MBR partition 4 unused) so you can use the partnew boot option in grubfm and the ISO should be a contiguous file. But the 'boot from ISO' option in grubfm also works for me.
https://github.com/a1ive/grub2-filemanager/releases/tag/latest

On Ventoy boot menu, I have set vtbreak=12 on grub shell and then launched SystemRescue 11.03. Got this output:

For context, vtbreak=12 force ventoy to stop at following place and print ventoy log:
https://github.com/ventoy/Ventoy/blob/b11c38779d319fc6dde97e5e9a45b26e68ddd6e1/IMG/cpio/ventoy/init_chain#L181-L191C1

Following is the output when launching SystemRescue 11.01 with vtbreak=12, so we can compare:

On Ventoy boot menu, I have set vtbreak=12 on grub shell and then launched SystemRescue 11.03. Got this output: !

maybe the initrd is compressed with a new, unsupported xz option, and xzcat need to be updated

Just take a look at one of the earlier fixes and realize how fragile the entire design is.

xzcat fails while forcing xzminidec says xzminidec: Memory usage limit reached
maybe the initrd is too big

I've recompiled xzminidec giving more max dict size, and it works: 1 << 28 instead of 1 << 26