cardo

Members
  • Posts

    119
  • Joined

  • Last visited

Posts posted by cardo

  1. On 12/21/2023 at 1:22 AM, cardo said:

    I have turned on syslog flash mirroring now, so the next time it occurs again I can post the logs. I'm starting to think that it is just getting to hot due to usage, maybe the logs will give some indication when it happens again.

    Hi @jinlife and @JorgeB. System locked up again today and it happened without any network usage to speak of. Here is the syslog that was captured on crash.

    syslog-previous

  2. 1 minute ago, jinlife said:

    Maybe you could post the diagnostics.

    Please take care of overheating issues with USB NICs when used heavily.

    Or maybe you can revert back to 6.12.4. 

    BTW: I'm using 2.5G NIC for months without reboot in 6.11.5.

    I have turned on syslog flash mirroring now, so the next time it occurs again I can post the logs. I'm starting to think that it is just getting to hot due to usage, maybe the logs will give some indication when it happens again.

  3. 1 minute ago, JorgeB said:

    Since v6.12.5 you can try the in tree driver for the 2.5GbE Realtek NIC, the plugin is now opcional, also enable the mirror to flash drive option in the syslog server and post that if it crashes again. 

    Thanks @JorgeB! After giving it some thought I'm starting to think that maybe the NIC is getting too warm and eventually causing the crash. It seems to occur after 12+ hours of constant usage. I'll set to mirror to flash though so I can get a good set of logs the next time it occurs. I'm not familiar what you mean by tree driver. Does that just mean that the support is now native and the plugin is no longer necessary?

  4. Hi All,

     

    I bought the following NIC a few months ago https://www.amazon.com/dp/B093FB9QWB?psc=1&ref=ppx_yo2ov_dt_b_product_details and I've been having nothing but problems with it since 6.12.5 was released. Initially it was a driver issue and then it was believed it was due to me using macvlan, but I remedied that and I'm still having a system freeze after several hours of pretty moderate network utilization. which leads to needing to power the system off and have to do a parity check since it is a dirty shutdownn. I have no idea if it is a hardware, driver or unRAID issue, but at this point I want to have something that supports 2.5Gbps or faster and is USB 3.0. I don't have an open slot on my motherboard.

     

    If anyone has any recommendations I would really appreciate it. Cost is no concern.

  5. On 12/13/2023 at 2:50 PM, cardo said:

    I just made the change. I'll report back if I have another system lockup. It generally happens within 24 hours. Thanks again!

    System just hard locked again. I have to power it down when this occurs. Just before it locked up I did see some some warning and errors related to the USB NIC about timeouts, etc. I stream music videos once a week from unRAID to my desktop PC. Both have 2.5Gbps cards. The desktop PC has an onboard NIC and unRAID has the RealTek external USB. The last time this occurred was also when I did 12+ hours of streaming.

     

    The issue started after 6.12.5, but I am not necessarily blaming unRAID or the NIC drivers it could very well be that the external NIC isn't good.

     

    Does anyone know of an external USB 2.5Gbps NIC that has built in unRAID support? I'm tired of fighting with the RealTek.

  6. 29 minutes ago, ich777 said:

    You have a macvlan trace in your syslog:

    Dec 12 22:17:53 MojoRyzen kernel: ------------[ cut here ]------------
    Dec 12 22:17:53 MojoRyzen kernel: NETDEV WATCHDOG: eth0 (r8152): transmit queue 0 timed out
    Dec 12 22:17:53 MojoRyzen kernel: WARNING: CPU: 20 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x14e/0x1c0
    Dec 12 22:17:53 MojoRyzen kernel: Modules linked in: xt_connmark xt_comment iptable_raw wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libchacha xt_mark tcp_diag udp_diag inet_diag veth macvlan xt_nat nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net tun vhost vhost_iotlb tap nvidia_uvm(PO) xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables bridge stp llc bonding tls r8152(O) igb i2c_algo_bit nvidia_drm(PO) nvidia_modeset(PO) edac_mce_amd edac_core intel_rapl_msr intel_rapl_common iosf_mbi kvm_amd nvidia(PO) kvm crct10dif_pclmul crc32_pclmul crc32c_intel video
    Dec 12 22:17:53 MojoRyzen kernel: ghash_clmulni_intel sha512_ssse3 sha256_ssse3 btusb sha1_ssse3 drm_kms_helper btrtl aesni_intel btbcm btintel input_leds crypto_simd wmi_bmof mxm_wmi cryptd drm bluetooth mpt3sas rapl nvme backlight syscopyarea k10temp raid_class hid_apple sysfillrect ahci sysimgblt ccp i2c_piix4 ecdh_generic scsi_transport_sas fb_sys_fops nvme_core ecc led_class libahci i2c_core tpm_crb tpm_tis tpm_tis_core tpm wmi button acpi_cpufreq unix [last unloaded: r8152(O)]
    Dec 12 22:17:53 MojoRyzen kernel: CPU: 20 PID: 0 Comm: swapper/20 Tainted: P           O       6.1.64-Unraid #1
    Dec 12 22:17:53 MojoRyzen kernel: Hardware name: To Be Filled By O.E.M. X570 Taichi/X570 Taichi, BIOS P5.00 10/19/2022
    Dec 12 22:17:53 MojoRyzen kernel: RIP: 0010:dev_watchdog+0x14e/0x1c0
    Dec 12 22:17:53 MojoRyzen kernel: Code: a4 c5 00 00 75 26 48 89 ef c6 05 a8 a4 c5 00 01 e8 59 23 fc ff 44 89 f1 48 89 ee 48 c7 c7 58 80 15 82 48 89 c2 e8 ab 73 93 ff <0f> 0b 48 89 ef e8 32 fb ff ff 48 8b 83 88 fc ff ff 48 89 ef 44 89
    Dec 12 22:17:53 MojoRyzen kernel: RSP: 0018:ffffc90000670ea8 EFLAGS: 00010282
    Dec 12 22:17:53 MojoRyzen kernel: RAX: 0000000000000000 RBX: ffff888106075448 RCX: 0000000000000003
    Dec 12 22:17:53 MojoRyzen kernel: RDX: 0000000000000104 RSI: 0000000000000003 RDI: 00000000ffffffff
    Dec 12 22:17:53 MojoRyzen kernel: RBP: ffff888106075000 R08: 0000000000000000 R09: ffffffff829513f0
    Dec 12 22:17:53 MojoRyzen kernel: R10: 00003fffffffffff R11: 2074696d736e6172 R12: 0000000000000000
    Dec 12 22:17:53 MojoRyzen kernel: R13: ffff88810607539c R14: 0000000000000000 R15: 0000000000000001
    Dec 12 22:17:53 MojoRyzen kernel: FS:  0000000000000000(0000) GS:ffff888ffed00000(0000) knlGS:0000000000000000
    Dec 12 22:17:53 MojoRyzen kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Dec 12 22:17:53 MojoRyzen kernel: CR2: 0000000000452b98 CR3: 0000000103894000 CR4: 0000000000350ee0
    Dec 12 22:17:53 MojoRyzen kernel: Call Trace:
    Dec 12 22:17:53 MojoRyzen kernel: <IRQ>
    Dec 12 22:17:53 MojoRyzen kernel: ? __warn+0xab/0x122
    Dec 12 22:17:53 MojoRyzen kernel: ? report_bug+0x109/0x17e
    Dec 12 22:17:53 MojoRyzen kernel: ? dev_watchdog+0x14e/0x1c0
    Dec 12 22:17:53 MojoRyzen kernel: ? handle_bug+0x41/0x6f
    Dec 12 22:17:53 MojoRyzen kernel: ? exc_invalid_op+0x13/0x60
    Dec 12 22:17:53 MojoRyzen kernel: ? asm_exc_invalid_op+0x16/0x20
    Dec 12 22:17:53 MojoRyzen kernel: ? dev_watchdog+0x14e/0x1c0
    ### [PREVIOUS LINE REPEATED 1 TIMES] ###
    Dec 12 22:17:53 MojoRyzen kernel: ? psched_ppscfg_precompute+0x57/0x57
    ### [PREVIOUS LINE REPEATED 1 TIMES] ###
    Dec 12 22:17:53 MojoRyzen kernel: call_timer_fn+0x6f/0x10d
    Dec 12 22:17:53 MojoRyzen kernel: __run_timers+0x144/0x184
    Dec 12 22:17:53 MojoRyzen kernel: ? tick_init_jiffy_update+0x7c/0x7c
    Dec 12 22:17:53 MojoRyzen kernel: ? update_process_times+0x7a/0x81
    Dec 12 22:17:53 MojoRyzen kernel: ? tick_sched_timer+0x43/0x71
    Dec 12 22:17:53 MojoRyzen kernel: ? __hrtimer_next_event_base+0x27/0x81
    Dec 12 22:17:53 MojoRyzen kernel: run_timer_softirq+0x2b/0x43
    Dec 12 22:17:53 MojoRyzen kernel: __do_softirq+0x129/0x288
    Dec 12 22:17:53 MojoRyzen kernel: __irq_exit_rcu+0x5e/0xb8
    Dec 12 22:17:53 MojoRyzen kernel: sysvec_apic_timer_interrupt+0x85/0xa6
    Dec 12 22:17:53 MojoRyzen kernel: </IRQ>
    Dec 12 22:17:53 MojoRyzen kernel: <TASK>
    Dec 12 22:17:53 MojoRyzen kernel: asm_sysvec_apic_timer_interrupt+0x16/0x20
    Dec 12 22:17:53 MojoRyzen kernel: RIP: 0010:cpuidle_enter_state+0x11d/0x202
    Dec 12 22:17:53 MojoRyzen kernel: Code: 2b ff 9f ff 45 84 ff 74 1b 9c 58 0f 1f 40 00 0f ba e0 09 73 08 0f 0b fa 0f 1f 44 00 00 31 ff e8 a3 c0 a4 ff fb 0f 1f 44 00 00 <45> 85 e4 0f 88 ba 00 00 00 48 8b 04 24 49 63 cc 48 6b d1 68 49 29
    Dec 12 22:17:53 MojoRyzen kernel: RSP: 0018:ffffc900001f7e98 EFLAGS: 00000246
    Dec 12 22:17:53 MojoRyzen kernel: RAX: ffff888ffed00000 RBX: ffff888109157000 RCX: 0000000000000000
    Dec 12 22:17:53 MojoRyzen kernel: RDX: 000009412b09c6cd RSI: ffffffff820d7e01 RDI: ffffffff820d830a
    Dec 12 22:17:53 MojoRyzen kernel: RBP: 0000000000000001 R08: 0000000000000002 R09: 0000000000000002
    Dec 12 22:17:53 MojoRyzen kernel: R10: 0000000000000020 R11: 000000000000afc8 R12: 0000000000000001
    Dec 12 22:17:53 MojoRyzen kernel: R13: ffffffff823237a0 R14: 000009412b09c6cd R15: 0000000000000000
    Dec 12 22:17:53 MojoRyzen kernel: ? cpuidle_enter_state+0xf7/0x202
    Dec 12 22:17:53 MojoRyzen kernel: cpuidle_enter+0x2a/0x38
    Dec 12 22:17:53 MojoRyzen kernel: do_idle+0x18d/0x1fb
    Dec 12 22:17:53 MojoRyzen kernel: cpu_startup_entry+0x2a/0x2c
    Dec 12 22:17:53 MojoRyzen kernel: start_secondary+0x101/0x101
    Dec 12 22:17:53 MojoRyzen kernel: secondary_startup_64_no_verify+0xce/0xdb
    Dec 12 22:17:53 MojoRyzen kernel: </TASK>
    Dec 12 22:17:53 MojoRyzen kernel: ---[ end trace 0000000000000000 ]---

     

     

    If you are using macvlan in your Docker settings please disable the Bridge in your Network settings, if you need the Bridge then please change to ipvlan in your Docker settings.

    Hi @ich777,

     

    Thank you for the quick response. I will admit I'm not entirely sure what the issue is here. I've been running this exact configuration for several years without issue. Was there a change in 6.12.5 or .6 that made my configuration an issue? Also, I currently swapped back to using my on board gigabit card and am not seeing any issues at all so far.

     

    I'm trying to figure out what I need to change.

     

    Thanks!

  7. Hi All,

     

    For the last several days I've had my unRAID lock up/go offline. Because of the lockup, I wasn't able to capture the syslog data, but I did notice that there were some no response type errors in eth0. Today while I was performing some file activity I lost my connection to the share, so I went to the syslog and captured a diagnostic. I do see a lot of errors. I'm not certain they are related to my RealTek device, but I thought I'd start here since the eth0 errors.

     

    I'm running 6.12.6 with the latest RealTek plugin and before 6.12.5 released, my system had been rock solid for years. Any help would be really appreciated.

    diagnostics-20231213-0649.zip

  8. Just now, itimpi said:

    You should download the zip file for the release and extract ALL the bz* type file overwriting those on the flash drive as described here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.  

    Hi,

     

    Thank you. I did just that and all is well again. I tried to delete the post since I resolved it on my own, but it didn't work.

  9. Hi All,

     

    Let me start by saying this is entirely my fault, but I desperately need help in getting my server back online. I was having driver issues for my NIC and decided to roll back to 6.12.4. the issue is that I had already upgraded to 6.12.6 and was only able to revert back to 6.12.5 in the GUI. I searched the forum and found a post that said that you should replace three files to go back to a prior version. the files that I replaced are as follows: bzroot, bzimage and bzroot-gui. I also included their accompanying hash files. The issue is that I replaced the 6.12.6 files with 6.12.4 files while the server was online.

     

    I removed the thumb drive from my unRAID server and placed it in another Windows machine and then attempted to copy back over the 6.12.6 files that I had over written with the earlier version. Unfortunately, I am still getting the checksum error, and based on a comment from another user, I may have made a horrible mistake by copying those files initially, while the server was running.

     

    Is there anyway for me to recover from this easily? Any help would be appreciated. Thank you in advance.

  10. 7 minutes ago, JorgeB said:

    You can copy if first you move the existing files, just don't overwrite them.

    Uh oh. Well that is a problem then. My internal USB with my original unRAID files, has a mixture of 6.12.6 and 6.12.4. I only copied bzroot, bzimage and bzroot-gui from 6.12.4.

     

    I just tried booting from the new media and it is still giving the checksum error even when disabling the internal media. I guess I'll pull the drive later and copy the 6.12.6 files back over the 6.12.4 files I mistakingly overwrote.

     

    Thanks again for the help.

  11. Just now, JorgeB said:

    With v6.12 you cannot replace the existing files with the server online, you can move those files to a different folder then copy the new ones.

    Ok, but if I boot from a newly created 6.12.6 media, will I be able to copy the files to the existing server drive inside my case or am I going to have to pull it? It's going to be a pain to do, so I'm hoping for a workaround.

  12. 34 minutes ago, JorgeB said:

    Thanks @ich777 and @jinlife, it works again.

    Hi @JorgeB,

     

    Thanks for testing this. As an somewhat unrelated aside, is there a way for me to replace the biz* files on my bootable unRAID USB drive without pulling the drive from the computer? I was attempting last night to roll back to 6.11 and was following instructions posted in the forum and apparently neglected to copy over all of the biz* files and now I am getting a checksum error. If I make new media can I boot to it and then copy the proper biz* files to the internal drive?

  13. Hi Everyone,

     

    I recently updated to 6.12.5 and my network stopped working. I have the following USB 2.5GB NIC https://www.amazon.com/gp/product/B093FB9QWB/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1, and was using the RTL8156(B) USB Drivers from user @jinlife. When starting up it would say that the eth0 interface was not found. I posted in the support thread and saw a recommendation to uninstall, reboot and then reinstall the driver and some code was updated. After rebooting the issue persisted even after a couple of reboots.

     

    I collected diagnostic logs and @jinlife pointed out in the system.log there was the following line:

     

    Dec  2 16:38:07 MojoRyzen kernel: igb 0000:08:00.0 eth123: renamed from eth0

     

    It was suggested that I copy a clean network.cfg from the installation media after renaming the existing one and I did that as well as replaced the network-rules.cfg and rebooted. It made no difference, but I collected a second set of logs just in case. I imagine if I can figure out what is renaming the interface and stop it, it will likely resolve the issue.

     

    The only thing I added software wise were the updates to 6.12.5 and 6.12.6 after .5 didn't help and .6 was released.  I have attached both sets of diagnostic logs if anyone can take a look.

     

    TIA!

    diagnostics-20231202-1639.zip diagnostics-20231202-2158.zip

  14. 2 hours ago, jinlife said:

    Maybe you can copy a brand new network.cfg file from unraid installer and overwrite yours in the config folder of the USB disk and then reboot. It will reset the network config and then you can start your experiment from the beginning. 

    Better to backup your entire USB disk before this in case any mistake happen.

    Yeah. I don't like the thought of doing that. I'll just look for a USB NIC with native support. Thanks anyway.

     

    EDIT: I tried this and it made no difference. I'll post in the support forum to see if I can figure out why eth0 is being renamed to eth122 when the USB NIC is made primary.

  15. Just now, jinlife said:

    The r8152/6 driver haven't been updated for months, it is still v2.17.1 version. It seems the card was driven succesfully.

    I can see in your log, the eth0 was changed to eth122, that is strange, please check whether some other plugin or configuration changed this.

     

    Dec  2 16:38:07 MojoRyzen kernel: r8152-cfgselector 4-3: reset SuperSpeed USB device number 2 using xhci_hcd
    Dec  2 16:38:07 MojoRyzen kernel: r8152 4-3:1.0 eth0: v2.17.1 (2023/06/13)
    Dec  2 16:38:07 MojoRyzen kernel: r8152 4-3:1.0 eth0: This product is covered by one or more of the following patents:
    Dec  2 16:38:07 MojoRyzen kernel:         US6,570,884, US6,115,776, and US6,327,625.
    Dec  2 16:38:07 MojoRyzen kernel: 
    Dec  2 16:38:07 MojoRyzen kernel: usbcore: registered new interface driver r8152
    Dec  2 16:38:07 MojoRyzen kernel: r8152 4-3:1.0 eth122: renamed from eth0

     

    To be honest it looked like it happened after me switching primary eth0 back and forth between the internal NIC and the USB one. I was also attempting to try different USB ports because I desperately wanted it to work. Is there any way for me to reset this so eth122 is removed?

  16. Hi,

     

    I have the following USB 2.5GB NIC https://www.amazon.com/gp/product/B093FB9QWB/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1, I was using your driver with success up until I updated to 6.12.5 and then it stopped working. When starting up it would say that the eth0 interface was not found. I saw the previous response about updating the driver, so I uninstalled the r8156 driver and then rebooted. I then downloaded the driver again and rebooted and the issue remained. I saw then there was an update to unRAID to 6.12.6 and I updated. The issue still remains

     

    I rebooted a number of times and it just won't work. I have attached the diagnostic logs.

    diagnostics-20231202-1639.zip

  17. Hi All,

     

    I purchased an ASUS USB-C2500 to replace my on board NIC. It is an external USB NIC. It shows up under system devices, But when I look at network settings only the onboard NIC appears. Do I need to take any other steps to make this work? There was something I read online that indicated you had to stop the array and then you could switch the MAC address, but because there is only one NIC showing up under network devices I'm assuming that won't work. Is there something I'm missing?

     

    Thanks in advance!