ceozero
-
Posts
17 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by ceozero
-
-
3 hours ago, ich777 said:
No, this is not possible in the debian-bullseye container or at least not how it ships OOB because it is not intended for that use case but you could maybe do that if you install everything that is needed.
You have to install all dependencies/packages to compile the Kernel first, after that you have to compile the driver, then you have to pack it and after that you have to place it in the correct directory on the USB Boot device.
Please also note that you have to do this each time you upgrade your Unraid version.
The point that I'm trying to make is that this is not practicable for most users.
Can't do anything about compilation.
Today I upgraded the debian kernel under esxi to 6.1, tried open source installation 525.116.04, it worked. Just simply use "./NVIDIA-Linux-x86_64-525.116.04.run -m=kernel-open", unfortunately, I can't use the latest 530 or 525 driver even after upgrading unraid to the beta version. Same kernel panic.
I can only temporarily relocate emby to debian, and continue to pay attention to this thread, until one day there will be a great master to solve this driver problem.
-
16 hours ago, ich777 said:
You can do it yourself, you'll find how I do it in my GitHub repo for the driver here: Click
don't know how to use this script, is there any documentation for reference? Can I run and compile it directly under unraid's ich777/debian-bullseye docker?
Or is it that the parameters I assigned are wrong?
DATA_DIR='/data'
NV_DRV_V='470.82.01'
UNAME='5.19.17'
LIBNVIDIA_CONTAINER_V='1.13.1'
CONTAINER_TOOLKIT_V='1.13.1'
thx
-
On 5/10/2023 at 12:28 AM, ich777 said:
As said above I think you have to add some parameters in ESXi so that newer cards are working, this is not the first time I see that.
Also please remove these two files from your modprobe.d folder: blacklist-nouveau.conf and nvidia.conf (why did you even do that?)
This is the part why it doesn't work:
0b:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) DeviceName: pciPassthru0 Subsystem: Shenzhen Colorful Yugong Technology and Development Co. TU116 [GeForce GTX 1660 SUPER] [7377:0000] Kernel driver in use: nvidia Kernel modules: nvidia_drm, nvidiaESXi does something to the device names and I think that was the issue the last time too.
The last user who reported that switched from ESXi to a native installation and it worked after that. Please also keep in mind that some hardware combinations and the 1660s series are complicated... at least on Linux.
Please look into the Visualizing Unraid subforums, there you should find the answer what you have to add to the ESXi host that the card will work without a Kernel Panic.
EDIT: I found that:
But there is nothing I can do about that since you are visualizing Unraid and this could cause issues, I also really can't help since I'm not familiar with ESXi (just search for ESXi in this thread and you will find a few posts, some even stating that drivers >=460 not working with ESXi).
grateful!
blacklist-nouveau.conf is a shielded driver that comes with esxi.
nvidia.conf is to set the PCI passthrough as the first choice.
After a few days of testing, I found out that this is not an esxi problem. It is not a question of whether to add parameters. I guess this should be some kind of limitation made by the nvidia driver,
I don't know how to use unraid to compile and install the driver, so I used esxi to virtualize a debian11, kernel 5.10.0-22-amd64, I downloaded countless nvidia drivers to compile and install for the kernel, and found the minimum version that can be used normally It's 470.82.01.Excuse me, is it possible to compile a 470.82.01 driver for our group of esxi users?
If not, is my only solution to fallback to unraid_6.9.2?
-
1 hour ago, ich777 said:
Have you yet tried to install the lagacy driver as mentioned above?
no work for v470
-
2 hours ago, ich777 said:
Have you yet tried to install the legacy driver version 470.xx, reboot and see if that version is working for you?
Can you please post the full Diagnostics?
When virtualizing via ESXi I think you have to add a parameter if I'm not mistaken so that newer cards will work.
Sorry, I can't output diagnostics with plugins installed. Because the nvidia-smi output is used for diagnostics. As long as nvidia-smi is used, it will be stuck. Cannot output diagnostics.
-
After updating from rtx750 to 1660s, it cannot be driven normally, and it cannot work after reinstalling or using a new system.
My unraid work has been under esxi for two years. I have always used rtx750 for emby, and now I can no longer drive it after updating to 1660s, nvidia-smi crashes directly, and the command freezes. It is also impossible to output the report, because nvidia-smi cannot output it.
QuoteMay 9 16:43:36 DELL-UNRAID root: plugin: nvidia-driver.plg installed May 9 16:44:13 DELL-UNRAID kernel: ACPI Warning: \_SB.PCI0.PE50.S1F0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20220331/nsarguments-61) May 9 16:44:13 DELL-UNRAID kernel: NVRM: GPU 0000:0b:00.0: RmInitAdapter failed! (0x26:0x56:1474) May 9 16:44:13 DELL-UNRAID kernel: BUG: unable to handle page fault for address: 0000000000004628 May 9 16:44:13 DELL-UNRAID kernel: NVRM: GPU 0000:0b:00.0: rm_init_adapter failed, device minor number 0 May 9 16:44:13 DELL-UNRAID kernel: #PF: supervisor read access in kernel mode May 9 16:44:13 DELL-UNRAID kernel: #PF: error_code(0x0000) - not-present page May 9 16:44:13 DELL-UNRAID kernel: PGD 0 P4D 0 May 9 16:44:13 DELL-UNRAID kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI May 9 16:44:13 DELL-UNRAID kernel: CPU: 41 PID: 8145 Comm: nv_queue Tainted: P O 5.19.17-Unraid #2 May 9 16:44:13 DELL-UNRAID kernel: Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.17369862.B64.2012240522 12/24/2020 May 9 16:44:13 DELL-UNRAID kernel: RIP: 0010:_nv010655rm+0x3b/0xb0 [nvidia] May 9 16:44:13 DELL-UNRAID kernel: Code: 93 be dd 02 48 8b bb 68 01 00 00 e8 7f cc 5a 00 85 c0 74 0b 48 83 c4 08 5b 41 5c c3 0f 1f 00 44 89 e7 e8 98 67 b6 ff 48 89 c7 <8b> 80 28 46 00 00 83 f8 01 74 38 80 bf 71 07 00 00 00 74 49 80 bf May 9 16:44:13 DELL-UNRAID kernel: RSP: 0018:ffffc9000ed77de0 EFLAGS: 00010246 May 9 16:44:13 DELL-UNRAID kernel: RAX: 0000000000000000 RBX: ffff888109322808 RCX: 0000000000000000 May 9 16:44:13 DELL-UNRAID kernel: RDX: ffffc9000ea11008 RSI: 0000000000000000 RDI: 0000000000000000 May 9 16:44:13 DELL-UNRAID kernel: RBP: ffff88a0c971b000 R08: 0000000000000000 R09: 0000000000000000 May 9 16:44:13 DELL-UNRAID kernel: R10: ffffc9000ed77e88 R11: 00000000645a07dd R12: 0000000000000000 May 9 16:44:13 DELL-UNRAID kernel: R13: ffff88a0c9718000 R14: ffff88810bf2d650 R15: ffff88a0c8890000 May 9 16:44:13 DELL-UNRAID kernel: FS: 0000000000000000(0000) GS:ffff88c0bd9c0000(0000) knlGS:0000000000000000 May 9 16:44:13 DELL-UNRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 9 16:44:13 DELL-UNRAID kernel: CR2: 0000000000004628 CR3: 000000001320a002 CR4: 00000000007706e0 May 9 16:44:13 DELL-UNRAID kernel: PKRU: 55555554 May 9 16:44:13 DELL-UNRAID kernel: Call Trace: May 9 16:44:13 DELL-UNRAID kernel: <TASK> May 9 16:44:13 DELL-UNRAID kernel: ? rm_execute_work_item+0xed/0x130 [nvidia] May 9 16:44:13 DELL-UNRAID kernel: ? _raw_q_schedule+0x69/0x69 [nvidia] May 9 16:44:13 DELL-UNRAID kernel: ? os_execute_work_item+0x48/0x88 [nvidia] May 9 16:44:13 DELL-UNRAID kernel: ? _main_loop+0xf1/0x115 [nvidia] May 9 16:44:13 DELL-UNRAID kernel: ? kthread+0xe4/0xef May 9 16:44:13 DELL-UNRAID kernel: ? kthread_complete_and_exit+0x1b/0x1b May 9 16:44:13 DELL-UNRAID kernel: ? ret_from_fork+0x1f/0x30 May 9 16:44:13 DELL-UNRAID kernel: </TASK> May 9 16:44:13 DELL-UNRAID kernel: Modules linked in: nvidia(PO) drm backlight xt_MASQUERADE ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod tcp_diag inet_diag efivarfs ip6table_filter ip6_tables iptable_filter ip_tables x_tables 8021q garp mrp bridge stp llc bonding tls crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl intel_cstate intel_uncore nvme i2c_piix4 intel_agp input_leds led_class e1000e intel_gtt nvme_core vmxnet3 i2c_core vmw_pvscsi agpgart ata_piix ac button unix May 9 16:44:13 DELL-UNRAID kernel: CR2: 0000000000004628 May 9 16:44:13 DELL-UNRAID kernel: ---[ end trace 0000000000000000 ]--- May 9 16:44:13 DELL-UNRAID kernel: RIP: 0010:_nv010655rm+0x3b/0xb0 [nvidia] May 9 16:44:13 DELL-UNRAID kernel: Code: 93 be dd 02 48 8b bb 68 01 00 00 e8 7f cc 5a 00 85 c0 74 0b 48 83 c4 08 5b 41 5c c3 0f 1f 00 44 89 e7 e8 98 67 b6 ff 48 89 c7 <8b> 80 28 46 00 00 83 f8 01 74 38 80 bf 71 07 00 00 00 74 49 80 bf May 9 16:44:13 DELL-UNRAID kernel: RSP: 0018:ffffc9000ed77de0 EFLAGS: 00010246 May 9 16:44:13 DELL-UNRAID kernel: RAX: 0000000000000000 RBX: ffff888109322808 RCX: 0000000000000000 May 9 16:44:13 DELL-UNRAID kernel: RDX: ffffc9000ea11008 RSI: 0000000000000000 RDI: 0000000000000000 May 9 16:44:13 DELL-UNRAID kernel: RBP: ffff88a0c971b000 R08: 0000000000000000 R09: 0000000000000000 May 9 16:44:13 DELL-UNRAID kernel: R10: ffffc9000ed77e88 R11: 00000000645a07dd R12: 0000000000000000 May 9 16:44:13 DELL-UNRAID kernel: R13: ffff88a0c9718000 R14: ffff88810bf2d650 R15: ffff88a0c8890000 May 9 16:44:13 DELL-UNRAID kernel: FS: 0000000000000000(0000) GS:ffff88c0bd9c0000(0000) knlGS:0000000000000000 May 9 16:44:13 DELL-UNRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 9 16:44:13 DELL-UNRAID kernel: CR2: 0000000000004628 CR3: 00000020d4442006 CR4: 00000000007706e0 May 9 16:44:13 DELL-UNRAID kernel: PKRU: 55555554
-
6 hours ago, surge said:
简单的操作方法就是：vps搭建好wireguard服务端，导出conf文件，然后在unraid导入conf文件，点击启动即可。不懂的话可以先上手熟悉一下wireguard。
谢谢，搭建好了，也用上了，请问你的unraid上用的是哪种模式。 是用 VPN tunneled access for system 这个么？
-
20 hours ago, surge said:
想了想折腾unraid的魔法上网有段时间了，尝试过如下方法
1. 修改网关（不够灵活）
2.安装v2ray代理软件，修改unraid的系统代理，通过v2ray来控制unraid开关魔法（还是感觉不够灵活）
3.买个国外的vps在上面搭建wireguard服务端，unraid刚好有个客户端，需要魔法的时候只需要开关vpn即可。
非常简单，非常灵活，非常优雅！
有详细操作吗？unraid的wireguard客户端是哪个？用的unraid的vpn管理器么？Tunnel wg0 ？
-
6.11.1使用后发现插件页面更新信息全部失效了。。。。其他正常。
-
On 11/5/2022 at 6:01 PM, JorgeB said:
You are having this issue:
https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-r2153/
Since we are still investigating what causes the problem if you want you can try downgrading to v6.10.3 to see if it's stable there.
The bios has been upgraded and returned to 6.10.3. At present, it has not crashed for several days. Everything is good...
I hope this bug can be fixed as soon as possible. thank.
-
1
-
-
1 hour ago, JorgeB said:
Errors 1 and 2 are a BIOS issue, looks for a BIOS update, error 3 seems like a problem with the syslog server configuration.
Unfortunately, I updated to the latest bios firmware when I returned to version 6.10.3.
If this is not a fatal mistake, I will ignore it.
thank you.
M/B: LENOVO 3135 版本 Not Defined - s/n:
BIOS: LENOVO Version M1UKT6EA. Dated: 10/06/2022
CPU: Intel® Core™ i9-9900T CPU @ 2.10GHz
-
2 hours ago, JorgeB said:
You are having this issue:
https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-r2153/
Since we are still investigating what causes the problem if you want you can try downgrading to v6.10.3 to see if it's stable there.
OK, I have returned to version 6.10.3,
But I still got some error logs,
Do I need to pay attention to them? Thank you, God
error 1
Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GPLD], AE_ALREADY_EXISTS (20210730/dswload2-326) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TPLD], AE_ALREADY_EXISTS (20210730/dswload2-326) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.GUPC], AE_ALREADY_EXISTS (20210730/dswload2-326) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.TUPC], AE_ALREADY_EXISTS (20210730/dswload2-326) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20210730/dswload2-326) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20210730/dswload2-326) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)error 2
Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: Aborting method \_SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: Aborting method \_SB.PR06._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: Aborting method \_SB.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: Aborting method \_SB.PR08._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI Error: Aborting method \_SB.PR09._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529) Nov 5 19:57:57 UNRAID-HOME kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)error 3
Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd/udp: socket 5: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd: socket 5: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Nov 5 19:57:57 UNRAID-HOME rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] -
19 hours ago, JorgeB said:
Enable the syslog server and post that after a crash.
There was no crash today, but there were 500 errors
-
P330 has been used under esxi for two years and has never died once,
Recently, I bought the unraid authorization and replaced it with unraid,
At present, the system crashes irregularly every day, about 8-10 hours.
It's so sad. have God to help me?
QuoteModel: Custom
M/B: LENOVO 3135 Version Not Defined - s/n:
BIOS:LENOVO Version M1UKT57A. Dated: 05/27/2020
CPU:Intel ® Core ™ i9-9900T CPU @ 2.10GHz
HVM: Enabled
IOMMU: Enabled
Cache: 512 KiB, 2 MB, 16 MB
Memory: 64 GiB DDR4 (maximum installable capacity 64 GiB *)
Network: bond0: fault tolerance (active backup), mtu 9000
Kernel: Linux 5.19.14-Unread x86_ sixty-four
OpenSSL:1.1.1q
Normal operation time: 11 minutes
unraid-home-syslog-20221104-0744.zip unraid-home-diagnostics-20221104-1528.zip
-
P330在esxi下用了两年从来没死过一次机，
最新买了unraid授权换成了unraid，
现在每天不定时死机，大概8-10个小时就会死机。
好难受的有大神帮忙瞅瞅么？
联想p330 tiny
Quote型号:Custom
M/B:LENOVO 3135 版本 Not Defined - s/n:
BIOS:LENOVO Version M1UKT57A. Dated: 05/27/2020
CPU:Intel® Core™ i9-9900T CPU @ 2.10GHz
HVM:已启用
IOMMU:已启用
缓存:512 KiB, 2 MB, 16 MB
内存:64 GiB DDR4 (最大可安装容量 64 GiB*)
网络:bond0: fault-tolerance (active-backup), mtu 9000
内核:Linux 5.19.14-Unraid x86_64
OpenSSL:1.1.1q
正常运行时间:11 分钟
unraid-home-syslog-20221104-0744.zip unraid-home-diagnostics-20221104-1528.zip
-
Any brother can help me?
I'm not sure if the kernel crashed.
But sometimes you can log in from the console after the crash. But you can't do anything.
QuoteOct 4 20:14:51 DELL-UNRAID kernel: CPU: 26 PID: 1916 Comm: kworker/26:1 Tainted: P O 5.10.28-Unraid #1 Oct 4 20:14:51 DELL-UNRAID kernel: Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.17369862.B64.2012240522 12/24/2020 Oct 4 20:14:51 DELL-UNRAID kernel: Workqueue: events macvlan_process_broadcast [macvlan] Oct 4 20:14:51 DELL-UNRAID kernel: RIP: 0010:__nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack] Oct 4 20:14:51 DELL-UNRAID kernel: Code: e8 dc f8 ff ff 44 89 fa 89 c6 41 89 c4 48 c1 eb 20 89 df 41 89 de e8 36 f6 ff ff 84 c0 75 bb 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 89 df 44 89 e6 31 db e8 6d f3 ff ff e8 35 f5 ff ff e9 22 01 Oct 4 20:14:51 DELL-UNRAID kernel: RSP: 0018:ffffc9000caf8dd8 EFLAGS: 00010202 Oct 4 20:14:51 DELL-UNRAID kernel: RAX: 0000000000000188 RBX: 000000000000c3c9 RCX: 00000000506806ee Oct 4 20:14:51 DELL-UNRAID kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffa01c3124 Oct 4 20:14:51 DELL-UNRAID kernel: RBP: ffff88816a511b80 R08: 0000000042a7b4bb R09: ffff88a5e088f580 Oct 4 20:14:51 DELL-UNRAID kernel: R10: 0000000000000000 R11: ffff88813070a400 R12: 000000000000e573 Oct 4 20:14:51 DELL-UNRAID kernel: R13: ffffffff8210b440 R14: 000000000000c3c9 R15: 0000000000000000 Oct 4 20:14:51 DELL-UNRAID kernel: FS: 0000000000000000(0000) GS:ffff88caa9600000(0000) knlGS:0000000000000000 Oct 4 20:14:51 DELL-UNRAID kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 4 20:14:51 DELL-UNRAID kernel: CR2: 000014749fcf9f28 CR3: 00000025ecd38004 CR4: 00000000007706e0 Oct 4 20:14:51 DELL-UNRAID kernel: PKRU: 55555554 Oct 4 20:14:51 DELL-UNRAID kernel: Call Trace:
(SOLVED) How to enable rsync function in unRAID
in General Support
Posted
mark .thk u