Fehlermeldungen im Protokoll nach Switch-Update


i-B4se

Recommended Posts

Mahlzeit,

 

ich habe gerade meine drei Switches geupdatet und dann wurden mir in Unraid folgende Fehlermeldungen im Protokoll hinterlegt:

Nov 26 16:15:54 NAS kernel: igb 0000:27:00.0 eth1: igb: eth1 NIC Link is Down
Nov 26 16:15:54 NAS kernel: igb 0000:26:00.0 eth0: igb: eth0 NIC Link is Down
Nov 26 16:15:54 NAS kernel: bond0: (slave eth1): speed changed to 0 on port 2
Nov 26 16:15:54 NAS kernel: bond0: (slave eth0): speed changed to 0 on port 1
Nov 26 16:15:54 NAS kernel: bond0: (slave eth0): link status definitely down, disabling slave
Nov 26 16:15:54 NAS kernel: bond0: now running without any active interface!
Nov 26 16:15:54 NAS kernel: bond0: (slave eth1): link status definitely down, disabling slave
Nov 26 16:15:54 NAS kernel: br0: port 1(bond0) entered disabled state
Nov 26 16:17:13 NAS  emhttpd: spinning down /dev/sdd
Nov 26 16:17:19 NAS  emhttpd: spinning down /dev/sdg
Nov 26 16:17:19 NAS  emhttpd: spinning down /dev/sdi
Nov 26 16:17:26 NAS kernel: pcieport 0000:00:01.2: PME: Spurious native interrupt!
Nov 26 16:17:26 NAS kernel: ------------[ cut here ]------------
Nov 26 16:17:26 NAS kernel: RTNL: assertion failed at net/core/dev.c (2891)
Nov 26 16:17:26 NAS kernel: WARNING: CPU: 0 PID: 20150 at net/core/dev.c:2891 netif_set_real_num_tx_queues+0x73/0x1ab
Nov 26 16:17:26 NAS kernel: Modules linked in: af_packet bluetooth ecdh_generic ecc xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_nat xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap ipvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod ipmi_devintf nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls igb ast drm_vram_helper drm_ttm_helper ttm drm_kms_helper drm ipmi_ssif amd64_edac edac_mce_amd edac_core kvm_amd wmi_bmof kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel backlight crypto_simd nvme agpgart cryptd i2c_piix4 i2c_algo_bit input_leds ahci syscopyarea sysfillrect rapl sysimgblt joydev led_class cdc_acm nvme_core libahci i2c_core k10temp ccp fb_sys_fops acpi_ipmi wmi ipmi_si button unix [last unloaded: igb]
Nov 26 16:17:26 NAS kernel: CPU: 0 PID: 20150 Comm: kworker/0:2 Not tainted 5.19.17-Unraid #2
Nov 26 16:17:26 NAS kernel: Hardware name: To Be Filled By O.E.M. X570D4U-2L2T/X570D4U-2L2T, BIOS L1.57 05/16/2022
Nov 26 16:17:26 NAS kernel: Workqueue: pm pm_runtime_work
Nov 26 16:17:26 NAS kernel: RIP: 0010:netif_set_real_num_tx_queues+0x73/0x1ab
Nov 26 16:17:26 NAS kernel: Code: 75 2a 80 3d c7 59 cb 00 00 75 21 ba 4b 0b 00 00 48 c7 c6 dd 2f 15 82 48 c7 c7 86 a5 0d 82 c6 05 ab 59 cb 00 01 e8 ed 11 15 00 <0f> 0b 8b b3 8c 03 00 00 89 ea 48 89 df e8 32 10 03 00 85 c0 0f 85
Nov 26 16:17:26 NAS kernel: RSP: 0018:ffffc9000469fd08 EFLAGS: 00010286
Nov 26 16:17:26 NAS kernel: RAX: 0000000000000000 RBX: ffff888131f28000 RCX: 0000000000000027
Nov 26 16:17:26 NAS kernel: RDX: 0000000000000001 RSI: ffffffff820d7be1 RDI: 00000000ffffffff
Nov 26 16:17:26 NAS kernel: RBP: 0000000000000004 R08: 0000000000000000 R09: ffffffff828653f0
Nov 26 16:17:26 NAS kernel: R10: 00003fffffffffff R11: ffff88903f33c06e R12: 0000000000000004
Nov 26 16:17:26 NAS kernel: R13: 0000000000000004 R14: ffff88810127b000 R15: ffff8884b38de800
Nov 26 16:17:26 NAS kernel: FS:  0000000000000000(0000) GS:ffff888ffe800000(0000) knlGS:0000000000000000
Nov 26 16:17:26 NAS kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 26 16:17:26 NAS kernel: CR2: 000000c000531000 CR3: 000000011eada000 CR4: 0000000000750ef0
Nov 26 16:17:26 NAS kernel: PKRU: 55555554
Nov 26 16:17:26 NAS kernel: Call Trace:
Nov 26 16:17:26 NAS kernel: <TASK>
Nov 26 16:17:26 NAS kernel: __igb_open+0x326/0x467 [igb]
Nov 26 16:17:26 NAS kernel: __igb_resume+0x1ce/0x213 [igb]
Nov 26 16:17:26 NAS kernel: ? pci_pm_default_resume_early+0x29/0x29
Nov 26 16:17:26 NAS kernel: __rpm_callback+0xce/0x13a
Nov 26 16:17:26 NAS kernel: ? pci_pm_default_resume_early+0x29/0x29
Nov 26 16:17:26 NAS kernel: rpm_callback+0x35/0x64
Nov 26 16:17:26 NAS kernel: rpm_resume+0x402/0x546
Nov 26 16:17:26 NAS kernel: ? process_one_work+0x1ab/0x295
Nov 26 16:17:26 NAS kernel: pm_runtime_work+0x5d/0x7f
Nov 26 16:17:26 NAS kernel: process_one_work+0x1ab/0x295
Nov 26 16:17:26 NAS kernel: worker_thread+0x18b/0x244
Nov 26 16:17:26 NAS kernel: ? rescuer_thread+0x281/0x281
Nov 26 16:17:26 NAS kernel: kthread+0xe7/0xef
Nov 26 16:17:26 NAS kernel: ? kthread_complete_and_exit+0x1b/0x1b
Nov 26 16:17:26 NAS kernel: ret_from_fork+0x22/0x30
Nov 26 16:17:26 NAS kernel: </TASK>
Nov 26 16:17:26 NAS kernel: ---[ end trace 0000000000000000 ]---
Nov 26 16:17:26 NAS kernel: ------------[ cut here ]------------
Nov 26 16:17:26 NAS kernel: RTNL: assertion failed at net/core/dev.c (2939)
Nov 26 16:17:26 NAS kernel: WARNING: CPU: 0 PID: 20150 at net/core/dev.c:2939 netif_set_real_num_rx_queues+0x61/0x83
Nov 26 16:17:26 NAS kernel: Modules linked in: af_packet bluetooth ecdh_generic ecc xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_nat xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap ipvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod ipmi_devintf nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls igb ast drm_vram_helper drm_ttm_helper ttm drm_kms_helper drm ipmi_ssif amd64_edac edac_mce_amd edac_core kvm_amd wmi_bmof kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel backlight crypto_simd nvme agpgart cryptd i2c_piix4 i2c_algo_bit input_leds ahci syscopyarea sysfillrect rapl sysimgblt joydev led_class cdc_acm nvme_core libahci i2c_core k10temp ccp fb_sys_fops acpi_ipmi wmi ipmi_si button unix [last unloaded: igb]
Nov 26 16:17:26 NAS kernel: CPU: 0 PID: 20150 Comm: kworker/0:2 Tainted: G        W         5.19.17-Unraid #2
Nov 26 16:17:26 NAS kernel: Hardware name: To Be Filled By O.E.M. X570D4U-2L2T/X570D4U-2L2T, BIOS L1.57 05/16/2022
Nov 26 16:17:26 NAS kernel: Workqueue: pm pm_runtime_work
Nov 26 16:17:26 NAS kernel: RIP: 0010:netif_set_real_num_rx_queues+0x61/0x83
Nov 26 16:17:26 NAS kernel: Code: 75 2a 80 3d ef 7a cb 00 00 75 21 ba 7b 0b 00 00 48 c7 c6 dd 2f 15 82 48 c7 c7 86 a5 0d 82 c6 05 d3 7a cb 00 01 e8 16 33 15 00 <0f> 0b 8b b3 04 03 00 00 89 ea 48 89 df e8 30 30 03 00 85 c0 74 af
Nov 26 16:17:26 NAS kernel: RSP: 0018:ffffc9000469fd20 EFLAGS: 00010282
Nov 26 16:17:26 NAS kernel: RAX: 0000000000000000 RBX: ffff888131f28000 RCX: 0000000000000027
Nov 26 16:17:26 NAS kernel: RDX: 0000000000000001 RSI: ffffffff820d7be1 RDI: 00000000ffffffff
Nov 26 16:17:26 NAS kernel: RBP: 0000000000000004 R08: 0000000000000000 R09: ffffffff828653f0
Nov 26 16:17:26 NAS kernel: R10: 00003fffffffffff R11: ffff88903f33ccd6 R12: 0000000000000000
Nov 26 16:17:26 NAS kernel: R13: 0000000000000001 R14: ffff88810127b000 R15: ffff8884b38de800
Nov 26 16:17:26 NAS kernel: FS:  0000000000000000(0000) GS:ffff888ffe800000(0000) knlGS:0000000000000000
Nov 26 16:17:26 NAS kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 26 16:17:26 NAS kernel: CR2: 000000c000531000 CR3: 000000011eada000 CR4: 0000000000750ef0
Nov 26 16:17:26 NAS kernel: PKRU: 55555554
Nov 26 16:17:26 NAS kernel: Call Trace:
Nov 26 16:17:26 NAS kernel: <TASK>
Nov 26 16:17:26 NAS kernel: __igb_open+0x343/0x467 [igb]
Nov 26 16:17:26 NAS kernel: __igb_resume+0x1ce/0x213 [igb]
Nov 26 16:17:26 NAS kernel: ? pci_pm_default_resume_early+0x29/0x29
Nov 26 16:17:26 NAS kernel: __rpm_callback+0xce/0x13a
Nov 26 16:17:26 NAS kernel: ? pci_pm_default_resume_early+0x29/0x29
Nov 26 16:17:26 NAS kernel: rpm_callback+0x35/0x64
Nov 26 16:17:26 NAS kernel: rpm_resume+0x402/0x546
Nov 26 16:17:26 NAS kernel: ? process_one_work+0x1ab/0x295
Nov 26 16:17:26 NAS kernel: pm_runtime_work+0x5d/0x7f
Nov 26 16:17:26 NAS kernel: process_one_work+0x1ab/0x295
Nov 26 16:17:26 NAS kernel: worker_thread+0x18b/0x244
Nov 26 16:17:26 NAS kernel: ? rescuer_thread+0x281/0x281
Nov 26 16:17:26 NAS kernel: kthread+0xe7/0xef
Nov 26 16:17:26 NAS kernel: ? kthread_complete_and_exit+0x1b/0x1b
Nov 26 16:17:26 NAS kernel: ret_from_fork+0x22/0x30
Nov 26 16:17:26 NAS kernel: </TASK>
Nov 26 16:17:26 NAS kernel: ---[ end trace 0000000000000000 ]---
Nov 26 16:17:29 NAS kernel: igb 0000:27:00.0 eth1: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Nov 26 16:17:29 NAS kernel: bond0: (slave eth1): link status definitely up, 1000 Mbps full duplex
Nov 26 16:17:29 NAS kernel: bond0: active interface up!
Nov 26 16:17:29 NAS kernel: br0: port 1(bond0) entered blocking state
Nov 26 16:17:29 NAS kernel: br0: port 1(bond0) entered forwarding state
Nov 26 16:17:30 NAS kernel: igb 0000:26:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Nov 26 16:17:30 NAS kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex

 

Ich meine, ja man sieht das der Link down ist etc., aber ist es normal das da CPU Warnungen rausgegeben werden?

 

Danke vorab!

Edited by i-B4se
Link to comment
  • 5 weeks later...

Das Problem besteht weiterhin.

Ich habe, da es ein Update für den Switch gab, diesen neu starten müssen und Unraid verliert danach die Verbindung bzw. baut diese nicht mehr richtig auf.

Der Switch zeigt nur noch eine 10 Mbit Up/Down an und erst nach einem Neustart vom Server ist die Verbindung wieder verfügbar. Ein anderer Port behebt das Problem ebenfalls nicht.

IPMI vom ASRock ist voll verfügbar und ich kann damit auch auf die Console zugreifen, sprich der Server läuft noch. Auch alle anderen Geräte am Switch sind erreichbar und machen keine Probleme.

Das ist definitiv nur bei dem Unraid-Server.

 

Kann man das Netzwerk von Unraid neu starten? Gibt es dafür einen Befehl?

Link to comment
4 minutes ago, mgutt said:

Dann wird das denke ich auch so sein, also vielleicht Kabel und/oder Buchse tauschen.

Schon getestet. Anderes Kabel von einem anderen Port der definitiv funktioniert, auch nach dem Neustart. 

 

4 minutes ago, mgutt said:

/etc/rc.d/rc.inet1 restart

Hab ich auch hier im Forum gefunden, aber dann kommt folgendes:

image.png.53cf15feb12d472de3c39266c62de80a.png

 

Unterm Strich muss ich den Unraid-Server neu starten um das Problem zu beheben.

Edited by i-B4se
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.