Leaderboard


Popular Content

Showing content with the highest reputation since 07/12/2018 in all areas

  1. 2 points
    get yourself stuff like debugger, IDA, ... reverse engineer jun's "patch" (its part of the loader) and redo it for the other systems (kernels, the loader is pretty much the same, the hack is specific for every platform aka kernel) i guess the 918+ is just the test to see if all protections are gone and the patch is 100% working, investing work on two other platforms and having to redo it because something was missing in the 1st try is not much fun i guess, if everything with 918+ goes well for a while i expect jun will release more just give it a while i guess its like solving a problem (doing one/1st platform patch) is fun and maintaining stuff (doing more platforms) is work, to make it useful for many people you will have to do both but you want to minimize the 2nd part, i think (just logic) jun will at least do a patch for 3617 later to see if potential problems are found, if 3617 can handle all hardware like 3615 it makes not much sense to maintain 3615 further, the update support of synology will end earlier for 3615, but i don't know anything about how jun's point is there so its pure speculation based on things i've catched here in the forum so be patient or start hacking (an if you are on hacking, just have a look for the sata kernel mod's synology did so we can have sata_*.ko/pata_*.ko drivers)
  2. 2 points
    I picked up an Asrock J3455B-ITX motherboard and performed a bunch of tests. Here's what I've found: When a screen is plugged in (i was using VGA), the system was very unstable - rebooting every 5-10mins. Disconnecting VGA cable and USB keyboard helped. Used serial cable to monitor boot progress. Hardware transcoding worked in both Plex and Video station. I had 3 hardware transcoded streams (1 x video station, 2 x plex) running simultaneously without any problems. However - after a some time, hardware transcoding wouldn't work from either app until the system was restarted. When using the 2 onboard SATA ports only, the kernel would panic and reference something about activating the AHCI_LED. Adding in a 2 port AHCI SATA card seemed to get around it (although i need to do this anyway as 2 ports isn't enough!) Booting is pretty slow compared to 1.02b. Seems to hang at "Post init" for some time. Maybe due to the following "failed to send sync event, type resync, finish 0, interrupt 0?" Network speeds are pretty disappointing too. File transfer to my existing NAS (4 drive SHR array / jun loader 1.02b / DSM 6.1.7): Whereas to the new "test" nas (4 drive RAID 0 array / jun loader 1.03b / DSM 6.2): So for me to get a working system i need to: Install a 2 port PCI-e SATA controller to get around the AHCI_LED panic Switch to CSM/BIOS boot mode. Otherwise the boot process doesn't always pickup the SATA controller Ensure no VGA cable plugged in Ensure boot USB stick is in USB2 port (only 1 on the back, the rest are USB3) Need to investigate the transcoding issue and try speed up the network as it's terrible
  3. 2 points
    Hi! I made a little tool which can help you to get your XPEnology up & running without installing any software. It contains (as portable versions): - Nirsoft's USB device view (helps to identify the VID & PID of your USB boot media) - XPEnology Serial Generator for DS3615XS, DS3617XS and DS916+ (a converted version of the HTML site) - Win32 DiskImager (to write your modified synoboot.img to your USB boot media) - OSFMount x64 (to mount the synoboot.img and modifiy it) - Notepad++ (best editor for changing values inside grub.cfg) - Synology Assistant (useful tool from Synology to find your XPEnology and install DSM) - TFTP/DHCP portable (a small TFTP, DHCP and Syslog server by Ph. Jounin) In the section "Preparation" all links open corresponding websites to download the files. Size: 78MB Format: stand alone EXE Link: https://mega.nz/#!wwlBhQjI!gms9Be7YOefvgfnniTtn8DjvX8Z_pfmwdhy_pwbYxtI You'll have to run it "As Administrator" because some of these tools (like Win32 DiskImager) need to be executed with higher rights. Hope this tool will help the community. Bug reports and comments are welcome Cheers Current version: V1.2.2 (2018-05-25) Changelog V1.2.2 - Added download links for DSM 6.1.7 - Removed download links for DSM 6.1.4 - Added warning window for DSM 6.2 V1.2.1 - Added Tftpd64 portable from Ph. Jounin which includes a TFTP, DHCP and Syslog server in case you don't have a DHCP running in your LAN - switched from buttons to dropdown list for DSM downloads V1.2 - Added download links for DSM 6.1.4, 6.1.5 & 6.1.6 for DS3615XS, DS3617XS & DS916+ V1.1 Initial release Hide
  4. 1 point
    As DSM 6.2 finally released, I spent a few days to identify new kernel side validation mechanism, and got some ideas to work around it, the early-stage experiment seems work, so, the exciting part(for me) is done. A new loader will be released when it is ready.
  5. 1 point
    This version is alpha, as the loader 1.03a2 is, so DO NOT use this on a "production" systems and be prepared to loose the data you have on the "test-system" (I recommend you have a very recent backup) !!!all sata_* and pata_* drivers are still not working because of the kernel source changes Synology did (same as in kernel 3.10.102 used and modded by Synology), as long as no one writes a patch for this I can use to fix this, it will stay this way !!! To check if the hardware is supported with a driver, use a running DSM installation or boot a live Ubuntu from usb. In console type the following: lspci -k | grep 'Kernel driver' That command will list the used kernel modules for the hardware. Modules for network and storage will be listed. Compare that with the list of modules that comes with the extra.lzma ramdisks provided below. extra.lzma for DS918+ v0.2 http://s000.tinyupload.com/?file_id=07387126858558680182 At the moment, kernel modules are listed by name in the following section. The listing will be improved later to look like the one in the 1.02b thread. At the moment the kernel module names can be looked up in the 1.02 driver extension thread. Kernel module list CPU list for DS918+ Image - 4th gen Intel Core aka Haswell seems to be minimum requirement If you wish to make a driver request do so in the topic linked below: If you wish to discuss problems about modules in these ramdisks then drop a post below. Please be specific and provide relevant information such as: ramdisk version, loader model, motherboard and any additional storage/networks cards present in the system. Other things good to know about DS918+ image and loader 1.03a2: 1. DS918+ image comes with a limit for 2 internal network ports in synoinfo.conf (the original hardware has two ports and does not have a pcie slot for extending) jun's loader does not changes this (now?), so if you plan to user more then 2 ports you will have to manually change the synoinfo.conf (3615 and 3617 are bigger business models and have options for additional network card, the default from synology is 8 on this systems) further information can be read here: 2. hardware transcoding seems to crash the system when a monitor is attached, unplug monitor, reboot try again to see if there is decoding hardware present you can try this (there should be something in like card0) ls -al /dev/dri/ when using plex you should download the 64bit version from website, with plex pass active (hardware-accelerated streaming is a premium feature and requires an payed active Plex Pass subscription), Settings > Server > Transcoder, Turn on Show Advanced, Turn on Use hardware acceleration when available 3. if your screen goes blank during boot and the system does not show up in network the kernel might have crashed on boot while loading i915.ko driver (CPU internal GPU) look in your bios for a legacy mode option, disable it and try again (boot process and crash can be seen when using a "good old" serial cable and a console program like putty on a 2nd computer - that's rarely done but if you want to know for sure, that's your way to find out, DSM does not have a typical boot screen that shows log info and login prompt after boot, that's redirected to the serial port)
  6. 1 point
    I am waiting for this too as I have no use for plex and my Xpenology 6.1.7 under Vmware 6.5 on HP Microserver Gen8 is working awesome.
  7. 1 point
    Hi there! Is there a possibility to build a new fork of this loader for DS3615xs/DS3617xs for older CPUs? How this can be done? Thanks in advance!
  8. 1 point
    DSM: 6.2-23739 Update 2 - Результат обновления: НЕУСПЕШНО! (не виден в сети) - версия DSM до обновления: DSM 6.2-23739 Update 1 - версия и модель загрузчика: Jun's Loader v1.03a2 - DS918 + - железо: Gigabyte N3150N-D3V - дополнительные комментарии: требуется перезагрузка! TEST.
  9. 1 point
    Без проблем также подсовывается файл bios (CPQJ0613.4B5), без создания загрузочной флешки.
  10. 1 point
    почитать материалы по сетевой безопасности и не выставлять голую "жопу" в сеть, долбиться будут в любом случае, а если с паролями вида 12345 - то и по самые гланды
  11. 1 point
    Там же пишут, что hw транскодинг работает на g4560, а это совсем не apollo lake, может кто тоже поэксперементирует. VideoStation and Plex work with hwaccel, no more rebooting. I've tried both BIOS and UEFI boot and they both behave the same way, it seems transcoding works fine with a G4560 as long as no displays are connected.
  12. 1 point
    новый биос (05.21.2018(A)) и ило (2.60) можно скачать с оф сайта без смс и регистрации. ило разархивировал и подсунул файл *.bin через веб интерфейс, биос тоже разархивировал и создал загрузочную флешку (средства для создания внутри архива)
  13. 1 point
    J4205 seems to work fine out of the box. I do have a PCIe SATA adapter which was recognized just fine. I also have 3 bonded NIC connections (1 internal, 2 gigabit ethernet USB 3.0 dongles), so I did have to increase the settings in synoinfo to reflect the additional NIC (standard is 2, had to bump to 3). Thank you guy that figured that out before me!!! Hw accelerated transcoding seems to work. One stream is averaging about 20-35% cpu via Emby streaming when I was playing it in a different resolution. Idles at 1-3% when running native resolution. The system has been rock solid for me. No resets, no dropped connections, no errors that I can see. I have 6x4TB WD Gold drives. Overall, 1.03a2 configured as DS918+ on the Asrock J4205 is running great.
  14. 1 point
    Pas de soucis, attention passe bien a la version 6.1.x et non 6.2 !
  15. 1 point
    Hi, Out of curiosity, what do you have you system configured as: DS918+, 916,3615xs, 3617xs? I'm very happy with my Supermicro X10SL7-F mbrd with E3-1241v3: it's rock solid (configured as a DS3615xs) with 9x8TB (WD80EFZX)in RAID 6 config; 6 of the drives are connected on the SATA ports and remainder on 3 of the 8 LSI2308 SAS ports. I did recently experience connection errors with one of the drives which has now been RMA'd back to WD, Vietnam, for replacement under warranty. Am using the box mainly media storage (photo collections; Plex server for my smart tv; and media downloads via Sonar, SABnzbd, etc). Using my old DS1513+ (5x4TB WD40EFRX) to back up important data via Hyperbackup. Have additional off-site backup of important data via a 4 mile wi-fi connection across the valley to my son's house. Use that same connection to access his video library and for his family to access mine. While I have both the X10SL7-F LAN ports bonded, I'm getting transfer rates of averaging 90 MB/s to my desktop PC whilst simultaneously transferring at about 30 MB/s to a notebook PC (also via a hardwired ethernet connection). This is with multiple (15~20 Mb) photo jpgs and the occasional video files ranging in size from 70 Mb to upwards of 500 Mb). I am getting read/write speeds on the Xpenology box maxing out my PCs single ethernet connection at 107~114 MB/s (mainly about 110~112 MB/s). No problems running Photostation for displaying photo library; but original media is stored separately on the disks. No problems running the DSM 6.1.7-15284-1 using Jun's 1.02b, I'm not game to try moving to DSM 6.2 with Jun's 1.03a, just yet.
  16. 1 point
    Поставил 6.2 с загрузчиком 1.03а2 еще 3 июля. Все стало на железо, мигрировал. Все настроилось. МАК и SN от настоящего 918+. Все работает, один серьезный баг, при простое (при отключенном спящем режиме), все равно уходит в сон, и из него уже не возвращается, только перезагрузка. Если активно пользоваться (файлы, фильмы и прочее) , то проблем нет. Уже даже штатно обновился на 6.2 -update 1. Железо N3700-ITX - сетевухи две, встроенная и дополнительная интел EXPI9300PT. Обе видны и объединены в BOND.
  17. 1 point
    i wonder if jun will release a 3615 / 3617 bootloader? seems that it was the most popular loader to go with
  18. 1 point
    WOL switch enabled in DSM?
  19. 1 point
    This is a variation of the 'Clean Drive' downgrade process I've described before in several threads 1) Disconnect your raid drives 2) Connect spare HDD to SATA port 1 3) Install DSM 6.x from fresh 1.02b loader, create admin user and server name matching live system, DONT create volume/raid. Update DSM to match your pre-beta version 4) Shutdown, reconnect raid drives to SATA ports 2-n 5) Boot, login, repair system partitions on raid, shutdown 6) Remove spare HDD and reconnect raid drives to SATA ports 1-n 7) Boot, repair packages etc My additional steps would be to power down the server between drive swaps and update DSM on the clean drive to the version matching the one running before crash.
  20. 1 point
    Hi, here you go. https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng
  21. 1 point
    Just thought to share some of the performance I'm seeing after converting from baremetal to ESXi in order to use NVMe SSDs. My hardware: SuperMicro X11SSH-F with E3-1230V6, 32GB RAM, Mellanox 10GBe, 8-bay hotplug chassis, with 2x WD Red 2TB (sda/sdb) in RAID1 as /volume1 and 6x WD Red 4TB (sdc-sdh) in RAID10 as /volume2 I run a lot of Docker apps installed on /volume1. This worked the 2TB Reds (which are not very fast) pretty hard, so I thought to replace them with SSD. I ambitiously acquired NVMe drives (Intel P3500 2TB) to try and get those to work in DSM. I tried many tactics to get them running in the baremetal configuration. But ultimately, the only way was to virtualize them and present them as SCSI devices. After converting to ESXi, /volume1 is on a pair of vmdk's (one on each NVMe drive) in the same RAID1 configuration. This was much faster, but I noted that Docker causes a lot of OS system writes which spanned all the drives (since Synology replicates the system and swap partitions across all devices). 32GB RAM is enough to avoid swap activity so that was irrelevant, so I isolated DSM I/O to the NVMe drives by disabling the system partition from the RAID10 disks: mdadm /dev/md0 -f /dev/sdc1 .../dev/sdh1 then mdadm -grow -n 2 /dev/md0 then repair from DSM Storage Manager (which converts the "failed" drives to hotspares) After this, no Docker or DSM system I/O ever touches a spinning disk. Results: The DSM VM now boots in about 15 seconds. Docker used to take a minute or more to start and launch all the containers, now about 5 seconds. Copying to/from the NVMe volume maxes out the 10GBe interface (1 gigaBYTE per second) and it cannot fill the DSM system cache; the NVMe disks can sustain the write rate indefinitely. This is some serious performance, and a system configuration only possible because of XPEnology! Just as a matter of pointing out what is possible with Jun's boot loader, I was able to move the DSM directly from baremetal to ESXi, without reinstalling, by passthru of the SATA controller and the 10GBe NIC to the VM. I also was able to switch back and forth between USB boot using the baremetal bootloader menu option and ESXi boot image using the ESXi bootloader menu option. Without the correct VM settings, this will result in hangs, crashes and corruption, but it can be done. I did have to shrink /volume1 to convert it to the NVMe drives (because some space was lost by virtualizing them), but ultimately was able to retain all aspects of the system configuration and many months of btrfs snapshots converting from baremetal to ESXi. For those who are contemplating such a conversion, it helps to have a mirror copy to fall back on, because it took many iterations to learn the ideal ESXi configuration.
  22. 1 point
    UPDATE: (tl;dr) Heretofore, XPEnology DSM under ESXi using virtual disks is unable to retrieve SMART information from those disks. Disks connected to passthrough controllers work, however. NVMe SSDs are now verified to work with XPEnology using ESXi physical Raw Device Mapping (RDM). pRDM allows the guest to directly read/write to the device, while still virtualizing the controller. NVMe SSDs configured with pRDM are about 10% faster than as a VMDK, and the full capacity of the device is accessible. Configuring pRDM using the ESXi native SCSI controller set specifically to use the "LSI Logic SAS" dialect causes DSM to generate the correct smartctl commands for SCSI drives. SMART temperature, life remaining, etc are then properly displayed from DSM, /var/log/messages is not filled with spurious errors, and drive hibernation should now be possible. Like many other posters, I was unhappy with ESXi filling the logfiles with SMART errors every few seconds, mostly because it made the logs very hard to use for other things. Apparently this also prevents hibernation from working. I was able to find postings online using ESXi and physical RDM to enable SMART functionality under other platforms, but this didn't seem to work with DSM, which apparently tries to query all drives as ATA devices. This is also validated by synodisk --read_temp /dev/sdn returning "-1" I also didn't believe that pRDM would work with NVMe, but in hindsight I should have known better, as pRDM is frequently used to access SAN LUNs, and it is always presented as SCSI to the ESXi guests. Here's how pRDM is configured for a local device: https://kb.vmware.com/s/article/1017530 If you try this, understand that pRDM presents the whole drive to the guest - you must have a separate datastore to store your virtual machine and the pointer files to the pRDM disk! By comparison, a VMDK and the VM that uses it can coexist on one datastore. The good news is that none of the disk capacity is lost to ESXi, like it is with a VMDK. Once configured as a pRDM, the NVMe drive showed up with its native naming and was accessible normally. Now, the smartctl --device=sat,auto -a /dev/sda syntax worked fine! Using smartctl --device=test, I found that the pRDM devices were being SMART-detected as SCSI, but as expected, DSM would not query them. NVMe device performance received about a 10% boost, which was unexpected based on VMWare documentation. Here's the mirroring operation results: root@nas:/proc/sys/dev/raid# echo 1500000 >speed_limit_min root@nas:/proc/sys/dev/raid# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] <snip> md2 : active raid1 sdb3[2] sda3[1] 1874226176 blocks super 1.2 [3/1] [__U] [==>..................] recovery = 11.6% (217817280/1874226176) finish=20.8min speed=1238152K/sec <snip> Once the pRDM drive mirrored and fully tested, I connected the other drive to my test VM to try a few device combinations. Creating a second ESXi SATA controller has never tested well for me. But I configured it anyway to see if I could get DSM to use SMART correctly. I tried every possible permutation and the last one was the "LSI Logic SAS" controller dialect associated with the Virtual SCSI controller... and it worked! DSM correctly identified the pRDM drive as a SCSI device, and both smartctl and synodisk worked! root@testnas:/dev# smartctl -a /dev/sdb smartctl 6.5 (build date Jan 2 2018) [x86_64-linux-3.10.102] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: NVMe Product: INTEL SSDPE2MX02 Revision: 01H0 Compliance: SPC-4 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Logical block size: 512 bytes Rotation Rate: Solid State Device Logical Unit id: error: bad structure Serial number: CVPD6114003E2P0TGN Device type: disk Local Time is: Wed Mar 28 19:00:29 2018 PDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Disabled or Not Supported === START OF READ SMART DATA SECTION === SMART Health Status: OK Current Drive Temperature: 26 C Drive Trip Temperature: 85 C <snip> root@testnas:/dev# synodisk --read_temp /dev/sdb disk /dev/sdb temp is 26 And, in Storage Manager: Finally, /var/log/messages is now quiet. There is also a strong likelihood that drive hibernation is also possible, although I can't really test that with NVMe SSD's.
  23. 1 point
    Unfortunately this didn't help. It turned out that 918+ has a different tools in /usr/bin and /usr/syno/bin. There are for example new these binaries that are missing on DS3515xs: root@DSM:~# nvme nvme-0.9 usage: nvme <command> [<device>] [<args>] The '<device>' may be either an NVMe character device (ex: /dev/nvme0) or an nvme block device (ex: /dev/nvme0n1). The following are all implemented sub-commands: list List all NVMe devices and namespaces on machine id-ctrl Send NVMe Identify Controller id-ns Send NVMe Identify Namespace, display structure list-ns Send NVMe Identify List, display structure create-ns Creates a namespace with the provided parameters delete-ns Deletes a namespace from the controller attach-ns Attaches a namespace to requested controller(s) detach-ns Detaches a namespace from requested controller(s) list-ctrl Send NVMe Identify Controller List, display structure get-ns-id Retrieve the namespace ID of opened block device get-log Generic NVMe get log, returns log in raw format fw-log Retrieve FW Log, show it smart-log Retrieve SMART Log, show it smart-log-add Retrieve additional SMART Log, show it error-log Retrieve Error Log, show it get-feature Get feature and show the resulting value set-feature Set a feature and show the resulting value format Format namespace with new block format fw-activate Activate new firmware slot fw-download Download new firmware admin-passthru Submit arbitrary admin command, return results io-passthru Submit an arbitrary IO command, return results security-send Submit a Security Send command, return results security-recv Submit a Security Receive command, return results resv-acquire Submit a Reservation Acquire, return results resv-register Submit a Reservation Register, return results resv-release Submit a Reservation Release, return results resv-report Submit a Reservation Report, return results dsm Submit a Data Set Management command, return results flush Submit a Flush command, return results compare Submit a Compare command, return results read Submit a read command, return results write Submit a write command, return results write-zeroes Submit a write zeroes command, return results write-uncor Submit a write uncorrectable command, return results reset Resets the controller subsystem-reset Resets the controller show-regs Shows the controller registers. Requires admin character device discover Discover NVMeoF subsystems connect-all Discover and Connect to NVMeoF subsystems connect Connect to NVMeoF subsystem disconnect Disconnect from NVMeoF subsystem version Shows the program version help Display this help See 'nvme help <command>' for more information on a specific command The following are all installed plugin extensions: intel Intel vendor specific extensions lnvm LightNVM specific extensions memblaze Memblaze vendor specific extensions See 'nvme <plugin> help' for more information on a plugin Or: root@DSM:~# synonvme Usage: synonvme --is-nvme-ssd <nvme path> check if a device is a nvme ssd --sn-fr-get <nvme path> get controllor SN and firmware reversion --model-get <nvme path> get nvme disk model --vendor-get <nvme path> get nvme disk vendor --get-location nvme_path / nvme_name get the pcie slot and card slot --smart-info-get nvme_path / nvme_name get the smart information --remaining-life-get nvme_path / nvme_name get the remaining life --temperature-get nvme_path / nvme_name get the temperature I have manually copies those binaries from 918+ to my XPEnology, commands are executed fine, but DSM is still not able to find the drive nor syno_hdd_util. It looks to me that there are also changes to the other binaries under /usr/bin and /usr/syno/bin. I suppose it's not a wise thing to overwrite everything by data from 918+ image on my XPEnology?
  24. 1 point
    DSM PAT files can be found here (Major updates): DSM 6.0.2: https://archive.synology.com/download/DSM/release/6.0.2/8451/ Chose .pat file DS3615xs DSM 6.1: https://archive.synology.com/download/DSM/release/6.1/15047/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.1: https://archive.synology.com/download/DSM/release/6.1.1/15101/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.2: https://archive.synology.com/download/DSM/release/6.1.2/15132/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.3: https://archive.synology.com/download/DSM/release/6.1.3/15152/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.4: https://archive.synology.com/download/DSM/release/6.1.4/15217/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.5: https://archive.synology.com/download/DSM/release/6.1.5/15254/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM6.1.6: https://archive.synology.com/download/DSM/release/6.1.6/15266/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM6.1.7: https://archive.synology.com/download/DSM/release/6.1.7/15284/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates for all DSM versions can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/ or http://archive.synology.com/download/DSM/criticalupdate/update_pack/ Critical Updates specifically for DSM 6.0.2 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-2/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-3/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-4/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-5/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-6/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-7/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-8/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-9/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-10/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-11/ Chose .pat file DS3615xs Critical Updates specifically for DSM 6.1 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15047-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15047-2/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.1 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-2/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-3/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-4/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.2 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15132-1/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.3 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-2/ - Does not apply to DS3615xs or DS3617xs or DS916+ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-3/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-4/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-5/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-6/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-7/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-8/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.4 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-2/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-3/ - Update was removed by Synology without warning http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-3/ - Re-added by Synology (different md5) http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-4/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-5/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.5 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15254-1/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.6 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15266-1/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly --------------------------------------------------------------------------------------------- All links above are provided for the sake of completeness but simply going to: https://www.synology.com/en-global/support/download or https://archive.synology.com/download/DSM/ and then clicking the desired subsequent links will yield all the above. Seek and you shall find. Change log [22/09/2017] Changed http://download.synology.com/download/DSM/release/ to http://usdl.synology.com/download/DSM/release/. Synology closed all DSM release downloads from http://download.synology.com/download/DSM/release/. Only Critical updates are available in that repository to this date. [14/12/2017] Added new updates [20/02/2018] Added new updates for 6.1.4 [26/05/2018] Added new updates for 6.1.5 and 6.1.6 and 6.1.7 - For releases http://usdl.synology.com/download/DSM/release/ is now redirecting to http://archive.synology.com/download/DSM/release/ so all links have been updated.

Announcements