May 19, 20251 yr 如题，今天发现进webui 主界面的docker和vm卡很久才出来，网页一直转圈圈，卡很久才出来，单独点击docker或者vm也是一样，像断了网一样或者延迟很高，第一时间感觉是U盘坏了，因为之前也试过，但回家后立刻换了备用U盘上去，发现一样的情况。然后我不启动序列，就没卡了，排查了很久，没找到问题，我无意间看到卡webui可能跟内存有关系，我果断只用一条去试，还是一样，没办法了，我就试着清除CMOS了，然后启动后我发现 不卡了，非常丝滑。真的很奇葩啊。
May 22, 20251 yr Before you cleared the CMOS, did you happen to notice if the Date / Time on the server was completely wrong (by a large amount)?
June 10, 20251 yr Author On 5/22/2025 at 10:51 AM, Squid said:Before you cleared the CMOS, did you happen to notice if the Date / Time on the server was completely wrong (by a large amount)?I checked the timestamps in the logs, and the server time was correct. The same issue occurred again yesterday — the WebUI was very sluggish. This time, I took screenshots of the logs, and the error messages were the same as before.Instead of clearing the CMOS this time, I unplugged the power cord and removed all USB devices. After waiting for about three minutes, I powered it back on, and everything worked fine again.I’ve read some articles suggesting that this might be related to USB power delivery — since my Unraid system isn’t running 24/7, there might still be residual power supplied to the USB ports when it’s shut down. While this hasn’t been an issue before, I’m wondering if it could be related to a kernel update or bug?
June 13, 20251 yr Author On 5/22/2025 at 10:51 AM, Squid said:Before you cleared the CMOS, did you happen to notice if the Date / Time on the server was completely wrong (by a large amount)?Hello, the problem is still occurring. Whenever this USB error log appears, my WebUI becomes very laggy. I restarted and entered BIOS, and found that the system time is indeed different from the actual time. How can I resolve this issue? Also, I don't know what the device "usb2-2" is — could it be the PCI wireless network card on the motherboard? My motherboard model is MSI MAG B760M MORTAR WIFI DDR5.
June 19, 20251 yr On 2025/6/13 at PM11点14分, Yang0hui said:您好，问题仍然存在。每当出现这个 USB 错误日志时，我的 WebUI 就会变得非常卡。我重启电脑并进入 BIOS，发现系统时间确实与实际时间不同。我该如何解决这个问题？另外，我不知道“usb2-2”这个设备是什么——会不会是主板上的 PCI 无线网卡？我的主板型号是 MSI MAG B760M MORTAR WIFI DDR5。一模一样的问题！我的主板是微星660，你说的这两个问题我现在也一样，一是这个错误日志，只要你登录webui，这个错误日志就开始出现，关闭页面就不会有了。二就是页面的某些信息会卡住出不来，比如仪表盘的docker、vm信息，还有主界面的硬盘信息，全是空白，过很久才出现 Edited June 19, 20251 yr by daixuan201
June 26, 20251 yr On 6/19/2025 at 10:51 PM, daixuan201 said:一模一样的问题！我的主板是微星660，你说的这两个问题我现在也一样，一是这个错误日志，只要你登录webui，这个错误日志就开始出现，关闭页面就不会有了。二就是页面的某些信息会卡住出不来，比如仪表盘的docker、vm信息，还有主界面的硬盘信息，全是空白，过很久才出现是的，我也是开机有大概率，不显示 cpu占用信息和磁盘的使用情况，需要重启才能好。On 6/19/2025 at 10:51 PM, daixuan201 said:一模一样的问题！我的主板是微星660，你说的这两个问题我现在也一样，一是这个错误日志，只要你登录webui，这个错误日志就开始出现，关闭页面就不会有了。二就是页面的某些信息会卡住出不来，比如仪表盘的docker、vm信息，还有主界面的硬盘信息，全是空白，过很久才出现你好，我也是一样，开机时有大概率 cpu占用情况和磁盘使用情况无法显示，需要重启后才能显示
July 1, 20251 yr Author Solution 我先回个贴，我暂时的解决方案是，进到bois把usb3.0的第二号通道禁用。已经运行一个多星期，你们试试卸载connect 看看能不能解决这个问题
July 14, 2025Jul 14 On 7/1/2025 at 12:14 PM, Yang0hui said:我先回个贴，我暂时的解决方案是，进到bois把usb3.0的第二号通道禁用。已经运行一个多星期，你们试试卸载connect 看看能不能解决这个问题这个和 usb3.0的第二号通道，有什么关系？
July 14, 2025Jul 14 Jul 14 22:06:25 MyNAS nginx: 2025/07/14 22:06:25 [emerg] 10582#10582: bind() to 127.0.0.1:80 failed (98: Address already in use) Jul 14 22:06:25 MyNAS nginx: 2025/07/14 22:06:25 [emerg] 10582#10582: bind() to 192.168.1.216:80 failed (98: Address already in use) Jul 14 22:07:10 MyNAS publish: curl to devices failed Jul 14 22:07:10 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:11 MyNAS publish: curl to devices failed Jul 14 22:07:11 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:11 MyNAS publish: curl to parity failed Jul 14 22:07:11 MyNAS publish: curl to paritymonitor failed Jul 14 22:07:11 MyNAS publish: curl to fsState failed Jul 14 22:07:11 MyNAS publish: curl to mymonitor failed Jul 14 22:07:12 MyNAS publish: curl to devices failed Jul 14 22:07:12 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:13 MyNAS publish: curl to devices failed Jul 14 22:07:13 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:13 MyNAS publish: curl to temperature failed Jul 14 22:07:14 MyNAS publish: curl to devices failed Jul 14 22:07:14 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:14 MyNAS publish: curl to parity failed Jul 14 22:07:14 MyNAS publish: curl to paritymonitor failed Jul 14 22:07:14 MyNAS publish: curl to fsState failed Jul 14 22:07:14 MyNAS publish: curl to mymonitor failed Jul 14 22:07:15 MyNAS publish: curl to devices failed Jul 14 22:07:15 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:16 MyNAS publish: curl to devices failed Jul 14 22:07:16 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:17 MyNAS publish: curl to devices failed Jul 14 22:07:17 MyNAS publish: curl to arraymonitor failed这是我的报错日志信息 ， 一开始显示端口被占用，然后 cur 失败，面板信息无法显示，经常要 重启才能变好
July 17, 2025Jul 17 On 7/14/2025 at 10:32 PM, mobility said: Jul 14 22:06:25 MyNAS nginx: 2025/07/14 22:06:25 [emerg] 10582#10582: bind() to 127.0.0.1:80 failed (98: Address already in use) Jul 14 22:06:25 MyNAS nginx: 2025/07/14 22:06:25 [emerg] 10582#10582: bind() to 192.168.1.216:80 failed (98: Address already in use) Jul 14 22:07:10 MyNAS publish: curl to devices failed Jul 14 22:07:10 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:11 MyNAS publish: curl to devices failed Jul 14 22:07:11 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:11 MyNAS publish: curl to parity failed Jul 14 22:07:11 MyNAS publish: curl to paritymonitor failed Jul 14 22:07:11 MyNAS publish: curl to fsState failed Jul 14 22:07:11 MyNAS publish: curl to mymonitor failed Jul 14 22:07:12 MyNAS publish: curl to devices failed Jul 14 22:07:12 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:13 MyNAS publish: curl to devices failed Jul 14 22:07:13 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:13 MyNAS publish: curl to temperature failed Jul 14 22:07:14 MyNAS publish: curl to devices failed Jul 14 22:07:14 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:14 MyNAS publish: curl to parity failed Jul 14 22:07:14 MyNAS publish: curl to paritymonitor failed Jul 14 22:07:14 MyNAS publish: curl to fsState failed Jul 14 22:07:14 MyNAS publish: curl to mymonitor failed Jul 14 22:07:15 MyNAS publish: curl to devices failed Jul 14 22:07:15 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:16 MyNAS publish: curl to devices failed Jul 14 22:07:16 MyNAS publish: curl to arraymonitor failed Jul 14 22:07:17 MyNAS publish: curl to devices failed Jul 14 22:07:17 MyNAS publish: curl to arraymonitor failed这是我的报错日志信息 ， 一开始显示端口被占用，然后 cur 失败，面板信息无法显示，经常要 重启才能变好问题解决了，我在go文件启动http服务前面一行，加了一盒sleep 10.休眠10秒，到现在为止，没有遇到问题。
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.