Jump to content
XPEnology Community

bglf83

Member
  • Posts

    145
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by bglf83

  1. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.2.3 - 25426 Update 2
    - Loader version and model: JUN'S LOADER v1.03b - DS3615xs
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Supermicro X10SRi-F, onboard NICs Intel but not used (not disabled either), Intel Pro/1000 PT (EXPI9400PTBLK listed as 82572)
    - Additional comments: Computer needs to be booted in Legacy BIOS mode and I confirmed the Intel 82572 NIC chipset uses Intel e1000e drivers.

  2. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.2.3 - 25426
    - Loader version and model: JUN'S LOADER v1.03b - DS3615xs
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Supermicro X10SRi-F, onboard NICs Intel but not used (not disabled either), Intel Pro/1000 PT (EXPI9400PTBLK listed as 82572)

    - Additional comments: Computer needs to be booted in Legacy BIOS mode and I confirmed the Intel 82572 chipset uses Intel e1000e drivers.

  3. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.2.2-24922 Update 6
    - Loader version and model: JUN'S LOADER v1.03b - DS3615xs
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Supermicro X10SRi-F, onboard NICs Intel but not used (not disabled either), Intel Pro/1000 PT (EXPI9400PTBLK listed as 82572)

    - Additional comments: Computer needs to be booted in Legacy BIOS mode and I confirmed the Intel 82572 chipset uses Intel e1000e drivers.

  4. I use an Intel Pro 1000 PT people also talk about the HP 360T. The common factor is they use the Intel e1000e driver built into DSM. Meaning they are natively supported.

    1.04b is only for the 918 and it may not have a supported PCIe network card list but the 1.03b for 3615xs does have that on the synology site.

    1.04b is good if you are trying to do hardware acceleration for video, otherwise I do not think there is a benefit. The actual versions of DSM are the same for both loaders.

  5. Hi,
     
    I'm planning to upgrade my ASRock Q1900DC-ITX from DSM 6.1 to DSM 6.2.
    In some test I recognized that the interal network card is not recognized by the latest Version of DSM 6.2
     
    I added a Intel 82576 network card, but that works only with Loader v1.03b.
    Now my question:
    Will v1.03b be supported in future and is there a recomended network card for v1.04b (PCIe 2.0 x1)?
    The thing is that if I buy a new networkiadapter, it shoud be compatible to the next loader an DSM Versions.
     
    Thanks for your help!


    I am not sure how safe the currently working cards are, however I believe 6.2 will receive 2 years of security updates after 7.0 comes out.
  6. Search the forums on how t check which network driver your machine is currently using. If it’s an e1000e it’s pretty safe.

    I can search from a desktop to find it if you cannot.

    • Like 1
  7. I was planning to use the 1.03b loader and stick with the 3215xs. My findings:
    1.02b was and is still working perfect
    1.04b worked after bios upgrade (looks to work without and with internal NIC disabled). Before bios upgrade I got the “13”error.
    1.03b starts but cant be discovered on the network. Have internal NIC disabled and NC360T installed (based on this forum, especialle microserver topic, this looks a supported card).
     
    Am is missing something with 1.03b loader (bios setting, extra drivers or something else like that)?
    I do not have real SN and mac. Any disadvantages for 1.04b over 1.03b or is it best to update my actual system with 1.04b?
     
    Hardware:
    Asus H87i-Plus
    CPU: Pentium G3420
    NIC HP NC360T
    Did you configure it to use legacy bios instead of UEFI for 1.03b?
  8. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.2.2-24922 Update 2
    - Loader version and model: JUN'S LOADER v1.03b - DS3615xs
    - Using custom extra.lzma: NO
    - Installation type: Bare Metal, Supermicro X10SRi-F, integrated NICs Intel but disabled, Intel Pro/1000 PT (EXPI9400PTBLK listed as 82572)

    - Additional comments: Computer needs to be booted in Legacy BIOS mode and I confirmed the Intel 82572 chipset uses Intel e1000e drivers.

    • Like 1
  9. Hi Guys,
    is there any Chance to get a MBR-Version of the 918+ Loader V1.04..

    i tried so much to convert these Loaders (also 1.03b) but without success..

    Cause my Supermicro X7DBP-i won't boot from GPT..

    or any hints would be also helpful..

    Thanks a lot..
    Why not just use the DS3615XS 1.03b loader?
  10. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.1.7-15284 Update 3
    - Loader version and model: JUN'S LOADER v1.03b - DS3615xs
    - Using custom extra.lzma: NO
    - Installation type: Bare Metal, Supermicro X10SRi-F, integrated NICs Intel but disabled, Intel Pro/1000 PT (EXPI9400PTBLK listed as 82572)

    - Additional comments: Computer needs to be booted in Legacy BIOS mode, I confirmed the Intel 82572 chipset uses Intel e1000e drivers and I had to delete the root .xpenoboot folder and reboot for everything to work right.

  11. I was successfully with DS3615xs 1.03b loader.

     

    I did have to delete the old xpenoboot folder as detailed below to resolve my network issues after I migrated from the 3617 to the 3615.

     

     

    On 7/27/2019 at 8:46 AM, bglf83 said:

    I am not sure if there is a difference between the 3615 and 3617 but I had to ask. I have an Intel Gigabit PRO 1000 CT that can load 1.04b on the current update, but it does not show the network adapter in the network list. I also have not been able to update all the way with the DS3617XS loader.

     

    I am considering getting the HP card, but I am not sure that is my issue.

     

    I am continuing research and it looks like with 1.04b, the issue I was having may be fixed by doing this:

    -------------------------------------

    @XbladeX From earlier experience with a problem like that:

    try these steps:

    Activate the SSH service in DSM (if not active)
    Connect to your NAS with an SSH client (e.g. putty) (or from Win 10, open a cmd window, run : ssh admin@my.nas.ip (replace with the actual IP)
    Enter your credentials (user: admin)
    Change folder to root (cd /)
    Delete the xpenoboot folder (sudo rm -r .xpenoboot)
    If the SSH service keeps stopping, you have to be quick.

    --------------------------------------

     

    I have an e1000e drive loaded for my NIC. I disabled all my other NICs.  To check what driver your NIC is using, log into SSH and run these commands.

     

    (I got this info from another person on the forum)

    ----------------------------------------------

    Open a SSH connection to your NAS, and type:
    lspci | grep 0200 (this will list your nic's)
    you should see something like: 
    ... Device 8086:xxxx  (indicating Intel)
    This should be eth0, so type:
    ethtool -i eth0 
    you should see something like:
    driver: e1000e (this is a driver supported in 6.2.1)
    If not, try using the above :xxxx device id to check if it is supported by the bootloader/DSM version you will try to us

    ------------------------------------------------

    • Like 1
  12. I am not sure if there is a difference between the 3615 and 3617 but I had to ask. I have an Intel Gigabit PRO 1000 CT that can load 1.04b on the current update, but it does not show the network adapter in the network list. I also have not been able to update all the way with the DS3617XS loader.

     

    I am considering getting the HP card, but I am not sure that is my issue.

     

    I am continuing research and it looks like with 1.04b, the issue I was having may be fixed by doing this:

    -------------------------------------

    @XbladeX From earlier experience with a problem like that:

    try these steps:

    Activate the SSH service in DSM (if not active)
    Connect to your NAS with an SSH client (e.g. putty) (or from Win 10, open a cmd window, run : ssh admin@my.nas.ip (replace with the actual IP)
    Enter your credentials (user: admin)
    Change folder to root (cd /)
    Delete the xpenoboot folder (sudo rm -r .xpenoboot)
    If the SSH service keeps stopping, you have to be quick.

    --------------------------------------

×
×
  • Create New...