TaoR Posted February 21 Share Posted February 21 除非我手动强制重启,否则一直无法访问webui的界面 我该怎么解决。。。 Quote Link to comment
TaoR Posted February 21 Author Share Posted February 21 (edited) Feb 21 23:19:15 TaoR-unraid kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks Feb 21 23:19:15 TaoR-unraid kernel: ACPI: Early table checksum verification disabled Feb 21 23:19:15 TaoR-unraid kernel: xor: measuring software checksum speed Feb 21 23:19:15 TaoR-unraid kernel: BERT: [Hardware Error]: Skipped 1 error records Feb 21 23:19:15 TaoR-unraid kernel: usb 1-6: device descriptor read/64, error -71 Feb 21 23:19:15 TaoR-unraid kernel: usb 1-6: device descriptor read/64, error -71 Feb 21 23:19:15 TaoR-unraid kernel: usb 1-6: device descriptor read/64, error -71 Feb 21 23:19:15 TaoR-unraid kernel: usb 1-6: device descriptor read/64, error -71 Feb 21 23:19:15 TaoR-unraid kernel: usb 1-6: device not accepting address 4, error -71 Feb 21 23:19:15 TaoR-unraid kernel: usb 1-6: device not accepting address 5, error -71 Feb 21 23:19:15 TaoR-unraid kernel: floppy0: no floppy controllers found Feb 21 23:19:25 TaoR-unraid sshd[1232]: error: Bind to port 22 on 2408:822a:******* failed: Cannot assign requested address. Feb 21 23:19:25 TaoR-unraid sshd[1232]: Server listening on 192.168.31.10 port 22. Feb 21 23:19:25 TaoR-unraid ntpd[1286]: bind(19) AF_INET6 2408:822a:c610:1511::c2d#123 flags 0x11 failed: Cannot assign requested address Feb 21 23:19:25 TaoR-unraid ntpd[1286]: failed to init interface for address 2408:*****::c2d Feb 21 23:19:25 TaoR-unraid smbd[1361]: smbd_open_one_socket: open_socket_in failed: Cannot assign requested address Feb 21 23:19:25 TaoR-unraid smbd[1361]: smbd_open_one_socket: open_socket_in failed: Cannot assign requested address Feb 21 23:19:26 TaoR-unraid mcelog: failed to prefill DIMM database from DMI data Feb 21 23:19:39 TaoR-unraid sshd[1232]: Received signal 15; terminating. Feb 21 23:19:43 TaoR-unraid avahi-daemon[6349]: Failed to parse address 'fe80::cabf:4cff:fe1f:a57f%br0', ignoring. Feb 21 23:19:50 TaoR-unraid emhttpd: /mnt/disk4: autotrim setxattr error: No space left on device Feb 21 23:19:54 TaoR-unraid avahi-daemon[10648]: Failed to parse address 'fe80::cabf:4cff:fe1f:a57f%br0', ignoring. Feb 21 23:19:54 TaoR-unraid kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm Feb 21 23:20:17 TaoR-unraid root: Error response from daemon: network with name br0 already exists Feb 21 23:20:21 TaoR-unraid root: Error response from daemon: Pool overlaps with other one on this address space Feb 21 23:20:21 TaoR-unraid root: Error response from daemon: invalid subinterface vlan name vhost2, example formatting is eth0.10 Feb 21 23:20:21 TaoR-unraid kernel: BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm Feb 21 23:20:22 TaoR-unraid kernel: nvme 0000:03:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update Feb 21 23:20:22 TaoR-unraid kernel: nvme 0000:03:00.0: failed VPD read at offset 1 Feb 21 23:20:24 TaoR-unraid webGUI: Successful login user root from 192.168.31.99 崩溃前的日志 Edited February 21 by TaoR Quote Link to comment
cyeilo Posted February 23 Share Posted February 23 是否在启用了网口的桥接功能的同时在docker中使用了 macvlan的自定义网络? 如果是的话 可以看看这篇文章寻找适合你的解决办法 https://www.jackiewu.top/article/6.12.4-release-note Quote Link to comment
JackieWu Posted February 23 Share Posted February 23 On 2/21/2024 at 11:38 PM, TaoR said: 崩溃前的日志 请上传诊断信息资料,需要更多的信息才好判断是什么问题,方法参考: Quote Link to comment
TaoR Posted February 23 Author Share Posted February 23 5 hours ago, cyeilo said: 是否在启用了网口的桥接功能的同时在docker中使用了 macvlan的自定义网络? 如果是的话 可以看看这篇文章寻找适合你的解决办法 https://www.jackiewu.top/article/6.12.4-release-note 谢谢您的答复! 不过当我使用双网关方式解决时,我遇到了一个问题: 我的路由器非openwrt,仅有一个网关,使用双eth时第二个eth ip 无法设置。。重复时则无效 Quote Link to comment
TaoR Posted February 24 Author Share Posted February 24 16 hours ago, JackieWu said: 请上传诊断信息资料,需要更多的信息才好判断是什么问题,方法参考: 谢谢您! 日志服务器一直没明白怎么用,这回使用上了 报错日志在附件~~ syslog-127.0.0.1.log Quote Link to comment
TaoR Posted February 26 Author Share Posted February 26 On 2024/2/25 at PM3点49分, JackieWu said: 请重新上传诊断信息资料包 谢谢大佬! 已更新! syslog-127.0.0.1.log Quote Link to comment
TaoR Posted February 26 Author Share Posted February 26 (edited) 2024年2月25日下午3点49分,JackieWu说道: 请重新上传诊断信息资料包 2024年2月23日下午6点16分,cyeilo 说: 是否在启用网口的桥接功能的同时在docker中使用了macvlan的自定义网络? 如果是的话可以看看这篇文章寻找适合您的解决方法 https://www.jackiewu.top/article/6.12.4-release-note 谢谢两位大佬的帮助,突然想起来,我在上个版本6.12.6有过更新汉化包插件,把汉化包删除了之后,一切都正常了。。。 一个小时后又崩了....是我高兴太早了 Edited February 26 by TaoR Quote Link to comment
JackieWu Posted February 26 Share Posted February 26 1 hour ago, TaoR said: 谢谢大佬! 已更新! syslog-127.0.0.1.log 请到“工具 - 诊断”下载诊断资料,然后上传上来。 Quote Link to comment
TaoR Posted February 26 Author Share Posted February 26 28 minutes ago, JackieWu said: 请到“工具-诊断”下载诊断资料,然后上传上来。 taor-unraid-diagnostics-20240227-0149.zip syslog-127.0.0.1.log 已更新,谢谢! Quote Link to comment
Solution JackieWu Posted February 26 Solution Share Posted February 26 32 minutes ago, TaoR said: taor-unraid-diagnostics-20240227-0149.zip syslog-127.0.0.1.log 已更新,谢谢! Cache 缓存池可能有问题,不确定是不是 nvme 固态的硬件问题造成的,建议你先把 Cache 缓存池停用一段时间进行观察。 另外建议你可以尝试关闭或卸载 Cache Dirs 插件观察一段时间。 Quote Link to comment
TaoR Posted March 1 Author Share Posted March 1 (edited) On 2/27/2024 at 2:24 AM, JackieWu said: Cache 缓存池可能有问题,不确定是不是 nvme 固态的硬件问题造成的,建议你先把 Cache 缓存池停用一段时间进行观察。 另外建议你可以尝试关闭或卸载 Cache Dirs 插件观察一段时间。 十分感谢! 确实是固态的问题 并且smart 文件系统状态检查 读写测试等方式都检测不出来 只有重新格式化时,才能发现问题…… 固态是致态的2022款 tiplus5000 已经联系售后邮寄回去检测 Cache Dirs 插件 已经卸载 请问,这个插件不启用的话,影响大么,为防止重复问题发生,我打算不重装它了 谢谢您的支持! Edited March 1 by TaoR Quote Link to comment
JackieWu Posted March 1 Share Posted March 1 (edited) 56 minutes ago, TaoR said: 十分感谢! 确实是固态的问题 并且smart 文件系统状态检查 读写测试等方式都检测不出来 只有重新格式化时,才能发现问题…… 固态是致态的2022款 tiplus5000 已经联系售后邮寄回去检测 Cache Dirs 插件 已经卸载 请问,这个插件不启用的话,影响大么,为防止重复问题发生,我打算不重装它了 谢谢您的支持! 插件自身是没问题的,可能只是固态的问题而已。 你的日志文件里面重复出现了下面的这种情况:当出现 nvme0: I/O 问题的时候貌似系统就会停止反应(例如此时是 01:15),半个小时后(01:48) Cache Dir 插件开始运行。这种情况日志里面出现了好几处,所以才认为是固态的问题。 就目前我接触到的 NVME 固态引起的问题,大多都是固态主控方面的原因(例如 Unraid 不兼容),比如说这个案例: 所以如果读者怀疑是固态的问题,那么可以考虑更换 Unraid 版本(更换内核版本)或者升级固态主控驱动(例如上面的例子)。 Edited March 1 by JackieWu Quote Link to comment
TaoR Posted March 1 Author Share Posted March 1 1 hour ago, JackieWu said: 插件自身是没问题的,可能只是固态的问题而已。 你的日志文件里面重复出现了下面的这种情况:当出现 nvme0: I/O 问题的时候貌似系统就会停止反应(例如此时是 01:15),半个小时后(01:48) Cache Dir 插件开始运行。这种情况日志里面出现了好几处,所以才认为是固态的问题。 就目前我接触到的 NVME 固态引起的问题,大多都是固态主控方面的原因(例如 Unraid 不兼容),比如说这个案例: 所以如果读者怀疑是固态的问题,那么可以考虑更换 Unraid 版本(更换内核版本)或者升级固态主控驱动(例如上面的例子)。 十分感谢您的讲解~~ Quote Link to comment
Recommended Posts
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.