flyride

Members
  • Content count

    85
  • Joined

  • Last visited

  • Days Won

    2

flyride last won the day on July 12

flyride had the most liked content!

Community Reputation

12 Good

1 Follower

About flyride

  • Rank
    Regular Member

Recent Profile Visitors

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

  1. Any idea why this works?
  2. flyride

    DSM 6.2 Loader

    Thanks for relaying your experience. But your comment #3 - let's all not forget that 1.03b development and 6.2 support is still seriously in beta. If you want stability and lack of problems, stay on 6.1 for now.
  3. As Dfds says, yes it's ok. Answers to your future questions in this regard are found here.
  4. flyride

    DSM 6.2 Loader

    I disagree with this generalization - Xeon does not offer any capabilities that desktop processors do not have. ECC RAM and improved security are Xeon's two main benefits, both which are irrelevant to DSM. So I would not worry about using DS3617xs with a non-Xeon processor as long as it supported the needed instruction set, which is a function of processor generation, not server vs. desktop. The final answer for your CPU should be discernible by reviewing the hardware capabilities as described in the Intel Ark pages. How to summarize all this? Basically, the DS916/3615/3617 DSM code base, AS COMPILED BY SYNOLOGY, seems to require a Sandy Bridge or later CPU. DSM on DS918 appears to use instructions that appeared in Haswell and later, which includes Broadwell, Skylake, Kaby Lake, Coffee Lake, Apollo Lake, Gemini Lake. The community is still compiling information about exactly which CPU's are supported, so don't assume this list is definitive. Also note that the embedded Linux kernel for DSM DS916/3615/3617 is v3.10 (even on DSM 6.2) and the DS918 uses v4.4. This may also turn out to be a threshold for CPU selection. For hardware transcoding, QuickSync processor extension is required both for Synology native support (via Video Station) or third party (i.e. Plex). QuickSync capability increases with each processor generation, so even if your processor has QuickSync support, it may not meet the specific requirements of the software you are trying to run. Also, not every modern processor has QuickSync silicon (no Atoms have it, most desktop processors do, some Xeons do). In addition to the above, DSM must support QuickSync with kernel drivers, and the required components are only available with DSM on the DS916 and DS918 platforms today.
  5. See this here
  6. flyride

    DSM 6.2 Loader

    Info Center reports what it expects on the intended hardware for the image and is not correlated to the actual CPU in the system. That said I don't think you can use more than 8 cores in DSM, if you have HT and more than 4 cores, disable hyperthreading.
  7. flyride

    Progress of 6.2 loader

    Yes, that is the way Synology is supporting the older CPU's; they are not upgrading the kernel, at least in 6.2. So if you want a newer kernel, 918 will be the way to go.
  8. flyride

    DSM 6.2 Loader

    Load a vmdk file in a text editor and you will have your answer.
  9. flyride

    DSM 6.1.7-15284 Update 2

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284U1 - Loader version and model: Jun's loader v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.5.0 U1-7388607 - Additional comments: REBOOT REQUIRED / No issues with physical RDM and controller pass-through.
  10. flyride

    DSM 6.1.7-15284 Update 2

    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 Update 1 - Loader version and model: Jun's Loader v1.02b - DS916 - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J4105-ITX - Additional comments: NO REBOOT REQUIRED
  11. flyride

    Original DSM (.pat file) from Synology usable?

    Unless you manually modify them yourself, you will not be using anything other than original PAT files from Synology. You should read the FAQ and best practices regarding updates. In short, nobody knows for sure whether an update is going to break XPEnology. Most folks either wait for someone to report success on a software/hardware platform similar to theirs before applying an update, or have a test system that they don't mind crashing to try it out on prior to committing the production system.
  12. flyride

    Extend VM disk for XPEnology

    If you are not using DSM to provide storage redundancy, why are you using it in the first place vs. a Linux fileshare or Docker host? You could theoretically use vSAN to achieve redundancy in the VMWare space (again DSM seems useless at that point). Like IG-88 says, you can provision on two datastores and the JBOD them together in DSM, but there is no redundancy. If you have a 1.5TB volume on a 3TB datastore, and you want a 2TB volume on a 3TB datastore, it's not difficult to add space to your VMDK, then use mdadm and btrfs/ext tools to expand the disk from command line. Another option is to create 2TB VMDK on the 2nd 3TB datastore, convert the volume to a RAID1, expand the 1.5TB VMDK to 2TB, repair which will automatically expand the volume, then drop the member on the 2nd datastore. You will then have a "critical" RAID1 which is the same as a Basic volume, you then can get rid of the error message with mdadm --grow -n 1 --force /dev/mdX
  13. Nice, I had not seen native NVMe for cache validated yet.
  14. flyride

    How to install XPEnology on a Dell Optipex SX280?

    XPEnology is only Intel-based, there is no support for the ARM platforms.
  15. flyride

    Two problem with esxi 6.7 - dsm 6.1

    See this post for your first issue.