Leaderboard

Решил немного облегчить жизнь новичкам и тем, кто успел подзабыть, где и что лежит. 1. Ссылка на загрузчики от 5.0 до 6.2 2. Как установить на примере загрузчика 1.04b для DSM 6.2 (918+) 3. Совместимость загрузчиков 6.0-6.2 и железа 4. Тестирование и как проверить работает ли транскодинг на примере Asrock J4105-itx, там же сборка extra.lzma с гибернацией дисков 5. Как отредактировать grub.cfg и заменить extra.lzma на работающей хрени 6. Пакет для активации железной кнопки Power off на корпусе хрени (крайняя версия 6.2-0002, на нее и ссылка) 7. Корректное отображение процессора в Информационном центре 8. Librusec на хрени через COPS (скачивание в fb2 и mobi на читалку с wi-fi прямо с хрени) 9. Torrent TV через Ace Stream в docker (актуальные команды в посте ID 273, инструкция в следующем) Просьба ссылки тут не обсуждать, добавляйте свои, если посчитаете полезным.

Just completed a new build, using an Asrock H370M-ITX board and 1.04b loader / DSM 6.2.2-24922, all fully functioning without any hassle or additional drivers. With 6 onboard SATA ports and 2 Intel NICs this is an ITX board to recommend.

Please see this for loaders vs. versions. 6.2.x has a number of hardware constraints on it, so you may need to pick your loader and platform carefully, referencing your hardware.

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 hardware is natively supported by DSM. Each DSM version is different as Synology does not need to support many types of hardware, as they build up a specific DSM for each hardware platform they sell. Fortunately, the base Linux kernel has much broader support for hardware than they intend. Most of us guessed at the hardware requirements and made (hopefully) intelligent selections on DSM versus hardware. Some build systems and then are distressed when the hardware isn't fully supported by the DSM platform they choose (sometimes this can be fixed by extra.lzma, and sometimes not). Unfortunately, Synology hardware knowledge is often imperfect, as the main boards are custom designed. Refer to the example below for DS3615 (I hope it will be completed more precisely in the future). DS3615xs Reference Hardware: CPU: Intel Core i3-4130 (Haswell) Chipset: Intel C20x? 4x1Gbe Ethernet: ??? Secondary SATA: ??? 10Gbe OEM: E10G18 (Aquantia AQC107) E10G17 (Mellanox Connect X-2/3/4) E10G15 (Tehuti) With even this information, we can make some good guesses on what hardware might be supported. We certainly can act on the 10Gbe cards since those are well known. Wouldn't it be great if we knew ALL the different drivers that are natively supported? Unfortunately this is a fairly difficult process if you are not a Linux guru (and a bit laborious even if you are). There are "user-reported" hardware compatibility threads out there, but many don't understand that those reports are both DSM version and platform specific. Furthermore, with the way hardware manufacturers reissue hardware with the same name but new PCI device number (such as the Intel PHYs on desktop motherboards), often not enough information is reported to confirm whether a specific piece of hardware is suitable for use. If you aren't sure if your hardware is supported, this post and the complementary DS918 driver guide aim to help you. Download the appropriate Excel spreadsheet to see key driver support in the DS3615 6.1.7 or 6.2.1 Synology custom kernel, and via loadable modules supplied with DSM. Hopefully it will help you select the best DSM platform for your purposes, and possibly inform your hardware purchases. DSM 6.1.7 DS3615 V1.04 2019-Feb-04.xls DSM 6.2.1 DS3615 V1.0 2019-Feb-04.xls

I generated an easy to install package to activate a mainboard connected power button for clean shutting down (instead login in web page). Install package for DSM 5.2, DSM 6.0 and DSM 6.1(.1): powerbutton_6.1-0004.spk powerbutton_6.1-0005.spk I have tested DSM 5.2 and DSM 6.1 for the DS3617 versions only in VM. Please report if there are any problems. Changelog Version 6.1-005 Added Braswell to INFO Version 6.1-004 Minor change for recognizing DSM 6.1.1 Version 6.1-003 Adding support for DSM 5.2 Version 6.1-0002 Combining DSM 6.0 and DSM 6.1 in one package Version 6.0/6.1-0001 Versions for DSM 6.0 and DSM 6.1 Hide

très bien , contacter moi mercredi ou jeudi je vous donnerais les info pour l'envoie etc ......

Hi everyone. After a grate help from 'dodo-dk' (You're the best man) and a lot of try and errors i managed to run DSM 6.2.1u6 on Proxmox 5.3-11. I'll share my insights and maybe it'll be useful for someone. Proxmox does have 4 LAN cards model to chose from the list, but as we all know Synology dropped drivers for some devices (e1000, vmware3...) so new version of DSM stopped working on Proxmox. But Proxmox allows you to chose different models (not shown in choosing list) , we just have to add it to 'args:' parameters, just like we did with usb boot key. For this to work you need to know few things: 1) This won't work on OVS bridge/bond - it has to be Linux bridge/bond 2) The Linux bridge/bond has to have gateway set When we are adding LAN card from 'args:' it looks like the LAN card chooses bridge/bond on which the gateway is set, so that's why it's needed to be set. First thing you may check it's if e1000e LAN card is available in your kvm. So in Proxmox shell write command: kvm -device help Under 'Network devices' you should see line: name "e1000e", bus PCI, desc "Intel 82574L GbE Controller" The next step is to find your 'args:' parameters. To do this we need to use another command: qm showcmd YOUR-VM-ID YOUR-VM-ID - is ID of your Xpenology machine with added e1000 LAN card. From the output you need to copy two arguments: netdev and device. In my case it looks like this: -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=00:11:32:2c:a7:85,netdev=net0,bus=pci.0,addr=0x12,id=net0' For this to work you have to remove the 'script' parts from 'netdev'' and change model from 'e1000' to 'e1000e' in device argument. you can also remove the " ' " signs. After changes it should look like this: -netdev type=tap,id=net0,ifname=tap100i0 -device e1000e,mac=00:11:32:2c:a7:85,netdev=net0,bus=pci.0,addr=0x12,id=net0 Next you need to add changed arguments in to the VM config file (/etc/pve/qemu-server/YOUR-VM-ID.conf). In my case 'args:' line looks like this: args: -device ich9-usb-ehci1,id=usb,multifunction=on,bus=pci.0,addr=0xa -drive file=/var/lib/vz/images/103/vm-103-USB103b.raw,format=raw,if=none,id=drive-usb-disk2,cache=writeback -device usb-storage,bus=usb.0,port=2,drive=drive-usb-disk2,id=usb-disk2,bootindex=1,removable=off -netdev type=tap,id=net0,ifname=tap103i0 -device e1000e,mac=BA:E2:8A:3B:AC:3E,netdev=net0,bus=pci.0,addr=0x12,id=net0 The last thing is to remove the 'net' device from config file, so just comment or remove the line with 'net' device. In Proxmox web interface the LAN device wont be visible, but it will work. So, summing things up, I'm not Proxmox specialist so i didn't knew all of that. One more time thank you 'dodo-dk' for your knowledge and time. God bless all Xpenology enthusiasts, Xpenology devs and Proxmox for being best free virtualization tool i know.

Bump for the addition of the 6.2.1 driver guide for DS3615. Comparing 6.1.7 and 6.2.1 is interesting, and I'll summarize findings here: r8168/r8169 support was completely removed from 6.2.1 on this platform Intel i40e and ixgbe drivers were enhanced on 6.2.1 to support newer cards Mellanox mlx4 and mlx5 drivers were enhanced on 6.2.1 to support newer cards Comparing DS3615 and DS918, in most cases there continues to be significantly better native driver support in DS3615, especially for 10Gbe+ cards. DSM supports many more 10Gbe+ cards than Synology lists on their compatibility matrix. However, loader 1.03b is really just broken, with many drivers causing kernel panics at boot, and some not working at all. Those who would use the driver list to inform an expensive hardware purchase should proceed with caution, and/or be willing to step backward to 1.02b and DSM 6.1.7 for compatibility reasons. @jun, if you are reading: there remains a need for the native driver library on DS3615 or DS3617, so if you can work 1.04b magic on the either platform, the community would benefit.

@Tretta Чот есть у мну ощущение что не взлетит у Вас эта свиноложи от 918+ на вашем камне ибо отсуйствие GPU в нем присутствует... Вам бы наверн лучше всего бут 1.3b брать от 3615 и dsm эту https://archive.synology.com/download/DSM/release/6.2/23739/DSM_DS3615xs_23739.pat и не обновлять...

Well, you need a certain minimum level of tech expertise to run XPEnology. If you aren't comfortable with that then you might be better off with a real Synology unit. There isn't a turnkey backup methodology to restore a broken XPEnology/DSM system. But there are a number of ways to back up various parts of it, here are some: 1. Keep a backup image of your loader on your PC hard drive so it can be rebuilt exactly every time 2. Save your system settings from DSM 3. If you are using ESXi, you can snapshot your VM prior to upgrade and roll it back if there is a problem 4. If you are using ESXi, you can backup your VM and scratch resources using any number of ESXi backup tools 5. If you want an separate copy of your data, build up another XPEnology NAS environment and use BTRFS replication 5a. If you are using Docker, you can replicate your whole Docker environment using BTRFS replication Backing up DSM itself to something like an image backup isn't the easiest thing to do, and generally isn't necessary.

A new usb drive won‘t help because of DSM‘s system partitions on each hdd which contain the „new“ system. There are several methods to get back in business. 1st) Boot a live linux, mount the raid and try to modify the text file which contains the version info (you‘ll have to search the forum for the exact name and path). 2nd) Disconnect all hdds, connect a new one, install the older version of DSM on it, shut down the system, reconnect the old drives and start it again. DSM should recognize the old RAID. 3rd) Hardcore method: delete each system partition (first partition) and reinstall DSM after that. Normally DSM should recognize the RAID array after the initial setup but with no warranty. In case of 2 & 3 all your settings will be lost.

Каких денег? Plex pass что ли? А на кой хрен он Вам? DLNA там холявный кстати. У меня установлен 4 года как бесплатно, на всех девайсах. Ну не нра Plex есть штатный DLNA и ему не нужен Videostation. Или есть ещё Serviio, тоже холява... Для мобилок Plex по моему рублей 300 что ли в play store/app store, если и стока отдать западло, на 4пда ломаные есть. В коди ставите официальный аддон бесплатно, так же и для мобилок... А с этим https://support.plex.tv/articles/201674343-scanning-disk-image-format-media/ он будет ещё и образы ремуксов искать...

А отключить транскодинг и тупо в браузере поток смотреть не умеет videostation?

Прокиньте на роутере 443 на ваш внутренний (5001 по умолчанию) и ходите через https без набора порта.

Если есть зарегестрированный домейн и проброшены порты на роутере-фаерволе, то можно создать бесплатный сертификат LetsEncrypt в поздних версиях DSM.

I don’t know if it works ootb with 1.02b but you won’t be able to use the 1.02b with DSM 6.2 (or I missed something). Usually Mellanox cards of this series are supported by Synology.

If you try it on proxmox and still get Hdd errors, than my guess would be some hardware malfunction.

@lamosca01 1 - Make sure you use a compatible CPU. 2 - Remove the old thermal paste from the cooler, and replace it with new. 3 - Avoid ESD damages during the swap. 4 - As always, make sure you have a functional backup of important data before starting.

Oui, énorme, pour la sécurité de ton NAS ! Les dernières failles sont comblées dans DSM 5.2 ou DSM 6.2 actuellement, et plus dans 6.1.

В общем, цитирую сам себя)) Решил, не дождавшись реальных владельцев этой платы, все же купить ее. Купил. Подготовился к нетривиальной процедуре прошивки ее в нужный для работы в DSM "IT-mode", начитался в интернете инструкций по этой процедуре прошивки БИОСа платы и... Вставил в компьютер, она инициализировалась и показала версию прошивки и ревизию и тут я приятно удивился, увидев что она уже прошита в "IT-mode". Что же, прекрасно, но пора подключить к ней пару дисков и попробовать загрузку XPenology. Перезагружаюсь, стартует загрузчик, система грузится, набираю заветный адрес в строке и вуаля - попадаю на страницу входа, вошел, проверил Диспетчер Хранения - все видит, все работает, все отлично. Итог - плату контроллера LSI 9211-i8 с прошивкой "IT-mode" смело можно рекомендовать для многодисковых конфигураций XPenology (DS918+ DSM 6.2.1). Вдруг кому-то эта информация будет нужной и полезной.

Yes. With Xpenology you can even change other components like the board and RAM.

bonjour , oui dispo contacter moi en Mp je vous donnerais info de payement et il me faudra aussi les votres

Удалите Cloud Station (ее поддержка завершена) Установите Synology Drive У меня уже полгода работает без проблем.

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: No - Installation type：BAREMETAL HP Proliant N54L

@MAKCOH Помимо правильных img и pat Нужно вписать vid pid от вашей флэшки в syslinux.config иначе установка всегда будет проходить с ошибкой... Это что касается 5,2 а для 6.0/6.1 загрузчик пропишет vid pid на шлэшку сам и она перестанет быть видна в системе...

? Dont understand your post....

ну тогда пробуйте по очереди

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: HP Proliant MicroServer Gen8 with E3-1265L V2 2.50GHz - Additional comments: Migrated from DS3617xs, internal nics do not work but Mellanox ConnectX-3 10GBe (MCX311A-XCAT) works, no need to disable internal nic in bios, you need them during installation, Shutdown and restart do not work

6.2.x не взлетит, 3616/3617 из-за сетевой карты, 918 из-за проца.

A little help for everyone who struggles a little bit with enabling the serial console in ESXi. This manual works 1:1: https://www.juniper.net/documentation/en_US/vmx15.1f4/topics/task/configuration/vmx-vm-connecting-vmware.html in short: # at ESXi: open Firewall for serial Console # at VM: add Serial Port 1 - Use Network - Connect at Power - Direction: Server - Port URI: telnet://:8601 In PuTTY the connection will be made as: Type: Telnet Hostname: IP-of-your-ESXi-Host Port: The-port-you-entered-in-the-config-of-the-VM (e.g. 8601) With this you have at every time contact to the Xpenology-VM-Console even a driver wont be load with a upgrade (like in Loader 1.02a).

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) - V2.76 - 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) - V1.0 (only available in V1.4.1) - OSFMount x64 (to mount the synoboot.img and modifiy it) - V1.5 - Notepad++ (best editor for changing values inside grub.cfg) - V7.5.3 - Synology Assistant (useful tool from Synology to find your XPEnology and install DSM) - V6.2-23733 - TFTP/DHCP portable (a small TFTP, DHCP and Syslog server by Ph. Jounin) - V4.6.2 - MiniTool Partition Wizard 10 (helps assigning already formatted/written USB devices to modify existing grub.cfg) - V10.3 - SoftPerfect Network Scanner - V6.2.1 - USB Image Tool - V1.75 - New: Rufus - V3.3 In the section "Downloads" all links open corresponding websites to download the files. For beginners I added a small HowTo for bare-metal installation. Update New link for download: https://mega.nz/#F!BtViHIJA!uNXJtEtXIWR0LNYUEpBuiA You'll have to run it "As Administrator" because some of these tools (like Win32 DiskImager) need to be executed with higher rights. It's possible that the SmartScreen filter will give you a warning, because the EXE isn't signed. Bug reports and comments are welcome Cheers Current version: V1.4.2 (2018-11-19)

- Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 update 6 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP MicroServer Gen8 - Additional comments: HP NC360T Network card, replication snapshot deactivated and removed and replaced by Replication Service...

- Outcome of the update: SUCCESSFUL - DSM version prior to update: DSM 6.2.1-23824U6 - Loader version and model: Jun v1.03b - DS3615 - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7 - Outcome of the update: SUCCESSFUL - DSM version prior to update: DSM 6.2.1-23824U6 - Loader version and model: Jun v1.04b - DS918 - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7 - Outcome of the update: FAILED - DSM version prior to update: DSM 6.2.1-23824U6 - Loader version and model: Jun v1.04b - DS918 - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J4105-ITX Failure notes - no network on Realtek, installed an Intel CT card and this doesn't work either. Tested a clean install using both NICs and encountered the same failure. BIOS version? Certain USB key device ID's? Need more information from anyone who is successfully installing 6.2.2 on 1.04b on an ASRock J-series device.

Mi fa piacere [emoji106]

This Intel website shows device ID's vs product names. The DSM 918 supported e1000e devices are visible in the spreadsheet here - just match them up. If you are just looking for something inexpensive for a PCIe x1 slot (most everybody has at least one of those), the Intel Gigabit CT is a good bet. 82574 chipset, device ID 10D3 and is current product, new for about $33 USD

Shr ничуть не хуже других вариантов стандартных raid'ов, если исходить, что вам не надо руками самому восстанавливать развалившийся том. А наверное 99% это не надо, потому что им надо не шашечки, и не в потрохах линукса покопаться, а ехать, и если информация ценная - надо иметь автоматический и регулярный бекап, тогда при развале тома быстренько этот том переинициализируем и восстанавливаем с бекапа, а если информация не такая уж и ценная - то при развале тома и хрен с ней ;-). Повторюсь - ни по скорости ни по надежности shr не хуже других соответствующих типов рейдов, ну и как побочный плюс - в некоторых случаях (см. Рейд калькулятор на сайте синолоджи) позволяет более полно использовать разноразмерные диски. Что кстати не является признаком того, что shr ориентирован на "мусорные" диски со свалки. п.с. Сижу исключительно на shr с 2010 года, дома два наса по четыре диска и на работе уже наверное с десяток 2 и 4 дисковых.

Большой файл, как вы его называете, есть не что иное как каталог в котором лежат базы в формате sql lite. Вся прелесть в том, что производится инкрементное бэкапирование и можно будет восстановить данные за любой промежуток времени (настраивается) от часа до недель. Если открывать этот каталог в файл стейшн, то можно провалиться внутрь и восстановить все вплоть до конечного файла. Не знаю почему у вас такое предубеждение к этому способу. Если просто использовать единичное бекапирование каталогов, то можно нарваться на вариант, когда случайно удаляется что-то важное, а бэкап успеет сработать до того, как из него успели восстановить, в этом случае информация потеряется навсегда. Я использую 2 одинаковых диска в зеркале для особо важных данных + их бэкап на 3й диск. Важные данные валяются на 3м диске + бэкап на 4й.

Думаю, что нет. Видюху можно пробросить в виртуалку, а вот про гпу проца не слышал.

Поставте пакет "Power button". Встроенную сетевую отключить в BIOS. C1 state выключить. Все работает включая сон и выключение.

This piece of kit is worth bout 700 bucks due to supply/demand right now, but I got one for 500. I was eager to put my janky Xpenology to bed, but the UI is so.... sluggish compared to my Xpenology with a 10 year old desktop processor. I'm really considering selling it and get a few bucks out of the deal. At least with my Xpenology, I can upgrade to 10 gb networking relatively cheaply. I love the Synology OS, but damn... their hardware sucks.

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 hardware is natively supported by DSM. Each DSM version is different as Synology does not need to support many types of hardware, as they build up a specific DSM for each hardware platform they sell. Fortunately, the base Linux kernel has much broader support for hardware than they intend. Most of us guessed at the hardware requirements and made (hopefully) intelligent selections on DSM versus hardware. Some build systems and then are distressed when the hardware isn't fully supported by the DSM platform they choose (sometimes this can be fixed by extra.lzma, and sometimes not). Unfortunately, Synology hardware knowledge is often imperfect, as the main boards are custom designed. Refer to the example below for DS918: DS918 Reference Hardware: CPU: Intel J3455 (Apollo Lake) GPU: Intel HD Graphics 500/505 Chipset: Intel SOC 2x1Gb Ethernet: ??? SATA: 88SE9125 PCIe SATA 6.0 Gb/s controller With even this information, we can make some good guesses on what hardware might be supported. Wouldn't it be great if we knew ALL the different drivers that are natively supported? Unfortunately this is a fairly difficult process if you are not a Linux guru (and a bit laborious even if you are). There are "user-reported" hardware compatibility threads out there, but many don't understand that those reports are both DSM version and platform specific. Furthermore, with the way hardware manufacturers reissue hardware with the same name but new PCI device number (such as the Intel PHYs on desktop motherboards), often not enough information is reported to confirm whether a specific piece of hardware is suitable for use. If you aren't sure if your hardware is supported, this post and the complementary DS3615 driver guide aims to help you. Download the attached Excel spreadsheet to see key driver support in the DS918 6.2.1 Synology custom kernel, and via loadable modules supplied with DSM. Hopefully it will help you select the best DSM platform for your purposes, and possibly inform your hardware purchases. DSM 6.2.1 DS918 V1.0 2018-Feb-03.xls

L5630 won't support the processor extension required by 1.04b/DS918+ Try using 1.03b/DS3615 instead of DS3617

организовал на неделе трансляцию с HD-камеры в ютуб через FFMPEG (машинки, кораблики - красота!), и возникла мысль добавить к ней какой-нибудь звук, чтоб дополнительно "оживить" картинку. звук хочу принимать по линейному входу через тот же FFMPEG, и миксить с видеопотоком, который уже принимается с камеры. на машине какая-то втроенная звуковуха есть, но среди девайсов я ничего про "sound" найти не смог. в аналогичных топиках пишут, мол, для вывода доступных устройств захвата надо запустить: $ arecord -l но это не работает (ash: arecord: command not found), ибо, как я понял, относится к ALSA (Advanced Linux Sound Architecture), а её необходимо как-то дюже сложно собирать. подскажите, друзья, можно ли как-то с минимальными телодвижениями (чтоб без докеров всяких) снять звук с линии (пусть даже не со встроенной карты, а с какого-нить USB), и пропихнуть его в FFMPEG? на "родном" syno-форуме подобные вопросы без ответов, а всякие другие посты про убунту/расп меня только глубже запутали, что я вообще не могу понять с какой стороны копать...

Your low ammount of free RAM is due to the 13,6 GB that's currently marked as reserved, leaving you with 2,4 GB with usable RAM. Take a look here, and se if it helps with your other problem as well.

Hat sich erledigt. Hab die synoboot.img mit ofsmount gemountet und den die grub.cfg editiert. USB Stick und MAC Adresse angepasst. Stick neu geflasht und nun geht er über 56 % und DSM sagt hallo.

Login (replace URL, PORT, USER, PASS) https://URL:PORT/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=USER&passwd=PASS for ActiveBackup its the following urls Get Activationstatus https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=get&version=1 Set ActivationStatus (use your SERIALNUMBER) https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="SERIALNUMBER"  for Office365 its the following urls Get Activationstatus https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupOffice365&method=get_activation&version=1 Set ActivationStatus (use your SERIALNUMBER) https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupOffice365&method=set_activation&version=1&serial_number="SERIALNUMBER" for GSuite its the following urls Get Activationstatus https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=get_activation&version=1 Set ActivationStatus (use your SERIALNUMBER) https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=set_activation&version=1&serial_number="SERIALNUMBER"

Your CPU is not compatible.. It needs some additional instructions that Haswell has (and Ivy Bridge does not). It needs to be 4th Gen or better for DS918.. No way around it - even in a VM.. You CAN use DS3615 or DS3617 though..

12 - How can I regain high amounts of reserved memory when looking in DSM's Resource Monitor? Add disable_mtrr_trim to the 'set common_args_3615' line in the grub.cfg file contained in the loader (applicable to jun's loader). It should look something like this: set common_args_3615='disable_mtrr_trim syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet' That should give you back all the reserved RAM. Note: DS3617xs use 'set common_args_3617' and DS916+ uses 'set common_args_916'

Very nice work....thanks everybody, and especially to Trantor... This build works perfectly well, and I had absolutely no trouble upgrading my 4.2 version to this one...just reinstalling a few packages and doing some basic configuration... The work that has been done is just amazing...