Ronnie_frown

Members
  • Content Count

    11
  • Joined

  • Last visited

Posts posted by Ronnie_frown

  1. Outcome of the update: SUCCESSFUL

     

    - DSM version prior update: DSM 6.2.3-25426 Update 1

    - Loader version and model: JUN'S LOADER v1.04b - DS918+

    - Using custom extra.lzma: NO

    - Installation type: Lenovo V520 i3 7100, 4GB RAM, 3.5" x 2 HGST Ultrastar 6TB, x1 3.5" OCZ 90 GB SSD HDD Bay

    - Additional comments:
        1. Update with DSM GUI to DSM 6.2.3-25426 Update 2 : Worked well.

        2. Plex HW transcoding works fine

  2. @IG-88 hey again, i followed your advice and picked up a TP-Link TG-3468 (has an r8169 controller adn kinda the only NIC i can find at our crappy local PC HW stores), installed DS3615xs, DSM 6.1-15047, loader 1.02b with extra lzma. got the same weird issue! checked the kernel and for some reason it is loading the driver for the r8168 :/ 

     

    reverted to my Ubuntu Server setup (which works perfectly fine with the new and the old NIC) to find out what driver the kernel is loading, got the following output:

     

     

    00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02)
        Subsystem: Hewlett-Packard Company 82801I (ICH9 Family) SMBus Controller
        Flags: medium devsel, IRQ 18
        Memory at feaffc00 (64-bit, non-prefetchable)
        I/O ports at 0400
        Kernel driver in use: i801_smbus
        Kernel modules: i2c_i801

     

    02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
        Subsystem: TP-LINK Technologies Co., Ltd. TG-3468 Gigabit PCI Express Network Adapter
        Flags: bus master, fast devsel, latency 0, IRQ 16
        I/O ports at e800
        Memory at febff000 (64-bit, non-prefetchable)
        Memory at fdffc000 (64-bit, prefetchable)
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Endpoint, MSI 01
        Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
        Capabilities: [d0] Vital Product Data
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Virtual Channel
        Capabilities: [160] Device Serial Number 90-2e-00-00-68-4c-e0-00
        Kernel driver in use: r8169
        Kernel modules: r8169

     

    i'm wondering why the "extra lzma" isn't fixing the issue of the missing DSM/Loader driver! :/

  3. 6 hours ago, IG-88 said:

     

    i don't know what driver ubuntu uses, you can check and report back

    ubuntu might be using the kernel build in driver of the actual kernel

    dsm for 3615/17 uses an older kernel 3.10.10x and jun's and my extra lzma contain the driver that realtek provides

    as your hardware is pretty old the kernel the build in kernel driver might work for you, it is possible to make a special version that contains the kernel driver instead of the realtek driver but that would be just for testing and not permanently supported

    best way would be to add a nic as pci/pcie card and use that

     

    @IG-88 Thanks allot for your feedback, at the moment i'm testing a DS3615xs, DSM 6.1-15047 and loader 1.02b with extra lzma. what i noticed is that sometimes the kernel/system picks up the right driver at boot with a cold start or i have to keep restarting till i get lucky. i was planning on building a new box after i'm done toying around with this old rusty one but for the time being, is it secure to run on 6.1? i use Plex remotely and this exposes my box to the internet in a way. are there any network adapters proven to play well with synology?

     

    again, many thanks for the assist.

  4. @IG-88 I’m having nightmares with the RTL8111/RTL8168! I loaded the extension but it didn’t work, the NIC is recognized and I can see it loaded in the kernel if i ssh into the box, the network tab in DSM states that I have gigabit connection up and running but .... I get full bandwidth up but around 1.5 - 2 mb down. Tried both ds2356 and 57 but no luck.

     

    i had a box briefly running well but I can’t remember what loader / dsm 6.2 version I was running, I do remember that I was trying to reivive a broken build by using a newer loader than the one it had before. 

     

    Any help would be appreciated 

  5. Any chance i can get some help with "Realtek 8111C-GR" (according to system spec sheet from HP)? it is detected under 6.1 and 6.2 with and without the extra driver extension but i'm getting full 100 MB UP and around 2 MB Down! i'm sure of the Gigabit speed system and network capabilities as i was running the system under Ubuntu server for a while without a hiccup.  any help would be appreciated.

     

    Current setup, HP DX2400 Microtower, intel E7600, 4 GB Ram, 1 TB Drive for testing.

     

    Below the output i could pull from my box:

     

    1- ethtool eth0 output:

    Supported ports: [ TP ]
            Supported link modes:   10baseT/Half 10baseT/Full
                                    100baseT/Half 100baseT/Full
                                    1000baseT/Full
            Supported pause frame use: No
            Supports auto-negotiation: Yes
            Advertised link modes:  10baseT/Half 10baseT/Full
                                    100baseT/Half 100baseT/Full
                                    1000baseT/Full
            Advertised pause frame use: Symmetric Receive-only
            Advertised auto-negotiation: Yes
            Speed: 1000Mb/s
            Duplex: Full
            Port: Twisted Pair
            PHYAD: 0
            Transceiver: internal
            Auto-negotiation: on
            MDI-X: Unknown
            Supports Wake-on: pumbg
            Wake-on: g
            Current message level: 0x00000033 (51)
                                   drv probe ifdown ifup

     

    2- dmesg |grep eth0 output:

    [   28.057505] eth0: 0xffffc9001170c000, 00:22:64:c0:e5:21, IRQ 18
    [   28.085655] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [   29.338180] init: dhcp-client (eth0) main process (8745) killed by TERM signal
    [   31.091525] r8168: eth0: link up
    [   31.091544] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [   32.218219] init: dhcp-client (eth0) main process (9060) killed by TERM signal

     

    3- lspci -k | grep 'Kernel driver' output: 

    Kernel driver in use: uhci_hcd
            Kernel driver in use: uhci_hcd
            Kernel driver in use: ehci-pci
            Kernel driver in use: pcieport
            Kernel driver in use: pcieport
            Kernel driver in use: uhci_hcd
            Kernel driver in use: uhci_hcd
            Kernel driver in use: uhci_hcd
            Kernel driver in use: uhci_hcd
            Kernel driver in use: ehci-pci
            Kernel driver in use: lpc_ich
            Kernel driver in use: ahci
            Kernel driver in use: r8168

     

  6. Feels like i'm talking to myself here but i hope someone would take the time to give some feedback.

     

    Apparently the above combination was working but i decided to reload the system with new drives and the same config, same problem reoccured, full Gigabit speeds up but with 2 mb down speeds !

     

    i tried all possible configs so far, with and without extra.lzma. 

     

    1- ethtool eth0 output:

    Supported ports: [ TP ]
            Supported link modes:   10baseT/Half 10baseT/Full
                                    100baseT/Half 100baseT/Full
                                    1000baseT/Full
            Supported pause frame use: No
            Supports auto-negotiation: Yes
            Advertised link modes:  10baseT/Half 10baseT/Full
                                    100baseT/Half 100baseT/Full
                                    1000baseT/Full
            Advertised pause frame use: Symmetric Receive-only
            Advertised auto-negotiation: Yes
            Speed: 1000Mb/s
            Duplex: Full
            Port: Twisted Pair
            PHYAD: 0
            Transceiver: internal
            Auto-negotiation: on
            MDI-X: Unknown
            Supports Wake-on: pumbg
            Wake-on: g
            Current message level: 0x00000033 (51)
                                   drv probe ifdown ifup

     

    2- dmesg |grep eth0 output:

    [   28.057505] eth0: 0xffffc9001170c000, 00:22:64:c0:e5:21, IRQ 18
    [   28.085655] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [   29.338180] init: dhcp-client (eth0) main process (8745) killed by TERM signal
    [   31.091525] r8168: eth0: link up
    [   31.091544] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [   32.218219] init: dhcp-client (eth0) main process (9060) killed by TERM signal

     

    3- lspci -k | grep 'Kernel driver' output: 

    Kernel driver in use: uhci_hcd
            Kernel driver in use: uhci_hcd
            Kernel driver in use: ehci-pci
            Kernel driver in use: pcieport
            Kernel driver in use: pcieport
            Kernel driver in use: uhci_hcd
            Kernel driver in use: uhci_hcd
            Kernel driver in use: uhci_hcd
            Kernel driver in use: uhci_hcd
            Kernel driver in use: ehci-pci
            Kernel driver in use: lpc_ich
            Kernel driver in use: ahci
            Kernel driver in use: r8168

     

    The main box spec sheet says that i'm supposed to have an "Integrated Realtek 8111C-GR GbE Ethernet Controller; Intel PRO/1000 PT Gigabit PCIe Controller" not an r8168

     

    Please assist !!!!!

  7. Hello all,

     

    i have an old HP DX2400, Intel E7600, 6 GB RAM running LDS3615xs, loader v1.02b, DSM 6.1.4-15217 Update 1.

     

    everything is running well except a weird transfer speed issue, I’m running all devices through a Gigabit switch, I’m getting around 60-70 MB/s upload speed to my box which is good enough but on the other hand I’m getting 1-2 MB/s download rate! Switching to my AC WiFi adapter on PC I get 350k!

     

    Tried the test with different PC/Laptops and different files with different sizes, reloaded the installation from scratch with a different HDD but no luck. Btw I’m only using a single HDD in this box since I’m still testing for functionality and stability at the moment.

     

    My aging DS212j runs at around 30-40 MB/s up and down as it always has so I’m kinda sure it’s not the network or the PCs connected to the box.

     

    wondering what could this be, appreciate all the assistance I can get.

  8. @Olegin i dusted an old HP DX2400 from the basement to test Xpenology before I go forward with building a new box, it’s got an intel e7600 and 4 gb of ram, have to say xpenology ran nicely before it crashed yesterday. What happened is that I followed what a member of the community did with his and moved the HDDs from the DS212j and aligned the HDDs to the SATA ports as they were in the DS212j. Booted, the volume was recognised, required a quick fix but it was A OK. Installed Plex media server and added my libraries and streamed music from the box for more than three hours without a hiccup. Then I tried to stream a movie (direct stream with no transcoding) it started stuttering saying that my server is too slow, so I rebooted the routers, switches and the Xpenology box, then boom ... the new volume totally crashed and I couldn’t bring it back. Moved the drives back to the DS212j and i’m Back to point zero.

     

    not sure what went wrong there, any insights? I’m going to try your suggestion with a fresh install on the test box from scratch but i’m Not sure the volume is going to hold afterwards, a bit of a hassle if it doesn’t  😕

  9. is it necessary that both boxes are running the same S/W version?

     

    Asking because i'm planning on migrating from my official Synology (DS212j, DSM 6.2.1-23824 Update 2) to a new custom Xpenology box already tested and running well (Loader v1.02b, DS3615xs, DSM 6.1.4-15217 Update 1). The official synology procedure mentions that both boxes should be running the same SW version.

     

    Thanks in advance for the help.

     

    ** forgot to mention that i'm running the original volume (2 x WD RED 2 TB) as JBOD (yes i know i should have some redundancy but i can't afford bigger drives at the moment)