Abzstrak

yeah the slots dont matter in the long run, ill leave it alone... now i recall why i left it like this I think I'll just replace the cable, rebuild to it and see what happens.

Yeah I moved around drives a lot previously (when upgrading from smaller drives), but didn't bother trying to fix the enumeration since it didn't affect anything. This might be a good reason to go ahead and do that.

sry, just added that

Im trying to figure this out, this drive has a few more months of warranty. If anyone can assist that would be great as I'm unsure if this is a real problem or maybe a cable or something? The drive was disabled by unraid automatically and is showing errors, however smart reports look ok i think other than 9800+ udma crc errors which i suspect are cable related?. Attached is a screenshot of the 295052 errors on the web gui, I'm also attaching the smart report. Also, whats the path forward here? I'm leaning towards swapping he cable and wiping out the drive and letting it rebuild. -- [edit] replacing the cable seems to have resolved this problem... 16TB takes a while, but everything is working well without issue now. [/edit]

i dunno, i have two onboard intel 1g NICs, I just set them up in LACP for again and its stable...I've no issue with this system for years, its an older i9 9900. I wish I had a way to get a faster NIC though, my own real avenue is the usb 3.1 gen2 ports..... oh well. The USB adapter seems fine on Arch though

nope, made it alittle over an hour before hard locking the whole system again...

Yeah I'm using a USB, i had no other viable options... I wouldnt use realtek otherwise :) i just went ahead and uninstalled, rebooted, reinstalled, rebooted, set as eth0, rebooted.... iperf is currently showing showing around 4.8GBps in my quick tests to me machine with a 10g fiber intel nic, which sounds good. I think I installed the driver some time ago and didnt manually update (do we need to)? it was probably before updating to unraid 7 anyway, its running at the moment, I'm not trusting it yet to not lock up as before, but maybe it will be fine now, i dont know.

yeah looking at the github, the 8152 driver does seem to be 2.20.1

maybe im wrong or confused with the version numbers? but Realtek lists 2.20.1 released on May 23 2025. https://www.realtek.com/Download/List?cate_id=585

same Here, the driver is too old. I need to figure out how to manually install too as the one in the current package would make my unraid box lockup with 30 minutes.

so im upgrading my network, and i have my unraid server (yes i need to update it) and it only has an onboard 1G and no slots available, so.... I decided to try a USB Realtek 8157 5GBps NIC in it. ok, so I loaded up the drivers in the app store and stuck what they said at the bottom of the go file ('ethtool -s eth0 autoneg on advertise 0x180000000002f') however it is only connecting at 2.5GBps. I know the switch and the SFP in there will handle 5gig, as i had no problem with my laptop using that same hardware (Arch Linux) I dont think it's advertising 5GBps as an option to the switch based on the below advertised link modes.) Anyone have any ideas? ethtool shows this (sorry, formatting is screwed up a bit): Settings for eth0: Supported ports: [ MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full 2500baseT/Full 5000baseT/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: 1000baseT/Full 2500baseT/Full 5000baseT/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: d 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

so im upgrading my network, and i have my unraid server (yes i need to update it) and it only has an onboard 1G and no slots available, so.... I decided to try a USB Realtek 8157 5GBps NIC in it. ok, so I loaded up the drivers in the app store and stuck what they said at the bottom of the go file ('ethtool -s eth0 autoneg on advertise 0x180000000002f') however it is only connecting at 2.5GBps. I know the switch and the SFP in there will handle 5gig, as i had no problem with my laptop using that same hardware (Arch Linux) I dont think it's advertising 5GBps as an option to the switch based on the below. Anyone have any ideas? ethtool shows this (sorry, formatting is screwed up a bit): Settings for eth0: Supported ports: [ MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full 2500baseT/Full 5000baseT/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: 1000baseT/Full 2500baseT/Full 5000baseT/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: d 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

so I'm in the process of moving to larger drives and then reducing my drive count. I've migrated data from two data drives (4TB) to a larger 16TB, but I still have 4.02GB showing on each of these old drives in the web gui that definitely do not have data (du confirms 0 bytes). I just wanted a sanity check that this is normal and fine and that I can just restart the array without these guys and let it do its thing for parity.

cool ty, thats what i was hoping. ive been lucky and only had to replace a drive once and it wasnt parity

So I ordered a couple of 16TB drives to replace a couple of my 4TB drives. I plan to replace the parity drive first, and I plan on just powering down, replacing the drive, reassigning parity to the new 16TB and starting the array. Do I have to do anything to make all the space on the new drive used correctly on the parity or data drives? Then I was thinking the old drives are 512b but these new ones are 4k, but given the way that unraid does the array I would think that wouldn't be an issue.... right?