Jazer

To me it seems also that having multiple timemachine backups on the same share is resposnible for this issue. Maybe also the mover mixes up stuff by destroying the integrity. I'm currently trying to use one machine per share, maybe this will be more stable. And yes - moving large amount of data (initial or large backups), lead to disconnectes.

+1 // Same here... Moved from OMV to unRAID and Timemachine is so unreliable. The good thing, I'm on a "trial" license and I will not purchase until this is fixed! Timemachine is one of the most important features for me. Any luck on fixing it?

/dev/sdc: ATA device, with non-removable media Model Number: WDC WD40EZRX-00SPEB0 Serial Number: WD-WCC4E1893XXX Firmware Revision: 80.00A80 Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0 Standards: Supported: 9 8 7 6 5 Likely used: 9 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 7814037168 Logical Sector size: 512 bytes Physical Sector size: 4096 bytes device size with M = 1024*1024: 3815447 MBytes device size with M = 1000*1000: 4000787 MBytes (4000 GB) cache/buffer size = unknown Nominal Media Rotation Rate: 5400 Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE Power-Up In Standby feature set * SET_FEATURES required to spinup after power up SET_MAX security extension * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * 64-bit World wide name * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Gen3 signaling speed (6.0Gb/s) * Native Command Queueing (NCQ) * Host-initiated interface power management * Phy event counters * NCQ priority information * READ_LOG_DMA_EXT equivalent to READ_LOG_EXT DMA Setup Auto-Activate optimization Device-initiated interface power management Software settings preservation * SMART Command Transport (SCT) feature set * SCT Write Same (AC2) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) unknown 206[13] (vendor specific) unknown 206[14] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase more than 508min for SECURITY ERASE UNIT. more than 508min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 50014ee2b4e61XXX NAA : 5 IEEE OUI : 0014ee Unique ID : 2b4e61XXX Checksum: correct This is the result of "hdparm -I /dev/sdc" for a 3,5" WDC Drive. At least power management seems to be supported. While this is a older drive, it also doesnt work on newer WD drives.

Yeah... I know about that. Even that isn't recommended, it still works for my usecase very well. I've a internal 2TB NVME Cache, which is basicly used and the Mover pushes the files to the Array with USB HDD's from time to time. Like I said, only the Standby handling with all my WD's (different Types) wont go to sleep (or can't provide the correct status). Maybe that's a known issue or even it's not unRAID related.

Hi, I've mixed configuration of disk... internal + USB and 3*Seagates + 3*WD. When I press "Spin down", all Seagates spin down, but all the WD still have a green orb. hdparm result for Seagate: /dev/sda: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 15 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 drive state is: standby hdparm result for WD: /dev/sde: SG_IO: bad/missing sense data, sb[]: f0 00 01 00 50 40 ff 0a 80 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 drive state is: unknown It seems to be a smart issue with DW drives. Is there a fix, how I can obtain the correct value for the WD drives?

You are right... I was not clear on this. Meanwhile there is also the plugin "RTL8152/3/4/6 USB Drivers", which is awesome and solved my issue. Please integrate support for RTL8156/b in the upcoming Unraid releases. Thx.

Ok... found out that the bond0 is using eth1 rather then eth0. Nevermind.

Thanks for providing the "RTL8152/3/4/6 USB Drivers" plugin. This is awesome! My USB RTL8156b is used as eth0 in a failover bond0 with an integrated 1Gbit LAN as eth1. The bond is set to active-backup... which leads to eth1 only usage. After investigating with iperf3, I found out that I've "retries" when using eth0 only. So if I disconnect eth1, eth0 works somehow fine (with reties) giving me abaout 1.7 Gbits/sec. As soon as I connect my eth1 again, I get 0.95 Gbits/sec provided by eth1. So it seams that I get drops on eth0 with RTL8156b. Is this a known issue? And how should I force the bon0 to use eth0 rather then eth1? Thx.

@ich777 Thanks for providing the plugin. This is awesome! Unfortunattely my network is not working. I've installed the plugin and followed the instructions, like adding... System shows: Bus 004 Device 002 Port 4-1 ID 0bda:8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G LAN I've also reboot more then twice. My eth0 shows: Settings for eth0: Supported ports: [ MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full 2500baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full 2500baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 100baseT/Full 1000baseT/Half 1000baseT/Full 2500baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 2500Mb/s Duplex: Full Auto-negotiation: on Port: MII PHYAD: 32 Transceiver: internal Supports Wake-on: pumbg Wake-on: g Current message level: 0x00007fff (32767) drv probe link timer ifdown ifup rx_err tx_err tx_queued intr tx_done rx_status pktdata hw wol Link detected: yes I get RX on ent0, but no TX. eth0 since 02/10/2023 rx: 864.70 KiB tx: 0 B total: 864.70 KiB monthly rx | tx | total | avg. rate ------------------------+-------------+-------------+--------------- Feb '23 864.70 KiB | 0 B | 864.70 KiB | 1 B/s ------------------------+-------------+-------------+--------------- estimated -- | -- | -- | daily rx | tx | total | avg. rate ------------------------+-------------+-------------+--------------- today 864.70 KiB | 0 B | 864.70 KiB | 11 B/s ------------------------+-------------+-------------+--------------- estimated -- | -- | -- | I'm using the latest Unraid. Any help on this?

Is there a post / documentation how to enable the RTL8125B in english? I know there is a chinese post, but even with google tanslate I feel somehow unsure to follow it. Maybe someone can summerize the required steps. Thx.

Same here. Any updates?