flyride

Members
  • Content Count

    1,898
  • Joined

  • Last visited

  • Days Won

    98

Everything posted by flyride

  1. Again, start with loader 1.02b for DS3615, and download a DSM PAT file for version 6.1.7 DS3615xs+ NOT DS3617 NOT 6.2.x When it installs, DON'T let it upgrade to 6.2.x. This is a version that is almost guaranteed to work on your hardware, and once you figure out what's going on you can experiment with other loaders and DSM versions.
  2. Syndicating an NVMe device via RDM will cause it to appear as the type supported by the virtual controller to which it is attached. In the case of my examples, DSM sees the NVMe drives as SAS. They could as easily by SCSI or SATA, all to which DSM provides direct support as disk devices. So there will be nothing output from the nvme command structure.
  3. MDRAID writes a superblock on each array member so it can still work if the drives are encountered out of order. That said, it's possible to defeat it if enough bad things happen to the array (missing members, etc).
  4. Did this post not explain the situation for you? DS918+ has no slot for 10Gbe card so the Synology support page would not apply.
  5. flyride

    DSM 6.2 Loader

    Guides: Choosing a loader and DSM / DS3615 native drivers / DS918 native drivers
  6. 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.
  7. 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
  8. 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.
  9. 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:
  10. flyride

    DSM 6.2 Loader

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

    DSM 6.2 Loader

    Dropped by whom? 6.2.1 is the latest available and it runs on 3615 image fine.
  12. 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.
  13. Are you certain that you need to use extra.lzma? DS3615xs has mptsas driver installed in the first place.
  14. 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 MDRA
  15. 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
  16. 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.
  17. That's all the GRUB menu will say. Which loader? Which DSM and version?
  18. Which loader and DSM are you trying to use? Recommended VM type is "Other 3.x Linux 64-bit" for ESXi, but I don't know if that translates to VMWare Workstation. EDIT: It would appear from topic that you have tried both 1.04b/DS918 and 1.03b/DS3617. I recommend 1.04b/DS918 and vmxnet3-equivalent NIC (not sure what VMW "host" type is), or 1.03b/DS3615 and e1000e NIC type
  19. r8168/r8169 is removed from DS3615 6.2.1 https://xpenology.com/forum/topic/13922-guide-to-native-drivers-dsm-617-and-621-on-ds3615/
  20. You are correct, it will limit the amount of RAM on passthrough. RAM can remain dynamic if you use RDM, however, which is equally functional.
  21. flyride

    DSM 6.2 Loader

    And this if you are using ESXi. Search is your friend.
  22. Do you have another PC you can use to experiment with ESXi first? Yes, there is a learning curve, but it's not awful. It would be wise to do some practice installations using both ESXi and XPEnology on ESXi before trying to convert your main hardware and storage. And, as always, when you do your "real" installation, your data should be backed up somewhere else in case of catastrophe. Performance-wise, any difference between ESXi and baremetal is negligible. You will be running a hypervisor in addition to XPEnology, but you can give the entire machine (RAM and CPU) to the XPEnolo