At the same time, no matter what options I try, I get it out during the startup process
boot failed This system image failed to boot. and initfarms next, maybe this is the wrong way, but I can't come up with anything. Thank you so much for your help!
Hello,
I'm trying to start iventoy-1.0.20/iventoy.sh and get this error on Raspi running Debian 12 ARM:
env: „/root/lib/iventoy“: file or directory not found
Here's the complete output running # bash -x /opt/iventoy-1.0.20/iventoy.sh start:
+ PROC_ENV='env IVENTOY_API_ALL=1'
+ PROJ_DIR=/root
+ PROJ_EXEC=/root/lib/iventoy
+ PROJ_PID=/var/run/iventoy.pid
++ id -u
+ uid=0
+ '[' 0 -ne 0 ']'
+ '[' start = -A ']'
+ '[' start = -R ']'
+ echo start
+ grep -P -q '^(start|stop|status)$'
+ :
+ case "$1" in
+ start
+ local PID
+ local RETVAL
++ iventoy_get_running_pid
++ local PID
++ local FILE
++ '[' -f /var/run/iventoy.pid ']'
++ echo 0
+ PID=0
+ '[' 0 -ne 0 ']'
+ cd /root
+ env IVENTOY_API_ALL=1 /root/lib/iventoy
env: „/root/lib/iventoy“: Datei oder Verzeichnis nicht gefunden
+ RETVAL=127
+ '[' 127 -eq 0 ']'
+ echo 'iventoy start FAILED'
iventoy start FAILED
My use case for iVentoy is to manage and install Virtual Machines in my Hyper-V lab configuration. Unfortunately, everything I have tried with these Gen1 Hyper-V machines running a Legacy BIOS have been unsuccessful in booting iVentoy, I believe the issue is with iVentoy but I'm happy to troubleshoot further.
Additionally, I am able to EFI boot my iVentoy configuration on both my Hyper-V Gen2 Lab VMs, and my own personal computer outside of the lab environment is also able to EFI boot.
I've tried numerous options in the configuration, switching to a lower resolution, swapping to CLI - unfortunately does not work.
The iVentoy console is able to see the Hyper-V machine, but is not able to get past HTTP start 200 [/ipxe/01-00-15-5d-01-17-10]
The best description of the error message is " Could not configure console. " which when searching this forum, I did find some references to it with how the solution is compiled or something along those lines and some older devices losing compatibility along the way.
I believe this issue should be repeatable by anyone running Windows 10/11 Pro or above and using the Hyper-V service that is included with the Operating System to simply create a Gen1 Virtual Machine with any specs and attempting to LAN boot (assuming your machine is also bridged to your local network or able to connect to iVentoy depending on your network).
I've attached two screenshots - the machines that are mentioned in the console are both throw-away test Virtual Machines I've created under Hyper-V.
Edit 2: Here are some additional resources and reports I found on the forum of people reporting similar issues, I'd be very happy to assist in troubleshooting here and getting this resolved once and for all. https://forums.ventoy.net/showthread.php?tid=2636
Ventoy 1.0.97 is not working or booting on Dell Latitude 5440 laptops.
Is there any way to add support for new devices in a future update?
I use ventoy daily for work, that is until the latest Dells just came in.
Thank you,
I have installed Ventoy on one of my HDDs. I then partitioned the rest space and can boot different ISOs from Ventoy. So far so good.
Could Ventoy be used to boot a Debian Live Persistent set up?
There are certain aspects in the said page that needs to be addressed. For example,
Quote:We can use:
FAT partition with boot flag,
ext4 partition with label persistence. The label "persistence" is mandatory.
I will have to ask the Wiki editors as to why a FAT partition with boot flag will be a necessity, or whether a FAT partition will be mandatory, or any other partition, like the ext4 partition will also do.
BTW, there is a detailed page in Unix & Linux Stack Exchange with the topic: How to create a Debian live USB with persistence? which is very complex to execute for non-programmers who use computers for purpose other than hard core programming.
