There is an esd file, I tried to convert it to vim to run. The result is a startup error. Tell me what am I doing wrong
Windows 7 AIO
https://www.dropbox.com/s/o7gngv8nf168d2...l.esd?dl=0

出现如下提示：
end Kernel panic - not syncing:Attempted to kill init!exit
请问是怎么回事呢？

I've booted "systemrescue-9.03-amd64.iso" many times with no problem on my Asus Rog Laptop.

I just changed the RAM (same size - just faster Ripjaws CL34 instead of stock CL40).  For what it is worth, the ram works fine, but not at the advertised speed (motherboard has no options to set CL, and seems to use old speeds instead... but I digress).

Since changing the RAM, I can no longer boot systemrescue-9.03-amd64.iso (I *can* boot a 32gb "dd" image of windows recovery - just not the iso) - it reports an out-of-memory problem, and returns to the ventoy menu.

How the brand of RAM might make any difference here I have no idea.

I created a whole new Ventoy USB and tried again (same problem).

If I change back to the old ram, I'll return here and let you know if it now works again.

I just did this, and it works:

In Windows 11, Start -> Recovery -> Create Recovery USB  (to make a 32gb USB stick)

In Linux (vmware in my case):-

dd if=/dev/sdb bs=8225280 of=Windows_Recovery.img

Mount the ventoy USB into linux, and copy the "Windows_Recovery.img" file onto it.

Reboot

TaDa!! (tested works) - I can now "restore my windows" (and run the recovery tools etc) from my external SSD!

I would like to be able to trigger ventoy installations/updates to USB devices via a script.

Are there command line options that would allow me to do this?

The new Linux distro experimental EasyOS can not be launched using Ventoy.  Here`s the feedback of the creator of Easy OS:

Quote:"What jumps out immediately in that photo is "mnt/zram0".

It seems that you haven't told the kernel where easy.sfs is.
From the photo, it has found initrd, but not easy.sfs.
The three files, vmlinuz, initrd and easy.sfs should all be together.
The kernel will use these parameters to find easy.sfs: specified on the kernel commandline, with "wkg_uuid=" and "wkg_dir=" parameters.
Instead of wkg_uuid, you could use "wkg_label=" or "wkg_dev="
In the latter case, if the working-partition is /dev/sdb2, then use "wkg_dev=sdb2".

But if you are booting from usb, then the drive letters may change, so best to use filesystem uuid or label.

So whatever bootloader you are using, you have specified where initrd is, but have not told the kernel where the ext4 working partition is (and where to find easy.sfs)."

Any idea when Super-UEFIinSecureBoot-Disk v3.4 will be reimplemented? It was the first and only time Ventoy worked on my laptop.

I'm working on building some custom tools built around wiping data and installing Windows 10 on laptops. Thankfully Ventoy has made this totally possible in an "All on one USB stick" method, but I am hoping to make the operation of the tool a bit more user-proof.

For information, here is my order of events:
1. Boot the laptop to the Ventoy drive.
2. Select to boot to a Linux Mint iso (we are just using the live disk environment at the moment)
    Ventoy handily injects script files we need to record information about the device, collect serial numbers, wipe SATA drives etc etc.
3. Reboot the computer to the Ventoy drive
4. Select to boot Windows 10 with an automated install.

I'm hoping there is a way that I can automate the movement between steps 2 and 4 above.

As in, I want to tell Ventoy to only boot to a certain option after I perform a task inside of the Linux Live Disk.

Initially, I was thinking I could edit the ventoy.json file from inside the live disk to adjust the available boot options and auto selection/timeout options (i.e. making Windows.iso select automatically after 1 second) however, trying to mount the Ventoy partition while inside the live disk has proven problematic.

Is there any recommendations about how I might be able to accomplish telling Ventoy to boot to certain .iso files based on various conditions?

My laptop Secure-Boot menus contain a few places that allow me to load the ventoy .cer file, which I did (it shows up with the name "grub").  I was a bit confused during the add process though, since it prompts me for a UUID number before allowing the add.

Anyhow - I still get the red "bad sig" error and it won't boot ventoy.

Does anyone have suggestions for how to get this to work?

If you need me to help get this working, I'm happy to do screenshots and experiments etc.

Hello forum,

is he Ventoy-stick strictly read-only (r/o), or could it happen, that a booted Linux-ISO does user the stick as Swap-device, or that it does write other things to the stick?


Thank's in advance!

Harry