Jump to content
XPEnology Community

Hiromatsu

Member
  • Posts

    15
  • Joined

  • Last visited

Posts posted by Hiromatsu

  1. 30 minutes ago, flyride said:

    You can turn on SHR with 3615/3617 by changing two lines in /etc.defaults/synoinfo.conf

    with this line: support_syno_hybrid_raid = "yes" above supportphoto="yes" ?

    Cool! Thanks for this supercool hint!

     

    18 minutes ago, IG-88 said:

    Thank you for that video, I will definitely give it a try

     

     

    18 minutes ago, IG-88 said:

    and keep in mind 24 is max. as long as you have not tested it (with a raid set), quicknick claimed there where certain higher drive counts but noone tested that afaik

    12, 16, 20, 24, 25, 26, 28, 30, 32, 35, 40, 45, 48, 50, 55, 58, 60, 64

    https://xpenology.com/forum/topic/8057-physical-drive-limits-of-an-emulated-synology-machine/?do=findComment&comment=87213

    not a problem 24 would be enough, I will just leave the rear backplane unattached!

    Is there still this limitation that it would not work if all HDDs are attached to a SAS Controller?

    Last time I tried one HDD had to be attached to the onboard sata controller.

     

     

    18 minutes ago, IG-88 said:

    if you need nvme ssd on baremetal then 918+ is you goal

     

     

    if you can give me the pci id i can look in the driver if it will work SAS2 is no problem, SAS3 depends on how new the chip is older SAS3 will work

    Does this contain anything you would would need? (It is an older card and the backplane its the Supermicro BPN-SAS3-846EL1

    <node id="storage" claimed="true" class="storage" handle="PCI:0000:06:00.0"> <description>Serial Attached SCSI controller</description> <product>SAS3008 PCI-Express Fusion-MPT SAS-3</product> <vendor>Broadcom / LSI</vendor> <physid>0</physid> <businfo>pci@0000:06:00.0</businfo> <logicalname>scsi7</logicalname> <version>02</version> <width units="bits">64</width> <clock units="Hz">33000000</clock> <configuration> <setting id="driver" value="mpt3sas" /> <setting id="latency" value="0" /> </configuration> <capabilities> <capability id="storage" />

     

     

    14 minutes ago, flyride said:

     

    At some point you have to make some decisions on which features you want to support.  NVMe direct support is only in DS918.  RAIDF1 support (if you ever need it) is only in 3615/3617.  10Gbe and SAS support is better in 3615/3617 but somewhat mitigated if you experiment with add-in drivers from IG-88.

     

    My main system is similar to yours - 10Gbe, and I use enterprise SATA SSD drives now so RAIDF1 is important.  I also have two U.2 NVMe drives, and the only way I found to get everything to work was to use ESXi to run DS3615 (for RAID F1 and 10Gbe support) and present the NVMe devices via RDM.

    You are absolutely right flyride!  I had an ESXi server running in a similar config for a year now and the electricity bill made me think of running it on Baremetal, because then I can use the power on and off schedule .

    Besides that: I love to tinker around and try things, so I will experiment with the drivers from IG-88

     

     

     

  2. 9 hours ago, IG-88 said:

     

    if using the new 0.6 extra.lzma for 6.2.2 from here

    https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

    there shouldn't be a difference between 3615 and 3617 with drivers

    if you still want to use 918+ then you can try it with the new 0.8 extra.lzma (eta next weekend) - but i dont see any added value with your hardware (no gpu, no m.2 nvme), only useful to test if you have problems with 3615

     

    Thank you, I would really like to do that, but I think I am kind of too stupid for that.

    Especially I would like to make use of SHR, which the 3615xs and 3617xs cant 

    I would really like to experiment a little, because I have two nvme devices here (not m.2, but PCI-E) and a Arago SAS3 controller + a 36 bay 4u chassis, but I wasn't able to make the changes in the config work for more than the drives that the 1.04b loader came with... 

    Will keep an eye on the release of the 0.8 extra.lzma, if I have an hour or two to tinker around

     

     

  3. Thank you very much,
    I set the BIOS to legacy already and the strange thing is that it connects with clean formatted HHDs and I can start the installation process...
    Just afterwards it is no longer responding and is no longer found via find.synology or the tool.

    Could that be because of the "wrong" type of onboard nics?

    I have read something of kernel panic if you don't have a Intel e1000e NIC or extra.lzma

    Therefore I bought a Intel PRO/1000 PT Server Adapter (EXPI9400PTBLK) but that didn't change a thing.

    I will try the DS3615xs installation instead...
    Thank you again

  4. Hello there,

     

    I am clueless on how to fix my problem.

    I have the following hardware:

    Supermicro X10SRi-F, Intel E5-1620v3, 64GB DDR4

    https://www.supermicro.com/en/products/motherboard/X10SRi-F

    using v1.04b is working like a charm.

     

    As I would like to use 10GBe networking I was trying to use loader v1.03b (DS3617xs)

    When using cleared HDDs I am able to complete the installation process, but the system doesn't come online afterwards.

     

    Does anybody have an idea why and how to fix it?

    Can I somehow provide logs?

     

    Kind regards

  5. Just tested with an I354 board (Supermicro A1SAi-2750F) but no luck. Looks like I354 isn't supported. I thought it would have been covered by the I350 drivers. Is it possible I'm doing something wrong? I got number of network interfaces by running: ls -A /sys/class/net | wc -l

     

    Also, when I select the config tool option, it only brings me to the "booting the kernel" screen instead of launching the config tool. Any thoughts?

     

    same problem here :sad:

     

    See my previous post.

     

    Sorry for not providing the necessary information:

     

    Hardware: Intel® Atom processor C2750, SoC, FCBGA 1283, 20W 8-Core

    Install Type: Baremetal

    NIC Model: C2000 SoC I354 Quad GbE controllers

    Storage: LSI 9211 8i

    Issue: perhaps Network

     

    My network card doesn't seem to be recognized.

    The driver is not in the supported drivers list.

    Can this be a problem? As far as I know Synology uses the same NICs with their RS2416+/RS2416RP+ series (Intel Atom C2538)

     

    Another issue is: I am not able to enter the config tool like Elpee described it here:

    Hi quicknick.

    I have a quick question here.

    Can I access XPEnology Configuration Tool BEFORE a successful installation? In short, I want to set MAC + SN + VID/ PID + Sata Port Mapping + Max of disks right after I boot the nas up for the first time.

     

    XPEnology-grub-menu.png

     

    I tried to select "XPEnology Configuration Tool v2.2" when I see the menu at the fisrt time, but I cannot access XPEnology Configuration Tool. All I have is the screen of "Booting the kernel".

     

    XPEnology-boot-kernel.png

     

    Thank you for your inputs.

     

    Could someone with better english skills please confirm if you only see the config screen via ssh?

    I am under the impression one should see the menu on the screen too?

    Is that correct?

  6. Just tested with an I354 board (Supermicro A1SAi-2750F) but no luck. Looks like I354 isn't supported. I thought it would have been covered by the I350 drivers. Is it possible I'm doing something wrong? I got number of network interfaces by running: ls -A /sys/class/net | wc -l

     

    Also, when I select the config tool option, it only brings me to the "booting the kernel" screen instead of launching the config tool. Any thoughts?

     

    same problem here :sad:

  7. [...]

     

    Looks like I found my issue.

    My machines has C2000 SoC I354 Quad GbE NIC controllers & LSI SAS 9211-8i. [...]

    A new loader with included drivers will be out in the coming days. Stay tuned.

     

    Sent from my SM-N920T using Tapatalk

     

    Sorry to ask, but is there an approximate ETA on this new loader with the included drivers for the i354?

  8. Was someone here sucessful with a Atom C2750 / C2550 MB?

    I tried to setup a baremetal system on my Supermicro A1SAM and system "seems" to boot correctly.

    Display shows "Kernel booting" and my router gives out dhcp leases to both of the pluged in ethernet ports.

    I am not able to connect via IP Adress:5000

    Neither does http://find.synology.com/ show any system, nor does the desktop app shows a system.

    PID/VID is changed and the same usb drive boots my Asrock QC5000-ITX just fine.

     

    Suggestions?

  9. The mpt3sas will be automatically load at boot in next release.

     

    You can easily edit /etc/rc.local and add your insmod command to load the mtp3sas.ok module :wink:

     

    Thank you very much @Trantor

     

    Sorry for not telling right away what kind of newbie I am:

     

    So I browsed for the rc.local file, but there isn't any :sad:

     

    Can I just create one?

    Or do I have to follow a special procedure?

     

    something like (I googled this but it is made for Fedora)

    su -

    (root password)

    touch /etc/rc.local

    chmod +x /etc/rc.local

    (add the insmod)

     

    systemctl enable rc-local.service

     

     

    And what content does the rc.local need to have?

    Is it sufficient to just have:

     

    #!/bin/sh

    # Copyright © 2000-2014 Synology Inc. All rights reserved.

     

    insmod /lib/modules/mpt3sas.ko

     

     

     

    Does this file needs to be in etc only or in etc.defaults too?

     

    Thank you

  10. Hello everyone,

     

    I am struggling with a proplem.

    In the /lib/modules/ folders there is a mpt3sas.ko

    This is the driver file for my HBA (LSI 9300 8i)

     

    I can SSH into my box and load it manually via: insmod /lib/modules/mpt3sas.ko

    But apparantly I am too stupid to find a way to automatically load the ko file during the boot up sequence.

     

    Can anybody help?

     

    If its important: I am running my box on ESXi 6.0 with the controller passed through.

×
×
  • Create New...