Leaderboard


Popular Content

Showing content with the highest reputation since 02/10/2019 in all areas

  1. 11 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
  2. 11 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, инструкция в следующем) Просьба ссылки тут не обсуждать, добавляйте свои, если посчитаете полезным.
  3. 9 points
    Bonjour, voici ma petite contribution après pas mal de déboire pour installer ce dernier opus de Synology. La version 6.2.2-24922 U2 sur un Proliant G7 - N54L. Après une première tentative d'ugrade depuis la version DSM 6.1.7-15284 vers la version 6.2.2-24922, la carte réseau Interne de ce serveur n'étant pas prise en charge j'ai dû revenir sur l'ancienne version du DSM, le 6.1.7. Sommaire: Description du serveur Matériel nécessaire à l'upgrade BIOS Moddé Loader et dsm (procédure pour grub.conf, flash, installation) 1. Pour la Configuration du Loader et la création de la clé USB 2. Montage du Loader et modification du fichier grub.conf 3. Gravure de l'image du Laoder sur la clé USB 4. Paramétrage du syno via SSH ou Winscp et Customizing A/ - Paramétrer la possibilité de se connecter directement en root avec putty ou Winscp pour plus de facilité quant aux futures modifications sur les fichiers système du DSM B/ - Paramétrer la possibilité de monter des volumes SHR / SHR2 C/ - Paramétrer le WOL dans le fichier synoinfo.conf D/ - Uploader le script "S99zzz_Shitdown.sh" E/ - Utilisation du bouton de façade du serveur pour mettre en veille proprement le serveur 5. Création Bond Paramétrage complet du Bios, test avant Flash en version 41-2013 mod Kamzata (vs 041- 2011 mod TheBay) Copies d'écran du paramétrage du BIOS pour fonctionnement shutdown, mise en veille et WOL Pour cette Upgrade : Matériel à ma disposition: - HP Proliant G7 N54L - AMD Turion II Neo N54L Dual-Core Processor, cadencé à 2200Mhz - 2Go de RAM ECC fournit avec ce serveur lors de son achat il y a 5 ans. Matériel Nécessaire: - Une carte réseau PCIe compatible, avec NIC Intel (peut-être meilleurs pour les compatibilité futures). Type Intel "i350-T2" ou "HP NC360T". Ces 2 cartes sont utilisées par beaucoup. Cartes sur Ebay - J'en profite pour acheter 4Go de Ram supplémentaire, ca lui fera du bien et 2 HDD de 6To pour remplacer deux HDD de 2To Coté BIOS: Celui de 2011 (V041 - 2011): TheBay_Microserver_Bios_041.rar Le Bios Mod: o41072911mod.rom Celui de 2013 (V041 - 2013): Kamzata Modded BIOS - run HPQUSB.rar Le Bios Mod: O41100113mod.rom Ne sachant plus si les Bios dans les fichiers RAR sont déjà customisés, je post en même temps les customs ROM qui doivent écraser ceux mis sur la clé USB lors de l'utilisaton de l'éxécutable "HPQUSB" Il suffit de supprimer celui présent sur la clé, de copier/coller le fichier mod.rom et de le renommer. Vous pouvez suivre ce Tuto qui est trés explicite : How to flash Bios HP Proliant (c'est le même Bios pour les 3 servers N36L; N40L et N54L) Coté Loader et DSM: il y a la liste de tous les Loaders ici j'utilise le Synoboot_3615 pour ma config. Le Fichier .pat du DSM 6.2.2-24922 c'est ici Ou si vous souhaitez la liste des DSM disponible sur le serveur de synology : c'est par ici On passe aux Choses sérieuses: Paramétrage complet du Bios et Photos PHOTOS A VENIR....................
  4. 7 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 (for DS918+) - v1.04b ---Beginning of addition by polanskiman--- link https://mega.nz/#!OV4gVKyZ!dCgfXx1bgAOyvbFwFiov3s7RSNoFuqnAcNmSllLoUiw (for DS3615xs) - v1.03b link https://mega.nz/#!zcogjaDT!qIEazI49daggE2odvSwazn3VqBc_wv0zAvab6m6kHbA (for DS3617xs) - v1.03b Please read this topic to know what loader to chose: ---End of addition by polanskiman---
  5. 6 points
    11 - Why all the issues with recent versions of DSM (6.2.x), and what options are available to mitigate them? Jun's loader attempts to fool the Synology code into thinking that the user hardware is actually Synology's platform hardware. How this is technically accomplished is a mystery to most everyone except Jun, but regardless of how it works, it has an impact on the DSM runtime environment. Some issues are fairly innocuous (spurious errors in the system logs, inability to leverage hardware features like CPU turbo and hibernation, etc.) but others may cause instability, driver and kernel crashes. By far, the most stable combination (meaning, compatibility with the largest inventory of hardware) is Jun's loader 1.02b and DSM 6.1.x. Jun has stated that the target platform for 1.02b was DS3615, and DS3617 was incidentally compatible enough to use the same loader. However, there are kernel crashes with DS3617 on certain combinations of hardware. There is otherwise no functional difference between DS3615 and DS3617, which is why DS3615 is recommended. DSM 6.2 introduced new, more stringent Synology hardware checks and Jun came up with another approach to bypass them. While the loaders do work with optimal hardware, on many systems the 6.2 loaders often result in kernel loadable module crashes and kernel panics. Many have also noted substantially poorer disk I/O performance compared with prior versions. DSM's embedded NIC drivers have been inventoried and documented, but much of that catalogue is useless as the 1.03b loader crashes all but a select few drivers on DSM 6.2.1 and later. And, users with new hardware often find that those few functional network drivers don't support the newest revisions of their on-board silicon. Similarly, the 1.04b loader explicitly adds support for the Intel Graphics (i915) driver, but upgrading to 6.2.2 causes it to crash on some revisions of the Intel Graphics hardware (such as Apollo Lake J-series systems). A very large number of forum posts can be attributed to users seeking to install DSM 6.2.x and encountering one of these two significant problems. ESXi or another virtualization platform is probably the best strategy to mitigate hardware support limitations on XPEnology and DSM 6.2.x. If your goal is to deploy the latest DSM versions and keep pace with Synology patches, you would be wisely advised not to deploy a baremetal XPEnology installation at this time. Unfortunately, this is an obstacle to those who want a baremetal solution to enable hardware accelerated video encoding support within DSM. It should be noted that many XPEnology super-users, forum admins and devs continue to use the stalwart combination of ESXi, Jun 1.02b and DS3615 DSM 6.1.7 for mission critical work, and have no intention of upgrading. That said, there really isn't much of a reason to stay current once you have a functioning system. DSM 7.0 is imminent and the current loaders are virtually guaranteed not to work with it. And each new 6.2 point release is objectively bringing new compatibility issues and crashes, for little or no functional/incremental benefit.
  6. 6 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"
  7. 5 points
    Обнаружил и испытал beta пакет Teamviewer, может кому пригодится для входа в DSM из-за NAT. P.S. Для того, чтобы подключиться нужно создать учетку TV и привязать к ней DSM. P.P.S. Если включить терминальный режим, то можно войти в консоль...
  8. 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"
  9. 4 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.
  10. 4 points
    Dear Xpenology forum members, I'm come back!!!! I have been very busy at work. So I could not cope with the changed code because I could not upgrade DSM. But! I have recently successfully migrationed the "ivybridge" of existing my systems to "haswell". I also added an additional LAN card. The latest version of "DSM 6.2.2-24922 Update 2" is now available for the DS3615xs, 918+ and other versions. I'll be updating and distributing the "ch_cpuinfo" tool soon so that it will work with the latest version. I'm sorry to have kept you waiting so long, and thank you for waiting. See you soon. Dear @Polanskiman , Thank you for your patience and care for the topic I could not manage. I'll update soon. Dear @gericb , Thank you for your concern and supportive mentality
  11. 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 !
  12. 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.
  13. 4 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
  14. 4 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. Просьба к админам прибить тему в шапке и дать мне доступ на редактирование первого поста этой темы, буду добавлять по мере поступления вопросов, ибо задолбали оленеводы, которые задают вопросы по установке, во всех подряд темах.
  15. 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 ##################
  16. 3 points
    Hi, Since I was not yet able to build a working cpufreq_ondemand.ko to allow automatic frequency scaling for JUN's loader 1.04b (DSM 6.2.2-24922 Update 2), i've written this script to allow dynamic CPU frequency scaling. It's hosted here : https://github.com/Trauma/cpufreq-userspace-scaler # cpufreq-userspace-scaler ##### Cpu frequency scaling script for cpufreq userspace governor ## If you're missing ondemand or conservative governors, this script is for you. This script is scaling cpu frequency according to current average load. You can set 3 frequency steps : low, mid, high. This 3 thresholds will automatically set cpu frequency accordingly : - the `lowload` threshold will set the cpu to his minimal frequency, unless you force it to `scalingminfreq` - the `midload` threshold will set the cpu to approximate mid range cpu frequency - the `highload` threshold will set the cpu to his maximal frequency, unless you force it to `scalingmaxfreq` If you set `scalingmaxfreq` and/or `scalingminfreq` the cpu will never override those values. ### Usage : ### Parameters : Variable name | Default | Type | Comments ----------------|---------|-----------------------------|----------- lowload | 050 | integer between 000 and 999 | 050 = load average : 0.50 midload | 065 | integer between 000 and 999 | 065 = load average : 0.65 highload | 085 | integer between 000 and 999 | 085 = load average : 0.85 scalingminfreq | auto | integer in hertz | 800000 = 800 Mhz scalingmaxfreq | auto | integer in hertz | 2500000 = 2,5 Ghz ### Default commande line : `./scaling.sh &` ### Custom command line example : `lowload=100 highload=200 scalingmaxfreq=2000000 scalingminfreq=1500000 ./scaling.sh &` Enjoy.
  17. 3 points
    GOT IT !!!... I've succesfully installed DSM 6.2.2-24922 update 2 to my Supermicro Server !!!.. After a lot of fails with installing for 916+ or 918+ i tried the DS3615xs Version Took the 1.02 MBR Loader of Genesys and replaced the files with thes from 1.03b Loader… and it worked ! i'am happy thanks to all for your support and by now i am really more experienced !.. have a nice day..
  18. 3 points
    The real answer is VMware or other hypervisor outside of XPenology. But while you are contemplating that, please read this and this.
  19. 3 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)
  20. 3 points
    Установил с нуля, восстановил данные, всё прекрасно работает и ничего не пропало. Спасибо Olegin_у и XPEH_у за помощь и уделённое мне внимание 😉
  21. 3 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 DS918: DS918 Reference Hardware: CPU: Intel J3455 (Apollo Lake) GPU: Intel HD Graphics 500/505 Chipset: Intel SOC 2x1Gb Ethernet: ??? SATA: 88SE9125 PCIe SATA 6.0 Gb/s controller With even this information, we can make some good guesses on what hardware might be supported. Wouldn't it be great if we knew ALL the different drivers that are natively supported? Unfortunately this is a fairly difficult process if you are not a Linux guru (and a bit laborious even if you are). There are "user-reported" hardware compatibility threads out there, but many don't understand that those reports are both DSM version and platform specific. Furthermore, with the way hardware manufacturers reissue hardware with the same name but new PCI device number (such as the Intel PHYs on desktop motherboards), often not enough information is reported to confirm whether a specific piece of hardware is suitable for use. If you aren't sure if your hardware is supported, this post and the complementary DS3615 driver guide aims to help you. Download the attached Excel spreadsheet to see key driver support in the DS918 6.2.1 Synology custom kernel, and via loadable modules supplied with DSM. Hopefully it will help you select the best DSM platform for your purposes, and possibly inform your hardware purchases. DSM 6.2.1 DS918 V1.0 2018-Feb-03.xls
  22. 3 points
    Hello @FOXBI. Is it possible to update your tool so that it is fully functional with the latest release of DSM 6.2? Thanks.
  23. 3 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
  24. 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.
  25. 3 points
    Биос был 1.4, но я вернулся на 1.3 (кажется она стабильнее) кроме HPET, выключил все что можно (Disable - C-states, SpeedStep, C1E, Suspend to ram). VT-d должна быть включена, влияет на DRM. USB legacy - Enable. CSM - Enable (PXE not used, Storage - Legacy only, Video not used Это важно) После перезагрузки, в BIOS не зайти. Поможет только перемычка ClearCMOS Power - Sport ShareMemory - 64Mb SuperIO - Disable Trysted - Disable IntelPlatformTryst - Disable Загружаться с флэшки в режиме Legacy (Выбрать в ручную не UEFI загрузчик) Почему в не UEFI? После тестов и сравнения логов с EFI и Legacy, было обнаружено что мать не правильно загружается в EFI, дисковая система начинает тормозить, в логах ошибки по RAID. Происходит рассинхронизация. Проблема в матери. Еще заметил что на встроенной сетевой карте сервак загружается минуту дольше чем на внешней Intel. И последнее предположение что транскодинг заработал после миграции с 916 на 918. Так как пробовал устанавливать на отдельный жестки начисто, в VS фризы как у всех. Скорее всего проблема в конфигах 918. А после миграции какая то часть остается от 916. Скрещивание бульдога с носорогом. Extra.lzma записывал от x01015918 на флэшку перед миграцией. После миграции папка /dev/dri появилась и VideoStation и Plex заработали. И на счет HPET, ее я ни разу не выключал. Теперь на нее думаю. Будет время свободное, выключу попробую. Это надо заново весь биос настраивать, после сброса.
  26. 3 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
  27. 2 points
    I finally made the jump for the update from 6.2.1-23824 Update 6 to 6.2.2-24922 Update 2, i only use a custom extra.lzma without i915 drivers, and everything work nicely, onboard Lan, HW transcode, i even made some test with geekbench to find out if the cpu burst work and its a big YES ! With the turbo states OFF in bios > https://browser.geekbench.com/v4/cpu/14202331 With the turbo states ON in bios > https://browser.geekbench.com/v4/cpu/14202575 *I made 2 bench of both turbo state to be sure. For the custom extra you can find it with instruction in this topic >
  28. 2 points
    For those who need a MBR Bootloader for DSM 6.2 i've uploaded it here, if someone will give them a Chance... i've successfully installed this on an Supermicro X7DBP-i with Intel Blackford 5000P Chipset. It is a loader for the DSM6.2-23739.pat and can be directly upgraded to 6.2.2-24922 Update 2.. http://ul.to/zg58eusm this loader is based on Jun's Mod of Genesys Loader and done with their help!... Thanks a lot..
  29. 2 points
    Bon j'ai fini au bout de 4h d'acharnement à réparer le système de fichiers mais au détriment de 2 services celui de SurveillanceStation et CloudSync. Un reparamétrage des deux et c'est revenu. Pfff quelle histoire ! Je pense que le pb ne venait pas de Plex, mais bien d'un défaut d'inodes qui devait exister depuis longtemps et que j'ai mis en évidence avec ces 2 commandes : find /volume2/photo -type d -exec chmod 775 {} ; find /volume2/photo -type f -exec chmod 664 {} ; Heureusement pour moi, j'ai réussi démonter le volume proprement pour faire un checkdisk et réparer ce qui n'allait pas ! merci google^^ Pour info voici les commandes qui m'ont sauvées la vie en root exclusivement et après avoir éteint tous services sauf ssh évidement : syno_poweroff_task -d vgchange -ay fsck.ext4 -yvf -C 0 /dev/vg1/volume2
  30. 2 points
    ------------------------------------- ESXi 6.x ------------------------------------- Voici les liens pour importer une VM directement dans ESXi 6.x via le client Web (et non vSphere Client) : DSM 6.2.2 (Loader 1.03b) Penser à ajouter vos disques de données après l'import et les rattacher au contrôleur SATA 1 (Mode : Indépendant - Persistant). Le synoboot.vmdk, lui, doit rester sur le contrôleur SATA 0 : basé sur ds3615xs: https://file.niko44.fr/sharing/RpXCHxwV4 basé sur ds3617xs: https://file.niko44.fr/sharing/J4WTEjj2B DSM 6.2.2 (Loader 1.04b) Incompatible chez moi (sur HP N54L), mais @Sabrina a réussi sur ESXI 6.7 : https://drive.google.com/open?id=1yGKoTCtoM60KfG29b6LlCYRHcfe_zRzU Dans le cas où vous rencontrez des problèmes, je vous recommande d'ajouter un port série avec une sortie dans un fichier pour pouvoir voir les logs du loader lors du boot de la VM. Puis déposer ce fichier dans le forum afin que la communauté puisse vous aider. ⚠️ Si vous utilisez déjà une VM DSM, il faut l'éteindre sinon les deux partagerons la même IP ; à défaut il faudra prévoir de modifier le fichier grub.conf. ⚠️ La virtualisation de DSM implique de ne pas avoir les infos S.M.A.R.T des disques durs... ⚠️ Pensez par la suite à installer le paquet Open-vm-tools pour une meilleure prise en charge par ESXi : https://spk.4sag.ru/ ------------------------------------- Virtual Machine Manager ------------------------------------- Thanks to @Sabrina DSM 6.2 basé sur ds3615xs : https://drive.google.com/open?id=1evd7W1AUBa3P9tukbDvjobGvdXdcrx5g Importer la machine au format .ova (Xpenology-Ds3615x-6.2.ova) Vous pouvez modifier le HDD à votre guise mais ne pas modifier le premier HDD qui est le boot Suivre les capture d'écran suivantes : ------------------------------------- VMWare WorkStation ou VMWare Fusion ------------------------------------------- Thanks to @Sabrina DSM 6.2 basé sur ds3615xs : https://drive.google.com/open?id=15tyMTku-mJIJQZHLzbIqSmBmp8nd7Ooo Importer le fichier Xpenology.ovf avec Vmware Fusion ou autre WorkStation : Il se peut qu'il vous mette une erreur mais il faut juste réessayer : Vous voyez le détail de la machine virtuel et vous allez en bas sur Personnaliser les réglages : Sur le panneau des réglages, vous choisissez le nombre de processeur et ram que vous voulez mettre Dans la partie réseau : Détection Automatique : Sur le Second HDD (Xpenology-disk2.vmdk) vous le redimensionner à votre guise et si vous voulez ajouter un HDD, vous pouvez mais il ne faudra pas oublier de le mettre en Sata : Vous devez faire en sorte de booter sur le premier HDD (Xpenology-disk1.vmdk) : Une fois démarrer vous chercher sur votre réseau l'ip de la machine est vous tomberez directement sur Création de votre compte administrateur :
  31. 2 points
    Good start in a forum... It has been 22 hours since you opened your thread and there’s no need to push and ask with „No one?“. Beside that you should read the Faq and forum rules. Aaah yes. We all know this PC/board... like thousands of other models. Do you think that users start searching the web for this to get informations about the chipset, CPU, NIC, etc.? Post as much details as possible about your system. We don’t have crystal balls nor do many of us have the will to do your job (searching the web for further and detailed system specs). Provide us with more informations and I think that someone will answer you soon. Cheers
  32. 2 points
    You might want to read the FAQs
  33. 2 points
    Я тут писал писал, просил просил подсказать как настроить. Все просто пишут всякий флуд и в итоге сам все настроил.
  34. 2 points
    no problem BEFORE: -I installed ESXi in the internal (32Gb) USB stick (I use an external bootable 8Gb USB stick with ESXi ISO injected with Realtek network driver) -test that the ESXi system boot correctly (without a Datastore) NOW: 1.boot GPARTED and create an unformatted partition in the free space of USB stick (I leave some free space between the last used partition and the new one, but i don't know if it is important) 2.using the terminal in GPARTED set the type of partition (if the new partition is /dev/sdb2): #gdisk /dev/sdb {press t} {select partition 2} {type fb00} {press w} {confirm with Y} 3.now change the partition number (from 2 to 10) to be sure that it will not be touch in future update #sfdisk -d /dev/sdb > esxi2.txt edit the text file and change /dev/sdb2 : start= 13500416, size= 16775168, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=50D5FE33-CDC7-413B-AF11-C32BF433AA85 to /dev/sdb10 : start= 13500416, size= 16775168, type=0FC63DAF-8483-4772-8E79-3D69D8477DE4, uuid=50D5FE33-CDC7-413B-AF11-C32BF433AA85 and move the line on the end of text file Then write back the partition table #sfdisk --force /dev/sdb < esxi2.txt 4.boot ESXi system (from modified USB stick). From terminal (I use SSH): check partition #partedUtil getptbl /dev/disks/mpx.vmhba32:C0:T0:L0 and format it #vmkfstools -C vmfs6 -S USB-Stick /dev/disks/mpx.vmhba32:C0:T0:L0:10 THAT's ALL Now you see in DataStore a new DataStore "USB-Stick" and you can create folder, upload file, create VM, etc... WITHOUT change "usbarbitrator" SO you can attach USB HDD on external port to pass the USB DEVICE to VM
  35. 2 points
    Einfachste Vorgehensweise: - System herunterfahren und alle HDDs abklemmen - eine einzelne leere HDD anschließen - System wieder hochfahren und aktuelles DSM installieren - testen, ob alles funktioniert; besonders die Netzwerkverbindung - System wieder herunterfahren, alte HDDs dran und dann upgraden
  36. 2 points
    Не спешите откатываться на 6.2.1, у меня тоже сперва после обновления на 6.2.2-24922 не виделась сеть, не пинговалось и прочее, уже тоже думал откатываться, либо искать сетевуху intel, но потом увидел, что здесь пишут, что нужно встроенную видеокарту выключить в биосе, слабо верилось, что это поможет, но помогло, нас без проблем сразу запинговался, пустил в web интерфейс и начал обновлять пакеты приложений. Теперь изображения при подключении монитора нет, в cli загрузчика зайти или reinstall сделать нет возможности, но зато последняя версия установлена.
  37. 2 points
    - Outcome of the update: FAILED (if no monitor connected) - DSM version prior to update: DSM 6.2.1-23824U6 - Loader version and model: Jun v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - ASRock J4105-ITX - Additional comments: I should say the 6.2.2 is working only if my VGA monitor is connected (regardless if it's power on/off). No HW transcoding available in 6.2.2 in this case. If moditor is disconnected, DSM won't start.
  38. 2 points
    Please see this for loaders vs. versions. 6.2.x has a number of hardware constraints on it, so you may need to pick your loader and platform carefully, referencing your hardware.
  39. 2 points
    Solved it Enabled SSH in the control panel Connect via SSH using putty edited both etc/synoinfo.conf and etc.defaults/synoinfo.conf with the following in vi: maxdisks=22 esataportcfg=0x0 usbportcfg=0x‭7FC00000‬ internalportcfg=‭0x3FFFFF‬ rebooted, and all disks appear fine Might be handy for anyone else having this issue. Cheers,
  40. 2 points
    Que dire à ta question.... : http://www.reseau-des-marabouts.com/
  41. 2 points
    On ne peut pas avoir le beurre, l'argent du beurre et c** de la crémière pour 0€^^ 😂
  42. 2 points
    This piece of kit is worth bout 700 bucks due to supply/demand right now, but I got one for 500. I was eager to put my janky Xpenology to bed, but the UI is so.... sluggish compared to my Xpenology with a 10 year old desktop processor. I'm really considering selling it and get a few bucks out of the deal. At least with my Xpenology, I can upgrade to 10 gb networking relatively cheaply. I love the Synology OS, but damn... their hardware sucks.
  43. 2 points
    Merci @Sabrina Je l'ai ajouté au sujet principal
  44. 2 points
    В BIOS обязательно выключить VT-d и в CSM установить все UEFI only, а Video там есть пункт выключить совсем. У меня версия 1.40. После настройки все видео выхода будут выключены, в биос больше не зайдете. Только поможет перемычка ClearCMOS. Плюс я установил x01015918_extra.lzma, это в первую очередь.
  45. 2 points
    Ich würde dir raten mit Subdomains zu arbeiten, dann müsstest Du Subdomains für dienst1.domain, dienst2.domain, usw bei deinem Strato-DNS anlegen und könntest dann ganz einfach Reverse -Proxy Einträge über die DSM-UI Konigurieren konfigurieren (Systemsteuerung->Anwendungsportal, Reiter "Reverse-Proxy"). Die Letsencrypt-zertifikate kannst Du ebenfalls über die DSM-UI anlegen lassen (Systemsteuerung->Sicherheit, Reiter "Zertifikat"). Ich habe z.B. mehrere Subdomains bei Netcup registriert, die als CNAME einen alias auf mein MyFritz-Konto verwenden. So habe ich DynDns über MyFritz und trotzdem eine funktionierende Namenslauflösung meiner Subdomains auf die IP, die mein MyFritz-Konto gerade verwendet. Das was Du vorhast (domain/dienst) kann der nginx in DSM zwar, aber NICHT über die UI. Hierzu müsstest Du Hand anlegen und das Ganze manuell konfigurieren. Wenn Du nicht weisst was Du da tust bzw. tun musst, würde ich stark davon abraten. Die andere Variante ist einfacher aufzusetzen und zu betreiben.
  46. 2 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.
  47. 2 points
    Кому лениво перезаписывать флешку или нужно сделать это удаленно при редактировании grub.cfg и замене extra.lzma, вспомнил про старый трюк, как это сделать прямо на работающей хрени: 1. Заходим по ssh через Putty или терминал 2. Делаем следующее: Admin@your_DS:~$ sudo -i #Заходим под root Password: #Вводим пароль Adminской учетки root@your_DS:~# mkdir -p /tmp/synoboot_part0 #Создаем временный каталог для монтирования 0 раздела загрузочной флешки root@your_DS:~# mkdir -p /tmp/synoboot_part1 #Создаем временный каталог для монтирования 1 раздела загрузочной флешки root@your_DS:~# cd /dev root@your_DS:/dev# mount -t vfat synoboot1 /tmp/synoboot_part0 #Монтируем 0 раздел загрузочной флешки root@your_DS:/dev# mount -t vfat synoboot2 /tmp/synoboot_part1 #Монтируем 1 раздел загрузочной флешки root@your_DS:/dev# ls /tmp/synoboot_part0 #Проверяем монтирование 0 раздела загрузочной флешки bzImage EFI grub info.txt root@your_DS:/dev# ls /tmp/synoboot_part1 #Проверяем монтирование 1 раздела загрузочной флешки checksum.syno extra2.lzma extra.lzma grub_cksum.syno rd.gz Sone.9 zImage 3. С помощью nano/mc правим grub.cfg и/или с помощью команд/mc заменяем extra.lzma 4. Перезагружаем хрень штатными средствами 5. Если перезагрузка сразу не планируется, то на всякий случай размонтируем и зачищаем: root@your_DS:/dev# cd / root@your_DS:/# umount /tmp/synoboot_part0 # Размонтируем 0 раздел загрузочной флешки root@your_DS:/# umount /tmp/synoboot_part1 # Размонтируем 1 раздел загрузочной флешки root@your_DS:/# rm -r /tmp/synoboot_part0 # Удаляем временный каталог root@your_DS:/# rm -r /tmp/synoboot_part1 # Удаляем временный каталог
  48. 2 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/.2) - 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 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
  49. 2 points
    The i915 driver can be changed? The one included in 1.04b crashes both system i’m testing (i3 6300 & nuc5i3)
  50. 2 points
    Из многочисленных тестов на больших серверах и разных NAS-ах включая (Dell Compellent, NetApp, Synology), iSCSI (блочный или файловые LUN) всегда получались значительно медленнее чем NFS или CIFS. Это важно для больших инсталяций с множественными 10Гб подключениями и полностью флэш дисками в массивах. У меня это работает как основные и резервные хранилища для VMware VSphere серверов для десятков серверов. Далеко не мелкий или средний офис. Единственное преимущество будет если сервер поддерживае аппаратную загрузку с ISCSI в BIOS, но и здесь флешка намного удобнее и дешевле. Для мелких офисов замечательно работает связка из ESXi сервера с хранилищем или бэкапом на 4-6 дисковом Syno /Xpeno (NFS/CIFS) через 1-2 гигабитных подключения. Для дома я вообще не вижу практического применения ISCSI. Разве что поиграться и поучиться.