Leaderboard


Popular Content

Showing content with the highest reputation since 09/05/2018 in all areas

  1. 35 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. 25 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 07/Apr/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.2 4.4.x Supported Supported EFI or Legacy BIOS Haswell or later recommended, AsRock Jxxxx fails on 6.2.2 1.03b DS3615 or DS3617 6.2 to 6.2.2 3.10.x Not Supported Not Supported Legacy BIOS only Nehalem or later 6.2.1+ seems to require Intel e1000e NIC 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 on ESXi failures reported 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
  3. 16 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. 16 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. Просьба к админам прибить тему в шапке и дать мне доступ на редактирование первого поста этой темы, буду добавлять по мере поступления вопросов, ибо задолбали оленеводы, которые задают вопросы по установке, во всех подряд темах.
  5. 9 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, инструкция в следующем) Просьба ссылки тут не обсуждать, добавляйте свои, если посчитаете полезным.
  6. 8 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
  7. 8 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
  8. 7 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"
  9. 6 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. 6 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
  11. 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
  12. 5 points
    I generated an easy to install package to activate a mainboard connected power button for clean shutting down (instead login in web page). Install package for DSM 5.2, DSM 6.0 and DSM 6.1(.1): powerbutton_6.1-0004.spk powerbutton_6.1-0005.spk I have tested DSM 5.2 and DSM 6.1 for the DS3617 versions only in VM. Please report if there are any problems. Changelog Version 6.1-005 Added Braswell to INFO Version 6.1-004 Minor change for recognizing DSM 6.1.1 Version 6.1-003 Adding support for DSM 5.2 Version 6.1-0002 Combining DSM 6.0 and DSM 6.1 in one package Version 6.0/6.1-0001 Versions for DSM 6.0 and DSM 6.1 Hide
  13. 5 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-5.0.4.1-fat.img | 15.6 MB | MD5 = 2f201876ef576f4ef78a3c3bbbcee529 NanoBoot-5.0.3.2-fat.img | 15.6 MB | MD5 = 89ce54b38e83c7b94c422f6c9a0dbedb NanoBoot-5.0.3.1-fat.img | 15.6 MB | MD5 = 07bd106a7f6204962c801ecf851f1dc9 NanoBoot-5.0.2.4-vfat.img | 32.0 MB | MD5 = e1353d7143cbf8cc31ed320f82cf65d6 NanoBoot-5.0.2.4-fat.img | 15.6 MB | MD5 = 32e1f823219ec7963162e4e394687112 NanoBoot-5.0.2.3-fat.img | 15.6 MB | MD5 = 6fc6be138eb070938a9f14ff64fa4239 NanoBoot-5.0.2.2-fat.img | 15.6 MB | MD5 = 6bbf71f64909cda57c3a63e523d13ed8 NanoBoot-5.0.2.2-ext2.img | 31.3 MB | MD5 = 60233f771b934b5237e2037be0e64b95 NanoBoot-5.0.2.1-fat.img | 15.6 MB | MD5 = 039abc91883e09fd2f443ee10ba5690e NanoBoot x86 5.0.x DS214Play NanoBoot-x86-5.0.3.1-fat.img | 15.6 MB | MD5 = 3c6776570962926497088e6b3889205c NanoBoot-x86-5.0.2.5-fat.img | 15.6 MB | MD5 = b76c423d39129b19b2e0a62f741aaa8c NanoBoot-x86-5.0.2.4-vfat.img | 32.0 MB | MD5 = 8bc6d3b5aed1f41fa0ce4d93b17f9bf1 NanoBoot-x86-5.0.2.4-fat.img | 15.6 MB | MD5 = 90948500efde437ae56dfd51f31f55f8 NanoBoot-x86-5.0.2.3-fat.img | 15.6 MB | MD5 = 7acb8faf796a0e5d5a54a9734ecec728 NanoBoot-x86-5.0.2.2-fat.img | 15.6 MB | MD5 = f333038c8bcf1e530ddeb55075b9827c NanoBoot-x86-5.0.2.1-fat.img |15.6 MB | MD5 = 5bf7241df633ff48ce6a571aa27df88c
  14. 5 points
    There is a better way^^ Just activate it: In your browser open the following urls one after another: Replace the following: URL, PORT, USER, PASS, SERIALNUMBER (dont replace any other symbols like : oder ") https://URL:PORT/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=USER&passwd=PASS https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="SERIALNUMBER" To get the current activation status call the 1. query above and then https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=get&version=1 ------------------------------ Example for url: server, port: 5001, user: admin, pass: admin, serialnumber: 123400 https://server:5001/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=admin&passwd=admin https://server:5001/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="123400"
  15. 5 points
    Господа модераторы! Какого ХРЕНа вы опять забанили нашего комрада 39911-архип, ранее он был известен как 5213-bob-the-builder, забаньте для кучи и меня, мы тогда с ранее упомянутым комрадом подумаем как увести русскою ветку и не только на другой форум. Или вам покоя не дает, то что кто-то набрал баллов лайков больше вас?! Детский сад Ё-моё. По-этому: 1. Прошу восстановить 39911-архип в правах и приплюсовать, то что было у 5213-bob-the-builder 2. Не трогать этот пост, пусть собирает лайки, они мне не нужны, это для Архипа/Boba.
  16. 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.
  17. 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.
  18. 4 points
    Bonjour, je me suis juste inscrit pour dire un énorme merci à Jun, Polanskiman et tous ceux qui ont bossé sur le projet XPEnology. Ces deux dernières semaines j'ai pu passer d'un DSM 5.0 à 6.1.7 presque sans aucun soucis sur une Asrock C2550 (neuve, l'ancienne ayant lâché après un peu plus de 4 ans de bons et loyaux services, ce qui est assez long pour ce modèle apparemment...) grace à votre boulot génial et la communauté qui m'a permis de contourner les problèmes commun à ce matos. Bravo et encore merci à vous tous pour rendre cela possible !
  19. 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ми гиг. В выходные планирую поставить на свою рабочую сборку и протестировать скорости копирования. Вывод - вполне годная плата для организации хрени дома. Продолжение следует...
  20. 4 points
    Hi everyone. After a grate help from 'dodo-dk' (You're the best man) and a lot of try and errors i managed to run DSM 6.2.1u6 on Proxmox 5.3-11. I'll share my insights and maybe it'll be useful for someone. Proxmox does have 4 LAN cards model to chose from the list, but as we all know Synology dropped drivers for some devices (e1000, vmware3...) so new version of DSM stopped working on Proxmox. But Proxmox allows you to chose different models (not shown in choosing list) , we just have to add it to 'args:' parameters, just like we did with usb boot key. For this to work you need to know few things: 1) This won't work on OVS bridge/bond - it has to be Linux bridge/bond 2) The Linux bridge/bond has to have gateway set When we are adding LAN card from 'args:' it looks like the LAN card chooses bridge/bond on which the gateway is set, so that's why it's needed to be set. First thing you may check it's if e1000e LAN card is available in your kvm. So in Proxmox shell write command: kvm -device help Under 'Network devices' you should see line: name "e1000e", bus PCI, desc "Intel 82574L GbE Controller" The next step is to find your 'args:' parameters. To do this we need to use another command: qm showcmd YOUR-VM-ID YOUR-VM-ID - is ID of your Xpenology machine with added e1000 LAN card. From the output you need to copy two arguments: netdev and device. In my case it looks like this: -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown' -device 'e1000,mac=00:11:32:2c:a7:85,netdev=net0,bus=pci.0,addr=0x12,id=net0' For this to work you have to remove the 'script' parts from 'netdev'' and change model from 'e1000' to 'e1000e' in device argument. you can also remove the " ' " signs. After changes it should look like this: -netdev type=tap,id=net0,ifname=tap100i0 -device e1000e,mac=00:11:32:2c:a7:85,netdev=net0,bus=pci.0,addr=0x12,id=net0 Next you need to add changed arguments in to the VM config file (/etc/pve/qemu-server/YOUR-VM-ID.conf). In my case 'args:' line looks like this: args: -device ich9-usb-ehci1,id=usb,multifunction=on,bus=pci.0,addr=0xa -drive file=/var/lib/vz/images/103/vm-103-USB103b.raw,format=raw,if=none,id=drive-usb-disk2,cache=writeback -device usb-storage,bus=usb.0,port=2,drive=drive-usb-disk2,id=usb-disk2,bootindex=1,removable=off -netdev type=tap,id=net0,ifname=tap103i0 -device e1000e,mac=BA:E2:8A:3B:AC:3E,netdev=net0,bus=pci.0,addr=0x12,id=net0 The last thing is to remove the 'net' device from config file, so just comment or remove the line with 'net' device. In Proxmox web interface the LAN device wont be visible, but it will work. So, summing things up, I'm not Proxmox specialist so i didn't knew all of that. One more time thank you 'dodo-dk' for your knowledge and time. God bless all Xpenology enthusiasts, Xpenology devs and Proxmox for being best free virtualization tool i know.
  21. 4 points
    Hi All After hours or reading, fixing & help from the community via posts and DM's I have finally got a stable system. Thanks to everyone that helped me Really Appreciate It . This is what was needed or what I have done to get this to work. 1. First check out this Table to make sure you using the correct Loader: In my case I used DS3615xs v1.03b 2. Create a new USB with this Loader v1.03b DS3615xs and change the VID, PID, MAC, S/N - See this post if you not sure where to change it. You can ignore the Older Versions listed of the DSM's. 3. Backup you Configs of your NAS. This is going to Settings, Update & Restore, Configuration Backup and then click on Backup Configurations 4. Shutdown your NAS 5. Now Either use the new USB that you have made or Overwrite the one you have. NOTE: Backup the old Grub.cfg File as you might need it again if something goes wrong since you have your old settings listed there. 6. Add the new USB, Power Up and the launch Synology Assistant. If you do not have this you can download it from the Synology Site. 7. Once Installed you Search for your NAS and it should state Migrate. 8. Click Migrate and you can Decide if you want to Migrate Or Clean Install 9. Click Next and now when it asks for the DSM select the Manually Install Option and download the .pat file from here - https://archive.synology.com/download/DSM/release/6.2/23739/ 10. Let the NAS do its thing and after a while you should see the Logon Page. NOTE: If you log on and you get Loading in Chrome and nothing else OR in I.E logs on and after 30 Seconds it crashes (Everything Stops, LAN, Services etc...) Reboot your NAS and follow the below. 1. SSH via Putty 2. Log On with your Admin/Root Account or User Account 3. If User Account then type sudo -i and enter the Admin/Root Password 4. Type ls -la / 5. You should see a folder called .xpenoboot 6. sudo rm -rf /.xpenoboot 7. Type ls -la / to check it is removed 8. Reboot your NAS by typing reboot Back to setup: 11. You now should be able to Log On and complete the update to DSM 6.2-23739 Update 2 12. If you do not see this you can do it via SSH as well. A. SSH via Putty B. Log On with your Admin/Root Account or User Account C. If User Account then type sudo -i and enter the Admin/Root Password D. cd \@autoupdate/ E. ls -l (Should Be TOTAL: 0) The Below Downloads DSM 6.2-23739 Update 2: If You Using DS3617xs Then Change This - !!!! DO NOT RUN THIS BEFORE CHECKING !!!! F. In Putty Copy & Paste - wget https://archive.synology.com/download/DSM/criticalupdate/update_pack/23739-2/synology_bromolow_3615xs.pat --2019-01-18 20:33:31-- https://archive.synology.com/download/DSM/criticalupdate/update_pack/23739-2/synology_bromolow_3615xs.pat Resolving archive.synology.com... 216.176.185.220 Connecting to archive.synology.com|216.176.185.220|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 20963899 (20M) [application/octet-stream] Saving to: 'synology_bromolow_3615xs.pat' synology_bromolow_3615xs.pat 100%[===================================================================================================================================>] 19.99M 347KB/s in 36s 2019-01-18 20:34:08 (570 KB/s) - 'synology_bromolow_3615xs.pat' saved [20963899/20963899] G. Now Check that it is all OK - synoupgrade --check-pat /volume1/@autoupdate/synology_bromolow_3615xs.pat (Change The Volume To Your One Can Be 1, 2, 3, 4, etc...) UPGRADE_CHECK_PAT Patch type is CU Check patch successfully H. Install The Update - synoupgrade --patch /volume1/@autoupdate/synology_bromolow_3615xs.pat (Change The Volume To Your One Can Be 1, 2, 3, 4, etc...) UPGRADE_PATCH Start DSM update... I. You should see the below after a few minutes. Let you NAS reboot and once up and running it will be on DSM 6.2-23739 Update 2 Broadcast message from root@NASNAME (unknown) at 20:36 ... The system is going down for reboot NOW! 13. Log On to your NAS and check all your settings, App etc.. One thing I noticed there was 2 Tasks that i needed to disabled. This is under Settings, Task Scheduler I hope this works for everyone. Leave your comments / updates below if anything needs to get changed Thanks
  22. 4 points
    Bump for the addition of the 6.2.1 driver guide for DS3615. Comparing 6.1.7 and 6.2.1 is interesting, and I'll summarize findings here: r8168/r8169 support was completely removed from 6.2.1 on this platform Intel i40e and ixgbe drivers were enhanced on 6.2.1 to support newer cards Mellanox mlx4 and mlx5 drivers were enhanced on 6.2.1 to support newer cards Comparing DS3615 and DS918, in most cases there continues to be significantly better native driver support in DS3615, especially for 10Gbe+ cards. DSM supports many more 10Gbe+ cards than Synology lists on their compatibility matrix. However, loader 1.03b is really just broken, with many drivers causing kernel panics at boot, and some not working at all. Those who would use the driver list to inform an expensive hardware purchase should proceed with caution, and/or be willing to step backward to 1.02b and DSM 6.1.7 for compatibility reasons. @jun, if you are reading: there remains a need for the native driver library on DS3615 or DS3617, so if you can work 1.04b magic on the either platform, the community would benefit.
  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
    to remove the update badge, run this: synoappnotify -c SYNO.SDS.AdminCenter.Application admin -f SYNO.SDS.AdminCenter.Update_Reset.Main -u 0
  25. 4 points
    Я оленевод. Вам посоветую быть чуть повежливей.
  26. 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 👌
  27. 4 points
    A kernel config related to pci is changed, so all non official pcie device drivers are broken. 通过我的 ONEPLUS A5000 上的 Tapatalk发言
  28. 3 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 ##################
  29. 3 points
    Before you begin to change something in your working system, it is strongly recommended to make backups of your most valuable data, so you do not regret about their irretrievable loss. Everything you do is your fear and risk, no one encourages you to do it. The easiest and most reliable way to safely try to do it, turn off all the disks and the boot flash drive from the current system, take a clean disk and another USB flash drive and try to install a new version of the bootloader and the system, if it rolled, then do already on the current system. 1. How to install (described for a computer with Windows): a) download the 1.04 b boot loader image (the original theme is here), create a directory in the root of the disk, for example, c:/918/ and put the bootloader image there b) determine the VID/PID of the flash drive or card reader into which it is inserted (control Panel-Device Manager-USB Controllers-Your flash drive/reader-Properties-Information-hardware ID, you need to ensure that the DSM system recognizes this disk and does not try to install itself on it, if you incorrectly define and register these parameters, the istall process will crash by mistake 13) c) download, install and run the OSFmount program, mount Partition 0 (15 Mb) from the bootloader file, remove the "Read-only drive" checkbox before mounting d) download, install and run Akelpad, open grub/grub file.cfg on previously mounted disk, edit and save: set vid=0xA234 #VID flash drive/reader set pid=0xB678 #PID of flash drive/reader set sn=1780PDN123456 #sn set mac1=001132123456 #mac of the first network card set mac2=001132123457 #mac of the second network card, the second and subsequent differ from the first by +1 in the last bit in the hex system ... set netif_num=2 #number of network cards ... set sata_args= 'SataPortMap=6' # sata controller, values: 6 - 1 controller on 6 ports; 22-2 controllers on 2 ports; 42-2 controllers, the first on 4 ports, the second on 2, etc. Where to get sn and mac - is your headache, Google will help you, the system will be installed and will work with those that are initially registered in the bootloader, but with the restriction of the functioning of some services and modules, such as: QC, push notifications, activation of codecs for transcoding, installation of syno licenses... e) unmount the disk in OSFmount f) download, install and run the Rufus program and record the previously prepared image on a flash drive g) insert the flash drive into the computer on which you plan to run xpen, connect the drives, turn on the power h) disable the firewall in the anti-virus, in the browser type http://find.synology.com or install Synology Assistant from the syno website and find the newly installed xpen on your network j) install DSM following the instructions of the installation program and start setting up (how to do it here is not described, because all the answers are in the syno knowledge base) There is a utility where the main programs for Windows x64 are collected 2. Transcoding (needs sn and mac from real syno hardware) Most likely to run on Intel processors starting from the 4th generation (Haswell), but there are nuances with motherboard models and BIOS. Check as follows: hardware (hw) transcoding - at the root of the system should be a directory /dev/dri with subdirectories in it, if not, but there is no HW transcoding to check - look for the directory with the terminal/ssh command cd /dev/dri . software (sw) transcoding - some codecs must run in DSM, you can check it with the command in the terminal / ssh cat /usr/syno/etc/codec/activation.conf If the result is the same, sw transcoding will ran {"success":true,"activated_codec":["h264_dec","h264_enc","mpeg4part2_dec","hevc_dec","aac_dec","aac_enc","ac3_dec","vc1_dec","vc1_enc"],"token":"123456789987654abc"} If there is nothing similar, there is no sw transcoding. 3. Perhaps the most optimal budget solutions with transcoding will be the following: ASRock J4105-ITX Asrock J5005-ITX Who wants more - use mb with the latest generation of Intel processors with Intel i210 or realtek 8111 . But this is already determined by the size of the your wallet and the functionality that you additionally want to get from xpen. P.S. Sorry for my english 😂
  30. 3 points
    Just completed a new build, using an Asrock H370M-ITX board and 1.04b loader / DSM 6.2.2-24922, all fully functioning without any hassle or additional drivers. With 6 onboard SATA ports and 2 Intel NICs this is an ITX board to recommend.
  31. 3 points
    Aide au choix d'une configuration /!\ Ce post est uniquement basé sur mes choix, et mes idées. Il est là dans le but de vous guider dans vos choix et si possible à vous aider à faire le bon choix. Je ne parlerai ici que de CPU Intel "grand public" ( Pentium, i3, i5 ... ), pas de Xeon ( pour le moment ). Je ne parle volontairement pas d'AMD car sa compatibilité avec Xpenology est plus compliquée qu'avec Intel, c'est pour cela que j'ai choisi Intel. Sommaire : Exprimer son besoin Choisir le modèle de carte-mère Le choix du processeur ( CPU ) Le choix de la RAM Le choix de l'alimentation Le choix de l'onduleur Choisir ses disques dur Les cartes d'extension PCIe 1/ Exprimer son besoin ( puissance, taille, .. .), prévoir le futur sans oublier le budget ! Tout d'abord il faut bien réfléchir à ce qu'on souhaite faire ( avec son Xpenology ), ce qu'on pourrait être emmené à faire, et ce qui ne nous intéresse absolument pas. Voici une liste des utilisations "courante" : - Serveur de fichiers local - Serveur de fichiers à distance ( SFTP ) - Serveur multimédia "simple" ( dnla, smb, ... ) - Serveur multimédia complet ( Emby, Plex, ... ) - ... La taille de la carte-mère dépendra du boitier que vous allez choisir ! Le boitier, c'est lui qui contient tout, trop gros n'est pas forcément pratique mais c'est ce qui permet le plus de flexibilité car il est possible d'y mettre une alim "standard" ATX, une carte-mère du même standard, ... Les cartes mère aux format ATX ont tous les avantages, elles ne sont généralement pas trop chère et possèdent le plus de ports SATA, slots de RAM, .... Ensuite il y a les cartes-mères format mATX, entre l'ATX et l'ITX elle possède un encombrement moyen tout en disposant en général d'au moins 4 ports SATA et de 2 slots de RAM de taille "normal" ( DIMM ). L'ITX est le format idéal pour une machine compacte, la carte-mère ne dépassant pas les 17cmx17cm. Certains modèles sont "classiques" avec un socket permettant d'y mettre le processeur de notre choix et deux slots de RAM, d'autres sont pré-équipé de processeur et possède en général des slots de RAM dit "So-DIMM", ce sont des barrettes mémoires plus courtes, utilisé en général dans les PC portable. Ces cartes prééquipées ont généralement des processeurs dits "fan-less" donc sans ventilateur, l'avantage c'est le silence, mais par contre ces processeurs sont généralement peu puissant ( bien que suffisant pour une utilisation classique d'un NAS ). Recapitulatif : ATX : Le choix ( de modèle de carte-mère et de boitiers ), les connectiques disponibles - l'encombrement mATX : Le choix ( de modèle ), le prix - Connectiques "généralement moins fournis, moins de slot de RAM, faible choix de boitier pouvant contenir plus de 5 ou 6 disques dur. mITX : Compact, choix plus important de boitier style "NAS", le silence ( pour les cartes déjà équipées de CPU ), la consommation électrique ( pour les cartes déjà équipées de CPU ) - Le prix, la puissance ( pour les cartes déja équipé de CPU ) 2/ Choisir le modèle de carte-mère ? J'ai mon boitier, je sais quelle carte-mère je peux y mettre, maintenant il me faut choisir un modèle parmi les 10ène et 10ène de modèles existants ! 1er conseil : Choisir une marque connue ! Bien que la panne puisse arriver même sur des grandes marques, le risque est beaucoup plus faible. Quand on fabrique un NAS, on le veut fiable et ne pas avoir peur de se réveiller un matin avec tout de "planter" ! Voici des marques connues : AsRock, Asus, MSI, Gigabyte et ce n'est pas parce que c'est une marque que c'est forcément plus cher ! Parfois malheureusement, pour certains types bien particuliers ( comme les cartes à CPU intégré, il faut se tourner vers des marques un peu moins connues afin d'avoir du choix ! ). 2ème conseil : Choisir une carte récente avec un Socket actuel ! Actuellement, ( 01/2018 ) le Socket d'Intel ( pour le grand public ) est le 1151, avant lui il y avait le 1150. Certains vendeurs vendent encore des cartes avec ce vieux Socket, méfiez-vous, cela peut être un bon plan ( car souvent moins cher, mais assurez-vous de trouver le CPU compatible qui sera surement plus dur à trouver qu'un CPU actuel ! ) 3ème conseil : Assurez-vous de la compatibilité de la ram avec votre carte-mère, si vous choisissez une carte mère 1151, il vous faudra de la DDR4, ensuite il faut vérifier le format ( généralement DIMM ( le SO-DIMM étant principalement pour les pc portables et certaines carte-mère au format MITX ) ), la fréquence et le CAS. Votre besoin de stockage est-il important ? Si oui, il faudra vous concentrer sur les cartes-mères possédant assez de ports SATA pour votre NAS et même pour la suite ! À savoir qu'il est aussi possible d'y ajouter des cartes d'extension proposant 2 à 4 ports SATA par port PCIe mais les vitesses de ses cartes sont inférieures a ce que proposent les ports intégrés à la carte-mère. Les cartes d'extension font l'objet d'une explication "en plus" en fin d'article afin de revenir sur les vitesses max. suivant l'interface utilisée, ... Est-elle compatible ? La grande question ! Une fois la carte-mère idéale trouvée, il faut vérifier qu'elle soit compatible avec Xpenology. Pour cela, une recherche sur le forum s'impose ! L'idéal serait de trouver un membre ayant la carte-mère que le modèle choisit afin de savoir si elle est compatible ! Exemple : Votre choix se porte sur cette carte-mère, une AsRosk Z370M Pro4. Une simple recherche dans le forum avec la référence de la carte-mère, nous indique ce post : Dans ce message, on peut voir le membre "EVOTk" utilise la même carte-mère, et a effectué avec succès la MAJ 6.2 Update 4 sous Jun's Loader v1.03b DS3615xs et sans avoir besoin du "extra" personnalisé. On peut donc être sur à 100% que la carte-mère que l'on a choisi sera compatible avec Xpenology. Mais que faire si personne n'utilise la même carte-mère que celle de notre choix ? Dans ce cas, que vérifier ? Principalement, il faut vérifier 2 choses : le chipset de la carte-mère, qui gère les ports SATA ( entre autres ) et le contrôleur réseau. Si on reprend l'exemple de la AsRosk Z370M Pro4, le chipset est "Z370" et le contrôleur réseau est "Giga PHY Intel® I219V", on retrouve ses infos dans les caractéristiques détaillées. On emploie toujours la même méthode, on va chercher si quelqu'un utilise une carte-mère donc le chipset est identique et avec succès, et idem pour le contrôleur réseau ! 3/ Le choix du processeur ( CPU ) : Le choix du CPU, va se faire en fonction : - de la carte-mère choisie ( il faut que le socket soit le même, et que le chipset soit compatible ), chez tous les fournisseurs connus de carte-mère, il est possible de trouver pour chaque carte-mère la liste des CPU supportés par celle-ci ( généralement dans "support" ). - de la puissance voulu pour votre NAS. - du budget que vous vous êtes fixé. Dans le monde du CPU, il y a tous les prix, cela va du CPU peu puissant a 30€, jusqu'à 500, 600 ou même plus de 1000€ ! Un bon indice pour connaitre la puissance d'un CPU est le "PassMark®", c'est une société privée de développement de logiciel qui propose des notes sous forme de score pour chaque CPU, GPU, ... en fonction de sa puissance de calcul ! Il est donc simple de comparer 2 processeurs ! Exemple : Intel Core i3-4130 ( c'est le processeur qui équipe nos DS3615xs ), sont score est de 4796 ( on peut aussi voir d'autres informations comme le nombre de cœur physique / logique, son TDP, son score si on n'utilise qu'un seul coeur ( ici, 1961 ). Maintenant, nous allons le comparer a l'Intel Celeron J3355 ( c'est le processeur qui équipe nos DS218+ ), son score est de 1180 ! Soit 4 fois inférieur au processeur du DS3615xs ! On peut donc en conclure ( grossièrement ) que le processeur du DS3615xs est 4 fois plus puissant que le processeur du DS218+. Ok, j'ai compris, mais à quoi ça sert d'avoir un gros processeur dans un NAS ? Et c'est bien beau ton score mais 1000 ça représente quoi au final ? Dans un NAS à proprement parler, avoir un processeur puissant n'est pas forcément utile ( bien qu'en cas d'utilisation de RAID, cela permet que les reconstructions en cas de pertes d'un disque ne dur pas des jours ! ) mais maintenant les NAS ne servent plus uniquement à stocker des fichiers ! Ils servent également de petits serveur web, de serveurs SFTP, ... mais aussi principalement de serveur de fichiers multimédias ou pour la virtualisation, et c'est pour c'est deux dernières applications que la puissance du CPU va tout changer ! Pour une simple utilisation de stockage de fichiers, alors un processeur "bas de gamme" avec un score de 1000 points environ sera largement suffisant pour une expérience satisfaisante. ( À titre d'exemple, beaucoup sur le forum utilise Xpenology avec un AMD Turion II N54L ( installé dans les G7 N54L NHP ), c'est un processeur qui possède un score de 1300 points et est largement suffisant pour une utilisation classique d'un NAS. Malgré tout, si vous deviez partir sur du neuf, je vous conseillerai de prendre un processeur avec au moins 2500 points, afin de ne pas vous retrouver trop vite limiter au cas où vos besoins augmentent. Vous avez dit : Serveur multimédia ? Soit vous ne faite que de la lecture en local, et il faut que les clients qui lisent les vidéos sur le NAS soient compatibles ( h264, h265 , ... ) et dans ce cas cela ne demande aucune puissance au NAS, c'est-ce que je définis comme une utilisation en "Serveur multimédia simple" Ou alors votre NAS doit être puissant afin de pouvoir lui-même décoder le flux afin de le rendre compatible avec le client ( box tv, télévisons connecté, ... ). À titre d'exemple, le score "passmark" d'un CPU capable de décoder un flux 1080p sur Plex doit être supérieur à 2000 pour qu'il soit capable de le faire. Exemple : Si on cherche sur Google le passmark pour le G4400 ( https://www.google.com/search?q=G4400+passmark ), on peut voir qu'il a un score de 3500 points, il est donc capable de décoder un flux sans soucis, par contre, il ne sera pas capable de faire 2 flux en même temps, pour cela il aura fallu que son score soit supérieur à 4000 points ! Si vous souhaitez plus de détails : Voici les recommandations PassMark pour Plex suivant le type de transcodage : 4K HDR (50Mbps, 10-bit HEVC) file: 17000 PassMark score (being transcoded to 10Mbps 1080p) 4K SDR (40Mbps, 8-bit HEVC) file: 12000 PassMark score (being transcoded to 10Mbps 1080p) 1080p (10Mbps, H.264) file: 2000 PassMark score 720p (4Mbps, H.264) file: 1500 PassMark score Source : Plex Support 4/ Le choix de la RAM : Quelles quantités de RAM choisir ? Je répondrai a cette question : 4 Go. Ne sachant pas quoi choisir, javais moi-même choisi 8 Go pour "être sûr". Au final, pour une utilisation "classique" c'est beaucoup ! À titre d'exemple, avec une utilisation de mon NAS, principalement en serveur multimédia ( 3 à 4 transcodages simultanés, serveur web, ... ) je ne suis jamais au-dessus de 40% d'utilisation. De plus, la DDR4 ne se vend pas en barrette inférieur a 4 Go. Seules des applications bien spécifiques peuvent vous demander plus ( virtualisation par exemple ). La RAM est également un élément qui se rajoute facilement sur un serveur. Comment la choisir ? Il faut regarder ce que préconise le fabricant du processeur et le fabricant de la carte-mère. Nous allons prendre comme exemple, la carte-mère AsRock Z370M Pro4 et le CPU I5-8600k. Voici les recommandations pour le processeur : Et celle pour la carte-mère On trouve toujours ces informations dans les caractéristiques détaillées des constructeurs. Le constructeur du processeur préconise de la RAM DDR4@2666Mhz. Le constructeur de la carte-mère dit, que nous pouvons utiliser de la DDR4 parmi toutes ces fréquences : "4300+(OC)* / 4266(OC) / 4133(OC) / 4000(OC) / 3866(OC) / 3800(OC) / 3733(OC) / 3600(OC) / 3200(OC) / 2933(OC) / 2800(OC) / 2666 / 2400 / 2133" du moment que la mémoire est non-ECC ( nous reviendrons sur le non-ECC plus tard ). Pour moi, un NAS c'est fait pour être le plus fiable possible, j'élimine déjà toutes RAM dites "Overclocker". Il nous reste comme choix : 2666 / 2400 / 2133, on retrouve le 2666Mhz, ce que intel préconise mais aussi deux autres fréquences. N'importe quelles barrettes ayant ces fréquences seront compatibles ! Suite a venir.... RAM ECC, CAS ? Kezako ? 5/ Le choix de l'alimentation : C'est tout comme le reste un élément important de votre configuration ! Voici un lien pratique sur le site de MSI pour estimer la consommation max de votre configuration, en fonction de votre CPU, ... => MSI Power Supply Calculator BeQuiet le propose également ICI. Pour la suite je vais faire mon exemple avec le simulateur d'MSI. Le simulateur ( de MSI ) calcule large* mais permet d'avoir une bonne idée de ce que va consommer au maximum notre NAS maison. * Par exemple, le simulateur estime la conso max d'un DD à 25W, les Disques Durs spécials NAS ne dépassent jamais 15W et la plupart sont à moins de 10W. Comme pour le reste, je vais faire une estimation en me basant sur ma config personnelle, soit i5-8600K, 7 HDD, 1 carte PCIe, 3 ventilateurs. Le simulateur d'MSI m'estime 297 Watts max ( le simulateur de BeQuiet estime 223 Watts ). Il me faudra donc au minimum une alim de 300W. Dites-vous bien que ceci est une consommation maximale cela ne représente pas la consommation réel de votre NAS. et les certifications ? Ça sert a quoi ? La certification 80 PLUS sert à promouvoir le rendement de l'alimentation. Plus le grade est élevé ( Bronze, Silver, ... ), plus l'alimentation à un bon rendement ! Pour avoir une alimentation avec un bon rendement, il n'y a pas de secret, il faut de bons composants à l'intérieur ! C'est donc un gage de qualité de l'alimentation. Voici ce que nous dit la norme 80 PLUS : Wikipédia Par exemple une alim 80 PLUS Bronze a 20% de charge doit avoir au minimum 81% de rendement pour être certifié. Une 80 PLUS Titanium elle devrait avoir 94% de rendement ! Note : Choisir une alim de 1000W alors que son PC ne consomme que 200W n'est pas un problème en soi ( le coup de l'alim est juste plus élevé ), par contre pour le bien de votre alimentation, faite en sorte que votre alim ne tourne pas en dessous de 20% de charge. En dessous d'une certaine charge, certaines alims ont du mal a stabiliser leurs tensions ( d'ailleurs on peut voir que a 10% de charges, seules les "Titanium", soit les plus hauts de gamme, sont testées. ). Les différents format : ATX, SFX, .... Dans les alimentations, on trouve différents formats ATX, ITX, Mini-ITX , FlexATX ... Le choix du format d'alimentation se fait un fonction du boiter ! Par exemple, si le boitier "Antec DF500" m’intéresse. Dans les caractéristiques du boitier je voit tout de suite, qu'il me faut un alimentation ATX : Si c'est le boitier Antec ISK 310-150 qui m'interesse, alors je voit dans les caractéristiques qu'il me faut une alimentation Mini-ITX et que le boitier est déja fournis avec une alimentation de ce format et d'une puissance de 150W : Les alimentations les plus courante sont les ATX, ce sont les plus encombrante, mais également les moins chère au niveau prix/puissance. Vous avez dit, Modulaire ? A venir 6/ Le choix de l'onduleur : Il existe sur le marché 3 types d'onduleur ( UPS / Uninterruptible power supply ou en français Alimentation Sans Interruption ). Cet appareil va servir de relais en cas de coupure de courant, mais pas seulement ! Il va aussi protéger vos appareils contre les sur/sous tensions, les parasites, la foudre, ... C'est un élément indispensable pour être tranquille ! Et encore plus en cas de RAID, en cas de coupure brusque de courant, c'est tout le RAID qui peut être corrompu et même s'il est très rare de perdre ses données à cause de cela, cela engendre une reconstruction longue et éprouvante pour les disques dur ! Les trois type d'onduleur sont : Off-line / Line-Interactive / Online Le Off-Line est le moins performant, c'est un modèle à bannir ! D'un temps de réponse très long, il ne sera pas protégé efficacement votre installation. Garder votre argent. Le Line-Interactive est une amélioration du Off-Line, avec son régulateur de tension, il est capable de compenser les variations de tension, et aussi de réagir très vite ( 2ms, voier moins ). Le On-Line est la "Roll-Royce" des onduleurs, sur ce type d'onduleur, le matériel est en permanence alimentée par la batterie ( qui se recharge donc en même temps si le courant n'est pas coupé ). Le temps de réponse est donc de 0ms, et d'un courant parfait tout le temps, puisque fabriqué en permanence par l'onduleur, toutes perturbations extérieures ne viennent pas jusqu’au matériel. Source : LDLC Pour nous, le meilleur choix est le Line-Interactive, il protège efficacement tout en restant dans une gamme de prix raisonnable ( les On-Line étant réservés à un usage bien spécifique sont hors de prix ! ) Pour la puissance, tout dépend de votre configuration, un conseil, prévoyez large ! Un onduleur prévu trop juste s'use plus vite et ne permet pas de faire évoluer sa config ! Un onduleur de bonne qualité est un achat sur le long terme ! La puissance d'un onduleur est toujours donnée en VA, et en Watts. Nous allons nous intéresser aux Watts. ( attention également à vérifier qu'il possède les prises qui vous conviennent ) Exemple : Onduleur parafoudre APC Back-UPS Pro 550 C'est un onduleur de 550VA/330Watts, Line-Interactive comme le dit sa fiche technique. Notre config AsRock Z370M Pro 4 - i5-8600K, 4 x Disque Dur 8 To Red Pour une carte-mère, on estime 20W environ, le i5-8600K a un TDP de 65W, par abus de langage, nous estimerons que cela est sa consommation max*, pour un disque dur RED nous prendrons une consommation de 10W ( c'est un peu moins en réel pour les RED, par contre certains disques consomment environ 11/12W ). Donc si on résume : CM + CPU + DD = 20 + 65 + 4x 10 = 125W, sachant de l'alimentation va un peu consommer, les ventilo du boitier également mais tout cela est négligeable ! Notre onduleur de 330W est donc largement capable ! Note : Si vous souhaitez également brancher votre BOX, ... dessus, n'oublier pas de le prendre un compte ! Il faut compter environ 15W pour une LiveBox, Freebox, ... ( Voir ici ). 7/ Choisir ses disques dur : Les disques durs, sont'ils tous identiques ? Alors non, les disques dur ne sont pas tous identiques ! Dans les grandes lignes, il y a deux tailles : 3"5 et 2"5 et 2 vitesses 5400 ( ou 5900 ) et 7200. Les tailles 2"5 sont souvent utilisé au pc portable, dans un pc "fixe" ou un serveur on utilise des 3"5 qui ont un prix au To bien meilleur ! Dans les vitesses, les disques tournant plus vite ( 7200rpm ) sont les plus performant, les 5400rpm étant ( toujours en règle général ) moins performant, mais aussi moins bruyant. Et les disque dit NAS alors ? Western Digital ( WD ), et Seagate font des disques spécial NAS ( WD Red et Seagate IronWolf ). Chez WD : Leur gamme NAS s’appelle RED, il y a les RED et les RED Pro. Les RED sont des disques 5400rpm. Garantie 3 ans Les RED Pro sont des disques 7200rpm. Garantie 5 ans Chez Seagate : ..... A VENIR Mais alors je ne peut pas mettre un disque "normal" ? Si bien sur, aucun soucis, mais bien que je n'est pas d'expérience personnel sur l'utilisation de disque classique dans un NAS, vous risquez de voir vos disques mourir plus vite qu'un disque NAS. Les disques de PC n'étant pas conçu pour travailler H24. 8/ Les cartes d'extension PCIe : Les cartes PCIe sont un moyen simple est rapide d'ajouter des ports SATA sur un ordinateur ! Les cartes "classiques" possèdent 2 ou 4 ports SATA ! Les performances sont-elles identiques ? Avant de parler des performances des cartes d'extension, nous allons parler des performances max. d'un port SATA directement connecté à la carte-mère ! Source : Wikipédia À l'heure actuelle, toutes les nouvelles cartes-mères sont équipés de ports SATA 3 ou SATA 6Gbit/s ou encore SATA 600, a chaque fois cela désigne la même chose. La vitesse max théorique est de 6 Gbit/s soit 768 Mo/s max. Idem pour les cartes d'extension, elles se doivent d'être équipé de ports SATA 3. Maintenant, revenons à nos moutons ! Comment connaitre le débit max de sa carte d'extension ? Pour cela, nous allons nous aider de ce tableau : Source : Wikipédia Exemple 1 : Et comme exemple, nous allons vouloir connaitre le débit max possible avec cette carte d'extension, vendu 41€ chez LDLC. 2 choses à connaitre, la version du Bus utilisé et la largeur de celui-ci. Dans l'exemple ci-dessus on peut lire : "Conforme aux bus PCI Express 2.0 5GBPS" et "PCI Express 1x". Si on regarde le tableau, qu'on regarde a la colonne PCIe 2.0, le débit par ligne est de 500 Mo/s. Notre carte ne possédant qu'une seule ligne ( PCI Express 1x ), donc la vitesse de la carte ne pourra pas dépasser 500 Mo/s. ( et ceux pour les deux ports SATA présent ! ). Les deux ports SATA devront se partager 500Mo/s ( et non 500 Mo/s pour chaque port ! ). Exemple 2 : Ici une autre carte vendue un peu plus cher ( 50€ ), toujours sur LDLC et qui possède également 2 ports SATA. On peut lire : PCI Express 2.0 2x, c'est donc du PCIe 2.0, avec une largeur de bus de 2 lignes ( 2x ). Si on regarde la colonne PCIe 2.x, on peut voir un débit par ligne de 500 Mo/s. Notre carte possédant 2 lignes, alors le débit théorique sera de 2x 500Mo/s soit 1000 Mo/s ! Par rapport a l’exemple précédent, les 2 ports SATA n'auront pas a se partager 500 Mo/s mais le double, soit 1000 Mo/s. Un gain non négligeable pour quelques euros de plus. Conclusion : Pour une utilisation "classique", sachant qu'un disque dur pour NAS a un débit de lecture d'environ 150Mo/s, la 1ère carte est largement suffisante ! Même avec 2 disques ( 2x 150Mo/s => 300Mo/s ), la carte ne saturera pas. Là ou le choix d'une carte plus performante peut être intéressant, c'est en cas de RAID, d'une carte PCI avec plus de 2 ports SATA, ou dans le choix de SSD, où dans ce cas les vitesses de lecture et d'écriture peuvent être grandement augmentées. et ou votre carte d'extension peut être un "frein" aux performances. Je rajouterai aussi une info importante et bonne à savoir, une carte PCIe 1x ou 2x , .. peut-être utilisée dans un port PCIe 16x sans soucis, seulement la vitesse de transfert sera dépendante de la carte et non du port.. Par contre l'inverse n'est pas possible, par exemple il n'est pas possible d'utiliser une carte PCIe 8x dans un port PCIe 4x . Note : Afin de ne pas polluer le topic, merci de me signaler les fautes grammaires / orthographes / ... par MP 😘
  32. 3 points
    Hi, I removed the faulty i915 drivers from extra, you can download and test it here. hw transcoding is working but performance is low on both videostation and plex but I don't think is related to the loader. on ASRock j4205-ITX you have to unplug any monitor before using hw transcoding otherwise the system will reboot, this one might be due to /dev/dri permissions or the DP to hdmi coverter on this board. reboot/shutdown is working properly again. I recommend doing a clean install, formatting the hard drive before testing. You can test disabling video outputs in the grub, for me it didn't install properly. video=eDP:d video=DP-1:d video=HDMI-A-1:d video=HDMI-A-2:d root@DS918:~# ls /dev/dri card0 controlD64 renderD128 root@DS918:~# cat /sys/kernel/debug/dri/0/i915_frequency_info PM IER=0x00000070 IMR=0xffffff8f ISR=0x00000000 IIR=0x00000000, MASK=0x00003fae pm_intr_keep: 0x80000000 GT_PERF_STATUS: 0x006030cb Render p-state ratio: 48 Render p-state VID: 203 Render p-state limit: 0 RPSTAT1: 0x12000030 RPMODECTL: 0x00000d92 RPINCLIMIT: 0x000027d8 RPDECLIMIT: 0x00005a00 RPNSWREQ: 800MHz CAGF: 600MHz RP CUR UP EI: 3192 (2660us) RP CUR UP: 477 (397us) RP PREV UP: 0 (0us) Up threshold: 85% RP CUR DOWN EI: 5109 (4257us) RP CUR DOWN: 482 (401us) RP PREV DOWN: 0 (0us) Down threshold: 60% Lowest (RPN) frequency: 100MHz Nominal (RP1) frequency: 250MHz Max non-overclocked (RP0) frequency: 800MHz Max overclocked frequency: 800MHz Current freq: 800 MHz Actual freq: 600 MHz Idle freq: 100 MHz Min freq: 100 MHz Boost freq: 800 MHz Max freq: 800 MHz efficient (RPe) frequency: 250 MHz Current CD clock frequency: 624000 kHz Max CD clock frequency: 624000 kHz Max pixel clock frequency: 624000 kHz [ 127.551937] ACPI: Power Button [PWRB] [ 127.601681] Linux agpgart interface v0.103 [ 127.674041] [drm] Initialized drm 1.1.0 20060810 [ 127.809306] [drm] Memory usable by graphics device = 4096M [ 127.882071] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 127.882075] [drm] Driver supports precise vblank timestamp query. [ 127.884752] [drm] Finished loading i915/bxt_dmc_ver1_07.bin (v1.7) [ 127.885302] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 128.859977] [drm] failed to retrieve link info, disabling eDP [ 128.861274] [drm] GuC firmware load skipped [ 128.865805] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 128.866518] acpi device:10: registered as cooling_device4 [ 128.866603] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input1 [ 128.866659] [drm] Initialized i915 1.6.0 20160919 for 0000:00:02.0 on minor 0 [ 128.882007] i915 0000:00:02.0: No connectors reported connected with modes [ 128.882013] [drm] Cannot find any crtc or sizes - going 1024x768 [ 128.882929] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 128.938416] Btrfs loaded, crc32c=crc32c-intel
  33. 3 points
    Hey there, this has been asked a couple of times but the only answers (if someone answered at all) were like, "Why bother? It works." In the picture above, both installations work. My inner monk (as well as my boss) prefer the right cabinet, however. In the following example I'll refer to a 10-bay system, if your setup is different, you can easily edit the numbers. I assume, you have successfully installed XPEnology on your box, following Polanskiman's tutorial. If you encountered any problems with drives not being recognized, or displayed as eSATA, etc. you checked Hedii's guide, as well. Still, your drives show up like this, maybe because your chipset would support 6 drives but your mainboard only offers 4 connectors. Drives 1,3,5,6 are connected to the mainboard, drives 7-10 to an additional 4-port controller, drives 11 and 12 to another 2-port controller. Drives 2 and 4 look like this in your dmesg: [ 1.835796] ata1: SATA max UDMA/133 abar m2048@0xfe525000 port 0xfe525100 irq 47 [ 1.835802] ata2: DUMMY [ 1.835806] ata3: SATA max UDMA/133 abar m2048@0xfe525000 port 0xfe525200 irq 47 [ 1.835807] ata4: DUMMY [ 1.835812] ata5: SATA max UDMA/133 abar m2048@0xfe525000 port 0xfe525300 irq 47 [ 1.835813] ata6: SATA max UDMA/133 abar m2048@0xfe525000 port 0xfe525400 irq 47 Playing around with internalportcfg (Hedii's guide) did not help you, getting rid of these "DUMMY" ports. Luckily Jun's loader has a feature called "sata_remap", mentioned here and here, that - well - does what it says. To fill the gaps, you can remap the drives from your 2-port controller. Reboot and press "C" in the GRUB menu. (See Polanskiman's guide "Step 7" and "Note 4" if you need help). At the command line enter: append "sata_remap=10>1:11>3:1>10:3>11" Be aware, that counting starts at 0, here. 10>1 will remap drive 11 to 2, 11>3 will remap drive 12 to 4, etc. After the next reboot, it will look like this: As you can see, the drives are now numbered sequentially from 1 to 10 with the two DUMMYs on ports 11 and 12. Now it's easy to hide them. Like in Hedii's guide open an SSH connection to your NAS and edit as follows: # first file to modify vi /etc/synoinfo.conf # second file to modify vi /etc.defaults/synoinfo.conf # In each file look for the line maxdisks="12" # and change it to maxdisks="10" Reboot and you finally have a 10-bay box displaying 10 sequentially numbered drives: Hope, this will help one or the other. Best Regards, The_Mole
  34. 3 points
  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
    OVAs for DSM 6.2.1-23824 Update 4 • DS918+ (requires Haswell/Braswell or newer CPU) • VM HW Level 10 (ESXi 5.5 or newer) • PVSCSI • VMXNET3 https://mega.nz/#!slFUCIwT!QHzujgbJeGtMKE5W2pvg8UoK7T6TputqQwFZHuNhxmY • DS3617XS (requires hardware that's supported by default DSM) • VM HW Level 10 (ESXi 5.5 or newer) • SATA • E1000E https://mega.nz/#!5wlSQCLK!WHVVNloohedGa_nAB6pgPMvC-twWlR32arZ0JqaFMvM VMware Tools: https://mega.nz/#!Q1FGyAbY!lmrry2WXNd7Lp7AtSsrduPpnlWPzEpPV9L96jrZn6HQ Deploy OVF, add disk(s) or passthrough a controller, find with Synology Assist and click install. Optionally if you've got an ESXi enterprise license you can change the serial port to network, server telnet://:1024 and have remote telnet access. If you want to passthrough a Intel Controller that doesn't contain ESXi boot or a datastore install this VIB and restart: https://mega.nz/#!p0dAhYYb!7AWamOXE6y0z-PBlW4VqtS1gYNuw-uG-dKYTuyI5tQM By default it will work with any combination of one or two 2, 4, 6 and 8 port SATA/SAS controllers. Only when using two 8+ port SAS controllers or one 12+ port SAS/SATA, or more than two extra (so more than three if you count the SATA controller for synoboot) controller changes to SasIdxMap/SataPortMap/DiskIdxMap/MaxDisks are required.
  37. 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.
  38. 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.
  39. 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.
  40. 3 points
    Как и обещал 8.1.3-5473 https://mega.nz/#!SkkwkABT!CtzlniTwXliXgFO9PhYesAoTtQ6fSF7oM_U__uLTgYw
  41. 3 points
    Может пригодится кому. Я долго бодался с j3455n-d3h. С загрузчиком 1.04b 918+ скорость копирования была порядка 30 Мбайт/c с просадками до 0. Вопрос решился установкой C-States = disabled в BIOS. Теперь +-100 стабильно по SMB.
  42. 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.
  43. 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
  44. 3 points
    Are you planning to update with the 1.04b links? Cheers!
  45. 3 points
    Да, все верно, только переустановкой DSM, финт с миграциями между разными версиями тоже не прокатывает.
  46. 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
  47. 3 points
    - Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2-23739U2 - Loader version and model: Jun v1.04b - DS918 - Using custom extra.lzma: NO - Installation type: BAREMETAL - J4105-ITX - Additional comments: tested on ESXi first, upgrading from 1.03a loader to 1.04b. then upgraded DSM to 6.2.1 and validated both vmxnet3 and e1000 VLAN drivers baremetal upgrade to 6.2.1 is working with Realtek NIC also /dev/dri is active for the first time on baremetal J4105 (Gemini Lake)
  48. 3 points
  49. 3 points
    11.06.18 как поставил 918 6.2 так до сих пор ВСЁ работает, железо 3150 скорость копирования как была раньше 1 гиг так и осталась вы просто меньше читайте этот форум а больше пробуйте самостоятельно здесь тусуются те у кого ничего не работает большинство как поставили xpenology так больше сюда и не заглядывают, кроме как только узнать о выходе нового релиза и не более
  50. 3 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