| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 14,038
» Latest member: neofita
» Forum threads: 1,683
» Forum posts: 6,750
Full Statistics
|
| Online Users |
There are currently 425 online users. » 1 Member(s) | 419 Guest(s) Applebot, Baidu, Bing, Google, Yandex, Dannyvit
|
| Latest Threads |
安装Ventoy后U盘的Windows下面识别及其...
Forum: Ventoy Discussion Forum
Last Post: longpanda
Yesterday, 10:05 AM
» Replies: 1
» Views: 124
|
Installation instructions
Forum: Ventoy Discussion Forum
Last Post: PeterLinu
03-12-2026, 09:06 PM
» Replies: 0
» Views: 493
|
Best way to manage multip...
Forum: Ventoy Discussion Forum
Last Post: Epictetus77
03-04-2026, 09:44 PM
» Replies: 1
» Views: 749
|
Ventoy enroll key manager...
Forum: Ventoy Discussion Forum
Last Post: Epictetus77
02-12-2026, 06:09 AM
» Replies: 30
» Views: 94,560
|
Is it possible to view ot...
Forum: Ventoy Discussion Forum
Last Post: EtaBeta
02-07-2026, 01:57 AM
» Replies: 3
» Views: 1,569
|
Problems with running on ...
Forum: Ventoy Discussion Forum
Last Post: Morpho
02-05-2026, 11:54 AM
» Replies: 8
» Views: 27,625
|
ventoy运行windows系统镜像问题
Forum: Ventoy Discussion Forum
Last Post: hxpro
02-04-2026, 04:54 PM
» Replies: 1
» Views: 3,033
|
the potentail risk when u...
Forum: Ventoy Discussion Forum
Last Post: longpanda
02-03-2026, 01:58 AM
» Replies: 5
» Views: 4,299
|
[SOLVED] HDD Regenerator ...
Forum: Ventoy Discussion Forum
Last Post: Morpho
02-02-2026, 12:25 PM
» Replies: 9
» Views: 58,415
|
Some ISOs won't boot with...
Forum: Ventoy Discussion Forum
Last Post: Haubi
01-29-2026, 09:21 AM
» Replies: 1
» Views: 5,574
|
|
|
| 求助arm架构下报错,见正文 |
|
Posted by: loooong - 07-18-2023, 07:55 AM - Forum: Ventoy Discussion Forum
- Replies (1)
|
 |
纯小白一枚;求助各位大佬;电脑平台:麒麟990/9006c arm结构 属华为PC;系统镜像:UOSV20(1050)/KOS(2203),系统镜像使用ultalso刻录至U盘正常进入系统;ventoy制作好后 在X86架构 win系统镜像能正常进入引导并成功安装系统;但是在arm架构990/9006cCPU下面 进入后提示报错见附件;烦请有什么好的 解决方法
报错内容:Synchronous Exception at 0*0000000075dd22b0
|
|
|
| iVentoy 启动映射网络驱动器的问题 |
|
Posted by: Solin - 07-18-2023, 05:58 AM - Forum: iVentoy Discussion Forum
- Replies (32)
|
 |
iventoy 版本:1.0.14
启动 Windows 10 安装程序提示找不到介质,根据说明用 Shift+F10 打开命令行,发现网卡正常识别,查看日志发现日志里网卡未获取到IP地址,手工重新执行挂载命令能正常挂载 iso 到 Y:,测试环境的 DHCP 服务获取 IP 地址的时间比较长,怀疑是驱动加载后还未获取到IP地址即开始挂载 ISO 导致挂载失败,测试银河麒麟安装盘也有类似情况,不知是否能增加等待 DHCP 获取地址时间或者能自定义 IP 地址获取等待时间来规避这个问题。
|
|
|
| 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
|
|
|
|