| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 13,625
» Latest member: r4nd0m486
» Forum threads: 1,672
» Forum posts: 6,720
Full Statistics
|
| Online Users |
There are currently 462 online users. » 0 Member(s) | 457 Guest(s) Applebot, Baidu, Bing, Google, Yandex
|
| Latest Threads |
Ventoy Linux still does n...
Forum: Ventoy Discussion Forum
Last Post: bahaedin
Yesterday, 10:05 AM
» Replies: 1
» Views: 208
|
Ventoy installation for o...
Forum: Ventoy Discussion Forum
Last Post: FroggieTheGremlin
10-23-2025, 01:09 PM
» Replies: 5
» Views: 307
|
Screen Resolution 800x600
Forum: Ventoy Discussion Forum
Last Post: fan_boy
10-20-2025, 08:32 PM
» Replies: 0
» Views: 160
|
Issues with windows vista...
Forum: Ventoy Discussion Forum
Last Post: johnson
10-19-2025, 04:10 PM
» Replies: 4
» Views: 10,742
|
Help $OEM$
Forum: Ventoy Discussion Forum
Last Post: venster
10-04-2025, 03:18 PM
» Replies: 2
» Views: 6,265
|
iso not working HP SSA Of...
Forum: Ventoy Discussion Forum
Last Post: rjc862003
09-30-2025, 02:02 AM
» Replies: 2
» Views: 8,580
|
Lost ISO partition
Forum: Ventoy Discussion Forum
Last Post: abba
09-29-2025, 12:05 PM
» Replies: 0
» Views: 964
|
Remove Version Number
Forum: Ventoy Discussion Forum
Last Post: XxJourdanYxX
09-26-2025, 06:42 AM
» Replies: 2
» Views: 9,197
|
Install Ventoy with a dat...
Forum: Ventoy Discussion Forum
Last Post: odie
09-25-2025, 03:14 PM
» Replies: 0
» Views: 1,332
|
big discussion on OpenSUS...
Forum: Ventoy Discussion Forum
Last Post: Dutchglory
09-21-2025, 12:44 AM
» Replies: 0
» Views: 2,827
|
|
|
| Experiencing red screen of death on boot |
|
Posted by: bootsie123 - 07-16-2023, 08:21 PM - Forum: iVentoy Discussion Forum
- Replies (5)
|
 |
Hi!
I'm trying to PXE boot into iVentoy from an HPE DL360 G6 and I keep on getting the red screen of death. As far as I can tell, everything is working correctly (meaning the server is getting an IP through DHCP from iVentoy and is able to communicate with it) until iVentoy serves the boot file which shows the list of bootable ISOs.
I'm not really sure where to begin debugging this so if anyone has any suggestions that would be great! Thanks!
iVentoy Logs:
Code: 2023/07/16 01:22:39.721 [DHCP] Proc DHCP DISCOVER pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:39.721 [DHCP] The client already exist, 192.168.3.200 1cc1-de6f-fa68 dhcp_rfc_proc_discover 1432
2023/07/16 01:22:39.721 [DHCP] Use the Last IP for PXE Client(1c-c1-de-6f-fa-68) in normal mode.
2023/07/16 01:22:39.722 [DHCP] Recv DHCP Discover from 1cc1-de6f-fa68, response DHCP OFFER with ip 192.168.3.200/255.255.255.0
2023/07/16 01:22:39.722 [DHCP] DHCP boot file is <ipxe.bios.0>
2023/07/16 01:22:44.774 [DHCP] Proc DHCP REQUEST pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:44.775 [DHCP] Recv DHCP Offer Request from 1cc1-de6f-fa68, response DHCP ACK
2023/07/16 01:22:44.775 [TFTP] Parse tftp option(tsize,0)
2023/07/16 01:22:44.775 [TFTP] TFTP RRQ client 192.168.3.200:2070 download <ipxe.bios.0> start ...
2023/07/16 01:22:44.775 [TFTP] Start send file ipxe.bios.0 to 192.168.3.200:2070 with blksize 512, has oack 1
2023/07/16 01:22:44.776 [TFTP] Recv an ERROR opcode pkt from client 192.168.3.200:2070.
2023/07/16 01:22:44.776 [TFTP] Parse tftp option(blksize,1456)
2023/07/16 01:22:44.776 [TFTP] TFTP RRQ client 192.168.3.200:2071 download <ipxe.bios.0> start ...
2023/07/16 01:22:44.776 [TFTP] Start send file ipxe.bios.0 to 192.168.3.200:2071 with blksize 1456, has oack 1
2023/07/16 01:22:44.802 [TFTP] Finished send file to 192.168.3.200:2071 with blksize 1456 blks 92
2023/07/16 01:22:53.009 [DHCP] Proc DHCP DISCOVER pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:53.009 [DHCP] The client already exist, 192.168.3.200 1cc1-de6f-fa68 dhcp_rfc_proc_discover 1432
2023/07/16 01:22:53.009 [DHCP] Use the Last IP for PXE Client(1c-c1-de-6f-fa-68) in normal mode.
2023/07/16 01:22:53.009 [PXE] Client 1c-c1-de-6f-fa-68 start PXE install in Legacy BIOS mode.
2023/07/16 01:22:53.009 [DHCP] Recv DHCP Discover from 1cc1-de6f-fa68, response DHCP OFFER with ip 192.168.3.200/255.255.255.0
2023/07/16 01:22:53.009 [DHCP] DHCP boot file is <http://192.168.3.15:16000/ipxe/01-1c-c1-de-6f-fa-68>
2023/07/16 01:22:54.002 [DHCP] Proc DHCP DISCOVER pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:54.002 [DHCP] The client already exist, 192.168.3.200 1cc1-de6f-fa68 dhcp_rfc_proc_discover 1432
2023/07/16 01:22:54.002 [DHCP] Use the Last IP for PXE Client(1c-c1-de-6f-fa-68) in normal mode.
2023/07/16 01:22:54.002 [PXE] Client 1c-c1-de-6f-fa-68 start PXE install in Legacy BIOS mode.
2023/07/16 01:22:54.002 [DHCP] Recv DHCP Discover from 1cc1-de6f-fa68, response DHCP OFFER with ip 192.168.3.200/255.255.255.0
2023/07/16 01:22:54.002 [DHCP] DHCP boot file is <http://192.168.3.15:16000/ipxe/01-1c-c1-de-6f-fa-68>
2023/07/16 01:22:56.034 [DHCP] Proc DHCP REQUEST pkt from client 1cc1-de6f-fa68
2023/07/16 01:22:56.034 [DHCP] Recv DHCP Offer Request from 1cc1-de6f-fa68, response DHCP ACK
2023/07/16 01:23:56.165 [HTTP] Client 192.168.3.200:34504 (51) timeout
RSOD:
|
|
|
| ER for 4K native support |
|
Posted by: VToy_Phan - 07-15-2023, 10:12 PM - Forum: Ventoy Discussion Forum
- No Replies
|
 |
Hello
Ventoy is a very good tool, but it would be excellent if it managed media in "advanced format", 4Kn (native 4K i.e. 4096 bytes for the size of the physical sectors, instead of 512 bytes) which is more than 12-year-old.
I had the problem with a JMicron 250GB USB SSD, it's quite frustrating.
"advanced format" (4Kn) is very common with recent SSD.
So, could you please record this ER ?
Is it a big workload ?
How long would it take to make a new release supporting 4Kn ?
I'd be happy to help by testing this new feature when ready.
Thanks.
VToy_Phan
|
|
|
iventoy does not start on Fedora 38 |
|
Posted by: bnsmb - 07-15-2023, 07:34 AM - Forum: iVentoy Discussion Forum
- Replies (3)
|
 |
Hi
iventoy 1.0.10 (like the preivous releases) does not start on my Thinkpad running Fedora 38:
Code: [xtrnaw7@t15g /tools/iventoy-1.0.10]$ date
Sat Jul 15 09:26:45 AM CEST 2023
[xtrnaw7@t15g /tools/iventoy-1.0.10]$ ls
data doc iso iventoy.sh lib log user
[xtrnaw7@t15g /tools/iventoy-1.0.10]$ ./iventoy.sh start
iventoy start SUCCESS PID=0
Please open your browser and visit http://127.0.0.1:26000 or http://x.x.x.x:26000 (x.x.x.x is any valid IP address)
[xtrnaw7@t15g /tools/iventoy-1.0.10]$ netstat -an | grep 26000
[xtrnaw7@t15g /tools/iventoy-1.0.10]$
[xtrnaw7@t15g /tools/iventoy-1.0.10]$ ps -ef | grep iventoy
xtrnaw7 1144458 48094 0 09:27 pts/7 00:00:00 grep --color=auto iventoy
[xtrnaw7@t15g /tools/iventoy-1.0.10]$
[xtrnaw7@t15g /tools/iventoy-1.0.10]$ cat log/log.txt
2023/07/14 07:43:49.830 [PXE] ### iVentoy start failed. ###
2023/07/14 07:45:07.491 [PXE] ### iVentoy start failed. ###
2023/07/14 07:45:09.783 [PXE] ### iVentoy start failed. ###
2023/07/14 07:45:42.791 [PXE] ### iVentoy start failed. ###
2023/07/15 09:26:08.041 [PXE] ### iVentoy start failed. ###
2023/07/15 09:26:28.333 [PXE] ### iVentoy start failed. ###
2023/07/15 09:26:33.840 [PXE] ### iVentoy start failed. ###
2023/07/15 09:26:56.634 [PXE] ### iVentoy start failed. ###
[xtrnaw7@t15g /tools/iventoy-1.0.10]$
Environment:
Code: [xtrnaw7@t15g /tools/iventoy-1.0.10]$ uname -a
Linux t15g.isbs.de 6.3.11-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Jul 2 13:17:31 UTC 2023 x86_64 GNU/Linux
[xtrnaw7@t15g /tools/iventoy-1.0.10]$ cat /etc/redhat-release
Fedora release 38 (Thirty Eight)
[xtrnaw7@t15g /tools/iventoy-1.0.10]$
There is not really much info in the log file and I can't find the reason in the output of strace (see the attachment)
Any clues?
regards
Bernd
|
|
|
| Can't launch Ventoy GUI 1.0.93 on Arch |
|
Posted by: webcaptcha - 07-15-2023, 04:23 AM - Forum: Ventoy Discussion Forum
- No Replies
|
 |
When I'm trying to launch Ventoy GUI I got an error
Code: Jul 14 21:27:04 home-laptop systemd[958]: Started Ventoy.
Jul 14 21:27:04 home-laptop krunner[13102]: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address
Any suggestions how to fix? Thanks.
|
|
|
| Request for removing libwim dependency |
|
Posted by: silent_x - 07-15-2023, 03:07 AM - Forum: iVentoy Discussion Forum
- Replies (5)
|
 |
First, I'd like to thank you for this PXE boot version ventoy. This is amazing!
I want to host iventoy on a openwrt x86 system. I got the glibc, libevent2 and etc installed. But still no way to makes it run iventoy. I ldd it and find it has a libwim dependency. But somehow I see a topic about no intention for supporting wim boot. So is it possbile to remove this dependency? Or please kindly provide suggestions on how to resolve this. Thanks. Heres my ldd output.
ldd iventoy
/lib64/ld-linux-x86-64.so.2 (0x7f26bc78c000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x7f26bc684000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x7f26bc67f000)
libevent-2.1.so.7 => /usr/lib/libevent-2.1.so.7 (0x7f26bc645000)
libevent_pthreads-2.1.so.7 => /usr/lib/libevent_pthreads-2.1.so.7 (0x7f26bc640000)
libdl.so.2 => /lib64/ld-linux-x86-64.so.2 (0x7f26bc78c000)
Error loading shared library libwim.so.15: No such file or directory (needed by iventoy)
libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7f26bc78c000)
libevent_core-2.1.so.7 => /usr/lib/libevent_core-2.1.so.7 (0x7f26bc61c000)
Error relocating iventoy: wimlib_decompress: symbol not found
Error relocating iventoy: g_tree_node_value: symbol not found
Error relocating iventoy: wimlib_free_decompressor: symbol not found
Error relocating iventoy: g_tree_node_first: symbol not found
Error relocating iventoy: wimlib_create_decompressor: symbol not found
Error relocating iventoy: g_tree_node_next: symbol not found
|
|
|
| Issue/Feature Request |
|
Posted by: markadms - 07-13-2023, 03:51 PM - Forum: iVentoy Discussion Forum
- Replies (1)
|
 |
First, thank you for this software, and for all of your hard work in improving it. I find it very useful.
The problem I have is with the unattended scripts. If I add an iso to iVentoy and click refresh under image management it clears out all of my added scripts for the isos. Also since you rapidly release new versions, unattended scripts have to be readded with each release.
After the second release I began to put my iso and scripts folder in the home folder and just create symbolic link in new releases to those folders. Would it be possible to have some kind of config file for the unattended scripts, similar to the json file we have in ventoy to help with this?
|
|
|
|