flyride

Members
  • Content Count

    1,848
  • Joined

  • Last visited

  • Days Won

    97

Everything posted by flyride

  1. Each hardware manufacturer registers PCI device type before a device is made available for sale. It's how the drivers can identify the hardware with which they are supposed to work. So a driver essentially has a list of the hardware ID's it can work with. The above is an extract of that information from the drivers Synology included in DSM 6.2.1 for DS918. You can see devID's within Synology or Linux by using lspci. I'm not sure what the MacOS command would be to do the same, but I am sure there is an equivalent command. What I'm suggesting to @hoidoi is to verify t
  2. You need the "right" NIC. Here are the device ID's of the Intel NICs that are presently supported on DS918 6.2.1:
  3. Your discovery is consistent with this report here. Note that 6.2.x doesn't like creating storage pools when the devices are attached to a SAS controller - but once they are built they can be moved to it and seem to work fine. Probably not compatible with most users' expectations of reliability and supportability.
  4. DS918 has direct support for much fewer devices than DS3615. For example, there are over 200 distinct Intel NIC types supported by DSM DS3615 under 6.1.7. On DS918 6.2.1, that number is 135. And it isn't just the older boards that are missing, in some cases Synology regressed to an older driver package and dropped support for new NICs they were not going to use in their platform. What's worse is that Intel releases multiple cards (multiple PCI device ID's) under a single nomenclature so you can have two of the "same" cards, and one works and the other doesn't.
  5. You mention 4K H.265 transcoding. What's really happening here is probably 4K H.265 decoding + H.264 encoding at a low quality profile. I don't think there is a H.265 display device that doesn't also support H.264. So if your expectation is that huge CPU is required for H.265 encoding (it is), it doesn't apply to real-time transcoding. Regardless of the method (hardware vs. software) the encoding profile to provide a H.264 stream in real-time is comparatively low quality to the source. You are always better off streaming a source file directly to the device that can accept it (
  6. Which DSM version shall I use? This is an oft-repeated question, complicated by the fact that different loaders support different DSM versions AND hardware platforms. In simple terms, DS3615/DS3617 has the widest support for hardware and packages, and DS916/DS918 has support for newer, low-cost CPU's, transcoding and NVMe cache (DS918 only). But the real questions are, what hardware do you have? What hardware do you want to buy in order to support what you want to do? And how does a DSM loader and platform support this? In order to answer, it's useful to understand what har
  7. H.265 encoding is incredibly processor-intensive. Depending on quality settings, my 8-core i9-9900K takes 12+ hours to complete a 1080p movie. If you still want to do this, this Docker build of Handbrake has a directory monitor/automatic encoding function: https://hub.docker.com/r/jlesage/handbrake
  8. The only RAID mode that doesn't have some level of hardware protection is RAID0 (striping without redundancy). RAID1/5/6/10 and the SHR1/2 counterparts are all "safe." The thing to consider for RAID5 is when you get to very large drive sizes, that the rebuild time is very long, which means your loss of redundancy is for a long time. Resist the urge to change something else until your rebuild is complete. All this said, no RAID approach is a substitute for backup. Don't ever think your data is protected from anything other than a physical disk failure. You need anoth
  9. Package center will only offer you packages that are compatible with the DSM version you are running. So I wouldn't worry about that too much. Upgrading DSM through the Control Panel is a different matter. Disable automatic updates and monitor the reports and testing that others are doing before upgrading DSM itself.
  10. Welcome, you might consider a few more options for your backup strategy. Bacula is functional but complex. Synology backup software platforms are all finicky IMHO and the performance is not stellar. For DSM NAS to DSM NAS backup, BTRFS snapshots/replication is excellent - efficient, fast and has a decent DSM UI. For client backups, consider the free VEEAM version backed up to DSM share. If you like the idea of BTRFS replication, you might revise the ProxMox box to also run XPE/DSM (not sure what other virtualization you have planned). DSM runs Plex fine, either native Synology
  11. 6.1 is supported, and just received the latest security update.
  12. I think people are underestimating the capability, stability and performance of 6.1 and always wanting to get on the latest. 6.1.7 DSM on DS3615/3617 on XPEnology is the most flexible, supports the most hardware and is essentially the same feature set of the latest 6.2.1 version. DS918 is the first DSM platform to support transcoding and NVMe cache, so it makes sense to focus new work there.
  13. Use Docker apps instead of ipkg. It's 2019!
  14. E1000e (newer Intel Gigabit NIC emulation) is in ESXi 6.5+
  15. EDIT: ODROID H2 is an Intel system - first I've seen it.
  16. No, you have to copy your data off first as DSM install will blank your drive.
  17. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 update 1 - Loader version and model: Jun 1.03b - DS3615 - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.5 - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 update 2 - Loader version and model: Jun 1.04b - DS918 - Using custom extra.lzma: NO - Installation type: BAREMETAL - Asrock J4105-ITX
  18. flyride

    DSM 6.1.x Loader

    1.02b is the loader for 6.1 through the latest, 6.1.7. It works fine with ESXi.
  19. No I'm talking about the network from the NAS to your workstation(s) so you can get better than 125MBps transfer rates.
  20. flyride

    DSM 6.2 Loader

    It's cosmetic. cat /proc/cpuinfo will display the correct CPU configuration which is what is actually running. If you care to "fix" it, see this thread.
  21. - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.1.7-15284U1, also repeated with 6.1.7-15284U2 - Loader version and model: Jun v1.02b - DS3615 - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.5 with C236 SATA passthrough, Mellanox ConnectX-3 passthrough
  22. Agreed as long as your target devices can support VPN.
  23. TeamViewer is a PC app which would give you the same functionality as RDP. So nothing to be gained there. I don't think you can TeamViewer the NAS console itself (all you will see is the boot screen). The whole point of using Guacamole is NOT to open ports for remote access (aside from SSL to the proxy device which is separate from the NAS). In order to stream media (Plex, DS Video) to Internet devices, you will need to open ports - there is no other option. This is also well outside the scope of OP's question about Quick Connect remote access services.
  24. Quick Connect is a combination of DDNS and remote proxy through a Synology server. It uses outbound polling to determine whether a connection request is pending. Therefore it does not need any ports opened on your firewall/router. But you are 1) using their cloud service and not paying for it (hence the negative recommendation), 2) providing them your access passwords and 3) giving them access to whatever data you are transferring. You are also trusting their security model with your access and your data. You can get the same access by opening ports on your firewall/router for