mwpmo

Members
  • Posts

    44
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mwpmo's Achievements

Rookie

Rookie (2/14)

4

Reputation

  1. This bug exists for nearly a year. Maybe it is now on the bottom of the priority debug list (or the bin😪)
  2. I hope they can fix the problem shortly, but I don't think they can. From the ONLY response from limetech on 21 May, I don't think they really know what the problem is and what is the root cause. Maybe they are bust dealing with other critical bugs, no other responses on this bug. Maybe there are only a small group of users using this USB 2.5Gb NIC. I reported the problem on 8156 USB NIC, but they just said maybe there is a problem in the another working 8125 NIC in my unRAID server. (I need to take out the m.2 SSD cache disk to install the mPCIe version of 8125 NIC) Quite disappointed cause several versions of 6.10 were released, but the problem has not been fixed.
  3. Just upgraded to 6.10.3, my RTL8156 USB 2.5G NIC still not working.
  4. Just upgraded to 6.10.2, my RTL8156 USB 2.5G NIC still not working. @zoggy My 8125 NIC (PCI device 0x10ec:0x8125 (r8169)), it run at 2.5GB FULL speed (nearly 300MB/s when I copying file to unRAID's SSD cache). BTW, this bug report is on RTL8156 USB 2.5GB NIC. For your problem in 8125, is it better to write a new bug report?
  5. Thanks a lot for your reply. Yes. Because the RTL8156 USB is not working. I installed a miniPCIe version of RTL8125 2.5GB NIC. (Total 4 NIC installed in server, 2 onboard R8169 NICs, 1 miniPCIe RTL8125 NIC and 1 USB RTL8156 NIC) I don't know RTL8125 used r8169 cause the UnRAID showing the speed at 2.5Gb speed and I can get a speed of nearly 270MB/s when I copying files to it. So I am sure my RTL8125 is running at 2.5Gb. Don't know what is the relationship between the the loading of r8169 driver in my RTL8125 and the missing RTL8156 USB NIC.
  6. Thanks a lot for your quick reply. Just submitted a bug report on this.
  7. [6.10 rc3 - 6.10.3] Realtek RTL8156 USB 2.5Gb NIC not working (since 6.10 rc3) Unraid found the device and list it in the System Devices page Bus 004 Device 002 Port 4-2 ID 0bda:8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G LAN But the NIC is not found in Network Setting page itmu-diagnostics-20220520-0705.zip
  8. Good to know that they will finally fix it. 👍 Cause the problem was already reported six months ago (since 6.10 rc3). Don't know why they take so long to fix it 😑
  9. Just updated to 6.10.0 release. My RTL8156 2.5Gb USB NIC is still not working ☹️😔
  10. Just updated to rc8. My RTL8156 2.5Gb USB NIC is still not working in rc8 ☹️
  11. I was a happy user of RTL8156 2.5Gb USB NIC (with around 280MB/s connection). However, since I upgraded to 6.10 rc3, unRAID cannot recognize it anymore and I have to switch back to slow on-board 1Gb NIC and the connection speed was decrease to around 120MB/s.. People here said the driver for RTL8156 were removed since rc3 and has already request limetech to add it back. So I wait and try rc4, rc5 and now rc7, the driver is still missing in the build. May I know why not to do so? And please put it back in future build.
  12. Just follow the instruction and the problem was fixed. Thanks a lot!
  13. HELP! Tons of UR kernel: REISERFS error What should I do to fix it? (unRAID 5.0 release) Last 15 line of syslog ===================== Nov 3 13:46:58 UR kernel: REISERFS error (device md17): vs-5150 search_by_key: invalid format found in block 146833420. Fsck? (Errors) Nov 3 13:46:58 UR kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 (Minor Issues) Nov 3 13:46:58 UR kernel: REISERFS error (device md17): vs-5150 search_by_key: invalid format found in block 146833420. Fsck? (Errors) Nov 3 13:46:59 UR shfs/user: shfs_read: read: (5) Input/output error (Errors) Nov 3 13:46:59 UR shfs/user: shfs_read: read: (5) Input/output error (Errors) Nov 3 13:46:59 UR kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 (Minor Issues) Nov 3 13:46:59 UR kernel: REISERFS error (device md17): vs-5150 search_by_key: invalid format found in block 146833420. Fsck? (Errors) Nov 3 13:46:59 UR kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 (Minor Issues) Nov 3 13:46:59 UR kernel: REISERFS error (device md17): vs-5150 search_by_key: invalid format found in block 146833420. Fsck? (Errors) Nov 3 13:47:00 UR shfs/user: shfs_read: read: (5) Input/output error (Errors) Nov 3 13:47:00 UR shfs/user: shfs_read: read: (5) Input/output error (Errors) Nov 3 13:47:00 UR kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 (Minor Issues) Nov 3 13:47:00 UR kernel: REISERFS error (device md17): vs-5150 search_by_key: invalid format found in block 146833420. Fsck? (Errors) Nov 3 13:47:00 UR kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 0 does not match to the expected one 1 (Minor Issues) Nov 3 13:47:00 UR kernel: REISERFS error (device md17): vs-5150 search_by_key: invalid format found in block 146833420. Fsck? (Errors)