Ventoy Forums › iVentoy General Use —— iVentoy 使用交流 › iVentoy Discussion Forum v
 iVentoy 启动映射网络驱动器的问题

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
 iVentoy 启动映射网络驱动器的问题
Solin Offline
Junior Member
**
Posts: 15
Threads: 2
Joined: Jul 2023
Reputation: 0
#1
07-18-2023, 05:58 AM
iventoy 版本：1.0.14
启动 Windows 10 安装程序提示找不到介质，根据说明用 Shift+F10 打开命令行，发现网卡正常识别，查看日志发现日志里网卡未获取到IP地址，手工重新执行挂载命令能正常挂载 iso 到 Y：，测试环境的 DHCP 服务获取 IP 地址的时间比较长，怀疑是驱动加载后还未获取到IP地址即开始挂载 ISO 导致挂载失败，测试银河麒麟安装盘也有类似情况，不知是否能增加等待 DHCP 获取地址时间或者能自定义 IP 地址获取等待时间来规避这个问题。
Find
Reply
longpanda Offline
Administrator
*******
Posts: 1,355
Threads: 84
Joined: Apr 2020
Reputation: 131
#2
07-18-2023, 03:59 PM
试试最新的 1.0.15 版本
Find
Reply
Solin Offline
Junior Member
**
Posts: 15
Threads: 2
Joined: Jul 2023
Reputation: 0
#3
07-19-2023, 01:45 AM (This post was last modified: 07-19-2023, 02:32 AM by Solin.)
(07-18-2023, 03:59 PM)longpanda Wrote: 试试最新的 1.0.15 版本

还是不行，启动时我发现出现安装界面的时间变长了（黑屏光标闪烁时间），脚本执行的时机不对？因为我命令行里看见系统都还未检测到网线已连接。

   
1.0.15 测试麒麟安装盘能正常进入安装界面了
Find
Reply
longpanda Offline
Administrator
*******
Posts: 1,355
Threads: 84
Joined: Apr 2020
Reputation: 131
#4
07-19-2023, 03:05 AM (This post was last modified: 07-19-2023, 03:18 AM by longpanda.)
脚本执行时机一直都是没变的，只是1.0.15 在脚本中增加了延时，最长30秒，不停的执行 ipconfig 和 ping ，看来在你这个环境上还是不行。
Find
Reply
longpanda Offline
Administrator
*******
Posts: 1,355
Threads: 84
Joined: Apr 2020
Reputation: 131
#5
07-19-2023, 03:07 AM
你图上 执行 ipconfig 开始显示网络无连接，后面能显示出来IP地址，这之间是有什么动作？ 还是只是等待了一段时间？
Find
Reply
Solin Offline
Junior Member
**
Posts: 15
Threads: 2
Joined: Jul 2023
Reputation: 0
#6
07-19-2023, 03:53 AM (This post was last modified: 07-19-2023, 03:57 AM by Solin.)
只是等了一段时间，脚本执行的时候网卡并未就绪，似乎网卡是在安装界面出现后才开始初始化的。
麒麟也是增加了延时？
Find
Reply
longpanda Offline
Administrator
*******
Posts: 1,355
Threads: 84
Joined: Apr 2020
Reputation: 131
#7
07-19-2023, 10:01 AM (This post was last modified: 07-19-2023, 10:03 AM by longpanda.)
你试试这个版本，我把时间放大到10分钟。你等待10分钟看看能不能连上，如果还连不上那你这个电脑应该有什么特殊之处，就用不了这个方案了。
正常只要网线连着，检测到网口有连接这个应该是很快的，最多获取IP地址慢。而你这个是一直显示没有连接状态（没插网线状态）。
https://www.123pan.com/s/rjSKVv-jriN.html提取码:YbeL

麒麟是Linux，Linux没有增加延时。这次的修改只针对Windows。
Find
Reply
lostbeing Offline
Junior Member
**
Posts: 2
Threads: 0
Joined: Jun 2023
Reputation: 0
#8
07-19-2023, 03:13 PM
使用的1.0.16
uos   kylin   deepin  还是无法引导
   
ubuntu  debian   centos  可以

附上deepin和ubuntu的日志

.zip   log.zip (Size: 1.83 KB / Downloads: 1)
Find
Reply
longpanda Offline
Administrator
*******
Posts: 1,355
Threads: 84
Joined: Apr 2020
Reputation: 131
#9
07-19-2023, 03:42 PM
(07-19-2023, 03:13 PM)lostbeing Wrote: 使用的1.0.16
uos   kylin   deepin  还是无法引导

ubuntu  debian   centos  可以

附上deepin和ubuntu的日志

UOS kylin deepin  如果最后是进入到 initramfs 的shell中，则在 initramfs 里面 执行 cat  /ventoy/log    命令，然后把结果拍照发过来看下。
Find
Reply
Solin Offline
Junior Member
**
Posts: 15
Threads: 2
Joined: Jul 2023
Reputation: 0
#10
07-20-2023, 12:49 AM (This post was last modified: 07-20-2023, 01:04 AM by Solin.)
(07-19-2023, 03:07 AM)longpanda Wrote: 你图上 执行 ipconfig 开始显示网络无连接，后面能显示出来IP地址，这之间是有什么动作？ 还是只是等待了一段时间？

(07-19-2023, 10:01 AM)longpanda Wrote: 你试试这个版本，我把时间放大到10分钟。你等待10分钟看看能不能连上，如果还连不上那你这个电脑应该有什么特殊之处，就用不了这个方案了。
正常只要网线连着，检测到网口有连接这个应该是很快的，最多获取IP地址慢。而你这个是一直显示没有连接状态（没插网线状态）。
https://www.123pan.com/s/rjSKVv-jriN.html提取码:YbeL

麒麟是Linux，Linux没有增加延时。这次的修改只针对Windows。

但 1.0.13，1.0.14 麒麟无法进入安装阶段，进入到 initramfs 
1.0.16 External 模式 前面不能正常进入安装阶段的 Win10 镜像正常了，但 ExternalNet 无法正常启动。

ExternalNet 模式下服务器端日志：

2023/07/20 00:38:36.318 [PXE] ===========================================================
2023/07/20 00:38:36.318 [PXE] iVentoy 1.0.16 [Linux 64] is running now ...
2023/07/20 00:38:36.318 [PXE] ===========================================================
2023/07/20 00:38:36.318 [TFTP] TFTP service is running ...
2023/07/20 00:38:36.590 [HTTP] API request: <{"method":"query_status"}>
2023/07/20 00:38:36.619 [HTTP] API request: <{"method":"sys_ip_list"}>
2023/07/20 00:38:36.629 [HTTP] API request: <{"method":"get_dhcp_mode"}>
2023/07/20 00:39:15.354 [HTTP] Client 172.20.25.10:50284 (62) read timeout (close), state=0
2023/07/20 00:39:19.519 [HTTP] Client 172.20.25.10:50285 (63) read timeout (close), state=0
2023/07/20 00:40:15.409 [HTTP] Client 172.20.25.10:50288 (64) read timeout (close), state=0
2023/07/20 00:40:19.129 [HTTP] Client 172.20.25.10:50301 (62) read timeout (close), state=0
2023/07/20 00:40:19.172 [HTTP] API request: <{"method":"sys_ip_list"}>
2023/07/20 00:40:19.191 [HTTP] API request: <{"method":"get_dhcp_mode"}>
2023/07/20 00:40:23.110 [HTTP] Client 172.20.25.10:50302 (63) read timeout (close), state=0
2023/07/20 00:41:15.465 [HTTP] Client 172.20.25.10:50305 (64) read timeout (close), state=0
2023/07/20 00:41:23.117 [HTTP] Client 172.20.25.10:50307 (62) read timeout (close), state=0
2023/07/20 00:41:24.129 [HTTP] Client 172.20.25.10:50310 (63) read timeout (close), state=0
2023/07/20 00:42:15.537 [HTTP] Client 172.20.25.10:50357 (64) read timeout (close), state=0
2023/07/20 00:42:23.134 [HTTP] Client 172.20.25.10:50358 (62) read timeout (close), state=0
2023/07/20 00:42:25.208 [TFTP] Parse tftp option(tsize,0)
2023/07/20 00:42:25.208 [TFTP] TFTP RRQ client 172.20.25.16:2070 download <iventoy_loader_16000> start ...
2023/07/20 00:42:25.208 [TFTP] DHCP ExternalNet client 172.20.25.16 should use loader ipxe.bios.0
2023/07/20 00:42:25.208 [TFTP] Start send file iventoy_loader_16000 to 172.20.25.16:2070 with blksize 512, has oack 1
2023/07/20 00:42:25.209 [TFTP] Recv an ERROR opcode pkt from client 172.20.25.16:2070.
2023/07/20 00:42:25.213 [TFTP] Parse tftp option(blksize,1456)
2023/07/20 00:42:25.213 [TFTP] TFTP RRQ client 172.20.25.16:2071 download <iventoy_loader_16000> start ...
2023/07/20 00:42:25.213 [TFTP] DHCP ExternalNet client 172.20.25.16 should use loader ipxe.bios.0
2023/07/20 00:42:25.213 [TFTP] Start send file iventoy_loader_16000 to 172.20.25.16:2071 with blksize 1456, has oack 1
2023/07/20 00:42:25.340 [TFTP] Finished send file to 172.20.25.16:2071 with blksize 1456 blks 92
2023/07/20 00:42:27.117 [HTTP] Client 172.20.25.10:50359 (63) read timeout (close), state=0
2023/07/20 00:43:06.044 [HTTP] DHCP external subnet mode invalid request <ipxe/01-00-1f-29-97-cf-dc>
2023/07/20 00:43:06.044 [HTTP] 404 </ipxe/01-00-1f-29-97-cf-dc>
2023/07/20 00:43:15.590 [HTTP] Client 172.20.25.10:50363 (64) read timeout (close), state=0
2023/07/20 00:43:23.149 [HTTP] Client 172.20.25.10:50364 (62) read timeout (close), state=0
2023/07/20 00:43:27.132 [HTTP] Client 172.20.25.10:50368 (63) read timeout (close), state=0
2023/07/20 00:43:45.833 [HTTP] 405 </ipxe>
2023/07/20 00:43:45.915 [HTTP] 405 </favicon.ico>
2023/07/20 00:44:00.977 [HTTP] DHCP external subnet mode invalid request <ipxe/01-00-1f-29-97-cf-dc>
2023/07/20 00:44:00.977 [HTTP] 404 </ipxe/01-00-1f-29-97-cf-dc>
2023/07/20 00:44:01.041 [HTTP] 405 </favicon.ico>
Find
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)