flyride

Members
  • Content Count

    352
  • Joined

  • Last visited

  • Days Won

    22

flyride last won the day on February 18

flyride had the most liked content!

Community Reputation

117 Excellent

3 Followers

About flyride

  • Rank
    Super Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. flyride

    Trouble getting SSL from Let's Encrypt

    Do you have a valid domain that you used for the Let's Encrypt CSR? It cannot be a made-up one, it has to be resolvable to the IP that services your host.
  2. Looking at the spreadsheets linked here and here, you can see the following: On DS918, v6.2.1 image, the ixgbe (linux device driver that supports X540 NIC family) driver is version 4-2-1-k, which happens to be the default driver in the 4.4 kernel tree On DS3615 image v6.1.7, the ixgbe driver is version 4.4.6, which is a custom build by Synology On DS3615 image v6.2.1, the ixgbe driver is a newer custom build at version 5.1.3 You may have a newer X540 card that is not supported by the older driver in the DS918 image. You should be able to prove it by going into Windows and getting the PCI device IDs for your cards and trying to match to the list of device ID's in the spreadsheets. Synology does not care about updating the ixgbe driver on DS918 because there is no way to install a 10Gbe card in their hardware. If someone builds a functioning, updated ixgbe driver in extra.lzma for DS918, that may work, otherwise you will need to stay on a DS3615 image to support your cards. I have never found that the grub MAC setting had any effect on whether a card was recognized by its driver. AFAIK the point is to enable use of a Synology MAC for a service that requires one, and perhaps secondarily to avoid MAC duplication with multiple XPEnology installations on the same LAN. Still not 100% sure what aspect of search you have not found yet, but if you click in the search box itself, you get this:
  3. flyride

    Looking to upgrade from Gen8

    You seem to have some sort of compromised install or hardware problem that you reported long ago and has continued. There are no responses, because others don't know why your system is randomly behaving that way, and the problem you describe is not happening to them. Reading through all your posts, you don't seem to be very satisfied with XPEnology ever, and seem to be looking for a reason to use something else. But if you do want to keep on, consider a validation test of your hardware (no overclock, full system and memory test, etc) and then a totally clean installation. Also verify your function prior to installation of, or do not use root-level customization like ipkg/opkg. Regarding your last statement about cost/value, I don't know where you come up with that; if it were true nobody would be using XPEnology Synology doesn't even make a product with the features of my own box, for instance, and the closest (grossly inferior) match is more than twice the cost of my parts.
  4. ixgbe driver is in the DS918 image. You might want to dig a little deeper in the logs to see what is going on. For your future reference:
  5. flyride

    DSM 6.2 Loader

    6.2.1-23824 is a newer patchlevel than 6.2-23739
  6. flyride

    DSM 6.2 Loader

    Dropped by whom? 6.2.1 is the latest available and it runs on 3615 image fine.
  7. Yes, DS918 is the only loader-supported DSM release that is on the 4.4 kernel tree. I'm sure that Synology is using 4.4 for all their newly released product lines. I'm not sure how anyone outside of Synology development would know if they intend to update the kernel on older products. They publicly state that they backport security updates to older kernels. If they were going to arbitrarily upgrade the kernel (or if they were compelled to do so for DSM functionality dependencies), the DSM 7.0 release would seem to be a likely opportunity.
  8. Are you certain that you need to use extra.lzma? DS3615xs has mptsas driver installed in the first place.
  9. Serial port console. You can redirect it virtually with ESXi.
  10. SHR is not deprecated, it is not a sales factor in the upper-end of their line and there is additional complexity and slight performance impact for using it. So in 6.x, until 6.2, it was disabled by default on the 3615/3617 image, but enabled on the 916 image. An imported SHR volume will work fine. In 6.2.x, you essentially have the option of using LVM when you create your Storage Pool ("fast" vs "flexible") which is how SHR is implemented. To your RAID5 btrfs question, Synology does not using btrfs native RAID at all. BTRFS only sees a single volume which is the output of MDRAID (without SHR) or LVM (with SHR). So you can safely use any RAID approach you wish with BTRFS on Synology.
  11. Your hardware offers some limitations you should be aware of: The CPU is too old to use loader 1.04b/DS918 Your onboard Broadcom NIC won't work with loader 1.03b/DS3615, you will need to disable in BIOS and add an Intel NIC serviced by e1000e driver You have two options: Use loader 1.02b and DS3615 DSM 6.1.7 and your Broadcom should be directly supported. You cannot upgrade beyond 6.1.7 in this configuration Use loader 1.03b and DS3615 DSM 6.2.x. As mentioned you need an Intel NIC installed and your Broadcom must be disabled in BIOS
  12. Just delete the XML tag with the serial number of the drive in question. When you reboot the tag will be regenerated and any reconnect history will start from 0.
  13. Edit /var/log/disk_overview.xml
  14. That's all the GRUB menu will say. Which loader? Which DSM and version?