r8152 VS Synology_HDD_db

The network adapter performance is underwhelming and it keeps disconnecting every 2-3 min. It is connected in a usb-c port on a Thinkpad T480s. I found a post online from someone having this issue on Ubuntu. I tried adding the udev file rules for Realtek adapters mentionned in his post without success.

Those udev rules came from this file: https://github.com/bb-qq/r8152/blob/master/50-usb-realtek-net.rules (lines 12 and 13, with 8 and 9 subbed in.)

I saw a post from someone recently who used these USB adapters and this driver to add 2.5 Gbe capability to a DS1821+, though it should work with most current Synology devices.

Thanks for the suggestion, I wasn't aware of this option. I have since found this page https://github.com/bb-qq/r8152 and as it's looking like the nic on my NAS is in distress I am looking into ordering a usb type-a CableCreation 2.5G Ethernet to USB Adapter for AU$30

You will need to install additional drivers.

Another way is to get a 2.5gbe usb adapter and plug it into the USB port on the Synology. There's some software on GitHub that will make this work. I opted to go with an official Synology card. I already have a relatively complex network set up. I don't want to chance a sudden incompatibility and lose a weekend trying to figure out what went wrong.

I used my https://github.com/007revad/Synology_HDD_db script to add them to DSM's compatible drive database and allow creating NVMe storage pool.

The bash script is here: https://github.com/007revad/Synology_HDD_db/blob/develop/syno_hdd_db.sh

You should probably schedule those commands to run at start-up in case a DSM update undoes your changes. See how_to_schedule (replace that command with the two command lines above).

Update: I managed to fix it by running this script. One tip is to save your script in a place that doesn't have spaces in the location path. Part of me wonders if I should have just stayed on DSM 6 since if it isn't broke don't fix it.

Or better yet, just schedule my Synology_HDD_db script to run at boot-up. https://github.com/007revad/Synology_HDD_db

I've just done the update and had a similar experience. Drives blacklisted but storage pool still up and available. Ran the script from https://github.com/007revad/Synology_HDD_db