Popular Content

Showing content with the highest reputation since 03/22/2018 in all areas

  1. 75 points
    Hi, everyone, Thanks for you patience. A new ds918 loader support 6.2/6.21 is uploaded. whats new: uefi issue fixed. i915 driver updated. link https://mega.nz/#F!Fgk01YoT!7fN9Uxe4lpzZWPLXPMONMA ---Beginning of addition by polanskiman--- ---End of addition by polanskiman---
  2. 54 points
    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.
  3. 28 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) - 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)
  4. 23 points
    In addition to bricked boxes due to inattentive upgrades, there seems to be a surge of questions regarding how to select a DSM platform, version and loader. This table should help navigate the options and current state of the loaders. While situations rapidly change, it should be correct as of the listed date. 6.x Loaders and Platforms as of 12/Jan/2019 Loader DSM Platform DSM Version Kernel DSM /dev/dri DSM NVMe cache Boot method CPU Needed Notes 1.04b DS918 6.2 to 6.2.1 4.4.x Supported Supported EFI or Legacy BIOS Haswell or later recommended 1.03b DS3615 6.2 to 6.2.1 3.10.x Not Supported Not Supported Legacy BIOS only Nehalem or later 6.2.1 requires Intel NIC 1.03b DS3617 6.2 only 3.10.x Not Supported Not Supported Legacy BIOS only Nehalem or later 6.2.1 crashes on USB kernel drivers 1.02b DS916 6.0.3 to 6.1.7 3.10.x Supported Not Supported EFI or Legacy BIOS (Jun) MBR (Genesys) Nehalem or later 1.02b DS3615 6.0.3 to 6.1.7 3.10.x Not Supported Not Supported EFI or Legacy BIOS (Jun) MBR (Genesys) Nehalem or later recommended 1.02b DS3617 6.0.3 to 6.1.6 3.10.x Not Supported Not Supported EFI or Legacy BIOS (Jun) MBR (Genesys) Nehalem or later 6.1.7 crashes under ESXi for unknown reason 1.01 DS916 or DS3615 or DS3617 6.0 to 6.0.2 3.10.x Not Supported Not Supported EFI or Legacy BIOS (Jun) MBR (Genesys) Nehalem or later obsolete
  5. 16 points
    Hello! I am xpenology user. And I am an IT engineer who creates shell scripts as hobbies. Please understand that it is written by a google translate site. because i’m korean who is not fluent in English. I created a tool to change cpu information for Xpenology’s users. Modify the actual cpu name and cores of your pc or server. Howto Run ============================================================= 1. Download attached file on your PC (ch_cpuinfo_en.tar) / (ch_cpuinfo_kr.tar is file for korean) 2. Upload file to your DSM location (by filestation, sftp, webdav etc....) 3. Connect to ssh by admin account. (dsm > control panel > terminal & snmp > terminal > enable ssh check) 4. Switch user to root: sudo su - (input admin password) 5. Change directory to where ch_cpuinfo_en.tar file is located: cd /volume1/temp 6. Decompress file & check file: tar xvf ch_cpuinfo_en.tar ls -lrt (check root’s run auth) 7. Run to Binary file ./ch_cpuinfo or ./ch_cpuinfo.sh (If you use busybox in DSM 5.x, you can use it as a source file) 8. When you execute it, proceed according to the description that is output. 9. Check your DSM’s CPU name, CPU cores at “information center” ==================================================== Addtional, Adjust binary to excute file made by shc(http://www.datsi.fi.upm.es/~frosal) The tool does not inclue worms, bad code. If you want to edit the CPU information yourself manually, please refer to the contents below. ——————————————————————————————————————————————————————————————— Location : /usr/syno/synoman/webman/modules/AdminCenter Source : admin_center.js / admin_center.js.gz(above 6.2) Add Before -> if(Ext.isDefined(f.cpu_vendor)&&Ext.isDefined(f.cpu_family)&&Ext.isDefined(f.cpu_series)){ o.push([_T("status","cpu_model_name"),String.format("{0} {1} {2}",f.cpu_vendor,f.cpu_family,f.cpu_series)])} if(Ext.isDefined(f.cpu_cores)){o.push([_T("status","cpu_cores"),f.cpu_cores])} Add contents: f.cpu_vendor="Intel";f.cpu_family="Xeon";f.cpu_series="E3-1230 V2";f.cpu_cores="1"; ——————————————————————————————————————————————————————————————— Finally, All descriptions are based on version 6.2, and the actual executable file supports both 5.x and 6.x. Please contact me by comment or bug report, i’ll respond to you as much as possible within my ability. Test & Made Environment ———————————————————————————————————— Base Server : HP Microserver gen8 + VMware ESXi 6.0 + RDM DSM : 6.2-23739 Update 2 (DS3615xs/DS3617xs) 6.1-15284 Update 2 (DS3615xs) ———————————————————————————————————— Thank you!! Have a nice day!! ============================================= Update new version 2018.08.26 I made the tool by adding and improving the function. Please refer to above for how to use it. I delete the old version attached files, new version uploaded and attached. If you use last version tool, you can use without restore. Additional,  It does not yet apply to "mobile web" and "DS finders". it's working.... and... Polanskiman give editable permission to me. so, i can do first article.. thanks Polanskiman !!! ============================================================================ Update new version (ch_cpuinfo ver 4.0) 2018.09.13 1. Mobile support (just 6.x / not yet 5.x) You can see it when you go into mobile browser or "DS mobile" menu in "DS Finder" 2. Improved CPU information collection command Some dmidecode commands have been found to be missing information and have been improved.(Thanks stefauresi !!! ) 3. Edited some variable names I adjusted some inconsistently coded variables Addtional, Usage is the same as before. and Existing users can apply by "2) Rerun". Unfortunately, DS Finder's own app does not reflect system information. It seems to refer to other information and it seems to have to study more. I checked as much as I could ... There may be errors found. Let me know in that time and I will reflect it If you want to edit the CPU information yourself manually, please refer to the contents below. ——————————————————————————————————————————————————————————————— Location : /usr/syno/synoman/mobile/ui (6.x), /usr/syno/synoman/webman/mapp(not yet 5.x) Source : mobile.js / mobile.js.gz(above 6.2) {name: "model",label: _T("common", "ds_model")}, -> Add Back Add Contents: {name: "cpu_series",renderer: function(value){var cpu_vendor="Intel";var cpu_family="Xeon";var cpu_series="E3-1230 V2";var cpu_cores="1"; return Ext.String.format('{0} {1} {2} ({3}Core)', cpu_vendor, cpu_family, cpu_series, cpu_cores);},label: _T("status", "cpu_model_name")}, ——————————————————————————————————————————————————————————————— ============================================================================ Update new version (ch_cpuinfo ver 5.0) 2018.10.30 1. Improved CPU information collection command (Thanks to gericb, Vileserver) Change to pure core value without applying thread, and For Native H/W users, changed to display the number of cpus, the number of cores per cpu, and the number of threads. ## Vmware 1 CPU / 1 Core Setting ## Vmware 1CPU / 2Core Setting ## ex. 1 CPU 1 Core Not support HT -> 1 Core (1 CPU | 1 Thread) 1 CPU 2 Core Support HT -> 2 Cores(1 CPU/2 Cores | 4 Threads) 2 CPU 4 Core Support HT -> 8 Cores(2 CPUs/4 Cores | 16 Threads) Addtional, Let me give you my excuse.... Where I work I count the number of threads by the number of logical cores. It was a habit of judging it because of work, so I was able to display the total number of cores without any thought. I apologize for the wrong information. Core information collection method, please refer to the contents below. ============================================================================================ ## before cat /proc/cpuinfo | grep "processor" | wc -l ## After(The result of the following command is combined and dispalyed.) cat /proc/cpuinfo | grep "processor" | sort -u | wc -l cat /proc/cpuinfo | grep "physical id" | sort -u | wc -l cat /proc/cpuinfo | grep "core id" | sort -u | wc -l cat /proc/cpuinfo | grep "siblings" | sort -u | awk '{print $NF}' cat /proc/cpuinfo | grep "cpu cores" | sort -u | awk '{print $NF}' Update new version (ch_cpuinfo ver 5.2) 2018.12.07 1. Use bash change to sh (for compatibility with DSM 5.x version) #!/bin/bash change to #!/bin/sh 2. Publish the source through github(https://github.com/FOXBI/ch_cpuinfo). For versions DSM 6.x and later, you can use the binary as before. If you use busybox in DSM 5.x, you can use it as a source file(ch_cpuinfo.sh). ============================================================================================ Reference images 1) First run 2) Redi 3) Restore 4) Mobile View Download files ch_cpuinfo ver 1.0 - delete -> ch_cpuinfo_en.tar -> ch_cpuinfo_ko.tar ch_cpuinfo ver 3.0 - delete -> ch_cpuinfo_en.tar -> ch_cpuinfo_ko.tar ch_cpuinfo ver 4.0 - delete -> ch_cpuinfo_en.tar -> ch_cpuinfo_ko.tar ch_cpuinfo ver 5.0 - delete -> ch_cpuinfo_en.tar -> ch_cpuinfo_ko.tar ch_cpuinfo ver 5.2 - update new version -> ch_cpuinfo_en.tar -> ch_cpuinfo_ko.tar
  6. 15 points
    Перед тем как что-то менять в своей работающей системе, настоятельно рекомендуется сделать резервные копии своих особо ценных данных, чтобы потом не жалеть об их безвозвратной потере. Все, что вы творите - это ваш страх и риск, никто не побуждает вас это делать. Самый простой и надежный способ безопасно попробовать - выключить хрень, отключить все диски и загрузочную флешку от действующей системы, взять чистый диск и другую флешку и попробовать установить новую версию загрузчика и системы, если прокатило, то делать уже на действующей системе. 1. Как установить (подготовительные работы описаны для компа с Windows): а) скачать образ загрузчика 1.04b (исходная тема тут), создать каталог в корне диска без символов на кириллице, например, c:/918/ и поместить туда образ загрузчика б) определить VID/PID флешки или картридера в который она вставлена (Панель управления - Диспетчер устройств - Контроллеры USB - Ваша флешка/ридер - Свойства - Сведения - ИД оборудования, нужно для того, чтобы система DSM опознала этот диск и не пыталась устанавливать себя на него, если неправильно определите и пропишите эти параметры, то система будет вылетать по ошибке 13 при установке в) скачать, установить и запустить программу OSFmount, смонтировать Partition 0 (15 Mb) из файла загрузчика, перед монтированием убрать галку Read-only drive г) скачать, установить и запустить программу Akelpad, открыть файл grub/grub.cfg на ранее смонтированном диске, правим, сохраняем: set vid=0xA234 #VID флешки/ридера set pid=0xB678 #PID флешки/ридера set sn=1780PDN123456 #sn set mac1=001132123456 #mac первой сетевой карты set mac1=001132123457 #mac второй сетевой карты, второй и последующий отличаются от первого на +1 в последнем разряде в шестнадцатеричной системе ... set netif_num=2 #количество сетевых карт ... set sata_args='SataPortMap=6' #контроллер sata, значения: 6 - 1 контроллер на 6 портов; 22 - 2 контроллера по 2 порта; 42 - 2 контроллера, первый на 4 порта, второй на 2 и т.п. Где брать sn и mac - ваша головная боль, гугл в помощь, система установится и будет работать с теми, которые изначально прописаны в загрузчике, но с ограничением функционирования некоторых сервисов и модулей, таких как: QC, пуш уведомления, активация кодеков для транскодинга, установка лицензий syno... Но для большинства и без них будет достаточно. На форуме писали, что прокатывало с sn и mac от других реальных моделей syno, но так не пробовал, поэтому утверждать не буду, кто хочет - дерзайте. д) размонтировать диск в OSFmount е) скачать, установить и запустить программу Rufus и записать ранее подготовленный образ на флешку з) вставить флешку в машину, на которой планируете запустить хрень, подключить диски, включить питание ж) отключить брандмауэр в антивирусе, в браузере набрать http://find.synology.com или установить Synology Assistant с сайта syno и найти вновь установленную хрень в вашей сети и) установить DSM установить хрень следуя инструкциям программы установки и приступить к настройке (как это делать здесь не описываю, ибо все ответы есть в базе знаний syno) Для ленивых есть утилита, где собраны основные проги для Windows x64 2. Если хрень не обнаружилась в сети, то скорее всего в загрузчике нет драйверов для ваших сетевых карт и/или для sata контроллеров. a) запустить программу OSFmount, смонтировать Partition 1 (30 Mb) из файла загрузчика, перед монтированием убрать галку Read-only drive б) скачать extra.lzma из этой темы и перезаписать в смонтированном диске в) размонтировать диск и перезаписать образ с добавленными драйверами на флешку г) попробовать запустить и найти хрень в сети, если не получилось, то увы и ах, либо просить, чтобы добавили дрова для ваших устройств в этой теме или самому их добавлять - теория тут 3. Транскодинг (нужны sn и mac от реальной железки) С наибольшей степени вероятности запустиnся на процессорах Intel начиная с 4го поколения (Haswell), но есть нюансы с моделями материнских плат и биосами. Проверяем следующим образом: hardware (hw) транскодинг - в корне системы должен быть каталог /dev/dri с тремя подкаталогами внутри, если его нет, но нет и hw транскодинга, чтобы проверить - ищем каталог в терминале/ssh командой cd /dev/dri. software (sw) транскодинг - должны подняться соответствующие кодеки, проверить можно командой в терминале/ssh cat /usr/syno/etc/codec/activation.conf Если результат такой, то он есть: {"success":true,"activated_codec":["hevc_dec","h264_dec","h264_enc","mpeg4part2_dec","ac3_dec","vc1_dec","vc1_enc","aac_dec","aac_enc","mpeg4part2_enc"],"token":"абракадабра"} Если ничего похожего нет, то нет и транскодинга. P.S. Просьба к админам прибить тему в шапке и дать мне доступ на редактирование первого поста этой темы, буду добавлять по мере поступления вопросов, ибо задолбали оленеводы, которые задают вопросы по установке, во всех подряд темах.
  7. 10 points
    This is a MAJOR update of DSM. DO NOT UPDATE TO DSM 6.2 with Jun's loader 1.02b or earlier. Your box will be bricked. Use loader 1.03b instead. You have been warned. https://www.synology.com/en-global/releaseNote/DS3615xs
  8. 8 points
    Compiled button.ko and evdev.ko with newest bromolow sources so itll work with dsm 6.2 (i guess it will only work for ds3615 and ds3617) HowTo: 1. download linux-VERSION_NUMBER.txz from newest branch https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/ according to your architecture https://github.com/SynoCommunity/spksrc/wiki/Architecture-per-Synology-model 2. extract archive and execute the following #if you have another architecture, change bromolow cp synoconfigs/bromolow .config make ARCH="x86_64" oldconfig make ARCH="x86_64" menuconfig # set as module: Device Drivers ---> Input device support --> Event interface make ARCH="x86_64" modules 3. search for button.ko and evdev.ko and put it into the package.tgz under modules/6.2/ in your powerbutton.spk and save. I attached a ready to go spk for bromolow (ds3615) but it works for ds3617 too POWERBUTTON_6.2-0001.SPK or https://www9.zippyshare.com/v/v32vxKUA/file.html
  9. 7 points
    Download: 1. synoboot vmdk https://mega.nz/#!fdBWBJYB!P3MbGY2v_X_udUhaSgVBQZ74KNRf7vtjMCO39u1I91Y 2. juns loader for DSM 6.2 https://mega.nz/#F!ZlkHQTTb!keje3RK017OjTp3vuWb-Cw 3. synology DSM.pat for synology 3615xs https://www.synology.com https://archive.synology.com/download/DSM/beta/6.2/23648/ 4. open vm tools spk http://spk.4sag.ru/?fulllist=true 5. XPEnology Tool for Windows x64 https://mega.nz/#!V480zKjC!ktZ2irGALS9EkX3XJHxkKIb2NedWMGIliTdcczSGt8A PREPARATIONS unzip synoboot.vmdk from DS3615xs 6.0.2 Jun's Mod V1.01 unzip synoboot.img from synoboot_3615 mount synoboot.img partition 0 with osf mount Make sure to uncheck Read-only drive Go to the mounted drive, Grub folder and edit grub.cfg with notepad++  set SN and mac1 fro example 0011322CA785 mark boot option lines you dont need in esxi #menuentry "DS3615xs 6.2 Baremetal $VERSION" --class os { # set img= # savedefault # loadlinux 3615 usb # loadinitrd # showtips #} # #menuentry "DS3615xs 6.2 Baremetal $VERSION Reinstall" --class os { # set img= # loadlinux 3615 usb mfg # loadinitrd # showtips #} # #menuentry "DS3615xs 6.2 Baremetal AMD $VERSION" --class os { # set img= # set zImage=bzImage # savedefault # loadlinux 3615 usb # loadinitrd # showtips #} menuentry "DS3615xs 6.2 VMWare/ESXI $VERSION" --class os { set img= savedefault loadlinux 3615 sata loadinitrd showtips } save file, dismount all and exit. ESXi part: Upload synoboot.vmdk and synoboot.img to esxi (in one folder) Create new VM name the xpenology vm as you want and select linux and for example ubuntu x64 select your storage (no pic needed) and you should see customize settings now remove default disk remove scsi controller remove cd/dvd drive now set cpu at 2 set memory 2GB set network adapter 1 mac addres you have in the grub.cfg for exapmple 00:11:32:2C:A7:85 now add existing hard disk and point to the vmdk uploaded before. Make sure its on SATA 0:0 now add another sata device and add vm disks to it (sata 1:0, 1:1 etc) and now, the vm is done and finish now start your VM and wait to see after few minutes open in new tab browser find.synology.com click connect and configure and manual install point to DSM 3615xs.pat file downloaded earlier after you confirm instalation you should see after 10 minutes reboot enter user password and name for dsm unmark autoupdate and SMART test skip configure quickconnect dont share location with synology (find.synology.com will not find virtual dsm) now DSM is redy
  10. 7 points
    версия: 3.1.16, linux, Release Notes: - Поддержка мультибитрейтных потоков при адаптивном вещании в HLS - Включена обработка запроса на пинкод/пароль от внешнего устройства при использование AirCast - Настройки приложения теперь можно менять с пульта - Расширен функционал "Engine API", для максимальной совместимости с приложениями, использующими устаревший API - Автоматическое восстановление соединения для AirPlay и Google Cast. - В пульте добавлена кнопка "Рестарт", для возможности повторного запуска контента с места остановки. - Оптимизация HLS - Устранение артефактов при трансляции по HTTP - Совместимость со сторонними приложениями, использующими устаревший API - Добавлены настройки транскодирования аудиодорожек при выдаче потока в HLS Hide Краткое описание: Ace Stream – это медиа-платформа с децентрализованной/распределенной системой поставки и хранения мультимедийных данных, предназначенная для создания интернет-сервисов с функциями AVoD (Аудио и Видео по Запросу) и Live Streaming («живого»/потокового вещания). Используя функции Ace Stream, вы сможете проигрывать в онлайне видео/аудио контент из P2P –сетей (по протоколу BitTorrent и/или AceStream), в любых удобных вам плеерах и на любых устройствах (SmartTV, ТВ-приставки, iPad, iPhone, и др.), поддерживающих соответствующие кодеки и стандартные форматы вещания (HTTP и/или HLS). Эта Тема переросла из этого топика по причине того что там было решение для просмотра в остовном live-tv b и с помощью ресурса ттв, здесь же пойдёт речь в остовном о самом движке Ace Stream, который претерпел с момента написания той статьи значительные изменения(см. Release Notes) Сама установка на убунту вкратце есть в вике разработчика здесь. Для пользователей xpenology у которых уже установлена как минимум DSM-5.2, а в идеале и настоятельно рекомендуется DSM-6.1, и у которых архитектура железа x64, я собрал уже готовое решение которое упаковано в контейнер докера и которое находится здесь. После запуска контейнера на вашем nas-server DSM, потребуется только один раз зайти в контейнер для правки ip вашей сети и записи в кроне для чистки кеша и регулярного обновления плейлистов, дополнительно но не обязательно, можно также занести данные учётки ттв в HTTPAceProxy для воможности просмотра архивов и использования функционала офф. виджета ттв(скрины в спойлере ниже). виджета ттв только андроид Hide
  11. 7 points
    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 !!! HP SmartArray Controller driver (hpsa.ko) is back in for testing (for now the one that comes with kernel 4.4.59), my P400 i had access to was to old for this driver so please try to test, newer controller even seem to have a IT mode so if present try it with this mode 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 (still online for testing against new 0.4) http://s000.tinyupload.com/?file_id=40794274174411841232 extra.lzma for DS918+ v0.3 http://s000.tinyupload.com/?file_id=09865768016965468337 extra.lzma for DS918+ v0.4 http://s000.tinyupload.com/?file_id=85078902011391385959 extra.lzma for DS918+ v0.5_test http://s000.tinyupload.com/?file_id=74512746059829955779 Note: the driver list below with related hardware is based on Trantor/Quicknick's older list for 5.2 and 6.0 so thanks goes to them and all others who helped to build the older list for 5.2 and 6.0. Caption (…) Not compiled for now, ask for it […] Either confirmed by users that it is not working OR not supported for DSM 6.2 (kernel 4.4.59) OR does not load at all. Driver was compiled/tested but removed - if someone finds a way to get it working in some way, tell us here and it will be added  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)
  12. 7 points
    List of mirror links to DSM 5.x and DSM 6.x boot loaders. Please drop a comment if you see a broken link or some erroneous information. All other posts will be deleted. Before downloading a loader I suggest you read this topic to know which loader to download. DSM 6.2(.1) - Read Jun's topic Jun's Loader v1.03b DS3615xs Synoboot_3615.zip | 17.3 MB | MD5 = e145097bbff03c767cc59b00e60c4ded Jun's Loader v1.03b DS3617xs Synoboot_3617.zip | 19.5 MB | MD5 = 94d18efbc349da2bd45d6e57adabc54f Jun's Loader v1.04b DS918+ synoboot-ds918.zip | 20.9 MB | MD5 = 5a5303a154d907b4adf99dfd201769e4 Jun's Loader v1.03a2 DS918+ Synoboot-ds918p.zip | 15.7 MB | MD5 = e941b495be057f0336e715f01346c841 DSM 6.1(.2/.3/.4/.5/.6/.7) - Read Jun's topic and Tutorial Jun's loader v1.02b DS3615xs DS3615xs 6.1 Jun's Mod V1.02b.img | 50.0 MB | MD5 = b4a2bc974070895407cd50990d96669a Jun's loader v1.02b DS3615xs with MBR partition (For older boards. Try if the above refuses to boot) - Rebuilt by @Genesys DS3615xs 6.1 Jun's Mod V1.02b (MBR_Genesys).img | 50.0 MB | MD5 = e30615bd02002479b58650c0862f25c4 Jun's loader v1.02b DS3617xs DS3617xs 6.1 Jun's Mod V1.02b.img | 50.0 MB | MD5 = e5d1608a9f43cf9a084277eb5640b439 Jun's loader v1.02b DS3617xs with MBR partition (For older boards. Try if the above refuses to boot) - Rebuilt by @Genesys DS3617xs 6.1 Jun's Mod V1.02b (MBR_Genesys).img | 50.0 MB | MD5 = 793c040f1093910e71236edc9a55de1f Jun's loader v1.02b DS916+ DS916p 6.1 Jun's Mod V1.02b.img | 50.0 MB | MD5 = 5ea01a50fd40426eb0e5344aa6d7bbff Jun's loader v1.02b DS916+ with MBR partition (For older boards. Try if the above refuses to boot) - Rebuilt by @Genesys DS916p 6.1 Jun's Mod V1.02b.img (MBR_Genesys).img | 50.0 MB | MD5 = 86bd66b2be35135cf13039ed783eb4c0 DSM 6.0.2 - Read Jun's topic and Tutorial Jun's loader v1.01 DS3615xs DS3615xs 6.0.2 Jun's Mod V1.01.zip | 24.0 MB | MD5 = cf9d920edef96d58ae709674dc71511b Jun's loader v1.01 DS3615xs with MBR partition (For older boards. Try if the above refuses to boot) - Rebuilt by @Genesys DS3615xs 6.0.2 Jun's Mod V1.01 (MBR_Genesys).img | 50.0 MB | MD5 = 25813aa17ee5b17db1b41d54bc6b4b74 DSM 5.2 XPEnoboot 5.2-5967.1 DS3615xs XPEnoboot_DS3615xs_5.2-5967.1.img | 24.0 MB | MD5 = 4b204b8200ea5d12dea8b578ad95f7ef XPEnoboot_DS3615xs_5.2-5967.1.iso | 19 MB | MD5 = c1ee885e6b74978512f2adb6fa6fc7ff XPEnoboot_DS3615xs_5.2-5967.1.vmdk | 19 MB | MD5 = 3fe4f459432f883fd2be8b7618a25159 XPEnoboot 5.2-5644.5 DS3615xs XPEnoboot_DS3615xs_5.2-5644.5.img | 24.0 MB | MD5 = a329929e5a91095e9258036485e01c9c XPEnoboot_DS3615xs_5.2-5644.5.iso | 17.4 MB | MD5 = a92ea8c869c48fc340a91e41a01d4cfd XPEnoboot_DS3615xs_5.2-5644.5.vmdk | 17.3 MB | MD5 = 9d5cfdc69e0e19ef207de9aaba76acf3 XPEnoboot 5.2-5644.4 DS3615xs XPEnoboot_DS3615xs_5.2-5644.4.img | 24.0 MB | MD5 = 59e96a63333b5c6d8911f902a23ca99f XPEnoboot_DS3615xs_5.2-5644.4.iso | 17.1 M | MD5 = bfa92964103438abd0f93c4ef58d0e38 XPEnoboot_DS3615xs_5.2-5644.4.vmdk | 17.1 MB | MD5 = 860259eaa222186860bc52bd6dff4919 XPEnoboot 5.2-5644.1 DS3615xs XPEnoboot_DS3615xs_5.2-5644.1.img | 24.0 MB | MD5 = d16c8877744a2d26bf44fc1b49a36484 XPEnoboot_DS3615xs_5.2-5644.1.iso | 22.2 M | MD5 = bdcb7a1a7586e208878807f2504cf2d5 XPEnoboot_DS3615xs_5.2-5644.1.vmdk | 22.1 MB | MD5 = 2d947faf0419668c1278fbee4281acb5 XPEnoboot 5.2-5592.2 DS3615xs XPEnoboot_DS3615xs_5.2-5592.2.img | 24.0 MB | MD5 = fbeba655ca0a77b56b025192b08eb55d XPEnoboot_DS3615xs_5.2-5592.2.iso | 21.1 MB | MD5 = c508e80e8a795514497244f798c663e2 XPEnoboot_DS3615xs_5.2-5592.2.vmdk | 21.1 MB | MD5 = ddeef445edeaba3684fcbb50c50adbe0 XPEnoboot 5.2-5592.1 DS3615xs XPEnoboot_DS3615xs_5.2-5592.1.img | 16.0 MB | MD5 = ebda68e9a7589ed1d145399f975d1232 XPEnoboot_DS3615xs_5.2-5592.1.iso | 16.1 MB | MD5 = 65c6b150ea6d26c70cc0d96d010ce5a6 XPEnoboot_DS3615xs_5.2-5592.1.vmdk | 16.0 MB | MD5 = 78cb2ff5bfcd14c1edb3dea93084443f XPEnoboot 5.2-5565.2 DS3615xs XPEnoboot_DS3615xs_5.2-5565.2.img | 16.0 MB | MD5 = 3016d6ffb5ea794033567ab7eb816184 XPEnoboot_DS3615xs_5.2-5565.2.iso | 15.6 MB | MD5 = a3ade9b08d24be96e2da775e4e06f13d XPEnoboot_DS3615xs_5.2-5565.2_vmdk.zip | 15.2 MB | MD5 = 4c314bbd4116427c5c85ceb08da7479c XPEnoboot 5.2-5565.1 DS3615xs XPEnoboot_DS3615xs_5.2-5565.1.img | 16.0 MB | MD5 = 1806870fe0a7b83ff65b25a9af9dc487 XPEnoboot_DS3615xs_5.2-5565.1.iso | 15.6 MB | MD5 = cfe9937aa76458c9e99efea5d3fee2db XPEnoboot_DS3615xs_5.2-5565.1_vmdk.zip | 15.3 MB | MD5 = 8c317e99b3db3869a480a6debf24b7b4 DSM 5.1 XPEnoboot 5.1-5055.1 DS3615xs XPEnoboot_DS3615xs_5.1-5055.1.img | 15.8 MB | MD5 = b069342f3bc6a10d1e0111e7c5341df7 XPEnoboot_DS3615xs_5.1-5055.1.iso | 14.1 MB | MD5 = c5c049a3e1e06aa6f498fb70c15dc133 XPEnoboot_DS3615xs_5.1-5055.1_vmdk.zip | 13.7 MB | MD5 = a654f3bb05033da98b32e55724f0b1ce XPEnoboot 5.1-5022.3 DS3615xs XPEnoboot_DS3615xs_5.1-5022.3.img | 15.8 MB | MD5 = 72175a41e5855b57b4c8ffc3d92f4b06 XPEnoboot_DS3615xs_5.1-5022.3.iso | 14.8 MB | MD5 = 46854ce39415d736fa5abd446ffa4352 XPEnoboot_DS3615xs_5.1-5022.3.vmdk | 14.8 MB | MD5 = a7343f03fe63a5aa7ad0fe01f41a4b76 XPEnoboot 5.1-5022.2 DS3615xs XPEnoboot_DS3615xs_5.1-5022.2.img | 15.8 MB | MD5 = 06b8435e1322c7a5ee5725ff80ea2a77 XPEnoboot_DS3615xs_5.1-5022.2.iso | 14.0 MB | MD5 = 0e211d3d19b7b461ae5df3aa91e18630 XPEnoboot_DS3615xs_5.1-5022.2.vmdk | 13.9 MB | MD5 = 929730848a31fc19bddd457998477a5f XPEnoboot 5.1-5022.1 DS3615xs XPEnoboot_DS3615xs_5.1-5022.1.img | 15.8 MB | MD5 = 6f7cb585519c5cb3acfb026d34585dbd XPEnoboot_DS3615xs_5.1-5022.1.iso | 13.4 MB | MD5 = 88bd5177fa7a4f54b7fcd5e4001bae5b XPEnoboot_DS3615xs_5.1-5022.1.vmdk | 13.3 MB | MD5 = f03125c86b2da60b5d38db1c6c62bcba DSM 5.0 NanoBoot 5.0.x DS3612xs NanoBoot- | 15.6 MB | MD5 = 2f201876ef576f4ef78a3c3bbbcee529 NanoBoot- | 15.6 MB | MD5 = 89ce54b38e83c7b94c422f6c9a0dbedb NanoBoot- | 15.6 MB | MD5 = 07bd106a7f6204962c801ecf851f1dc9 NanoBoot- | 32.0 MB | MD5 = e1353d7143cbf8cc31ed320f82cf65d6 NanoBoot- | 15.6 MB | MD5 = 32e1f823219ec7963162e4e394687112 NanoBoot- | 15.6 MB | MD5 = 6fc6be138eb070938a9f14ff64fa4239 NanoBoot- | 15.6 MB | MD5 = 6bbf71f64909cda57c3a63e523d13ed8 NanoBoot- | 31.3 MB | MD5 = 60233f771b934b5237e2037be0e64b95 NanoBoot- | 15.6 MB | MD5 = 039abc91883e09fd2f443ee10ba5690e NanoBoot x86 5.0.x DS214Play NanoBoot-x86- | 15.6 MB | MD5 = 3c6776570962926497088e6b3889205c NanoBoot-x86- | 15.6 MB | MD5 = b76c423d39129b19b2e0a62f741aaa8c NanoBoot-x86- | 32.0 MB | MD5 = 8bc6d3b5aed1f41fa0ce4d93b17f9bf1 NanoBoot-x86- | 15.6 MB | MD5 = 90948500efde437ae56dfd51f31f55f8 NanoBoot-x86- | 15.6 MB | MD5 = 7acb8faf796a0e5d5a54a9734ecec728 NanoBoot-x86- | 15.6 MB | MD5 = f333038c8bcf1e530ddeb55075b9827c NanoBoot-x86- |15.6 MB | MD5 = 5bf7241df633ff48ce6a571aa27df88c
  13. 7 points
    Updated powerbutton package to work with dsm 6.2 for ds3615, ds3617 and ds918+ POWERBUTTON_6.2-0002.SPK or https://www39.zippyshare.com/v/R3ftOA3X/file.html
  14. 6 points
    This is an updated tutorial version from the one I made last year. It will enable you to migrate from DSM 5.2 to DSM 6.1.7 directly without the need to upgrade to DSM 6.0.2 first. If for some reason you want to upgrade to DSM 6.0.2 first or simply you do not want to upgrade to DSM 6.1.7 but only to DSM 6.0.2 then use the link above. To upgrade from DSM 6.0.2 to DSM 6.1.7 read here. As most of you know by now Jun was able to find a way to install DSM 6 on non Synology boxes. Here is the thread that I recommend reading. At least make an effort and read the OP: https://xpenology.com/forum/topic/6253-dsm-6xx-loader/ Below is what you need for the operation. I will assume you are doing all this under Windows 10, 8, 7 or XP. If you are on a MAC computer have a look at this post I made on how to burn the image to a USB drive and then mounting the USB drive for editing the content. The rest of the tutorial still applies. If you are currently using DSM 5.1 or below first update to DSM 5.2. If you are doing a fresh install of DSM 6.1 then carry on with the tutorial and omit references to DSM 5.2. - Win32 Disk Imager to make a bootable USB drive; - A 4GB (or any size really) USB drive (flash drive) to install the loader. Not that this is necessary but use preferably a brand name (Kingston, SanDisk...); - A way to read your USB drive VID/PID. Here is a how-to >>> VID and PID; - A good text editor: Notepad++ I really don't recommend using Windows's Notepad; - DSM 6.1.4 PAT file. Chose the one you need: DS3615sx or DS3617sx or DS916+. Download the ".pat" file not the ".pat.md5" - Jun's official v1.02b loader (mirror). This is a hybrid UEFI/BIOS loader so it should work in most machines which are capable or reading GUID partition table (GPT). For older machines that can only read MBR the above loader will simply not boot. If that is your case then use @Genesys's v1.02b loader rebuilt image which is MBR based. Note: Jun's loader supports Intel CPUs. For AMD CPUs Jun has stated that the loader needs some work but it has been reported by many users using HP machines that it actually works. The C1E function in the bios (in some HP machines) needs to be deactivated. I am unsure for other motherboards brands therefore if you have an AMD machine that is not an HP you might be out of luck. Try looking in the bios configuration and play around. - Custom extra.lzma ramdisk. This ramdisk is optional and should only be used if the default ramdisk included in the loader is not detecting your hardware. I am just providing it for those who are having issues with network detection or unrecognised HDD controllers. This custom ramdisk contains additional and updated modules & firmwares. Credits go to @IG-88 for compiling the modules against the latest DSM 6.1.3 source code. I do not warranty they all work but I think most do. If you chose to use this ramdisk, you will need to replace (or rename, so you can revert) the default extra.lzma ramdisk from Jun's loader with this one. If you a have question specific to the custom ramdisk please post it in the topic of IG-88, not here. - If you are doing a fresh install make sure your drives are plugged in direct succession starting from the 1st SATA port. Usually the first port is described as SATA0 on motherboards. Check with your MoBo manufacturer for exact nomenclature. - OSFMount to modify the grub.cfg file within the loader's image and if necessary to replace the extra.lzma ramdisk with the custom one. This is not strictly necessary as Jun has made it possible to configure what needs to be modified via the Grub Boot Menu. If you prefer using Jun's Grub Boot Menu configuration technic, simply skip Point 4, read Note 4 instead and pick up at Point 5. PLEASE READ EVERYTHING PRIOR ATTEMPTING ANYTHING Use this loader at your own risk. I wont be held responsible for any loss of data or black smokes that may result in the use of this loader. Please note that this loader has a limited amount of modules (drivers) included. If it is fundamental for you to have a NAS operating as quick as possible I recommend you look at the included drivers very carefully at the bottom of this tutorial before attempting an upgrade. If they are not there you will have to compile your own modules/firmwares or use the custom ramdisk provided above. Don't ask me to compile modules for you. I wont do it. One last thing: DO NOT UPDATE DSM BEYOND VERSION 6.1.7 with loader v1.02b. IN OTHER WORDS DO NOT UPDATE TO DSM 6.2 You have been warned. Here we go: 1 - BACKUP your data and save your configuration prior any attempts to migrate from DMS 5.2 to DSM 6.1. I can't stress this enough. JUST DO IT, as Nike likes to say. Also, print this tutorial if you can. It will make your life easier. 2 - Turn off your NAS and unplug the USB drive you are currently using with DSM 5.2. I recommend you put this USB drive aside in case migration to DSM 6.1 doesn’t go as expected and you need to revert to DSM 5.2. It will just make your life easier. 3 - Now go to your workstation/PC, plug a new USB drive (or the old one if you really don’t have any spare USB drives). Use the link I provided earlier to check your USB drive VID/PID. Write down the info somewhere as we will need it later. 4 - Now launch OSFMount. Select Mount New, then select the image file you downloaded earlier (i.e. .img extension file) to open. Now select partition 0 (the one that is 15 MB). Click Ok. Then at the bottom of the window make sure to un-tick the "Read only drive". Click Ok. The partition should now be mounted in file explorer. At this point you can navigate to the /grub directory and edit the grub.cfg file. If you need to replace the extra.lzma ramdisk with the custom ramdisk provided above then you will also need to mount partition 1 (the one that is 30 MB). Below is what you will see in the grub.cfg file. I am only showing below the portion of the code that is relevant for the purpose of this tutorial [...] set extra_initrd="extra.lzma" set info="info.txt" set vid=0x058f set pid=0x6387 set sn=C7LWN09761 set mac1=0011322CA785 set rootdev=/dev/md0 set netif_num=1 set extra_args_3615='' set common_args_3615='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet' set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0' set default='0' set timeout='1' set fallback='1' [...] You want to modify the following: Change vid=0x090C to vid=0x[your usb drive vid] Change pid=0x1000 to pid=0x[your usb drive pid] Change sn=C7LWN09761 to sn=generate your sn here with DS3615xs or DS 3617xs or DS916+ model (this will depend on which loader you chose) Change mac1=0011322CA785 to mac1=[your NIC MAC address #1]. You can also add set mac2=[your NIC MAC address #2] and so on until mac4 if you have multiple NICs. However, this is not necessary. Recommended: Change set timeout='1' to set timeout='4' - This will allow you more time to make a selection in the Grub Boot Menu when it appears on screen. Once you are done editing the grub.cfg file, save it and close your text editor. Now in OSFMount click on Dismount all & Exit. You are now ready to burn the image to your USB drive. 5 - Now use Win32 Disk Imager to burn the image file onto the USB drive. This will also make the USB drive bootable. 6 - Eject and unplug the USB drive from your workstation. Plug it in your NAS (avoid USB 3.0 ports. Use USB 2.0 port if available). Boot your NAS and before doing anything fancy, access your BIOS so to make your USB drive the 1st boot drive if it's not the case. The Jun official loader can boot in UEFI or in legacy BIOS, so you chose what suits you best. Also, make sure your HDDs are booting in AHCI mode and not in IDE. Finally, if disabled, also enable the serial port in BIOS. Some BIOS don't have this option so don't get too cranky on this if you can't find it. Save changes to the BIOS and REBOOT the NAS. 7 - Once rebooted, if you have a monitor connected to your NAS you will see the following Grub Boot Menu: ADVICE: even before you see the Grub Boot Menu press the up/down key. This will stop the countdown so you will be able to select the desired line. You won’t see much other than the following after you press enter: If you booted the USB drive in EFI mode then you will see the same text without the last 3 lines but that's ok. 8 - Now go back to your workstation, and launch Synology Assitant or go to http://find.synology.com. Within one minute or so you should normally be able to see your NAS on your local network (it took ~55 seconds on a test I did on a VM). Just follow the instructions and either chose "Install" if you wish to have a clean install or chose “Migration” if you are coming from DMS 5.2 and wish to update while retaining your data. You will be asked to provide the .PAT file you downloaded earlier (DSM_DS3615xs_15217.pat or DSM_DS3617xs_15217.pat or DSM_DS916+_15217.pat). 9 - When the migration is finished you will most probably have to update some of your packages. You can then proceed and update DSM 6.1 up to DSM DSM 6.1.7-15284. It is possible you might either need to hard reboot or re-image your usb drive. Make sure to deactivate auto-updates within DSM. Link to individual files (DSM and critical updates) can be found here: https://xpenology.com/forum/topic/7294-links-to-dsm-and-critical-updates/. DO NOT UPDATE TO DSM 6.2. The loader is not compatible. 10 - You are done. If you have questions, first search the forum and/or Google then leave a comment if nothing helps. Please provide your hardware specifications (motherboard model, LAN controller, driver controller etc). Failure to prove such information will lead to the post being deleted or not answered. -------------- Note 1: If after following the tutorial you can’t find your NAS through http://find.synology.com ou Synology Assistant it is highly possible that the drivers of your NIC are not included in the ramdisk of the loader. Make an effort and use Google to know what modules your NIC and HDD controller are using, then check if those modules are included in the custom extra.lzma ramdisk. If yes then use the custom ramdisk. Don't ask me to look for you. If nothing works then ask your question. Note 2: Synology increased security since the introduction of DSM 6. Root access through SSH is no longer possible out of the box. You can however use your admin account and elevate permissions with the following command if you need root permissions: sudo -i Note 3: Please check you have the right VID/PID prior proceeding. If you get the following error ”Failed to install the file. The file is probably corrupted. (13)" it most certainly means your VID and/or PID is/are wrong. If you still have the same error message after verifying the VID/PID then try another USB drive. Note 4: Configuration added to the grub.cfg file can also be done directly during the Grub Boot Menu, so technically you can skip Point 4 and burn the image on the USB drive without editing anything (read Point 5 onward first). If you wish to do the changes from the Grub Boot Menu directly you need to press the letter 'C' when you see the Boot Menu. You will literally only have one second, so be fast. Once you press 'C' you will be in a Grub command line environment. To change your VID enter the following: vid 0xYOUR 4 DIGITS USB DRIVE VID Do the same for pid, sn and mac1. Press enter at each command. The commands are: pid 0xYOUR 4 DIGITS USB DRIVE PID sn YOUR NAS SERIAL NUMBER mac1 YOUR NAS MAC1 ADDRESS If you have multiple NICs you can also issue mac2, mac3 and mac4 as commands. Maximum is mac4. See below: mac2 YOUR NAS MAC2 ADDRESS mac3 YOUR NAS MAC3 ADDRESS mac4 YOUR NAS MAC4 ADDRESS If you think you made a mistake in the numbers simply re-issue the command. When you are done press esc and select the appropriate menu entry. Below is an example (fake numbers) of how it looks under the Grub command line environment : Note 5: If you encounter the error "We've detected errors on your hard drives [drive number] and the SATA ports have also been disabled" during installation, then you have to fallback to adding SataPortMap to the grub environment. Press the letter 'C' at the Grub Boot Menu and then add the following: append SataPortMap=XX where XX is the number of drives. Don’t forget to update this parameter if you add additional drives to your machine. If you use Reinstall, don't forget to re-select the first line of the Boot Menu once the NAS has rebooted after the installation else the Loader will re-select Reinstall and you will be faced with some issues so please beware of this. @@@@@@@@ What does SataPortMap mean? @@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ ############## Know issues ##################### - When running on a slow single core machine, there is a race condition that causes the patcher to load too late. The most obvious sign is that console is not working properly. - Some ethernet drivers crash when set MTU above about 4096 (Jumbo frame). ############# Included default modules & firmwares in Jun's Loader ############# ############## Tutorial UPDATES ##################
  15. 5 points
    Video tutorial on how to get XPEnology to run on an HP Microserver Gen8 via ESXi 6.7, and install DSM 6.2 on SSD drive on ODD port, and pass drivebays to VM with RDM (Raw Data Mapping) MANY Thanx go to the great tutorial already posted here by @luchuma [ Tutorial: Install/DSM 6.2 on ESXi 6.7 ] I just always prefer to watch a video
  16. 5 points
    Господа модераторы! Какого ХРЕНа вы опять забанили нашего комрада 39911-архип, ранее он был известен как 5213-bob-the-builder, забаньте для кучи и меня, мы тогда с ранее упомянутым комрадом подумаем как увести русскою ветку и не только на другой форум. Или вам покоя не дает, то что кто-то набрал баллов лайков больше вас?! Детский сад Ё-моё. По-этому: 1. Прошу восстановить 39911-архип в правах и приплюсовать, то что было у 5213-bob-the-builder 2. Не трогать этот пост, пусть собирает лайки, они мне не нужны, это для Архипа/Boba.
  17. 5 points
    I have some findings after doing a little research and adjusting settings, it looks like I found the sweet spot for power draw and performance, as well as having functioning WOL, lower fan speed, and as an added bonus HDD's going to sleep! I am using the very latest Latest Service Pack 2018.09.0 (P03093_001_spp-Gen8.1-SPPGen81.4.iso) with all firmware updates and current iLO. HPE decided you needed a warranty to get the download, let's not muck about with that: Download here I set the iLO time manually to a time server under Network>iLO Dedicated Network Port>SNTP Propagate NTP time to host. Unchecked use DHCPv4 and DHCPv6. I don't use IPv6 so I have that disabled, and under IPv4 I have ping gateway on startup unchecked. My WINS server is my router, if this is pointing to your XPEnology then there might be a sleep wake problem for hibernation of disks (more on that later.) I also don't have a shared network port enabled under iLO. The iLO network tweaks are probably not required but it improved my configuration. Third thing you may want to double check after firmware is that your BIOS settings are set correctly including the correct time: System Options> Embedded NICs: Network boot disabled for both (unless you PXE boot from the Network) USB Options>Removable Flash Media Boot Sequence: Internal DriveKeys First (that is where XPEnology lives) SATA Controller Options>Embedded SATA Configuration: Enable SATA AHCI Support SATA Controller Options>Drive Write Cache: Disabled Power Management Options> HP Power Profile: Set to Custom HP Power Regulator: OS Control Mode Power Management Options>Advanced Power Management Options: Intel QPI Link Power Management: Enabled Minimum Processor Idle Power Core State: C1E State Minimum Processor Idle Power Package State: Package C6 (retention) State Maximum Memory Bus Frequency: I set mine to 1333MHz (This depends on your RAM) Memory Interleaving: Full Interleaving PCI-E Gen 3 Control: I disabled mine because I have no use for it, helps with power draw. If you have something plugged in don't disable. Dynamic Power Savings Mode Response: Fast Collaborative Power Control: Enabled DIMM Voltage Preference: Optimized for Power, again this depends on your RAM Server Availability> Wake-On LAN: Enabled Thermal Shutdown: Enabled Power Button: Enabled Automatic Power-On: Restore Last Power State Advanced Options>Advanced System ROM Options> MPS Table Mode: Full Table APIC Power-On Logo: Disabled, it speeds up the bootup time and still has a prompt for F9 to get into BIOS. Leave everything else alone or set to your specific preferences if you know what you are doing, double check the BIOS date and time and then save your settings to get back into DSM. DSM settings: There are a lot of things that can affect your overall power draw and performance to keep your drives from properly going to sleep, read this page to understand the implications of certain packages. Control Panel> Regional Options>Time: Set the correct time zone, and click update now. Don't worry about NTP Service unless you use Surveillance Station. Performance: Uncheck Memory Compression. Will trigger a reboot. Hardware & Power> General: Everything is ticked, except the Fan Speed Mode. Power Schedule: Leave this alone for now. HDD Hibernation: I do 10 Minutes on both and enable Hibernation logs. Not checking Enable auto poweroff for now. Info Center> Service: Double check you don't have anything running that could affect sleep and wake, for example SMB is the only service running but it could act as a Master Browser which would affect the hibernation so I have it disabled. Another thing I prefer to do on my box is completely remove Universal Search: SSH into the NAS and run these commands: sudo -s synopkg uninstall SynoFinder I don't have any media indexing going on but that may be a factor as well. Other thoughts: Splitting up your hard drive disk groups could have an effect on what your hibernation looks like, check the logs, about half your drives may hibernate while others won't, it depends on the services running and many other factors that are far too much to name here. If you want the unit to go into a complete power off/on state try a package called Advanced Power Manager. I swear by this package and confirmed that it works on both my DS216+II, and XPEnology bare metal Gen8. There are many advanced functions that you can tweak that affect how your NAS "Sleeps" so explore it. Wake-on-LAN works if I have the unit go into an auto-poweroff state, but I use my Router to send a wake request to get it back up to where it was. I am using BTRFS but have not noticed any overworked HDD's crunching data into the night, everything remains stable and quiet and my fan speeds have gone down to 19% and idle is sitting well below 39w. Did I mention time is a factor to your hibernation? Make sure that your BIOS time and Synology DSM times are in sync, otherwise your 10 minute hibernation will never happen. I hope I helped somebody in these forums, and answered my own question at the same time.
  18. 5 points
    Hi, I created spk packages for virtualbox 5.2 on DSM 6.2 (currently for bromolow), more info here, since I've split phpvirtualbox and virtualbox you will need also this. Give it a spin if you are brave enough. Standard disclaimer apples.
  19. 5 points
    Цель: организовать интернет здорового человека на конечных устройствах (нас, пк, ноуты, телефоны) оптимальным вариантом по простоте и скорости настройки. Краткий roadmap документа: 1. Выбор и покупка VPS 2. Установка OpenVPN на VPS 3. Подключение клиентов 4. Tips & Triks 5. Ссылки "И сказал он: Поехали! " 1. Выбор и покупка VPS На самом деле вариантом VPS с Linux на борту масса, другое дело что их придется поискать. Из зарубежных можно рекомендовать https://www.digitalocean.com/, https://www.vultr.com/, https://www.ovh.com/, https://www.arubacloud.com, ну или поискать на https://lowendbox.com. Не реклама, не претендую на истину в последней инстанции, вполне возможны варианты лучше приведенных. Я воспользовался VPS от arubacloud.com за 1 € (1 vcore, 20 ssd, 1 gb ram, 2 tb inet) расположенной в Италии. После оплаты и проверки платежа, VPS будет доступна через некоторое время. Из предлагаемых ОС я выбрал Ubuntu, манов на русском/английском как настроить OpenVPN на эту систему достаточно. 2. Установка OpenVPN на VPS Подготовка Первым делом сменим пароль суперпользователя root ( и запомним его :)): passwd root Обновим источники приложений и операционную систему до актуального состояния apt-get update apt-get upgrade Установим консольную утилиту Easy-RSA для генерации сертификата сервера и сертификатов для каждого из клиентов, которые будут использоваться для подключения: apt-get install easy-rsa cd /usr/share/easy-rsa nano ./vars Задаем переменную длины ключа: export KEY_SIZE= 1024 Это стандартное значение. Если требуется повышенная безопасность, то можно установить значение 2048. Однако следует помнить, что нагрузка на сервер будет изменяться пропорционально этому значению.Остальные параметры заполняются в соответствие с вашими пожеланиями, например export KEY_COUNTRY="RU" export KEY_PROVINCE="RU" export KEY_CITY="Moscow" export KEY_ORG="MyCompany LTD." export KEY_EMAIL="your_email_address" Включаем использование наших переменных source ./vars Очищаем папку с ключами ./clean-all Генерируем корневой сертификат. В процессе генерации утилита будет использовать уже указанные нами данные в переменных, поэтому нажимаем Enter на все вопросы. ./build-ca Генерируем таким же образом сертификат сервера. Отвечаем Y на запрос о подписывании сертификата. ./build-key-server server Теперь генерируем сертификаты для каждого устройства, которое планируется подключать к серверу. Повторяем команду нужное количество раз, изменяя имя сертификата (в примере сертификат называется macbook) ./build-key macbook Генерируем ключ Диффи-Хеллмана: ./build-dh В результате в папке /usr/share/easy-rsa/keys у нас теперь лежат наши сертификаты и ключи. Установка OpenVPN Ставим vpn: apt-get install openvpn Для версии 2.4-2.5 Если нужна поддержки новых опций таких как tls-crypt, lz4-v2 и прочего, нужно ставить версию 2.4. В репо Ubuntu по умолчанию только 2.3. Правда, к сожалению, эти опции не поддерживаются клиентом Syno, или я просто не смог до конца разобраться как их запустить. Hide Копируем все наши сгенерированные сертификаты и ключи: mkdir /etc/openvpn/keys cp -R /usr/share/easy-rsa/keys/ /etc/openvpn/keys Мы сконфигурируем сервер таким образом, чтобы при подключении к нему с любого устройства весь интернет-трафик заворачивался в туннель и таким образом сменим собственный IP-адрес на IP-адрес нашего VPS. Повышенная секурность Для большей секурности предлагаю создать отдельного, не привилегированного пользователя для запуска службы: adduser --system --shell /usr/sbin/nologin --no-create-home ovpn ( по выбору ) groupadd ovpn ( по выбору ) usermod -g ovpn ovpn Hide Сгенерировать и дать правильные права на чтение ключу ta.key Положить его в папку /etc/openvpn/keys cd /etc/openvpn/keys openvpn --genkey --secret ta.key chmod 544 ta.key Вносим в файл конфигурации сервера openvpn следующие строки: nano /etc/openvpn/server.conf Конфиг сервера # #General # port 1194 #порт OpenVPN сервера proto tcp #протокол на котором он работает, есть вариант с udp dev tun #тип тунеля, бывает еще и tap user ovpn #наш пользователь созданный выше group ovpn #группа нашего пользователя persist-key persist-tun status /var/log/openvpn-status.log #логи log /var/log/openvpn.log #логи verb 3 #уровень детализации логов # #Encryption # auth SHA256 #Тут и ниже параметры шифрования и алгоритмы которые используются tls-server tls-auth /etc/openvpn/keys/ta.key 0 key-direction 0 cipher AES-256-CBC ca /etc/openvpn/keys/ca.crt #Пути до ранее сгенерированных ключей и сертификатов cert /etc/openvpn/keys/vanish.crt key /etc/openvpn/keys/vanish.key dh /etc/openvpn/keys/dh1024.pem mssfix 0 #удаление отпечатков браузера comp-lzo adaptive # #Network # server #подсеть из которой будут выдаваться ip клиентам ifconfig-pool-persist ipp.txt #когда клиент подключается, здесь появится запись, так же можно прописать конкретный ip push "redirect-gateway def1" #для пропуска трафика через шлюз push "dhcp-option DNS" #наши новые DNS сервера push "dhcp-option DNS" keepalive 10 120 Hide Теперь необходимо настроить наш VPS в режим работы маршрутизатора, включаем форвардинг: nano /etc/sysctl.conf убрать комментарий (#) на строке: net.ipv4.ip_forward = 1 Включаем трансляцию адресов чтобы клиенты изнутри могли ходить в интернет через наш VPS: iptables -t nat -A POSTROUTING -s -o eth0 -j MASQUERADE Чуть позже нужно добавить правило для нормально работы сервисов syno: iptables -A PREROUTING -d ___ip адрес vps____/32 -p tcp -m multiport --dports 80,443,5000,5001(список всех необходимых портов через запятую) -j DNAT --to-destination ___ip_syno_из подсети___ Для того чтобы тунель не определяли по обратному пингу я еще блокирую icmp: Iptables -A INPUT -p icmp -m icmp –icmp-type 8 -j REJECT --reject-with icmp-port-unreachable Если куплено доменное имя, то у хостера нужно подправить записи A на ip нашего VPS Это базовый минимум из того что нужно для повседневной работы. Творчество приветствуется. Посмотреть что наворотили можно так: Iptables –vnl Iptables –t nat –vnL Чтобы созданное нами правило пропуска трафика не удалилось после перезагрузки сервера установим пакет iptables-persistent: apt-get install iptables-persistent dpkg-reconfigure iptables-persistent При установке на вопрос о сохранении текущих правил IPv4 отвечаем утвердительно. Стартуем сервер: systemctl start openvpn systemctl status openvpn Вывод нормальной работы Просмотр логов Если интересно смотреть что происходит при старте, можно в отдельном терминале запустить tail –f /var/log/openvpn.log до запуска systemctl start openvpn Hide 3. Настройка клиентов Приступаем к настройке со стороны клиента. Вне зависимости от используемой операционной системы нам всего лишь требуется несколько файлов: корневой сертификат сервера (ca.crt), персональный сертификат клиента и соответствующий ему ключ (macbook.crt и macbook.key), ключ шифрования сессии (ta.key), а также конфигурационный файл для клиента. Первые три файла у нас уже есть на сервере в папке /etc/openvpn/keys - их можно легко скачать с сервера с помощью SFTP или WinSCP. А вот конфигурационный файл нам нужно создать вручную. Создаем на компьютере-клиенте отдельную папку и помещаем туда сертификаты. Затем создаем конфиг для клиента с любым именем и расширением ovpn: Конфиг файл клиента .ovpn сlient dev tun proto tcp remote __ip vps___ 1194 auth SHA256 cipher AES-256-CBC resolv-retry infinite nobind persist-key persist-tun comp-lzo verb 3 mssfix 0 tls-client tls-auth ta.key 1 remote-cert-tls server key-direction 1 ns-cert-type server Hide Сохраняем файл и устанавливаем клиентское приложение. Вариантов множество - для Windows и Linux лучше использовать официальное приложение, которое можно скачать по ссылке https://openvpn.net/index.php/open-source/downloads.html. После установки клиента для Windows достаточно лишь скопировать конфигурационный файл и сертификаты в папку C:\Program Files\OpenVPN\config и запустить подключение. На Android есть два нормальных клиента – OpenVPN Connect (простой интерфейс, быстрая настройка) и OpenVPN для Android – тут выбор тюнинга побогаче. Работают оба стабильно, если сеть меняется с WiFi на сотовую – переключаются корректно. Операция установки аналогична на windows, скормить ovpn, скормить сетрификаты/ключи. А теперь самая мякотка – подключить это все в synology. Xpenology. На готове должны быть ключи, сертификаты, работающий сервер с настройками приведенными выше и доступ по ssh к xpenology. Панель управления – Сеть – Сетевой интерфейс – Создать профиль VPN. К сожалению web-интерфейс рассчитан только на создание подключения с парольной аутентификацией ( и такие сертификаты можно сделать, разница от наших – вводить каждый раз пароль при подключении, что утомительно, но секурнее) Нас же интересует аутентификация по сертификату. Поэтому заполняем предложенные поля любыми данными: *протокол - TCP Щелкаем далее, и устанавливаем следующие настройки: Подключаемся к xpenology по SSh. Затем нам будет необходимо поправить созданный автоматически файл /usr/syno/etc/synovpnclient/openvpn/client_oXXXXXXXXXX. У меня установлен mc, а гуру vi могут это сделать прямо в консоли, остальным может быть удобно скопировать файл к себе в папку общего доступа и отредактировать файл там с использованием более привычных инструментов. При редактировании файла обратите внимание что у Linux и windows разные подходы к обозначению конца строки, поэтому используйте текстовый редактор который сможет сохранить файл в привычном xpenology формате. Конфиг клиента Xpenology В моем случае файл конфигурации выглядит следующим образом: dev tun^M proto tcp^M remote ___ip_VPS___ 1194^M auth SHA256^M cipher AES-256-CBC^M resolv-retry infinite^M nobind^M persist-key^M persist-tun^M comp-lzo^M verb 3^M mssfix 0^M tls-client^M remote-cert-tls server^M key-direction 1^M ns-cert-type server^M ^M up /usr/syno/etc.defaults/synovpnclient/scripts/ovpn-up route-up /usr/syno/etc.defaults/synovpnclient/scripts/route-up redirect-gateway script-security 2 plugin /lib/openvpn/openvpn-down-root.so /usr/syno/etc.defaults/synovpnclient/scripts/ip-down ca ca.crt key ___имя_клиента__.key cert __имя_клиента__.crt tls-auth ta.key 1 Затем с помощью команды mkdir создаем директорию keys в директории /usr/syno/etc/synovpnclient/openvpn/ куда и положим с помощью команды cp имеющиеся у нас файлы сертификатов и ключи от них. С помощью этой же команды необходимо скопировать измененный файл конфигурации обратно в соответствующую директорию. Hide Для того чтобы подключиться к серверу OpenVPN необходимо зайти в Панель управления – Сеть – Сетевой интерфейс, выбрать созданное нами подключение и нажать на кнопку «Подключить» Результат: Все сервисы, в том числе которые в докере/виртуалбоксе будут работать, если вы не забыли указать порты в правилах выше. Доступ к NAS извне будет только через сервер в Италии/Чехии, т.е. увеличится пинг. Заметно. Скорость скачивания торрентов убавится, но зато Ваш провайдер не будет знать чем занимается Ваш NAS. Доступ по локальной сети через Ваш роутер (по адресам вида 192.168.1.ХХ или 192.168.0.ХХ) должен остаться. Даже если в цепочке ноут - NAS у обоих запущен клиент OpenVPN трафик не должен пойти через VPS а напрямую. Таким образом мы сохраним скорость доступа максимально внутри Вашей локальной сети. После подключения и некоторых шаманств с временем (через отдельное приложение в браузере) можно добиться такого результата: Тест думает что мы действительно в Италии. 4. Tricks & Tips Если будем давать пользоваться друзьям то можно сделать подключение проще и красивее. Вместо передачи 4 файлов можно сделать 1. Для этого нужно открыть сгенерированный ранее фалй .ovpn для товарища, и привести его к виду Измененный конфигурационный файл основная часть настроек без изменений ниже добавляем: <tls-auth> -----BEGIN OpenVPN Static key V1----- скопировать данные из файла ta.key -----END OpenVPN Static key V1----- </tls-auth> <ca> -----BEGIN CERTIFICATE----- скопировать данные из файла ca.crt -----END CERTIFICATE----- </ca> <cert> -----BEGIN CERTIFICATE----- скопировать данные из файла имя_клиента.crt -----END CERTIFICATE----- </cert> <key> -----BEGIN PRIVATE KEY----- скопировать данные из файла имя_клиента.key -----END PRIVATE KEY----- </key> Hide И сохранить. Таким образом мы интегрировали необходимые ключи и сертификаты в файл настроек клиента. Теперь для подключения нужно передать только один файл .ovpn Если ранее сгенерированные ключи больше не требуется, их надо правильно отключить. Иначе если кто-нибудь их сможет получить – то будет иметь возможность подключаться к вашему серверу. Отзываем сертификат: cd /usr/share/easy-rsa/ source ./vars ./revoke-full ___имя_клиента__ Созданный файл положить в /etc/openvpn/keys/crl.pem В файле конфигурации openvpn сервера добавить строку crl-verify /etc/openvpn/keys/crl.pem И сделать рестар Systemctl restart openvpn Для удобства отлова проблем при подключении не забываем делать в отдельных консолях: tail -f /var/log/openvpn.log tail -f /var/log/openvpn-status.log 5. Используемые материалы https://habr.com/post/233971/ https://community.vscale.io/hc/ru/community/posts/209661629-Установка-и-первичная-настройка-OpenVPN-на-Ubuntu-16-04 https://docs.openvpn.net/ https://habr.com/post/216197/ https://www.linode.com/docs/networking/vpn/set-up-a-hardened-openvpn-server/#client-configuration-file
  20. 5 points
    Thank you everyone but the one doing all loader work here is Jun not me. So thanks to him on the loaders.
  21. 4 points
    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
  22. 4 points
    Итак, не сдержался и решил попробовать, что же можно выжать из этой железки. Тестовый стенд: ASRock J4105-ITX, память Crucial DDR4 SO-DIMM 2400MHz PC4-19200 CL17 - 4Gb CT4G4SFS824A, флешка, винт 2.5 на 250 Гиг. Подготовил флешку, как описывал тут, воткнул память, подключил винт и питание. Подключил телек по hdmi, но как выяснилось этого можно было не делать, ибо все взлетело из коробки, даже в биос лезть не пришлось. Потребление по ватт метру 10 ватт, папка /dev/dri на месте, установил Video station, кодеки активировались. С танскодом 4к получилось вот что: На четырех потоках потребление выросло до 30 ватт, радиатор проца заметно нагрелся, по-этому кто планирует использовать сборку в таком режиме - подумайте о хорошем обдуве радиатора. Далее решил проверить гибернацию, поставил этот extra.lzma с помощью этого трюка. Картина получилась не айс, винт периодически просыпался (такое же было давным давно на 6.1 3615), по-этому советую на нее забить, пусть лучше винты постоянно крутятся - целее будут. Далее побаловался с виртуалками, вынь 10 про на таком железе это нечто с чем-то 😂 Вообщем, кому они жизненно необходимы, то будет жить бубунта и виртуальная DSM для опытов, но памяти лучше добавить до 8ми гиг. В выходные планирую поставить на свою рабочую сборку и протестировать скорости копирования. Вывод - вполне годная плата для организации хрени дома. Продолжение следует...
  23. 4 points
    Инструкция по установке крайней версии прокси: 1. Ставим Docker в Центре пакетов хрени. 2. На виндовой машине ставим PuTTy, на *nix пользуемся терминалом. 3. Заходим на хрень по ssh. 4. Устанавливаем контейнер командой sudo docker run -d --privileged --net=host --name=ace86fed -e TZ=Europe/Moscow sybdata/ace86fed:v3133 bash -c "/bin/start.sh 600" --name=ИМЯ_КОНТЕЙНЕРА - можете править на какое нравится, но тогда в следующей команде нужно будет его подставлять TZ=Europe/Moscow - думаю, что не нужно объяснять, что это... 5. Заходим в контейнер: sudo docker exec -it ace86fed /bin/bash 6. Правим учетку на ТТВ в файле /opt/HTTPAceProxy-master/plugins/config/p2pproxy.py (midnight commander есть в контейнере, либо используем встроенный редактор nano): nano /opt/HTTPAceProxy-master/plugins/config/p2pproxy.py # Insert your email on torrent-tv.ru here email = 're.place@me' # Insert your torrent-tv account password password ='ReplaceMe' 7. Ставим ffmpeg, если нужно будет смотреть архивы ТТВ. yum install ffmpeg 8. Перезапускаем контейнер в вэбморде хрени в Docker. 9. Закрываем PuTTy или терминал. Все! Качаем плейлист или настраиваем девайсы/приложения на http://ip_или_домен:8000/channels/?type=m3u
  24. 4 points
    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"
  25. 4 points
    Recently I deployed Bitwarden (https://bitwarden.com/) in Synology Docker and thought I would share my experience for others looking to do so. ***For experienced individuals comfortable with synology command line and linux environments with docker, I take no responsibility for any issues encountered*** ***Read fully before considering*** History: I've used a number of password managers (lastpass, keeper, keepass, etc) and still use some for professional reasons. For personal use I was using KeepassX so I could control the safe (in Dropbox) and did not want my personal data cloud hosted. I need it to run on linux, windows, osx as well as mobile (android) support. I also am a strong proponent of two factor authentication, keepass offers it but is a lackluster implementation. I wanted a more robust self hosted password manager that I could host on my synology. Feature Requirements: There is a number of things I wanted in my personal password management that Bitwarden offered over the others TOTP (Time Based One Time Passcode) Two factor authentication with Authy or Google Authenticator Self hosted password manager with central database stored on my synology Robust device and application support (Linux, Windows, OSX, IOS App, Android App, Browser integrations etc) Push syncing of changes so conflicts in password safe are avoided or less likely Secure software with good development (bitwarden has a cloud hosted solution as well as self hosted, so they are diligent in ensuring updates are made regularly https://help.bitwarden.com/security/ and community involvement is very good) Free for personal use and open source Setup Requirements: You will need to have the following requirements met to follow this guide: Latest XPenology/Synology: Currently on DSM 6.1.6-15266 with JUN'S LOADER v1.02b - DS3617xs Latest Synology Docker Package: Currently on 17.05.0-0370 (https://www.synology.com/en-global/dsm/packages/Docker) Your own public domain (in this use case I use a personal public facing domain with public DNS) An understanding of Domains, Extenal DNS, SSL Certificates (Lets Encrypt), Reverse Proxies, Linux/Synology cli, Docker Process: Please fully read the bitwarden self hosting documentation (https://help.bitwarden.com/article/install-on-premise/) before attempting any of these steps Create your bitwarden external DNS record (I used bw.<mydomain> this guides example will be bitwarden.domain.com) You have two options for your dns record: "A record" which is a record to the External IP address you use to reach your synology/xpenology device (eg: bitwarden.domain.com A record to Your public IP) "CNAME record" which is a record to the existing DNS Record of your synology/xpenology device (eg: bitwarden.domain.com CNAME record to nas.domain.com) Create an SSL Certificate using Lets Encrypt within DSM Certificate Manager Go to "Control Panel" -> "Security" -> "Certificate" -> "Add" "Add a new certificate" -> "Next" Description "Bitwarden Certificate", "Get a certificate by Lets Encrypt" -> "Next" Domain name: "bitwarden.domain.com", Email: "<your email address>" -> "Apply" Create a Reverse Proxy in DSM to the docker port used by bitwarden Go to "Control Panel" -> "Application Portal" -> "Reverse Proxy" -> "Create" Description: "Bitwarden https reverse proxy" Source: Protocol: "HTTPS", Hostname: "bitwarden.domain.com", Port: "443", HSTS and HTTP/2 "Unchecked" Destination: Protocol: "HTTP", Hostname: "localhost", Port: "8123" Associate Reverse Proxy with Certificate Go to "Control Panel" -> "Security" -> "Certificate" -> "Configure" Services: "bitwarden.domain.com" Certificate: "bitwarden.domain.com" -> "OK" Ensure docker is installed and collect docker folder location Install docker from the package manager Confirm docker shared folder location "File Station" -> folder "docker" right click properties and collect path (mine was "/volume1/docker" and will be referenced as the path in this article) SSH connect to synology/xpenology internal IP address or hostname as administrator account linux/osx terminal command: ssh admin@<nas internal ip or dns> (enter admin user password) windows use putty or bash for windows to connect (provide admin user and passwords as credentials) Switch to root user for docker access command: sudo su - (enter admin user password when prompted for password) Change to the docker folder command: cd /volume1/docker (or whatever your path to docker shared folder may be) Follow bitwarden self hosted setup procedure (reference https://help.bitwarden.com/article/install-on-premise/) Get a self hosting installation id and key here https://bitwarden.com/host copy these value to be used when running installation Import bitwarden.sh script command: curl -s -o bitwarden.sh \ https://raw.githubusercontent.com/bitwarden/core/master/scripts/bitwarden.sh \ && sudo chmod u+x bitwarden.sh Run installation using script command: ./bitwarden.sh install follow prompts in code block: root@nas:/volume1/docker# ./bitwarden.sh install _ _ _ _ | |__ (_) |___ ____ _ _ __ __| | ___ _ __ | '_ \| | __\ \ /\ / / _` | '__/ _` |/ _ \ '_ \ | |_) | | |_ \ V V / (_| | | | (_| | __/ | | | |_.__/|_|\__| \_/\_/ \__,_|_| \__,_|\___|_| |_| Open source password management solutions Copyright 2015-2018, 8bit Solutions LLC https://bitwarden.com, https://github.com/bitwarden =================================================== Docker version 17.05.0-ce, build 9f07f0e-synology docker-compose version 1.14.0, build c7bdf9e (!) Enter the domain name for your bitwarden instance (ex. bitwarden.company.com): bitwarden.domain.com (!) Do you want to use Let's Encrypt to generate a free SSL certificate? (y/n): n 1.17.2: Pulling from bitwarden/setup Digest: sha256:cf55e0288b6392ee9c35022089396c3c561773ddc963945f1afea8fce359757f Status: Image is up to date for bitwarden/setup:1.17.2 (!) Enter your installation id (get it at https://bitwarden.com/host): <my_installation_id> (!) Enter your installation key: <my_installation_key> (!) Do you have a SSL certificate to use? (y/n): n (!) Do you want to generate a self-signed SSL certificate? (y/n): n !!!!!! WARNING !!!!!! You are not using an SSL certificate. Bitwarden requires HTTPS to operate. You must front your installation with a HTTPS proxy. The web vault (and other Bitwarden apps) will not work properly without HTTPS. !!!!!!!!!!!!!!!!!!!!! Generating key for IdentityServer. Generating a 4096 bit RSA private key ....................................................................................++ ......................................++ writing new private key to 'identity.key' ----- (!) Do you want to use the default ports for HTTP (80) and HTTPS (443)? (y/n): n (!) HTTP port: 8123 (!) Is your installation behind a reverse proxy? (y/n): y (!) Do you use the default ports on your reverse proxy (80/443)? (y/n): y (!) Do you want to use push notifications? (y/n): y Building nginx config. Building docker environment files. Building docker environment override files. Building app settings. Building FIDO U2F app id. Building docker-compose.yml. Setup complete Once setup is complete you will need to create some missing folders (this is due to the docker version on synology not creating bind mount locations on container creation, likely a version bug) there should be a new folder creating in your /volume1/docker location called /volume1/docker/bwdata create the following folders in the bwdata directory from your current location (/volume1/docker location) command: mkdir bwdata/core bwdata/core/attachments command: mkdir bwdata/ca-certificates command: mkdir bwdata/logs bwdata/logs/admin bwdata/logs/api bwdata/logs/identity bwdata/logs/mssql bwdata/logs/nginx bwdata/logs/notifications bwdata/logs/icons command: mkdir bwdata/mssql bwdata/mssql/data bwdata/mssql/backups If there are any failures on the ./bitwarden.sh start stating "ERROR: for <container name> Cannot start service <container name>: Bind mount failed: '/volume1/docker/bwdata/<path>' does not exists" make sure to create that missing <path> specified in the error Run setup using script command: ./bitwarden.sh start if there are not missing folders as per notes above the service should now be running on port 8123 and reachable from your external dns entry https://bitwarden.domain.com Run updatedb using script command: ./bitwarden.sh updatedb this will run database migrations on bitwarden for any latest database changes to run Additional changes to consider: modify your bwdata/env/global.override.env for the following features add smtp email disable registrations after you create your accounts other override features specific to your use case restart containers after change to global environment vars Update bitwarden version: To update to the latest version run: command : ./bitwarden.sh updateself command: ./bitwarden.sh update Hopefully this guide is helpful to anyone looking to host bitwarden on their synology/xpenology device.
  26. 4 points
    to remove the update badge, run this: synoappnotify -c SYNO.SDS.AdminCenter.Application admin -f SYNO.SDS.AdminCenter.Update_Reset.Main -u 0
  27. 4 points
    Я оленевод. Вам посоветую быть чуть повежливей.
  28. 4 points
    Massive thanks to jun! Hardware acceleration is now working on my 8th gen i7-8700K. Using new ds918 loader 1.04b. Bare metal on DSM 6.2.1. Even with Plex running inside a Docker container it is detecting the hardware (for anyone wondering, this required the plex user having ownership of /dev/dri/* and setting the device flag + mounting /dev/dri in the container). This is really super... I thought it would only be possible with another big kernel upgrade from Synology. Fantastic to have it working with these CPU's. Thanks again for the amazing work jun 👌
  29. 4 points
    Всем привет! Долго искал и нашел как сделать, чтобы скачивать книги минуя MyHomeLib прямо на читалку. Особенно актуально в пору отпусков. Первоисточник тут. Итак, поехали: 1. Запоминаем путь где лежит Librusec, например, /volume2/Downloads/Librusec/lib.rus.ec 2. Ставим php 5.6 3. Ставим и настраиваем Web Station Проставляем все галки и выбираем все расширения, в open_basedir в конец строки через двоеточие добавляем путь к библиотеке из п.1 5.Скачать и распаковать архив copsfb2.zip в корень web-сервера 6. В директорию (от корня web-сервера) copsfb2/create_db/ скопировать librusec_local_fb2.inpx и соответственно отредактировать в copsfb2/create_db/create_db_conf.php параметр $inpx_file 7. На директорию (от корня web-сервера) copsfb2/fb2lib/ дать права на запись для группы http, под которой работает web-сервер. 8. Отредактировать в copsfb2/config_local.php параметры: $config['zipbook_directory'] должна указывать путь к архивам с книгами (п.1). Другие параметры пока не трогаем! 9. Запустить проверку: http://diskstation/copsfb2/checkconfig.php . diskstation - адрес вашей хрени. В выводе должны быть все Ok, кроме последнего, где говорит, что не найден metadata.db, это нормально 10. Запускаем загрузку INPX и создание metadata.db: http://diskstation/copsfb2/create_db/create_db.php 11. Если предыдущий пункт прошел успешно, запускаем http://diskstation/copsfb2/index.php, проверяем навигацию по библиотеке и закачку. Если есть проблемы, проверяем настройки путей и open_basedir 12. По желанию редактируем остальные параметры в copsfb2/config_local.php и copsfb2/config.php, например, ставим пароль на доступ к странице.
  30. 4 points
    There are no real questions here, just sharing my experience of trying to repurpose old hardware and bring it new life. Hopefully you can too! I came across an old HP Mini 5103 Netbook I had unused. It wasn't capable in running light weight linux OS's very well but didn't want to throw it out. I checked the specs: Intel Atom N455 Processor (1.66 GHz, 512KB L2 cache, 667 MHz FSB) 2GB DDR3 1333 MHz SDRAM Dedicated 10/100/1000 NIC 250GB 2.5" 7200RPM HDD 3 USB Ports 1 SD Card Slot 6-cell (66 WHr) high capacity Li-Ion Battery Low power consumption (approximately 15w on average) ... I realized this is really a close match to most entry level Synology NAS devices. My only concerns were the lack of additional SATA ports (1 hard drive). I thought I would give it a test with the latest xpenology, and it works remarkably well. I found it responsive in the UI and strangely more responsive than my current (higher performance) device. This led me to question, Can I get a couple hard drives on here? We'll we only have one 250GB Sata 2.5" 9.5mm drive. I have a 500GB USB drive laying around and thought, this drive is USB, but could USB drives be added to an SHR Raid? With a google search I found this video of xpenology interpreting USB drives as regular HDD's by changing some settings in /etc.defaults/synoinfo.conf: I found this useful in proving the point that you can add USB drives and interpret them as internal SATA drives. I made the following changes to my config /etc.defaults/synoinfo.conf ### Increase disk capacity #maxdisks="12" maxdisks="24" ### ### Disable esata port discovery #esataportcfg="0xff000" esataportcfg="0" ### ### Increase internal drive discovery #internalportcfg="0xfff" internalportcfg="0xffffffffff" ### ### Enable synology SHR # Ref https://xpenology.com/forum/topic/9281-synology-hybrid-raid-shr/?page=0#comment-79472 #supportraidgroup="yes" support_syno_hybrid_raid ="yes" ### ### Disable usb discovery #usbportcfg="0x300000" usbportcfg="0" ### Once I made these changes I could restart and see any USB drives plugged in were viewed as internal drives Now I created a Disk group and Volume that was SHR for mixed drive sizes to get the most out of them. I found after a restart I would have a Degraded Raid, I think this may have to do with the USB being slower to discover and looks like a drive was removed and added on boot. I can rebuild the raid and its good again. But this is something to consider regarding stability. My next attempt is to get 2 external hard drives and raid them without the internal SATA drive, they may be more consistent being the same connection and handle a reboot with out a degraded state. If thats the case, I think its a real winner for repurposing old hardware. I also came across an old 4GB SDCard, and thought, instead of the USB, why not use the SD for booting and that would be 3 free USB ports for External HDD's. I found this post I followed the same process, inserted the SD Card into the Mini, copied the PID and VID and setup the boot loader on the SD Card. After that, I set the bios to boot from SDCard and restarted. When going to the URL it sees the device as a "new hardware" and you "recover" the device. After that SD Card boot was all good. If all goes well with the USB HDD Raid where it can handle a reboot, I may consider getting some big external USB HDD's and raid them. Some use cases for this would be: - a backup location for my primary xpenology box (good to run upgrades on before doing the primary) - store media files that are network shared (movie streaming, music etc) that aren't a major concern of losing and don't require massive disk performance - with a working battery (mine is dead, but may consider getting a replacement) it has its own build in UPS, so it could handle power outages etc. and could be used in remote places like your parents house for remote access and other centralized services you manage for others - home automation box - the list goes on. This setup is probably not recommended for stable use but more of a stretching the boundaries of what can be done with xpenology when your hardware is limited or your use case is experimental. *** Edit *** Ended up going with an internal 2TB HDD and 3 external 4TB HDD's for a total of 9TB usable space with SHR. Velcro attached the drives to the lid and strangely enough the metal finish was a brown tone like the HP case, this was a coincidence.
  31. 4 points
    A kernel config related to pci is changed, so all non official pcie device drivers are broken. 通过我的 ONEPLUS A5000 上的 Tapatalk发言
  32. 4 points
    More work to come for me... Good job @jun
  33. 4 points
    New package full modified for the new version 6.1.6 with kernel build 15266 VirtualBox_x64_5.0.40-115130-1_6.1.6.spk Enjoy!
  34. 3 points
    Решил немного облегчить жизнь новичкам и тем, кто успел подзабыть, где и что лежит. 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, инструкция в следующем) Просьба ссылки тут не обсуждать, добавляйте свои, если посчитаете полезным.
  35. 3 points
    ok, further info, I managed to keep 2 x 4k streams simultaneously with minimal buffering by enabling CSM / UEFI ONLY .....
  36. 3 points
    @mandreto10 I highly suggest you review your attitude and the way you talk to others. People have been trying to help you but your arrogance is beyond my understanding. I have spend countless hours restructuring and running the forum, making tutorials, helping thousands of people and when I read your posts I even wonder why people answered to you in the first place. To this day I have never, not even once, come across a user in the this forum that has shown such behavior. You are new here so modesty is probably something you should consider if you want others to help. For your information no one here is paid to: 1 - make the loader 2 - run the forum 3 - moderate the forum 4 - contribute to the forum You can start by reading the Rules and Guidelines. That will give you a general understanding of how we roll here. Then you can read the FAQs. That should provide a general understanding of what XPEnology is and how it all works. If you have additional questions please ask them in the appropriate section and in a manner that is respectful to others. Thank you.
  37. 3 points
    Si cela vous intéresse, je suis en train de vous préparer un tuto pour l'installation de DSM 6.1 sur Hyper-V.
  38. 3 points
    This is just one person's opinion and I do not speak for anyone else: I'm not an admin here, I did not write the loaders. I'm just a tech-savvy user, that likes DSM and how it performs on my own hardware - far better than on Synology hardware. Over time, I have figured out a lot of things about XPEnology, and am willing to spend some personal time to help others, just like countless other contributors here. You are on a forum where the stated purpose is to enable people to use a hack. It's not a product support page. This collective effort has spanned 10 years of DSM releases, and people are still using some of the old software versions. So ALL the information here is still relevant to someone, and nobody's being paid to curate the part you think you need, just for you. If you want to use XPEnology, you need to put in the time (and have the tech skills) to understand the ecosystem and the tools involved. Many people, myself included, have done research and written up documentation or coded tools to try and help with this. But it won't be delivered on a platter like FreeNAS, which is bankrolled by the commercial side of the product. As you perceive a need for things to be organized differently, may I suggest that you become an expert here and start contributing instead of lecturing to people you don't know, and who don't owe you anything on how a loosely structured forum and its content should be presented. Again, I personally am happy to help when I have something useful to contribute, but I'm having a hard time getting over the attitude and general lack of patience that I perceive from you. This has caused me to delete several draft posts (intended to be of assistance to you) out of exasperation. In a prior post, I suggested that "maybe XPEnology wasn't for you" and while it's not for me to defend that, I do believe that your approach may prove to be very frustrating, should you persist.
  39. 3 points
    https://www.synology.com/en-global/releaseNote/DS3615xs Release Note: Version: 6.1.6-15266 Version: 6.1.6-15266 (2018-03-27) Important Note The update is expected to be available for all regions within the next few days, although the time of release in each region may vary slightly. This update will restart your Synology NAS. What's New in DSM 6.1.6 Fixed an issue where iSCSI service may stop under windows cluster environment. Fixed an issue where the history record of Resource Monitor may not be updated. Fixed an issue where Korean files may not be read by HFS+. Fixed a security vulnerability regarding p7zip (CVE-2017-17969). Fixed multiple security vulnerabilities regarding NTP (Synology-SA-18:13). Fixed multiple security vulnerabilities regarding Linux kernel (CVE-2017-15649, CVE-2017-17712). Fixed a security vulnerability regarding isc-dhcp (CVE-2018-5732). Fixed multiple security vulnerabilities regarding Samba (Synology-SA-18:08). Fixed multiple vulnerabilities (Synology-SA-18:14). Hide
  40. 3 points
    Как и обещал 8.1.3-5473 https://mega.nz/#!SkkwkABT!CtzlniTwXliXgFO9PhYesAoTtQ6fSF7oM_U__uLTgYw
  41. 3 points
    Hi, I've spent several days on this HW transcoding problem with asrock j3455-itx motherboard. I've read all the post of this thread and some other related threads in this forum. Gotta say this might be a general problem with this motherboard. Basically, it's the i915 driver's problem and it can be searched(/dev/dri missing, i915 driver problem) from other linux forums. Finally I kind of found a way to make /dev/dri appear when install DS918+ DSM 6.2 using j3455-itx. Here is my method(But to be knoest, the performance is poor.) 1. My method only work on 1.03a2 + extra.lzma_v0.5(I'm not sure whether the extra.lzma is necessary but I included it when making my usb boot) I tested that my method won't work in 1.04b, maybe because the updated i915 driver as @jun stated. 2. When you modify the grub.cfg, changing the vid/pid/SN/MAC, also add a new arg 'i915.alpha_support=1' in the line 'set comon_args_918 = xxx', so it looks like: set common_args_918='syno_hdd_powerup_seq=1 HddHotplug=0 syno_hw_version=DS918+ vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_hdd_detect=0 syno_port_thaw=1 i915.alpha_support=1' Install the system(I never tried migratiion) and then the /dev/dri appears and HW transcoding works fine in video station if you also have real SN/MAC. (But the performance is quite poor. I've a 35 min 4K h264 movie. For offling hw transcoding to medium quality, it says about 3 hours to finish. But SW transcoding saied 1hr to finish....sign...) Another thing: DSM 6.2 seems quite slow than DSM 6.1. When I tried in install DSM 6.2, after the screen said 'find.synology.com', it took 5min for DS assistant to find my nas, and 10 min to finish install the DSM. Then the machine reboot, another 6 min before DS assistant finds the ip of my nas. While for installing DSM 6.1, normally it only took 2 min to finish each step. Besides that, in 6.2, my package center seems different from the others. Because I only got the category 'all' in the left panel, while from the picture I browsed from the internet, there should be categories like 'recommended', 'back up', 'utility'.... Last but not least, shutdown is not working for my 6.2. I have to use the shutdown command in command line to turn off my nas. At first I thought this motherborad would be perfect for dsm 6.2 and ds918+ since its specification is quite close to the genuine one. But now I stayed at DS916+ and DS6.1.7.
  42. 3 points
    Hi, I've made new release, VirtualBox is updated to 5.2.20. I've created packages for few more architectures, you can find them now in release page on github, I've tested only bromolow package. Also note that currently there is a bug with upgrade procedure so you will have to uninstall old version and then install new one. Regards, Seba
  43. 3 points
    Hi folks, I'm a lost-cause kinda aging nerd - I can't help myself when it comes to trying out all kinds of options before paying for software (or hardware for that matter). The $$ aren't that big a problem - I guess I enjoy the challenge. Anyway, storage at home led me to a Freenas environment for a while. Working with linux for many years, I was keen to build up my freebsd skills. It as a satisfying ride for quite some time. Freenas is everything you could want it to be. I bought a beefy whitebox and went crazy with virtualbox and all kinds of (sometimes tricky) configuration. At end-of-financial year, I decided to look for a low power box so I could leave the NAS functions online (already using many raspian boxes for various projects). I went shopping at my local (Ultimo in Sydney AUS) shop for a low power box to be my freenas always-on box.. I had a bit of a rush of blood and bought a DS218+ and some new drives - go figure.. there were no good, cheap off the shelf options that didn't need a lot of fiddling about. The Synology DS218 became my favourite new toy. In no time flat, I'm running out of space on the DS218 ;-)... Thought about a DS918+ and giving my DS218 to one of my kids. Somehow, I stumbled across the xpenology project and stopped dead in my tracks. I'm often asked by family and friends to help them with their home kit. What I've learned so far makes xpenology sound like a great option for people watching their dollars. I'm going to dive in and use it for a while - see if my daughter and sons might get a nice new Christmas present (build from spares or course - making something is always more satisfying than handing over $$$. Looking forward to the experience! Ben
  44. 3 points
  45. 3 points
    HP MicroServer Gen8 with E3 1260L works fine. Did a migration from DSM 6.1 DS3615 to 6.2 DS3617
  46. 3 points
    Hi all, Managed to get this working now! Thanks for those who read the post. I have created a brief guide below that may help someone else, my problem was that the http://find.synology.com/ would not find my TerraMaster. Once I went to the web address of the TerraMaster (previously reserved on my router) I was able to continue the installation. Good luck to those who are trying to do this. Installing XPenology on to TerraMaster F4-220.pdf
  47. 3 points
    Оптимизация и тонкая настройка из коробки сразу доступны логи движка по ссылке при услови что порт для супервизора 9903 проброшен http://ip::9903/logtail/acestream # это аналог в терминале tail -f -n 0 /var/log/supervisor/acestream.log аналогично доступны логи для HTTPAceProxy, только после правки в HTTPAceProxy/aceconfig.py строчки 140 на: logfile = "/var/log/supervisor/acehttp.log" путь для правки nano /opt/HTTPAceProxy-master/aceconfig.py и тогда http://ip::9903/logtail/acehttp движок запускается с ключами: --live-cache-type memory # - хранить кеш в оперативной памяти --live-cache-size 524288000 # - максимальный размер кеша в bit, (по умолчанию: 209715200 bit (200 Мб)), здесь по личному опыту проишёл к тому что от зависимости объёма вашей памяти 200 Мб достаточно но 500 Мб ещё лучше, а сам я выставил вообще 1000 Мб --core-sandbox-max-peers 15 # - это значение позволяет автоматически находить пиры с хорошей скоростью отдачи и подсоединять их к себе, по умолчанию 5 --live-buffer 25 кстати в контейнере уже выполнено echo "tmpfs /tmp tmpfs rw,nosuid,nodev 0 0" | tee -a /etc/fstab что монтирует /tmp в tmpfs в коробке уже установлен скрипт сканирования источника как рекомендует сам автор ресурса потому как у него есть ограничение по исходящему трафику, и он не может позволить беспрерывную долбежку, вот его содержание: #!/bin/sh FNAME="tv.m3u" URL="http://pomoyka.lib.emergate.net/trash/ttv-list/ttv.all.iproxy.m3u?ip=" GNAME="${FNAME}.gz" curl --fail -R -z "${GNAME}" -o "${GNAME}" -H "Accept-Encoding: gzip" "${URL}" && \ gunzip -c "${GNAME}" >"${FNAME}" curl скачивает файл из $URL в tv.m3u.gz, используя метод сжатия gzip если он ранее уже был скачан, а на сервере изменен не был, то скачивание не производится это реализовано через поддержку хедеров If-Modified-Since и Last-Modified таким образом трафик остается на минимально необходимом уровне 1-2 Mb в сутки вместо 50,100,200 и больше Mb gunzip разжимает tv.m3u.gz в tv.m3u, который и нужен будет нам # правим под себя ip выполняем в терминале контейнера cd /var/www/html/ && ./scan-m3u.sh заносим в крон 0 */6 * * * cd /var/www/html/ && ./scan-m3u.sh лист доступен будет по ссылке http://ip:8844/tv.m3u # если порт nginx 80 пробросить на 8844! отдельно что касается использования HTTPAceProxy в которой реализована поддержка API torrenttv, что позволяет более комфортно пользоватся так как подтягиваются програма передач, иконки и архивы. за это отвечает плагин p2pproxy_plugin.py у которого в настройках заносим учётные данные ттв вип путь для правки nano /opt/HTTPAceProxy-master/plugins/config/p2pproxy.py строчки 19 и 20 # Insert your email on torrent-tv.ru here email = 're.place@me' # Insert your torrent-tv account password password ='ReplaceMe' ссылки этого плагина соответсвенно http://ip:8000/channels/?type=m3u http://ip:8000/archive/dates/?days=1 #(требуется доустановить ffmpeg) Install FFmpeg 3.4 add-apt-repository ppa:jonathonf/ffmpeg-3 apt-get update apt-get install ffmpeg по категориям http://ip:8000/channels/?group=3&type=m3u #расшифровка групп выше но также парралельно есть плагин torrenttv_plugin.py который так же частично использует API для подтягивания иконок и програмы но не требует учётки ттв и при этом также нет возможности смотреть архивы путь для правки nano /opt/HTTPAceProxy-master/plugins/config/torrenttv.py строчка 15 заносим источник типа # Insert your Torrent-tv.ru playlist URL here url='' и строчка 27 , интервал сканирования источника в минутах, оптимально значение 360 ссылки этого плагина соответсвенно http://ip:8000/torrenttv http://ip:8000/torrenttv/playlist.m3u здесь правим сортировку каналов в строчке 28 и 30 на True nano /opt/HTTPAceProxy-master/plugins/modules/playlist.py здесь правим specified flags проца, доступные значения nano /opt/HTTPAceProxy-master/aceclient/aceclient.py строчка 247 ffmpeg_cmd += '-hwaccel auto -hide_banner -loglevel fatal -re -i %s -c copy -f mpegts -' % url где добавляем ключ допустим для интел -cpuflags sse4.2 или лучше -cpuflags avx2 # если иструкция avx2 поддерживается вышим процем логи прокси: тыц ,тыц ,тыц
  48. 3 points
    можешь малинку(raspberry pi 3) взять, ман свежий здесь или на свою хрень поставить этот контейнер и я тебе гарантирую что ты будешь смотреть на телеке любое "кино" что есть в сети на торрентах + 900+ каналов тв просмотр начинается сразу при начале скачивания, перемотка, посмотрел и забыл поток на выбор или http и hls
  49. 3 points
    NOTE OF CAUTION It is strongly advised to never apply an update on a 'production' box as soon as the update is made available. ALWAYS test the update on a test machine first and make sure all features are working as expected. Also, I personally recommend you to wait several days (maybe 4/5 days) after the update is available to apply the update on a 'production' box. Reason is that Synology seems to have been making updates available and then suddenly withdrawing them for no apparent reason. This could mean that the update has some issues and needs to be withdrawn from the public.
  50. 3 points
    download this: https://www.dropbox.com/s/ytimsezu9cl61xx/synoboot_1.02b_ESXi_only.zip?dl=0 the only option available is ESXi, so you should not have problems regarding boot choice, it's for DS3615xs (i find has a better custom package support than DS3517xs). - extract and upload synoboot.vmdk and synoboot.img in your datastore - create a new VM (HW Version 11 or 13) dependent if you are on ESXi 6.0u2 or ESXi 6.5b - operating system should be Other -> FreeBSD 64bit - set bios to EFI - set nic to VMXNET3, set the mac manual to the same as the one in the grub.cfg - set scsi controller 0 to "LSI logic SAS" - add sata controller 0 if not there yet present - add existing hdd -> browse datastore -> add synoboot.vmdk - edit this hdd to "independent - persistent" and sata 0:0 on controller 0 - add how many new scsi disk you like, thin provisioning - dependent - save and poweron the VM - from your browser, go to find.synology.com, it should pop-up, connect and install it (manual or from internet is the same), reboot after finish the setup - create a new volume to your needs, if you want shr you have to modify synoinfo.conf - download this zip for open-vm-tools https://www.dropbox.com/s/k4hc343gwdepiuf/open-vm-tools_bromolow-6.0_10.0.7-1.spk.zip?dl=0 - extract the zip, install the spk in package manager - now ESXi should see that vm tools are installed and running Pretty much done.