Leaderboard

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.

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---

Hello @FOXBI. Is it possible to update your tool so that it is fully functional with the latest release of DSM 6.2? Thanks.

Я тут писал писал, просил просил подсказать как настроить. Все просто пишут всякий флуд и в итоге сам все настроил.

Почтовый сервер. Предпочитаю не зависеть от провайдеров или других компаний. Домейны и почта у меня собственная уже больше 20 лет с тех пор как появился DSL с постоянным подключением. Раньше, до synology пользовался универсальным linux сервером на дистрибутиве, в развитии которого я принимал участие. Со спамом и пр. довольно успешно справляюсь. Помогает более чем 30летний опыт управления сетями всех размеров и сетевой безопасности. Фотки в облаках? Нет, спасибо не надо. Моя личная жизнь не для всеобщего обозрения и не зависит от прихоти или политики компаний. DNS для собственного удобства. Не все мои и клиентские домейны нужно помещать в открытый доступ. Виртуалки тоже для удобства. Иногда надо находясь не дома, а скажем у клиента, проверить что-то снаружи. VPN не всегда поможет.

Не удалять, а форматировать!!! Не первые 2, а тот который ~2,5G. А безопаснее etc.default грохнуть или файл VERSION отредактировать.

Установил с нуля, восстановил данные, всё прекрасно работает и ничего не пропало. Спасибо Olegin_у и XPEH_у за помощь и уделённое мне внимание 😉

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

------------------------------------- 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/kxEmQV0Qe basé sur ds3617xs: https://file.niko44.fr/sharing/DfsAoTCHu 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 :

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

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

Обнаружил и испытал beta пакет Teamviewer, может кому пригодится для входа в DSM из-за NAT. P.S. Для того, чтобы подключиться нужно создать учетку TV и привязать к ней DSM. P.P.S. Если включить терминальный режим, то можно войти в консоль...

Petite mise à jour des liens et quelques corrections.

My point was, not sure of the need to upload the content of your tool as it defies the purpose of having a tool and might confuse people. But as I said up to you 🙂. That's all.

Been there. Elite 8300 PITA of a system to set up Xpenology. Someone on the forum sugested Hybrid partition usb working. Found it, credit goes to "Mitja" https://xpenology.com/forum/topic/12867-user-reported-compatibility-thread-for-dsm-62/page/2/?tab=comments#comment-107653 Use 1.03b ds3615 (maybe 3617 works, but 3615 is prefered). You MUST create "HYBRID" partition bootable usb for HP Compaq Elite 8300. Using it myself, update from 6.2.1 to 6.2.2 or clean install of latest 6.2.2 working perfect. Allow me to make it easyer for you: ----------------------------------------------------------- PART 1. preparation: -Download: "gdisk-windows-1.0.4.zip" (for windows) or appropriate one for other systems from here https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.4/gdisk-binaries/ -unzip content to folder (in the instructions bellow I unziped it in folder named "a" and copied that folder to root of a C disk) -in the BIOS of the HP Compaq Elite 8300 turn OFF UEFI boot by going to boot menu and press (I think) "F5" while UEFI option is highlighted, this will disable PC to default to UEFI boot on restart or powering on after power off. -in option ROM loading menu set all to legacy (storage, gpu, network) -on the working pc create standard clean usb with 1.03b - ds3615xs as usual leave it in the PC when done. -go to computer manager/disk managment (right click "My Computer" or "This PC" select "Manage" then "disk managment") - IMPORTANT - DATA LOSS POSIBLE IF YOU MAKE MISTAKE!!! note your USB key disk number ( Disk 0 is usually system partition). Please be carefull and double check! in the down listed commands the USB Key is "Disk 2" , copy/paste commands to lets say notepad, and CHANGE to match your situation (including for folder "a" in a root off a C disk if you didnt do it that way). ----------------------------------------------------------- PART 2. creating HYBRID partition USB Key- "gdisk-windows-1.0.4.zip" unziped to folder "a" in root of a C disk, USB KEY is "Disk 2" - !!!ALTER THIS TO MATCH YOUR SITUATION!!! first command "cd c:\a" - "a" represents folder named "a" and location in root (C:\) of a C disk - !!!ALTER THIS TO MATCH YOUR SITUATION!!! second command: "gdisk64 2:" - nr.64 represents 64bit system is running on, if you use 32bit system use #gdisk32 2:" -nr.2 represents Disk 2 on the system - !!!ALTER THIS TO MATCH YOUR SITUATION!!! -open command prompt as admin List of commands as per situation above (64bit sys, gdisk in folder "a" root C, USB is "Disk 2") press ENTER after each one of course:-------------------------------------- cd c:\a gdisk64 2: r o h 1 2 3 n "JUST PRESS ENTER - THIS SHOWING UP (DO NOT TYPE ANYTHING): Enter code (MBR partition #1):" y "JUST PRESS ENTER - THIS SHOWING UP (DO NOT TYPE ANYTHING): Enter code (MBR partition #2):" n "JUST PRESS ENTER - THIS SHOWING UP (DO NOT TYPE ANYTHING): Enter code (MBR partition #3):" n w y exit -------------------------------------- Now window will probably pop up asking you to format the drive, DO NOT DO IT!! Safely remove USB and put it in Elite 8300 and You are ready to go. This way created USB is harder to reformat and use again. Best way I found is to use free version of "MiniTool Partition Wizard" , first rebuild MBR whitin the program then delete partitions one by one (apply betwen each operation). I am sure you manage it and find best way if you need to reformat and reuse USB Key. Sorry for my English, not native speaker.... Good Luck!!

thanks very much for your help! Actually this method worked for me: WARNING: you'll loose your configuration and installed apps! create the syno pendrive from scratch (it's corrupted during upgrade) create an ubuntu live pendrive boot up linux and open terminal sudo -i apt-get install mdadm lvm2 mdadm -Asf && vgchange -ay fdisk -l | grep /dev/sd mdadm -AU byteorder /dev/md0 /dev/sda1 /dev/sdb1 (and list all your first partitions of the disks) mkfs.ext4 /dev/md0 now all your 1st partitions are formatted, reboot removing ubuntu pendrive and inserting syno pen choose reinstall use manual install and select last working PAT wait....., and you'll be DONE (of course all apps and configs are lost, but data should be there)

- Outcome of the update: SUCCESSFUL - DSM version prior to update: DSM 6.2.1-23824 Update 6 - Loader version and model: Jun v1.04b - DS918 - Using custom extra.lzma: NO - Installation type: BAREMETAL - DELL POWEREDGE T20 Xeon E3-1225V3 - Additional comments: The update went seamless. It reboots ok and performs very well.

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,

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"

Bjr, Pour info, je ne sais pas si tout le monde à ce droit là, mais pour renommer un sujet, il suffit de cliquer SANS relâcher sur le titre du sujet. Le champ passe aussitôt en édition.

На J5005 стартует только с VGA, ни с HDMI, ни DVI. Я себе сделал заглушку, пока так.

Если удалить любой из разделов, то хрень воспримет диск как чужеродное тело и начнет его размечать по новой и все данные сгинут. Своп можно не форматировать, только раздел с корнем хрени.

je te partage mon fichier d'install docker de Plex, version "linuxserver/plex:latest" et format json. Le chemin dev/dri y est inscrit et permet le transcodage hardware, en tout cas avec un serial valide mais après tout, cela ne semble finalement pas être indispensable. IL faut modifier les chemins d'accès à tes médias en fin de fichier mais pour le reste, ça devrait coller. J'ai juste viré le numéro "id" car je ne sais pas trop s'il est perso ou pas ^^; Fais un export json du tiens pour comparer! linuxserver-plex.json

Ah ok je n'ai pas de sérial valide. Mais je ne comprends plus rien lol. je n'ai même pas de fichier activation sur ma conf actuelle 😂. et ca marche. En fait ca marche au petit bonheur la chance le truc 😅 Je ne sais pas si ca vaut le coup maintenant de changer de conf si le transcodage ne marche pas. Et c'est apparemment la loterie 😐

@JRCOMTECH Read here, but in Russian, use Google translate.

Salut, Surement un problème de droit oui. Comment est installer Plex ? Via Docker ? Tu a configurer le PID/VID d'un user dans Plex ?

t'embête pas c'est super sympa, mais je vais tenter ta 1ère solution. Cette nuit la copie de toutes mes photos s'est terminée, je vais pouvoir recréer le dossier photo proprement.

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

Comme souvent, tout dépend de tes attentes. Moi je voulais une lentille fixe mais de haute qualité, alimentée en PoE, vision nuit correcte et résistante aux intempéries. Résultat j'ai pris une Foscam https://www.amazon.fr/dp/B00NCR4DQA/ref=cm_sw_em_r_mt_dp_U_2G69CbJ6MX5X8 (le commentaire avec la vidéo est de moi^^). Je l'ai acheté le 4/12/2015, elle est toujours dehors au moment où j'écris ces lignes et elle marche toujours impec! Seul regret (toutes caméras confondues) aucune de dispose d'un anti-araignée! C'est pénible de voir ces salles bebetes passées devant constamment quand elle décide de tisser sa toile depuis la caméra 😅

Можно, читайте

Hi guys, For some of you who wish to expand btrfs Syno volume after disk space increased. Before: df -Th btrfs fi show mdadm --detail /dev/md2 SSH commands: syno_poweroff_task -d mdadm --stop /dev/md2 parted /dev/sda resizepart 3 100% mdadm --assemble --update=devicesize /dev/md2 /dev/sda3 mdadm --grow /dev/md2 --size=max reboot btrfs filesystem resize max /dev/md2 After: df -Th btrfs fi show mdadm --detail /dev/md2 Voila Kall

Si aucune raison particulière et si tout marche, je ne conseille pas de mise à jour à DSM 6.2. DSM 6.1 est maintenu à jour par Synology si nécessaire (sécurité y inclus). Tous les paquets meme les dernières versions marchent. DSM 6.2 n'est pas une mise à jour mais plutôt un "upgrade" avec des fonctionnalité nouvelles. En d'autres termes à moins d'avoir besoin de nouvelles fonctionnalité restez sur DSM 6.1.7.

Hello @Dartremil and welcome to the forum. This thread is not a "guide" so I suppose you are referring to the tutorial I made. If not and either way, both the tutorial and this thread clearly state that you can't upgrade past DSM 6.1 WITH loader v1.02b. However, you can install DSM 6.2 with either loaders v1.03b and v1.04b depending which loader model you chose (DS3615/DS3617 or DS918+ respectively). Quotes from all topics: Please note that both this topic and the tutorial were designed for DSM 6.1 so they are not aimed at addressing DSM 6.2. There is another thread for DSM 6.2: Also please have a look at the faqs. This should help clear up some questions you may have: https://xpenology.com/forum/forum/83-faq-start-here/

Надо отключить диски загрузиться под лайф usb linux открыть раздел 1 системный найти там скачанный файл обновления и удалить его на всех дисках

Hi guys, I’m a 3d artist looking into IT in my spare time and looking to usually get weird things done to accommodate my pipeline that is on a budget. Owning two 3617xs (real ones) and looking to expand with some others but I need one on GCP, and google does not rent syno, so I have to build one myself with I hope xpenology 😉

I advice against that but well it is up to you. Maybe you can send him the zip file directly.

If you can't access your Xpenology box but you still wish to try and 'fix' some configuration files or perhaps you wish to finally make that backup that you should have done before fiddling with the root user, then you can access the content of the system partition and data partitions through a Live Ubuntu CD (or whatever unix flavoured OS you so desire). Here is how to: 1 - Make a Live Ubuntu USB drive. Ideally it is more convenient to make a persistent Live Ubuntu USB drive but that's not required for this tutorial and it would just complicate things unnecessarily. 2 - Once you're done burning Ubuntu on the USB flash drive, go plug it in your Xpenology box and boot from it. 3 - Once in Ubuntu, launch Terminal. You will need to first be root so type: sudo -i 4 - Now install mdadm and lvm2 by typing the following command: apt-get install mdadm lvm2 You should get the following Postfix Configuration menu: Select as shown in the pictures above. If you wish to mount the data partition alone then proceed with the following command: 5 - To mount the data partition, simply issue this command and you are done: mdadm -Asf && vgchange -ay If you also wish to mount the system partition then proceed with the following commands (adapt to your case accordingly): 6 - Then you need to check your raid array and partitioning of your drives: fdisk -l | grep /dev/sd In my case I see this. Note I only have 2 drives /dev/sda and /dev/sdb root@server:/etc.defaults# fdisk -l | grep /dev/sd Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors /dev/sda1 256 4980735 4980480 2.4G fd Linux raid autodetect /dev/sda2 4980736 9175039 4194304 2G fd Linux raid autodetect /dev/sda3 9437184 3907015007 3897577824 1.8T f W95 Ext'd (LBA) /dev/sda5 9453280 3907015007 3897561728 1.8T fd Linux raid autodetect Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors /dev/sdb1 256 4980735 4980480 2.4G fd Linux raid autodetect /dev/sdb2 4980736 9175039 4194304 2G fd Linux raid autodetect /dev/sdb3 9437184 3907015007 3897577824 1.8T f W95 Ext'd (LBA) /dev/sdb5 9453280 3907015007 3897561728 1.8T fd Linux raid autodetect System partitions are the ones labeled sda1, sdb1. If you have more drives in the array, subsequent system partitions will probably be called sdc1, sdd1 so on and so forth. You get the point. 7 - Once you figured out all system partitions, you can examine the foreign endian array members by issuing (this is for my case, with 2 drives): mdadm -Ee0.swap /dev/sda1 /dev/sdb1 If you have 3 drives then you add /dev/sdc1. You get the idea. 8 - Finally, assemble the array and fix the byte order (this is for my case, with 2 drives): mdadm -AU byteorder /dev/md0 /dev/sda1 /dev/sdb1 Same comment as previous command; add any additional system partitions that you may have. Beware of the /dev/md0. It's normal, not a mistake. Your system partition should now be mounted and you can navigate through the system files. Simply unmount the drives and shutdown the machine when you are done. If for some reason you need to reboot and want to access the partitions again then you will need to re-install mdadm and lvm2 because the Live Ubuntu USB is not persistent. --------- Reference: https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Storage/How_can_I_recover_data_from_my_DiskStation_using_a_PC http://xpenology.com/forum/viewtopic.php?f=2&t=22100&p=83631&hilit=version#p83631 http://xpenology.com/forum/viewtopic.php?f=2&t=20216&p=74659&hilit=mdadm#p74659 >> Thanks to Jun

I accidentally deleted the old file. New version accessible from HERE: Synology 3rdParty repository.xlsx --> editable on my private OneDrive Have fun 😉

At first you need to install the Docker package in the DSM Package Center. After that, you can install containers, for example Portainer https://portainer.readthedocs.io/en/latest/deployment.html $ sudo docker volume create portainer_data $ sudo docker run -d -p 9000:9000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer

Hi i'm Dave, glad to join I have a synology NAS DS214play and since I want upgrade it I've ordered: i3 8100T + noctua 9Li fan Asrock H370M-ITX/ac microstar 721 case 16GB Ram 2 x WD red 4TB (+ 2 WD Red 4TB i have in my previous NAS) 1 x 240GB M.2 drive nice to meet you

Hello Forum, I'm Charles Windom. I am a Solutions/Cloud Architect working for a popular virtualization/cloud company. am currently running Thecus N5550 and HP Proliant MicroServer NL54 clocked at 2.2Ghz My server is: 2 each - HP Proliant MicroServers running FreeNAS 11-2U1 only on one of the servers 16GB RAM in each server 1 Dual Port Gigabit NIC in each server 5 each real Hitachi 4TB Enterprise SATA 3 drives in each server Looking to try out Xpenology on the free server to Xperiment :-) Thecus currently has 5 each 8TB NAS drives configured in RAID5 for streaming only. Other unit used for backup and some archival storage

Salut a tous, Je m'appelles Joss, j'ai 40 ans et je vie en France. Je suis graphiste et photographe, et il m'arrive de bidouiller des machines plus ou moins évoluées (sans entrer dans le code) Je fais ici mes premiers pas dans le monde du NAS, j'ai entendu parler de leurs possibilités (qui pourraient bien aider mon workflow), mais je n'ai pas encore eu l'occasion de toucher à ce genre de machine. (hormis un premier test sur Freenas) Je souhaite recycler des composants un peu anciens, question de budget, pour voir ce que je peux en tirer. Hi all, Josh here, 40 years old, from France, I'm graphist, photographer, and IT curious (really not expert) I'm doing my first steps in the NAS world, just hear about but never touch anything (just a little quick try on Freenas) I hope to build a machine from old spare parts I've got, and see what's possible to do with. La machine: Motherboard : GA-T671MG (Gigabit) Processor: Celeron dual core E3200 RAM : 2x 1Go DDR2 HDD: 3x 1To Pci cards extends: 2x VIA VT6421A + MSI STAR usb3/Sata6 (PEX8608-BA50BC G) PCIe 4x

Well i got a DS110j that i have had a few years, still going strong. Found a compaq elite 8000 knocking around at work so grabbed that on wednesday. Due to the small form factor of this device and it only uses 2.5 inch drives, i have upgraded the one drive to 2tb and ordered a drive caddy for the other drive so i can have a small raid. Got the one drive working last night with DSM 6.1 installed but have ordered a low profile usb stick as they are only pittance any way and will do some swapping of bits but will be mainly used at home as a small media server / Torrent sites

Hi everyone. I am from Southern California USA. I am really new to this and want to learn more. So I am here. I have grown to love NAS systems and this seems like a great challenge and a way to learn more. So you will see me around asking stupid questions but I am just trying to figure things out. Be patient with me. Thank you all.

Hello world! Hi am Alvin from the Philippines, I am a new user of Synology it's just been 6 months and stumbles xpenology by accident. I would like to know more about this so I can build my own NAS at home.

Hi everyone! I'm US IT freelancer and a shop merchant. And just decided to try xpenology:) While not busy in IT, working at this lawn mover shop.

@Eduardo From what I have read in here, Jun's 1.03 and DS3617xs seems to be working with DSM 6.2 on the Gen 10, if you add a supported Intel based nic, you can use 6.2.1 update 2 (the current "latest and greatest").

All links below are provided for noobs and because I am a nice guy, but simply going to https://archive.synology.com/download/DSM/ or https://www.synology.com/en-global/support/download and then clicking the desired subsequent links will yield everything I am linking below. Seek and you shall find. Also keep in mind that I am not updating this post very often so you are better of learning how all this works. --------------------------------------------------------------------------------------------- DSM PAT files can be found here (Major updates): DSM 6.0.2: https://archive.synology.com/download/DSM/release/6.0.2/8451/ Chose .pat file DS3615xs DSM 6.1: https://archive.synology.com/download/DSM/release/6.1/15047/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.1: https://archive.synology.com/download/DSM/release/6.1.1/15101/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.2: https://archive.synology.com/download/DSM/release/6.1.2/15132/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.3: https://archive.synology.com/download/DSM/release/6.1.3/15152/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.4: https://archive.synology.com/download/DSM/release/6.1.4/15217/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.5: https://archive.synology.com/download/DSM/release/6.1.5/15254/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM6.1.6: https://archive.synology.com/download/DSM/release/6.1.6/15266/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM6.1.7: https://archive.synology.com/download/DSM/release/6.1.7/15284/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM6.2: https://archive.synology.com/download/DSM/release/6.2/23739/ Chose .pat file for DS3615xs or DS3617xs or DS918+ accordingly DSM6.2.1: https://archive.synology.com/download/DSM/release/6.2.1/23824/ Chose .pat file for DS3615xs or DS3617xs or DS918+ accordingly DSM6.2.2: https://archive.synology.com/download/DSM/release/6.2.2/24922/ Chose .pat file for DS3615xs or DS3617xs or DS918+ accordingly Critical Updates for all DSM versions can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/ or http://archive.synology.com/download/DSM/criticalupdate/update_pack/ Critical Updates specifically for DSM 6.0.2 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-2/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-3/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-4/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-5/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-6/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-7/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-8/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-9/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-10/ http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-11/ Chose .pat file DS3615xs Critical Updates specifically for DSM 6.1 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15047-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15047-2/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.1 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-2/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-3/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-4/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.2 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15132-1/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.3 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-2/ - Does not apply to DS3615xs or DS3617xs or DS916+ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-3/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-4/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-5/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-6/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-7/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-8/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.4 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-2/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-3/ - Update was removed by Synology without warning http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-3/ - Re-added by Synology (different md5) http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-4/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-5/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.5 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15254-1/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.6 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15266-1/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.7 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/15284-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/15284-2/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.2 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/23739-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/23739-2/ Chose .pat file for DS3615xs or DS3617xs or DS918+ accordingly Critical Updates specifically for DSM 6.2.1 can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/23824-1/ http://download.synology.com/download/DSM/criticalupdate/update_pack/23824-2/ http://download.synology.com/download/DSM/criticalupdate/update_pack/23824-3/ http://download.synology.com/download/DSM/criticalupdate/update_pack/23824-4/ http://download.synology.com/download/DSM/criticalupdate/update_pack/23824-5/ http://download.synology.com/download/DSM/criticalupdate/update_pack/23824-6/ Chose .pat file for DS3615xs or DS3617xs or DS918+ accordingly Critical Updates specifically for DSM 6.2.2 can be found here: None to this date (27/05/2019) Chose .pat file for DS3615xs or DS3617xs or DS918+ accordingly ---------------------------------------------------------------------------------------------

Установочный FAQ / Часто задаваемые вопросы по установке Перевод. Оригинал здесь https://xpenology.com/forum/topic/9394-installation-faq/ Целью данного руководства являются ответы на обычно задаваемые вопросы! Это не раздел, где просят о помощи. Для этой цели Вы можете использовать форум. 1. Откуда я могу загрузить (скачать) загрузчики? Загрузчики, как текущая версия, так и предыдущие версии могут быть найдены здесь: https://xpenology.com/forum/topic/7848-links-to-loaders/ Настоятельно рекомендуется прочитать тему (по крайней мере основной пост), сделанную инициатором/разработчиком загрузчика, @jun: https://xpenology.com/forum/topic/6253-dsm-6xx-loader/ 2. Есть ли какое-нибудь руководство по установке / обновлению системы DSM на baremetal? Смотрите инструкцию, доступную здесь: https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ 3. Как мне использовать SHR (Synology Hybrid RAID) в DSM 6? SHR может быть переподключен путём правки файла 'synoinfo.conf' , расположенного в '/etc.defaults/' Закомментируйте (или удалите строку): и добавьте 4. Сколько дисков я могу использовать? Члены сообщества опробовали системы, содержащие вплоть до 24 дисков, и они были стабильны. Физический предел 26 дисков из-за ограничений в технологии адресации дисков в Линукс. 5. Могу ли я загружаться с HDD, а не с USB? Нет, рекомендуется и поддерживается конфигурация загрузки с USB. 6. Требуется ли мне подключение последовательного порта? Последовательный порт необходим для просмотра расширенной информации о загрузке / загрузке драйвера и ошибок, для проведения диагностики, но не требуется для обычного использования. 7. После меню загрузки Grub, мой монитор показывает сообщение 'booting from kernel' (загрузка из ядра) и больше ничего - что не так? Это нормально для загрузчика XPE 6 - подключите последовательный порт для просмотра дополнительных диагностических данных или используйте Synology Assistant для подключения к NAS. 8. Нужны ли мне постоянно подключенные клавиатура и монитор? Клавиатура и монитор полезны для начальной настройки, чтобы выбрать опцию меню загрузки grub и проверить начальную загрузку, после чего они не требуются. 9. Как мне настроить автоматические обновления DSM? Автоматические обновления DSM должны быть отключены в панели управления > обновление и восстановление, чтобы избежать выхода из строя Вашей системы, в том случае, если обновление не совместимо с загрузчиком. Всегда проверяйте информацию на форуме, прежде чем применять обновление вручную. 10. Какой MAC адрес я должен использовать в настройках конфигурации grub? Рекомендуется, но не требуется, чтобы MAC адрес конфигурации grub был таким же, как и в установленном сетевом адаптере. Вы можете проверить MAC адрес вашей сетевой карты, посмотрев в BIOS или запустив live ОС, например Ubuntu. 11. Номера слотов HDD в менеджере хранения не совпадают с портами на моем контроллере диска - почему? Диспетчер хранилища определяет номера дисков на основе перечисления контроллеров на уровне шины / слота, которые нельзя изменить. Рекомендуется вручную записывать дисковые слоты/серийные номера/порты контроллера. 12. Как восстановить большие объемы зарезервированной памяти при просмотре монитора ресурсов DSM? Добавьте в строку 'set common_args_3615' в файл grub.cfg содержащийся в загрузчике (применимо к загрузчику jun's). Это должно выглядеть примерно так: Это должно вернуть Вам весь объём зарезервированной ОЗУ. Примечание: DS3617xs использует строку 'set common_args_3617' и DS916+ использует строку 'set common_args_916' 13. Мне нужно / я хочу переустановить DSM. Я беспокоюсь о своих данных. Что мне нужно сделать? Повторная переустановка DSM не влияет на Ваши данные, так как пользовательские данные хранятся на другом разделе в отличие от DSM. Однако может потребоваться переустановка всех пакетов и перенастройка параметров.

Juns bootloader he creates a custom zImage which loads up the DSM software, could he, compile a new kernel with the LIMIT set to something like 24/32 something in the region of 2017... server cores. Seeing as we can get a single CPU with 8 cores then HT to 16 logical, 8 is becoming rather limiting.