Leaderboard


Popular Content

Showing content with the highest reputation since 01/26/2020 in all areas

  1. 13 points
    Hi all:) After a little bit of reverse engineering I was able to bypass the license checking mechanism introduced in DSM 6 successfully with a simple two line binary patch of synocodectool and therefore enable transcoding without a valid serial number[emoji4]. I wrote a little script to make it easier for everyone. For more information please check the github repo: https://github.com/likeadoc/synocodectool-patch HOWTO: 1. wget https://raw.githubusercontent.com/likeadoc/synocodectool-patch/master/patch.sh 2. chmod +x patch.sh 3. ./patch.sh Done:) If things go wrong simply restore the original file: ./patch.sh -r Cheers
  2. 6 points
    This is the new 2nd test version of the driver extension for loader 1.04b and 918+ DSM 6.2.2, network drivers for intel and realtek are now all latest and the same as in 3615/17 from mid. december (also broadcoam tg3 driver is working), tries to address the problems with the different GPU's by haveing 3 versions of the pack additional information and packages for 1.03b and 3615/3617 are in the lower half under a separate topic (i will unify the 918+ and 3615/17 parts later as they are now on the same level again) mainly tested as fresh install with 1.04b loader with DSM 6.2.2, there are extra.lzma and extra2.lzma in the zip file - you need both - the "extra2" file is used when booting the 1st time and under normal working conditions the extra.lzma is used (i guess also normal updates - jun left no notes about that so i had to find out and guess). Hardware in my test system used additional driver: r8168, igb, e1000e, bnx2x, tn40xx, mpt2sas The rest of the drivers just load without any comment on my system, i've seen drivers crashing only when real hardware is present so be warned, i assume any storage driver beside ahci and mps2sas/mpt3sas as not working, so if you use any other storage as listed before you would need to do a test install with a new usb and a single empty disk to find out before doing anything with your "production" system i suggest testing with a new usb and a empty disk and it that's ok then you have a good chance for updating for updating its the same as below in the 3615/17 section with case 1 and 2 but you have extra.lzma and extra2.lzma and you will need to use https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS918+_24922.pat most important is to have zImage and rd.gz from the "DSM_DS918+_24922.pat" file (can be opened with 7zip) together with the new extra/extra2, same procedure as for the new extra for 3615/17 (see below) all 4 files extra.lzma, extra2.lzma (both extracted from the zip downloaded), zImage and rd.gz go to the 2nd partition of the usb (or image when using osfmount), replacing the 4 files there if you want the "old" files of the original loader back you can always use 7zip to open the img file from jun and extract the original files for copying them to usb if really wanting to test with a running 6.2.x system then you should empty /usr/lib/modules/update/ and /usr/lib/firmware/i915/ before rebooting with the new extra/extra2 rm -rf /usr/lib/modules/update/* rm -rf /usr/lib/firmware/i915/* the loader will put its files on that locations when booting again, this step will prevent having old incompatible drivers in that locations as the loader replaces only files that are listed in rc.modules and in case of "syno" and "recovery" there are fewer entries, leaving out i915 related files, as long as the system boots up this cleaning can be done with the new 0.8 test version there a 3 types of driver package, all come with the same drivers (latest nic drivers for realtek and intel) and conditions/limitations as the 3615/17 driver set from mid. december (mainly storage untested, ahci and mpt3sas is tested). 1. "syno" - all extended i915 stuff removed and some firmware added to max compatibility, mainly for "iGPU gen9" (Skylake, Apollo Lake and some Kaby Lake) and older and cases where std did not work, i915 driver source date: 20160919, positive feedback for J3455 and J1800 2. "std" - with jun's i915 driver from 1.04b (tested for coffee lake cpu from q2/2018), needed for anything newer then kaby lake like gemini lake, coffee lake, cannon lake, ice lake, i915 driver source date: 20180514 - as i had no source i915 driver is the same binary as in jun's original extra/extra2, on my system its working with a G5400, not just /dev/dri present, tested completely with really transcoding a video, so its working in general but might fail in some(?) cases, also 9th gen cpu like i3 9100 might not produce a /dev/dri, needs testing 3. "recovery" - mainly for cases where the system stops booting because of i915 driver (seen on N3150 braswell), it overwrites all gpu drivers and firmware with files of 0 size on booting so they can't be loaded anymore, should also work for any system above but guarantees not having /dev/dri as even the firmware used from the dsm's own i915 driver is invalid (on purpose) - if that does not work its most likely a network driver problem, safe choice but no transcoding support start with syno, then std and last resort would be recovery anything with a kernel driver oops in the log is a "invalid" as it will result in shutdown problems - so check /var/log/dmesg the often seen Gemini Lake GPU's might work with "std", pretty sure not with "syno", most (all?) testers with gemini lake where unsuccessful with "std" so if you don't like experimenting and need hardware transcoding you should wait with the version you have the "_mod" on the end of the loader name below is a reminder that you need to to "modding" as in make sure you have zImage and rd.gz from DSM 6.2.2 on you usb for booting, the new extra.lzma will not work with older files 0.8_syno ds918+ - extra.lzma/extra2.lzma for loader 1.04b_mod ds918+ DSM 6.2.2 v0.8_syno http://s000.tinyupload.com/?file_id=27662133308664190275 SHA256: 21B0CCC8BE24A71311D3CC6D7241D8D8887BE367C800AC97CE2CCB84B48D869A 0.8_std ds918+ - extra.lzma/extra2.lzma for loader 1.04b_mod ds918+ DSM 6.2.2 v0.8_std http://s000.tinyupload.com/?file_id=00354004133254441591 SHA256: F611BCA5457A74AE65ABC4596F1D0E6B36A2749B16A827087D97C1CAF3FEA89A 0.8_recovery ds918+ - extra.lzma/extra2.lzma for loader 1.04b_mod ds918+ DSM 6.2.2 v0.8_recovery http://s000.tinyupload.com/?file_id=02568989419278984390 SHA256: 5236CC6235FB7B5BB303460FC0281730EEA64852D210DA636E472299C07DE5E5 !!! still network limit in 1.04b loader for 918+ !!! atm 918+ has a limit of 2 nic's (as the original hardware) If there are more than 2 nic's present and you can't find your system in network then you will have to try after boot witch nic is "active" (not necessarily the onboard) or remove additional nic's and look for this after installation You can change the synoinfo.conf after install to support more then 2 nic's (with 3615/17 it was 8 and keep in mind when doing a major update it will be reset to 2 and you will have manually change this again, same as when you change for more disk as there are in jun's default setting) - more info's are already in the old thread about 918+ DSM 6.2.(0) and here https://xpenology.com/forum/topic/12679-progress-of-62-loader/?do=findComment&comment=92682 I might change that later so it will be set the same way as more disks are set by jun's patch - syno's max disk default for this hardware was 4 disks but jun's pach changes it on boot to 16!!! (so if you have 6+8 sata ports then you should not have problems when updating like you used to have with 3615/17) Basically what is on the old page is valid, so no sata_*, pata_* drivers Here are the drivers in the test version listed as kernel modules: The old thread as reference !!! especially read "Other things good to know about DS918+ image and loader 1.03a2:" its still valid for 1.04b loader !!! This section is about drivers for ds3615xs and ds3617xs image/dsm version 6.2.2 (v24922) Both use the same kernel (3.10.105) but have different kernel options so don't swap or mix, some drivers might work on the other system some don't at all (kernel oops) Its a test version and it has limits in case of storage support, read careful and only use it when you know how to recover/downgrade your system !!! do not use this to update when you have a different storage controller then AHCI, LSI MPT SAS 6Gb/s Host Adapters SAS2004/SAS2008/SAS2108/SAS2116/SAS2208/SAS2308/SSS6200 (mpt2sas) or LSI MPT SAS 12Gb/s Host Adapters SAS3004/SAS3008/SAS3108 (mpt3sas - only in 3617), instead you can try a fresh "test" install with a different usb flash drive and a empty single disk on the controller in question to confirm if its working (most likely it will not, reason below) !!! The reason why 1.03b loader from usb does not work when updating from 6.2.0 to 6.2.2 is that the kernel from 6.2.2 has different options set witch make the drivers from before that change useless (its not a protection or anything), the dsm updating process extracts the new files for the update to HDD, writes the new kernel to the usb flash drive and then reboots - resulting (on USB) in a new kernel and a extra.lzma (jun's original from loader 1.03b for dsm 6.2.0) that contains now incompatible drivers, the only drivers working reliable in that state are the drivers that come with dsm from synology Beside the different kernel option there is another thing, nearly none of the new compiled scsi und sas drivers worked They only load as long as no drive is connected to the controller. ATM I assume there was some changes in the kernel source about counting/indexing the drives for scsi/sas, as we only have the 2.5 years old dsm 6 beta kernel source there is hardly a way to compensate People with 12GBit SAS controllers from LSI/Avago are in luck, the 6.2.2 of 3617 comes with a much newer driver mpt3sas then 6.2.0 and 6.2.1 (13.00 -> 21.00), confirmed install with a SAS3008 based controller (ds3617 loader) Driver not in this release: ata_piix, mptspi (aka lsi scsi), mptsas (aka lsi sas) - these are drivers for extremely old hardware and mainly important for vmware users, also the vmw_pvscsi is confirmed not to work, bad for vmware/esxi too Only alternative as scsi diver is the buslogic, the "normal" choice for vmware/ESXi would be SATA/AHCI I removed all drivers confirmed to not work from rc.modules so they will not be loaded but the *.ko files are still in the extra.lzma and will be copied to /usr/modules/update/ so if some people want to test they can load the driver manually after booting These drivers will be loaded and are not tested yet (likely to fail when a disk is connected) megaraid, megaraid_sas, sx8, aacraid, aic94xx, 3w-9xxx, 3w-sas, 3w-xxxx, mvumi, mvsas, arcmsr, isci, hpsa, hptio (for some explanation of what hardware this means look into to old thread for loader 1.02b) virtio driver: i added virtio drivers, they will not load automatically (for now), the drivers can be tested and when confirmed working we will try if there are any problems when they are loaded by default along with the other drivers they should be in /usr/modules/update/ after install To get a working loader for 6.2.2 it needs the new kernel (zImage and rd.gz) and a (new) extra.lzma containing new drivers (*.ko files) zImage and rd.gz will be copied to usb when updating DSM or can be manually extracted from the 6.2.2 DSM *.pat file and copied to usb manually and that's the point where to split up between cases/way's case 1: update from 6.2.0 to 6.2.2 case 2: fresh install with 6.2.2 or "migration" (aka upgrade) from 6.0/6.1 Case 1: update from 6.2.0 to 6.2.2 Basically you semi brick your system on purpose by installing 6.2.2 and when booting fails you just copy the new extra.lzma to your usb flash drive by plugging it to a windows system (witch can only mount the 2nd partition that contains the extra.lzma) or you mount the 2nd partition of the usb on a linux system Restart and then it will finish the update process and when internet is available it will (without asking) install the latest update (at the moment update4) and reboot, so check your webinterface of DSM to see whats going or if in doubt wait 15-20 minutes check if the hdd led's are active and check the webinterface or with synology assistant, if there is no activity for that long then power off and start the system, it should work now Case 2: fresh install with 6.2.2 or "migration" (aka upgrade) from 6.0/6.1 Pretty much the normal way as described in the tutorial for installing 6.x (juns loader, osfmount, Win32DiskImager) but in addition to copy the extra.lzma to the 2nd partition of the usb flash drive you need to copy the new kernel of dsm 6.2.2 too so that kernel (booted from usb) and extra.lzma "match" You can extract the 2 files (zImage and rd.gz) from the DSM *.pat file you download from synology https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3615xs_24922.pat or https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3617xs_24922.pat These are basically zip files so you can extract the two files in question with 7zip (or other programs) You replace the files on the 2nd partition with the new ones and that's it, install as in the tutorial In case of a "migration" the dsm installer will detect your former dsm installation and offer you to upgrade (migrate) the installation, usually you will loose plugins, but keep user/shares and network settings DS3615: extra.lzma for loader 1.03b_mod ds3615 DSM 6.2.2 v0.5_test http://s000.tinyupload.com/?file_id=87576629927396429210 SHA256: BAA019C55B0D4366864DE67E29D45A2F624877726552DA2AD64E4057143DBAF0 DS3617: extra.lzma for loader 1.03b_mod ds3617 DSM 6.2.2 v0.5_test http://s000.tinyupload.com/?file_id=06641076704622277403 SHA256: 4A2922F5181B3DB604262236CE70BA7B1927A829B9C67F53B613F40C85DA9209
  3. 4 points
    Для желающих протестировать 8.2.2-5766-x64 Fix Товарищи, пересобирать пакеты я не буду, нет на это времени, только замена файликов. Для желающих запихнуть эти файлы в SS для ARM - не стоит, получите полностью нерабочую систему.
  4. 3 points
    For the community, please note that this critical update does NOT apply to DS3615xs and DS3617xs.
  5. 2 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, 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
  6. 2 points
    Господа, я понимаю ваше желание получить всё и сразу. Попробуйте понять и меня. У меня не так много времени на разработку и проверку. Я мог бы конечно бросить все дела и заняться исключительно SS, но мне это не нужно. Это отнимает очень много личного времени и я занимаюсь "чтением" кода исключительно в свободное время. Как только будут новости, вы их сможете прочитать в этой теме. Не нужно мне в личку сыпать сообщениями с просьбой выслать файлики, это бесполезно. Те, кто успел получить нестабильный вариант конечно могут поделиться с остальными, но на то он и нестабильный, что за его работоспособность я отвечать не хочу. На этом всё.
  7. 2 points
  8. 2 points
    Устанавливаем резалку рекламы Pi-hole в докер на Synology. Вступление: мануалов много, но они не совсем правильные. Часть из них используют bridge сеть докера, тем самым затрудняя доступ из локальной сети к нутрям контейнера. Не каждому понятно как в него пробраться. Часть мануалов рекомендуют привязывать к контейнеру HOST-сеть докера. Тем самым блокируя порты самой Synology, так как Pihole использует тот же 80-й порт и прочие. Я нашел адекватный мануал на английском и решил оставить след по нему в виде скриншотов и надписей на русском языке. А как вы знаете - они есть даже в общественных парижских туалетах. Оригинал мануала лежит вот тут Итак, если очень кратко: редактируем под себя файл настроек, заходим в SSH на Synology под root, говорим докеру скомпоновать контейнер и вуаля. Далее, распишу более подробно. У меня образ Pihole был заранее скачан. Я не уверен, скачает ли докер его сам, поэтому заранее зайдите в реестр докера и слейте себе образ Pihole под ваш процессор. Будем считать, что образ (в неправильном переводе на русский звучит как "Изображение") у вас скачан. Идем по ссылке выше, качаем файл docker-compose.yaml и редактируем его под свои нужды: Основной смысл редактирования - привести настройки сети к вашим. Как отредактировали этот файл, то кладем его на файлостанцию. Разумно сделать отдельную папку Docker и в ней делать папки для конкретного контейнера. И в эти папки уже прокидывать при нужде папки из контейнеров. В итоге, у меня оно вот так: В папку pihole я положил отредактированный ранее файл docker-compose.yaml Теперь залазим на нашу Synology каким-то терминалом, пролазим в папку с файлом docker-compose.yaml и выполняем команду: docker-compose up -d Пролазим именно под рутом, иначе демон докера будет ругаццо! Видим, что все готово. Идем опять в админку докера и видим наш работающий свеженький контейнер. Было: Стало: Отлично! Теперь нужно нарыть пароль для админки. Если вы его указали в конфиге, то перепрыгивайте на следующий шаг. Если не указывали, то дважды щелкаем на контейнере в админке докера (скрин выше) и лезем в журнал. В Журнале ищем пароль: Пароль найден. Переходим по адресу, присвоенному контейнеру в docker-compose.yaml и заходим в админку: Вуаля! Пол дела сделано! Надавив Dashboard, справа вверху на красном фоне вы можете глянуть количество блокируемых доменов. У меня их было порядка 120 тысяч. "Но ведь это не так и много!" - скажете вы и будете в чем-то правы )) Я подошел к вопросу точно так же, как и вы и по итогу у меня почти 3.5 млн доменов блокируемого хлама. Кто-то скажет, что это дескать неправильно, гнаться за количеством. Но лично мне и в моей ситуации - это нисколько не вредит. Да, нушные сайты заблокированы. Заблокирован фейсбук и куча прочей дряни. И даже фишки.нет заблокирован кастомными списками. Но для предприятия это не есть проблемой. Всё что нужно для работы у меня работает. А остальное - юзверя дома будут фейсбучить и так далее. В любом случае - разблокировать домен с пихолькой очень легко. Итак, теперь нам нужно 120 тысяч блокируемых доменов расширить до 3.4 миллионов. Может не всем нам, но кому-то наверняка нужно. Так что этим и займемся. Благо - это лишь пара скриншотов и десяток кликов мышом! Идем на сайт https://firebog.net Видим кучку готовых списков. В соседней вкладке/окне браузера открываем админку и идем в настройки: Settings - Blocklist Копипастим нужные списки в соответствующее поле и жмем Save and Update. готовый полный список на сегодня: Подожем немного, пока наша пихолька подгрузит в себя громадные списки доменов хлама и выходим на главную страницу (Dashboard). Ух-ты! 3.4 млн блокируемого говнища! Ура! Ну как-то так, ребята! Если у вас не работает какой-то сайт, то на главной странице есть список клиентов (Top Clients (total)) Ищем в нем нужного вам клиента и смотрим куда он бродит: Как видите - из этой панели легко можно увидеть блокируемые домены и добавить их в список нефильтруемых (Whitelist). Последнее, что нужно сделать, это указать в настройках роутера, чтобы при раздаче DHCP он выдавал в качестве адреса DNS сервера - именно адрес вашей пихольки. У меня в микроте это выглядит примерно так: Учтите, что настройка mac-lan докера предполагает, что часть "верхних" адресов может быть занята этой созданной докером сеткой. Если только пихолька будет у вас пользоваться этой сетью докера - то проблем не будет. Но если к этой сетке когтить иные контейнеры, то могут возникнуть грабли с адресами. Короче, это вопрос нудный, писать долго и я думаю, большинство понимают о чем речь. upd: забыл сказать: мозила резала на ура! В хроме попробовал - оказалось много рекламы. Почистил кеш DNS хрома и системы - не помогло. Дальше разбираться не стал. Это я к тому пишу, что от браузера зависит эффективность этого мероприятия. Учитывайте! Вот два дня работы системы в сети с несколькими десятками клиентов. Ну, вроде всё рассказал. Надеюсь, это будет полезным кому-то! Могу лишь добавить, что в ЖЖ у меня adblock и ghostery не справлялись с рекламой. После установки пихольки рекламы в ЖЖ почти нет. То же самое и с фишками. Удачи! Экономьте трафик! US Robotics 33600 - наше всё! Помним, любим, скорбим ))
  9. 2 points
    ***For experienced individuals comfortable with synology and linux command line, I take no responsibility for any issues encountered*** ***Read fully before considering*** Please read all necessary documentation for setting up Xpenology before reading this guide. Try the start-here guides below: https://xpenology.com/forum/forum/83-faq-start-here/ This guide docuements the process of using Linux to modify the synoboot.img for your environment and writing to a usb hard drive. Additonally, this guide shows the upgrade process from 6.1.7 to 6.2.2 with extra drivers (extra.lzma file), your use case my not have the same requirements, so please make you know the process for your environment regardless of the directions shown here. Collect required files ***this guide is using synology model 3617, adjust accordingly for the model you want to use*** Recommended to save your files to a unique folder on your system, in this example we will use folder "xpenology-3716-20200215" (model and timestamp) Download the 6.2 boot loader from this post: https://xpenology.com/forum/topic/12952-dsm-62-loader/ Downloaded extra drivers files from this post (this post also includes links to the synology pat file as well): ***Extra Drivers are only needed if your devices are not supported by the current boot loader files*** https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ Download the synology pat file (from the post above) Extact files for modifications Extract synoboot zip file unzip synoboot_3617.zip -d synoboot Extract extra drivers zip file unzip extra3517_v0.5_test.zip -d extra_lzma Extract Synology DSM pat file ***Requires 7zip*** Install 7zip for your linux distribution (example shown is Ubuntu) sudo apt install p7zip-full p7zip-rar Use 7zip to extract pat file 7z -odsm x DSM_DS3617xs_24922.pat Your folder should now have 3 new folders within as shown ls -1 Output: dsm <--- new folder DSM_DS3617xs_24922.pat extra3617_v0.5_test.zip extra_lzma <--- new folder synoboot <--- new folder synoboot_3617.zip Create mount folders to modify synoboot.img files make these folders to mount the partitions of the synoboot.img for editing mkdir usb mkdir usb/part1 mkdir usb/part2 mkdir usb/part3 Mount synoboot.img partitions First view the partition layout of the synoboot.img for mounting information fdisk -l synoboot/ds3617_6.2/synoboot.img Output: Disk synoboot/ds3617_6.2/synoboot.img: 50 MiB, 52428800 bytes, 102400 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: B3CAAA25-3CA1-48FA-A5B6-105ADDE4793F Device Start End Sectors Size Type synoboot/ds3617_6.2/synoboot.img1 2048 32767 30720 15M EFI System synoboot/ds3617_6.2/synoboot.img2 32768 94207 61440 30M Linux filesystem synoboot/ds3617_6.2/synoboot.img3 94208 102366 8159 4M BIOS boot Important mounting information Units byte size: here its 512 bytes Start byte for each partition: to mount these partitions you need to multiply the start byte by the unit byte size for the offset Mount partition 1 (we use bash arithmetic expansion to multiple the offset) sudo mount -o loop,offset=$((512*2048)) synoboot/ds3617_6.2/synoboot.img usb/part1 Mount partition 2 sudo mount -o loop,offset=$((512*32768)) synoboot/ds3617_6.2/synoboot.img usb/part2 Mount partition 3 ***This partition does not get modified and does not need to be mounted, but shown for those interested in looking at the contents*** sudo mount -o loop,offset=$((512*94208)) synoboot/ds3617_6.2/synoboot.img usb/part3 Collect required hardware information for modifying grub.cfg in partition 1 Get USB vid/pid information ***Run this command before plugging in your usb drive*** lsusb Output: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2c07 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Plugin your USB drive and run lsusb again to see the new device (comparing the two outputs makes this easier to know which drive is the USB) Output: Bus 002 Device 009: ID 0781:5583 SanDisk Corp. <--- new drive Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2c07 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Our USB VID is 0781 Our USB PID is 5583 Get Network Interface Card (NIC) MAC address Find MAC address of NIC on your synology device (can be found in bios, use a bootable usb linux distribution, or physical nic mac information on card label if available) Our MAC was in the bios of our motherboard, it is 90:2B:34:AC:9F:C4 If you have access to your device through cli you can use ifconfig to find the MAC address as well Get Synology Serial Number Generate a serial number for the model being used or use existing if your device is being upgraded (https://xpenogen.github.io/serial_generator/index.html) Our Serial Generated is 1130ODN024917 (Note these are not official synology serial numbers) We will use these values for modifying grub.cfg on partition 1 Modify grub.cfg on partition 1 ***VIM is the editor used to modify files, please ensure you are familiar with the editor you choose*** Edit grub.cfg sudo vi usb/part1/grub/grub.cfg Modify the following lines (Shift+i to go into insert mode in VIM) set vid=0x0781 <--- Our VID found earlier set pid=0x5583 <--- Our PID found earlier set sn=1330NZN022235 <--- Our Serial Number generated earlier set mac1=902B34AC9FC4 <--- Our NIC MAC address found earlier ***You may want to modify SataPortMap for your environment and timeout if you want a faster boot time when grub loads*** Save changes (Hit escape a few times) :wq (write and quit) Add extra driver files (optional) to partition 2 ***Only needed if you require extra drivers*** List current files in partition 2 to view permissions and ownership ls -la usb/part2/ Output: total 11068 drwxr-xr-x 2 root root 16384 Dec 31 1969 ./ drwxrwxr-x 3 user user 4096 Feb 16 09:46 ../ -rwxr-xr-x 1 root root 1860613 Aug 1 2018 extra.lzma* -rwxr-xr-x 1 root root 6441636 Aug 1 2018 rd.gz* -rwxr-xr-x 1 root root 3006864 Aug 1 2018 zImage* Copy extra.lzma file to partition 2 sudo cp extra_lzma/extra.lzma usb/part2/ sudo cp dsm/rd.gz usb/part2/ sudo cp dsm/zImage usb/part2/ List files in partition 2 to view permissions and ownership after copy ls -la usb/part2/ Output: total 13748 drwxr-xr-x 2 root root 16384 Dec 31 1969 ./ drwxrwxr-x 3 user user 4096 Feb 16 09:46 ../ -rwxr-xr-x 1 root root 4570532 Feb 16 09:55 extra.lzma* -rwxr-xr-x 1 root root 6465192 Feb 16 09:58 rd.gz* -rwxr-xr-x 1 root root 3019392 Feb 16 09:58 zImage* Each file should retain root ownership and permissions, the files copied should have a different size and date stamp Unmount partitions sudo umount usb/part1/ sudo umount usb/part2/ sudo umount usb/part3/ confirm each partition is unmounted ls -la usb/part1/ ls -la usb/part2/ ls -la usb/part3/ Output: total 8 drwxrwxr-x 2 user user 4096 Feb 16 09:46 ./ drwxrwxr-x 3 user user 4096 Feb 16 09:46 ../ Find USB device name Ensure USB drive is unplugged ls -1 /dev/sd* Output: /dev/sda /dev/sda1 This shows the existing storage devices, sda is the drive (my laptop root hdd), sda1 is the first partition Plug in your USB drive ls -1 /dev/sd* Output: /dev/sda /dev/sda1 /dev/sdb /dev/sdb1 /dev/sdb2 /dev/sdb3 You may not see the same partitions, but you want to see the additional device (sdb) showing Format USB drive ***Please backup any data you want to retain from this drive, as it will be lost*** ***Commands shown here are potentially dangerous, make sure you know the correct drives to format and double check your syntax (or use an alternative tool within your comfort level)*** Unmount any partitions that may have auto mounted (example shown here attempts to unmount any drives listed for the USB drive device sdb) sudo umount /dev/sdb1 sudo umount /dev/sdb2 sudo umount /dev/sdb3 Wipe all filesystems off existing drive sudo wipefs --all /dev/sdb Output: /dev/sdb: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54 /dev/sdb: 8 bytes were erased at offset 0xe51fffe00 (gpt): 45 46 49 20 50 41 52 54 /dev/sdb: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa /dev/sdb: calling ioctl to re-read partition table: Success Check USB drive layout sudo fdisk -l /dev/sdb Output: Disk /dev/sdb: 57.3 GiB, 61505273856 bytes, 120127488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Confirm clean output without any partitions remaining Write Synoboot Image to USB drive ***Commands shown here are potentially dangerous, make sure you know the correct drives to write to and double check your syntax*** sudo dd if=synoboot/ds3617_6.2/synoboot.img of=/dev/sdb bs=512 Output: 102400+0 records in 102400+0 records out 52428800 bytes (52 MB, 50 MiB) copied, 9.14248 s, 5.7 MB/s Check drive and partition information to ensure it was written correctly sudo fdisk -l /dev/sdb Output: GPT PMBR size mismatch (102399 != 120127487) will be corrected by w(rite). <--- this can be ignored, it alerts because fdisk does not support GPT partitions Disk /dev/sdb: 57.3 GiB, 61505273856 bytes, 120127488 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: B3CAAA25-3CA1-48FA-A5B6-105ADDE4793F Device Start End Sectors Size Type /dev/sdb1 2048 32767 30720 15M EFI System /dev/sdb2 32768 94207 61440 30M Linux filesystem /dev/sdb3 94208 102366 8159 4M BIOS boot Unmount and plug into your Xpenology device sudo umount /dev/sdb1 sudo umount /dev/sdb2 sudo umount /dev/sdb3 Last minute changes after write You can still make changes to the paritions/files on the USB drive by mounting the partition on your system sudo mount /dev/sdb1 usb/part1 sudo mount /dev/sdb2 usb/part2 sudo mount /dev/sdb3 usb/part3 This mounts the usb drive directly to the folder specified, you can edit files as per previous steps in the guide
  10. 2 points
    Well I didn't follow the guide perfectly. Previously I created the flash drive with custom extra.lzma & extra2.lzma without zImage and rd.gz files from DSM 6.2.2... so it couldn't detect my Realtek NIC. Now I was using 6.2.1 with Jun's loader. I updated my system to 6.2.2 from DSM OS.. during first reboot i manually turn off the system and removed USB Drive. Then I Inserted the USB drive to other PC, mounted partition 2 and copied and replaced just extra.lzma. Then I inserted the USB Drive to Synology system and booted the system. It showed up in my LAN and installed the 6.2.2 update successfully.
  11. 2 points
    Alors Bonne nouvelle !!! Je viens de faire cette mise a jour et tout fonctionne. J'ai encore quelques tests a faire mais tout semble fonctionner Pour ceux qui ont un doute : Lancez la mise a jour lorsque ça redémarre éteignez tout enlevez la clef et placez l'extra 0.5 remettre la clef et redémarrez et normalement tout fonctionne pour ma part j'ai du faire un hard reset de plus c'est tout
  12. 2 points
    самая стабильная 8.0.3, она работает без перезапуска службы.
  13. 2 points
    That particular server has been up on 6.1.x since October 2017. It's a pretty complicated build, so I haven't rushed to upgrade it, although I think all its services are now supportable on 1.03b and DSM 6.2.2. The only inbound services on my network are IP and port firewalled VPN termination points and a guacamole (remote access proxy) server. Personally, I wouldn't ever expose a Synology server directly to the Internet for any reason. Therefore, I don't have too much heartburn about the latest security patches not being available. Even on 6.2.2, Synology lags so far behind core OS support, I'm not sure it matters all that much.
  14. 2 points
    Тестируем 8.2.7-6221-х64, отписываемся.
  15. 2 points
    new drivers up - lets see who bricks his unit first because of not reading properly (yes i know its a lot of text)
  16. 2 points
    Hey! New to NAS systems and Xpenology, but everything online pointed this way for DIY home servers. Trying to set up my home ecosystem to eliminate our digital clutter.
  17. 2 points
    Hi, You might be also interested in the search engine I've made: https://search.synopackage.com . There are also packages source list, which I'm trying to keep up to date. This is pretty hard task, because many of those sources are temporaly unavailable and after a while they back online again Feel free to use it and comment
  18. 2 points
    my answer was just half joking, also a suggestion it is a question how easy it should be made to pirate things, there might be more consequences when it gets to common i wish it would be that way its just i devote much time into this, i'm not just using what i found here, turn around and walk away, there was and is the thought of giving something back (i dont need the drivers from the package for myself, i do have hardware that is able to get along with the native dsm drivers, compared with the time it would be much cheaper just to buy a synology box) no, but it can be be seen that way the patch as it is now is extremely comfy and the author did invest some time to make it that way (and its obvious he does not need it this way for himself) there can also be the question that you ask to much and did not ask yourself how can you help, if you think its not enough documented then make this tutorial instead of asking others to do it also most people have special interests and if someone likes to crack a nut using reverse engineering and disassembler he might not be that interested in writing a tutorial that even someone who never used linux can use, thats the point where we might work together - i have no coding skill, so what, i still can help
  19. 2 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 The download link/folder also contains @IG-88's extra.lzma (V0.6) for the DS918+. 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. 2 points
    @Timbo On a "home-lab-server" only capable of ESXi v5.5.0, I'm running a virtual DSM 6.1.7-15284 Update 3 with no problems. On my N54L's I run the same version of DSM as baremetal.
  21. 2 points
    @Polanskiman exactly! The patch patches a function in synocodectool that checks with synologys servers if the serial number is valid and prevents it from erroring out. I added multipatch support two days ago, so applications like videostation (which ship with their own version) can also be patched. You can choose which binary you want to patch from a handydandy little menu. Furthermore, I also uploaded all original & patched binaries going back to DSM 6.0 to my Github repository. Should ******* hit the fan you can either try restoring the app from the automatically created backup or just download the original version from Github. Regarding overwrites: Until now Synology only updated synocodectool in releases (namely 6.0, 6.1, 6.1.2, 6.1.4, 6.2.1), so critical updates should not affect the binary. The patch itself checks your dsm version & the hash of the binary and compares it to a predefined list of hashes before patching so you do not accidentally patch an unsupported version. Should a new versions of synocodectool be released, I will update the script to include it.
  22. 2 points
    В декабре 2019 перешел на двухголовый huanan x79-16D. Плату покупал на авите, память на али, один проц достался на халяву, второй купил на ali. Сейчас у меня 44 ядра (88 потоков), 256 оперативы, нвороченный adaptec, 4xLAN недорогой hp (который по сути есть переименованный дорогой intel) и видеокарта. Переезд esxi и подключение виртуалок прошло без проблем. Потрудиться пришлось с opnsense из-за зоопарка сетевых интерфейсов. Что ещё нового: добавил терабайт m.2 как кэш в esxi; plex - отдал 64Г оперативы (у меня в нём много пользователей, все заметили ускорение проигрывания музыки), нарисовался касяк: бесплатная лицензия esxi позволяет добавить в вм только 8 ядер, а планировал 16. Засада! Теперь смотрю цены на esxi (если кто подскажет дельный совет по лицензии - буду премного благодарен). Изначально хотел поставить десятку на голое железо и посмотреть графики процессоров в диспетчере задач, но в процессе забыл про это дело...
  23. 2 points
    Here is a working ams as above for "loader 1.03b with 3517 DSM 6.2.2" please extract into /volume1/Downloads/ as above My previous zip contains some excess directories and duplicate library files; I have added the hpilo.ko for 918 / 3157 as labeled (thanks IG-88) this is tested on my Microserver g8 running 2.70 ilo To start, execute: insmod /volume1/Downloads/hp-ams/hpilo.ko sudo LD_LIBRARY_PATH=/volume1/Downloads/hp-ams/lib /volume1/Downloads/hp-ams/sbin/amsHelper -f -I0 -M1,5,14,16,18,23,99 script something like: more /usr/local/etc/rc.d/S99HP-AMS.sh #!/bin/sh modprobe /volume1/Downloads/hp-ams/hpilo.ko sudo LD_LIBRARY_PATH=/volume1/Downloads/hp-ams/lib /volume1/Downloads/hp-ams/sbin/amsHelper -f -I0 -M1,5,14,16,18,23,99 You'll see the below messages on both platforms if it is working, safe to ignore... NET-SNMP version 5.7.3 AgentX subagent connected error: Unable to open /usr/lib/rpm/rpmrc for reading: No such file or directory. Can't find directory of RPM packages System used: Microserver G8 HP Ethernet 1Gb 2-port 361T Adapter1.52, 0x80000fc5, 1.1752.0Slot 1 iLO2.70 May 07 2019System Board Intelligent Platform Abstraction Data0.00System Board Intelligent ProvisioningN/ASystem Board Redundant System ROMJ06 05/21/2018System Board Server Platform Services (SPS) Firmware2.2.0.31.2System Board System Programmable Logic DeviceVersion 0x06System Board System ROMJ06 04/04/2019System Board System ROM Bootblock02/04/2012 hp-ams3517.zip
  24. 2 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. Просьба к админам прибить тему в шапке и дать мне доступ на редактирование первого поста этой темы, буду добавлять по мере поступления вопросов, ибо задолбали оленеводы, которые задают вопросы по установке, во всех подряд темах.
  25. 2 points
    Failure to comply with the below guidelines will result in your topic or post being deleted. ---------------------------IF YOU ARE CREATING A TOPIC SCROLL DOWN TO THE NEXT SECTION--------------------------- ---------------------------IF YOU ARE SIMPLY MAKING A POST READ RIGHT BELOW--------------------------- I remind everyone that the DSM Updates Reporting forum is SOLELY AIMED at REPORTING SUCCESSFUL or UNSUCCESSFUL updates. This forum is NOT meant for asking questions whether they are in direct connection with the update or not. Such posts will be removed. Please follow the template below when making a post in this forum. It makes it easier for others to check the status of an update. - Outcome of the update: (Successful update or not) - DSM version prior update: (DSM 6.1.7-15284 UPDATE 3) - Loader version and model (3615xs or 3617xs or 916+ or 918+) - Using custom extra.lzma: (Yes / No and from who / version) - Installation type: (BAREMETAL / VM / Hardware details (specially NIC)) - Additional comments: (Problems encountered etc. No questions allowed here. Comments should be in direct connection to the upgrade. All other comments will be removed) EXAMPLE: - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.3 UPDATE 7 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Gigabyte H97N - NIC: Intel I217-V & Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10) - Additional comments: HANGED BUT A REBOOT FIXED IT You can copy paste the above and modify the data according to your specific situation. Keep UPPER CASE and use RED color in the first line if the update is UNSUCCESSFUL. Use BOLD as above. If you have specific comments because there is a problem with an update use the Additional Comments line to mention them. If you have a question then use the appropriate sub-forum, not this one. When posting, please DO NOT refer to your hardware in your signature or post links to your configuration from any external website or from your About Me section. If for some reason you modify those (or the link breaks) one day then your post becomes useless to the community. ---------------------------IF YOU ARE CREATING A TOPIC READ BELOW---------------------------------- If you are the one creating a topic because a new update has been released by Synology please stick to the following guideline: 1 - Visit https://xpenology.com/forum/forum/78-critical-updates/ first to check that the topic has not been created. If not, then use the following topic naming convention: If it is a critical update: DSM X.X.X-XXXXX - Update X If it is an intermediate update: DSM X.X.X-XXXXX If it is a major update: DSM X.X-XXXXX 2 - Add the following tags to the topic according to the type of update: If it is a critical update: dsm x.x.x, critical update If it is an intermediate update: dsm x.x.x, intermediate update If it is a major update: dsm x.x.x, major update 3 - Visit this topic and create the OP following the same format: Screenshot of the release note Link to the Release note Copy and paste release note content using the spoiler tag as shown below
  26. 1 point
    Hey a newbie (to here - but over 40 years IT experience!!) I've had a DS412+ for the last 8 years and finally decided to make the move to a new model. I then discovered Xpenology in the last week and have never looked back... I am running: all brand new hardware, latest gen: Fractal Node304 case (brilliant ITX case) Intel i3-9100 AsRock Z390M-ITX motherboard (dual intel nics onboard, 6x sata connectors, M.2 slot) 8Gb RAM 256Gb Adata 256Gb SSD 4 x 8Tb Seagate Ironwolf (from old NAS) running Jun's Loader 1.04b std version with the std driver extension (hw transcode working, dual nic's working) setup as a 918+ This post from IG-88 is BRILLIANT!! "Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+" DSM 6.2.2-24922 Update 5 The above setup cost around 2/3 of the price here for a real synology DS918+, at significantly higher performance and much more flexibility. A few comments to hopefully help people here: it is surprisingly easy to initially setup - the turorials on here are fabulous and I am very impressed with the community Test and play with the setup using an old sata drive to work it out before going to your real disks You CAN migrate from an old Synology NAS to your new Xpenology !! I could not find anything on this in here so did a full backup first and then put the disks into the new setup in the same drive sequence as on the DS412+. On first boot, with NO change to the grub.cfg I had working, it asked if I wanted to migrate and it did successfully!! I had everything in an SHR array. I used the dummy serial number in the grub, but used the ream mac addresses from my old Synology and all the transcoding issues seem to have gone. It is stupidly fast now compared to my old one, and from the specs I reckon that I would close to double the performance of the 918+ too. Issues: I've just plugged the SSD in and DSM can't see it - but it shows up in the sudo fdisk -l as per below Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes I've also plugged in an Intel X520-DA2 2x SFP+ 10Gb network card and it is not being seen at all - neither in ifconfig, or in DSM. I set the grub.cfg file with 4 x nics and added two more macs, mac3 and 4, continuing the sequence from my original macs. Can anyone please advise me where i should look or what I may be doing wrong? I don't know Linux well and cannot find any reasonable hwinfo type commands here...
  27. 1 point
    I suppose you were referring to the source code of the loader. In simple terms the source code is not public and never was. Only one person is responsible for creating the current loader. As for not being able to collaborate that's just non sense, sorry. Most people here started from scratch and ended up collaborating more than what they thought they could. Perhaps you should stick around see how you can help. I am not a coder myself yet I have created several tutorials, I give advise and administer the forum on a daily basis. Like everyone I am not always right but we are all here to help each other. What kind of "web stuff" do you develop?
  28. 1 point
    So @IG-88 I am a little embarrass to say this. But I think the problem is between the keyboard and the chair. It turns out I plugged xpenology into an old switch which I didn't own. It didn't support 1Gbps AND X557 didn't seem to support 100MBps. So once I fixed that. I was able to boot up and install 918+ without any problem. So about picking which DS3617xs vs DS918+ loader and the potential implication. which one should I really pick? It seems like from your comment and also the table in I wouldn't have transcode either way. So what is the advantage picking one over the other? is UEFI important? I am going to see if I have a chance to install ds3617xs and see if it work and reported back. Thank you @IG-88 for your help
  29. 1 point
    the 0.5 extra does did you also copy the new zImage and rd.gz? beside activating CSM legacy mode in bios and a reboot did you also choose the right boot device, the usb might show up 2x as uefi and 1x as legacy maybe try loader 1.04b 918+ with 0.8_recovery extra/extra2 that loader supports legacy and uefi
  30. 1 point
    Hello! I am xpenology user. And I am an IT engineer who creates shell scripts as hobbies. Please understand that it is written by a google translate site. because i’m korean who is not fluent in English. I created a tool to change cpu information for Xpenology’s users. Modify the actual cpu name and cores of your pc or server. Howto Run ============================================================= 1. Download attached file on your PC (ch_cpuinfo.tar) (ch_cpuinfo_en.tar) / (ch_cpuinfo_kr.tar is file for korean) 2. Upload file to your DSM location (by filestation, sftp, webdav etc....) 3. Connect to ssh by admin account. (dsm > control panel > terminal & snmp > terminal > enable ssh check) 4. Switch user to root: sudo su - (input admin password) 5. Change directory to where ch_cpuinfo.tar file is located: cd /volume1/temp 6. Decompress file & check file: tar xvf ch_cpuinfo.tar ls -lrt (check root’s run auth) 7. Run to Binary file ./ch_cpuinfo or ./ch_cpuinfo.sh (If you use busybox in DSM 5.x, you can use it as a source file) 8. When you execute it, proceed according to the description that is output. 9. Check your DSM’s CPU name, CPU cores at “information center” ==================================================== Addtional, Adjust binary to excute file made by shc(http://www.datsi.fi.upm.es/~frosal) The tool does not inclue worms, bad code. If you want to edit the CPU information yourself manually, please refer to the contents below. ——————————————————————————————————————————————————————————————— Location : /usr/syno/synoman/webman/modules/AdminCenter Source : admin_center.js / admin_center.js.gz(above 6.2) Add Before -> if(Ext.isDefined(h.cpu_vendor)&&Ext.isDefined(h.cpu_family)&&Ext.isDefined(h.cpu_series)){ o.push([_T("status","cpu_model_name"),String.format("{0} {1} {2}",h.cpu_vendor,h.cpu_family,h.cpu_series)])} if(Ext.isDefined(h.cpu_cores)){o.push([_T("status","cpu_cores"),h.cpu_cores])} Add contents: h.cpu_vendor="Intel";h.cpu_family="Xeon";h.cpu_series="E3-1220 V3";h.cpu_cores="4 Cores (1 CPU/4 Cores | 4 Threads)"; h.cpu_detail="<a href='https://ark.intel.com/content/www/us/en/ark/search.html?_charset_=UTF-8&q=E3-1220 V3' target=_blank>detail</a>" Change contens: String.format("{0} {1} {2}",h.cpu_vendor,h.cpu_family,h.cpu_series) to String.format("{0} {1} {2} {3}",h.cpu_vendor,h.cpu_family,h.cpu_series,h.cpu_detail) ——————————————————————————————————————————————————————————————— Finally, All descriptions are based on version 6.2, and the actual executable file supports both 5.x and 6.x. Publish the source through github(https://github.com/FOXBI/ch_cpuinfo). For versions DSM 6.x and later, you can use the binary as before. If you use busybox in DSM 5.x, you can use it as a source file(ch_cpuinfo.sh). Please contact me by comment or bug report, i’ll respond to you as much as possible within my ability. Test & Made Environment ———————————————————————————————————— Base Server : HP ML310e v2 gen8 + VMware ESXi 6.0 + RDM DSM : 6.2.2-24922 Update 2 (DS3615xs/DS3617xs/918+) 6.1-15284 Update 2 (DS3615xs) Base Server : Intel E5-2630 v2 + VMware ESXi 6.7u2 DSM : 6.2.2-24922 Update 2 (DS3617xs) ———————————————————————————————————— Change Log 1. Support DSM 6.2.2-24922 Update 2 2. Consolidate and change to run in accordance with used DSM language environment(Only One File) 3. Add link for cpu detail information(Intel, AMD Site Link) - Support above version 6.x Thank you!! Have a nice day!! ============================================= Download links: ch_cpuinfo ver 1.1.0-r01 - new version update -> ch_cpuinfo.tar Reference images # 1.04b + DS918+ # 1.03b + DS3615xs # 1.03b + DS3617xs # Normal output is possible even when using more than 8core.
  31. 1 point
    Bonsoir, Je rebondis sur cette phrase : Si les VM ne concernent que SS, alors il est peut-être plus judicieux de ne pas mapper de disques en RDM mais d'utiliser des vmdk basiques sur un disque (ou plusieurs en raid éventuellement) dans un datastore. Personnellement, je n'utilise pas SS, mais je suppose que l'affichage se fait via une interface Web. Dans ce cas, il ne doit pas être trop compliqué de créer un site Web regroupant (via des onglets, des iframes ou autres) l'affichage des différentes entités SS des VM. Avec une configuration lue dans un fichier (php de préférence) pour permettre d'étendre et de modifier facilement le site. Le trafic réseau restera dans switch virtuel. C'est juste une idée pour pousser le bouchon un peu plus loin. Jacques
  32. 1 point
    Did you change your BIOS to boot in Legacy mode? ACPI boot is not supported on 1.03b.
  33. 1 point
    This is a repost of an archive I posted in 2015. This method works for DSM 6.2 using Jun's loader 1.03b for me. 1) Enable SSH and ssh into your DiskStation 2) Become root ( sudo -i ) 3) Make a mount point ( mkdir -p /tmp/mountMe ) 4) cd into /dev ( cd /dev ) 5) mount synoboot1 to your mount point ( mount -t vfat synoboot1 /tmp/mountMe ) 6) Profit! admin@DiskStation:~# sudo -i root@DiskStation:~# mkdir -p /tmp/mountMe root@DiskStation:~# cd /dev root@DiskStation:/dev# mount -t vfat synoboot1 /tmp/mountMe root@DiskStation:/dev# ls -l /tmp/mountMe total 2554 -rwxr-xr-x 1 root root 2605216 Aug 1 10:40 bzImage drwxr-xr-x 3 root root 2048 Aug 1 10:40 EFI drwxr-xr-x 6 root root 2048 Aug 1 10:40 grub -rwxr-xr-x 1 root root 103 Jul 3 15:09 GRUB_VER -rwxr-xr-x 1 root root 225 Aug 1 10:40 info.txt root@DiskStation:/dev#
  34. 1 point
    Нет. Доступ возможен местами и при наличии валидной связки Серийник - МАК Active Backups работает. По Cloud Station не скажу, не использовал Как и из обычного RAID можно вывести один избыточный хард, но RAID будет вопить и требовать его вернуть или заменить.
  35. 1 point
    Dans DSM 6, avec File Station : Cliquer sur Paramètres / Connexion à distance / Configuration de la connexion Cliquer sur l'icone FTP Entrer les paramètres de connexion Valider Le serveur distant apparaît dans la liste des dossiers sur la gauche. Jacques
  36. 1 point
    you dont write anyhing about the loader, dsm version or extra driver package used in general this type of behavior point to cable and switch, not the driver
  37. 1 point
    @The_Dave Regarding HW transcoding - if all the other prerequisites are met( loader 1.04b & /dev/dri exists) then it activates hw transcoding for all synology apps (i.e. Moments, VideoStation, PhotoStation, AudioStation..) ------ Plex, Emby & Jellyfin should be unaffected by this patch since they don't use synologys license checking mechanism and come bundled with their own version of ffmpeg.
  38. 1 point
    Hello! This is a short guide about how to downgrade from DSM 6.2 to DSM 6.1 after a failed upgrade. I made this mistake myself, so i'm sharing how to fix it! Your going to need a spare HDD or SSD. Make sure there is nothing on it. You've installed DSM before, so you should have your synoboot.img from JunsLoader. Your current bootloader on your USB in now NONFUNCTIONING, you will need to reflash your USB with JunsLoader. Once you have your new, reflashed USB stick, unplug ALL drives from the motherboard. Make sure there are NO SATA interfaces connected. Plug in your new, empty drive to the motherboard and boot from the USB stick. (You will need a keyboard for this step) The first option in the GRUB interface is what you are looking for. Use http://find.synology.com or Synology Web Assistant to find your DSM. Follow the steps and install DSM 6.1 from a PAT file. DO NOT INSTALL 6.2 IF YOU LEFT A DRIVE IN IT WILL SAY RECOVER. GOTO 2. Let Synology do its thing and eventually you will have a working 6.1. While the PC is ON, connect the drives to the motherboard (with you data on it). Under Storage Manager they will pop up and say Unused. You might need to reboot, at this option. It took me some fiddling around, but eventually Synology will prompt you with a Recover Crashed Partition prompt. Click Yes. All of your data will appear, and Synology will automatically perform RAID scrubbing.
  39. 1 point
    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. 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. Common drivers missing from this platform, or newer driver versions that support the latest silicon may be available by installing additional compiled modules. DSM 6.1.7 DS3615 V1.04 2019-Feb-04.xls DSM 6.2.1 DS3615 V1.0 2019-Feb-04.xls
  40. 1 point
    This version is alpha, as the loader 1.03a2 is, so DO NOT use this on a "production" systems and be prepared to loose the data you have on the "test-system" (I recommend you have a very recent backup) !!!all sata_* and pata_* drivers are still not working because of the kernel source changes Synology did (same as in kernel 3.10.102 used and modded by Synology), as long as no one writes a patch for this I can use to fix this, it will stay this way !!! HP SmartArray Controller driver (hpsa.ko) is back in for testing (for now the one that comes with kernel 4.4.59), my P400 i had access to was to old for this driver so please try to test, newer controller even seem to have a IT mode so if present try it with this mode To check if the hardware is supported with a driver, use a running DSM installation or boot a live Ubuntu from usb. In console type the following: lspci -k | grep 'Kernel driver' That command will list the used kernel modules for the hardware. Modules for network and storage will be listed. Compare that with the list of modules that comes with the extra.lzma ramdisks provided below. extra.lzma for DS918+ v0.2 (still online for testing against new 0.4) http://s000.tinyupload.com/?file_id=40794274174411841232 extra.lzma for DS918+ v0.3 http://s000.tinyupload.com/?file_id=09865768016965468337 extra.lzma for DS918+ v0.4 http://s000.tinyupload.com/?file_id=85078902011391385959 extra.lzma for DS918+ v0.5_test http://s000.tinyupload.com/?file_id=04554930831776996450 Note: the driver list below with related hardware is based on Trantor/Quicknick's older list for 5.2 and 6.0 so thanks goes to them and all others who helped to build the older list for 5.2 and 6.0. Caption (…) Not compiled for now, ask for it […] Either confirmed by users that it is not working OR not supported for DSM 6.2 (kernel 4.4.59) OR does not load at all. Driver was compiled/tested but removed - if someone finds a way to get it working in some way, tell us here and it will be added  If you wish to make a driver request do so in the topic linked below: If you wish to discuss problems about modules in these ramdisks then drop a post below. Please be specific and provide relevant information such as: ramdisk version, loader model, motherboard and any additional storage/networks cards present in the system. Other things good to know about DS918+ image and loader 1.03a2: 1. DS918+ image comes with a limit for 2 internal network ports in synoinfo.conf (the original hardware has two ports and does not have a pcie slot for extending) jun's loader does not changes this (now?), so if you plan to user more then 2 ports you will have to manually change the synoinfo.conf (3615 and 3617 are bigger business models and have options for additional network card, the default from synology is 8 on this systems) further information can be read here: 2. hardware transcoding seems to crash the system when a monitor is attached, unplug monitor, reboot try again to see if there is decoding hardware present you can try this (there should be something in like card0) ls -al /dev/dri/ when using plex you should download the 64bit version from website, with plex pass active (hardware-accelerated streaming is a premium feature and requires an payed active Plex Pass subscription), Settings > Server > Transcoder, Turn on Show Advanced, Turn on Use hardware acceleration when available 3. if your screen goes blank during boot and the system does not show up in network the kernel might have crashed on boot while loading i915.ko driver (CPU internal GPU) look in your bios for a legacy mode option, disable it and try again (boot process and crash can be seen when using a "good old" serial cable and a console program like putty on a 2nd computer - that's rarely done but if you want to know for sure, that's your way to find out, DSM does not have a typical boot screen that shows log info and login prompt after boot, that's redirected to the serial port)
  41. 1 point
    with this line: support_syno_hybrid_raid = "yes" above supportphoto="yes" ? Cool! Thanks for this supercool hint! That's the one. I think you also must comment out #supportraidgroup="yes"
  42. 1 point
    At some point you have to make some decisions on which features you want to support. NVMe direct support is only in DS918. RAIDF1 support (if you ever need it) is only in 3615/3617. 10Gbe and SAS support is better in 3615/3617 but somewhat mitigated if you experiment with add-in drivers from IG-88. My main system is similar to yours - 10Gbe, and I use enterprise SATA SSD drives now so RAIDF1 is important. I also have two U.2 NVMe drives, and the only way I found to get everything to work was to use ESXi to run DS3615 (for RAID F1 and 10Gbe support) and present the NVMe devices via RDM.
  43. 1 point
    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 >
  44. 1 point
    nice find, i guess i will have a look and check out why DS1019+ is "better" then 918+ to justify the effort of hacking it too, its just a "smaller" unit not a business unit edit: looks like the 1019+ is nearly the same hardware as 918+ and there is no "new" hack, more a mod to juns loader and they used my 918+ extra/extra2 drivers - not newly compiled ones for that model (i hope they at least give credit by mentioning this forum as source) atm i cant see anything useful compared to 918+ - any info why this 1019+ was done? here are some translations for the chinese stuff http://www.gebi1.com/thread-294293-1-1.html 2019/12/22 Added snail-only version, the system is downgraded to 6.21-up6 (the highest version supported by snail). DS1019 + introduction: 1. Made with UEFI boot mode. ASRock J3455 and 5th generation processors and above are supported. Specific self-test (the motherboard must be set to uefi type to boot, otherwise it cannot be connected) 2.Perfect support for solid state drives 3. The IMG package has been integrated with the system (model DS1019 +, version number: 6.22-up4) and has been installed. You can enter the system after booting. 4. Integrate a part of the network card driver, which can support the operation of non-internet network cards. Anyone who has used 2 in 1 knows that this image only supports writing to the hard disk, and writing to a U disk does not work. You can prepare a solid or mechanical hard disk greater than or equal to 16G, and expand the storage partition later. There are many tutorials in the forum. Do your own research. Don't repeat. It is based on the JUN mod base package. Are there any unknown bugs that have not been found? If any bugs are found, I do not know how to fix them anyway. -------------------------------------------------- Files: these are 2 disk images (not for flash drives) with several partitions and an installed system DSM : 6.2.1, 6.2.2 UEFI : yes Installing the system from scratch has not been tested. login : admin password : 123456 https://mega.nz/#F!Yg5GXQ5A!GV6wJnppgk8In0EAheRZIw
  45. 1 point
    Записываем загрузочную флешку. Редактируем grub.cfg программой OSFMount Начальная стадия установки DSM, это создание загрузочной флешки. После определения Хардового конфига (железо, его конфигурация) и дальнейших потребностей для себя от DSM, определяем версию DSM загрузчика под неё. На данный момент, имеется три версии загрузчика под разные эмуляции DSM , это : ds3615 , ds3617, ds918+ Под ds3615 , ds3617 - последний загрузчик v1.03 b Под ds918+ - последний загрузчик v1.04b Имеются и более ранние версии, всё зависит от вашей конфигурации и желаемого результата. Совместимость загрузчика и железа (возможно, список не полный): Все версии собраны здесь: https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg!7AoyySoS И так..... Определились с загрузчиком, начинаем его редактировать под себя и записываем на флешку. Нам необходимы, любая флешка от 128мб и установленные программы: OSFMount - небольшая бесплатная утилита, которая позволяет монтировать ранее сделанные образы дисков и представлять их в виде виртуальных приводов. Необходима для монтирования и последующей редакции образа загрузчика. https://www.osforensics.com/tools/mount-disk-images.html Notepad++ - свободный текстовый редактор с открытым исходным кодом для Windows. Необходима для редактирования grub.cfg https://notepad-plus-plus.org/ Rufus - это утилита, которая помогает форматировать и создавать загрузочные Flash. Необходима для записи загрузчика. https://rufus.ie/ Данные программы, кроме OSFMount, могут быть и другими, в зависимости от вашего предпочтения. Скачиваем необходимый вам загручик и открываем его в программе OSFMount, монтируем образ. Открываем ранее скачанный образ загрузчика Выбираем необходимый нам раздел. В нём находится нужный нам для редакции файл grub.cfg Обязательно снимаем галочку с опции: read only - только для чтения. Монтируем образ и открываем необходимый нам файл grub.cfg Редактируем в Notepad++ Редактируем значения: set vid=0x(Ваш vid - обязательно) set pid=0x(Ваш pid - обязательно) К вопросу о значении "0x" (мнения разнятся)..... Загрузчик имеет исходный формат (0xabcd). Значение 0x говорит что это шестнадцатеричный код. Если VID и PID вашей флешки состоит из цифр (1234), то без значения "0x" загрузчик работает , если имеются буквы (12АБ), то без значения "0x" может не сработать. Потому лучше прописывайте VID и PID как в исходнике: "0xВаши данные" set sn=Ваш серийник set mac1=Ваш mac1 set mac1=Ваш mac2,3,4 (если сетевая карта имеет больше одного порта) Значения set sn и set mac можно оставить по дефолту, если ван не нужны такие функции, как транскодинг, Push уведомления и QuickConnect. Так же, необязательно, но лучше отредактировать значение: set timeout='1' - изменить значение "1" на другое, скажем на 5 или больше. Это значение отвечает на время видимости начального загрузчика из трёх пунктов. Многие не успевают прочесть то, что там написано. Изменение этого значения даст возможность увеличить время отображения начальной страницы Отредактировав под себя grub.cfg , сохраняем его и размонтируем образ Теперь можно записать загрузчик на флешку Открываем , выбираем наш, уже правленый образ загрузчика и записываем на флешку Ну вот и всё, загрузочная флешка готова. Можно начинать установку DSM Из личного опыта........ Всегда сохраняйте свой, правленый образ загрузчика. Всякое может случиться и всегда полезно иметь уже готовый для записи образ. Лично я, всегда делаю ДВЕ флешки. Тоже, на непредвиденный случай.
  46. 1 point
    THANKS! This is absolutely what I needed. The QNAP TS-x69 Pro board has the option to disable UEFI boot and boot just legacy but for some reason the normal bootloader from the Jun's would not boot in legacy mode on this device. UEFI would boot but then no ethernet. I know legacy on MBR worked ok too as I booted FreeDOS usb stick. Thanks to your modded MBR loader its working great! Damn QNAP OS is limited to 3GB or it locks up and also prevents SSD cach on this older model. XPeneology and DSM breaks both those beariers and give this old NAS new life 8GB RAM and a pair of 500GB SSDs for cache.
  47. 1 point
    No attack so far, but I remember a time when I could see those many bots knock at the door and be blocked in real time thanks to the DSM notifications, it was very frightening. Now I try to be less naive, there's surely room for improvement but here's what I did. - admin account is disabled - I changed the default 5000/5001 DSM ports - disabled http access outside my local network, it's https only with let's encrypt certificate. - added two-factor authentication to all accounts - enabled auto block after 2 failed attempts within 20 minutes (well, this one is a bit excessive...) - allowed DSM access to my own country only in DSM firewall. Good luck guys!
  48. 1 point
    I've been under attack for a couple of days now and what's impressive is that the amount of IP's they have at their disposal(643 currently) Anyway here's a blacklist I've put together from all the attacking IP's if you want to block them at your gateway. Additionally, make sure to disable your admin account as that seems to be the only account they are targeting Blacklist.txt Here's how it will look in the auth log. 2019-07-29T08:11:03-04:00 Hostname synocgid: pam_unix(webui:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=139.59.84.30 user=admin 2019-07-29T08:11:48-04:00 Hostname synocgid: pam_unix(webui:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=52.221.135.26 user=admin 2019-07-29T08:14:37-04:00 Hostname synocgid: pam_unix(webui:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=128.199.80.77 user=admin 2019-07-29T08:16:22-04:00 Hostname synocgid: pam_unix(webui:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=206.189.119.148 user=admin PS. I guess if you Synology is not open to port 5000 your probably OK for now.
  49. 1 point
    Today my Synology can't login in DSM!!! First, I named it as synology_A. There is another Synology it works well,named it as synology_B. synology_A info: Product:DS3617xs Version:DSM 6.1.5-15254 Update 1 bootloader:DS3617xs 6.1 Jun's Mod V1.02b Then I telnet in Synology telnet x.x.x.x sudo -i #login in as root, password is same as admin. Then I compare synology_A and synology_B's Process.I find synology_A has many [defunct] process. root@synology_A:~# ps -ef | grep cgi root 2948 10340 0 Mar20 ? 00:00:00 [synoscgi_______] <defunct> root 10280 1 0 Mar19 ? 00:00:08 /usr/syno/sbin/synocgid -D root 10340 1 0 Mar19 ? 00:00:26 synoscgi system 10470 10340 0 Mar19 ? 00:00:00 synoscgi system 29109 10340 0 17:28 ? 00:00:00 synoscgi root 29180 29148 0 17:30 pts/5 00:00:00 grep --color=auto cgi system 31659 10340 0 Mar20 ? 00:00:00 synoscgi system 31834 10340 0 Mar20 ? 00:00:00 synoscgi system 31924 10340 0 Mar20 ? 00:00:00 synoscgi Kill the parent process: root@synology_A:~# kill -9 10340 root@synology_A:~# ps -ef | grep cgi root 10280 1 0 Mar19 ? 00:00:08 /usr/syno/sbin/synocgid -D root 29205 29148 0 17:30 pts/5 00:00:00 grep --color=auto cgi Then I start up the process 'synoscgi' root@synology_A:~# synoscgi synoscgi: error while loading shared libraries: /lib/libsynoshare.so.6: invalid ELF header Hahahaha,the 'libsynoshare.so.6' is a invalid ELF header. I use shell compare synology_A and synology_B's Directory '/lib' I find there is two file is different!. synology_A: fc6a81a0cef83cc98e7af02e068646ec ./libsynoshare.so.6 657ad98f8a46e0961804b3ad69ff257e ./libsynopkg.so.1 synology_B: 8efad47899b4eeaaccebb6efb5cf8ddc ./libsynoshare.so.6 5bb625ce2b7193e3a2cc3637cd33c7ec ./libsynopkg.so.1 Ok,Try to copy synology_B's file to synology_A. root@synology_A:~# scp root@x.x.x.x:/lib/libsynoshare.so.6 /lib/libsynoshare.so.6 root@synology_A:~# scp root@x.x.x.x:/lib/libsynopkg.so.1 /lib/libsynopkg.so.1 Start the process,it works!: root@synology_A:~# synoscgi Copyright (c) 2003-2018 Synology Inc. All rights reserved. Usage: synoscgi (Version 15254) --help: this help --mode: scgi|apid (required) run as synoscgi or synoapid scgi related params: --idle-child={childNumber} (optional, default: 10) max idle child number --max-child={childNumber} (optional, default: 65535) max child number apid related params: --conf (required) apid config realpath Then Reboot it! root@synology_A:~# init 6 Finally synology_A comes back to life! I can login again. Note: 1. The above two files you can ask someone to send to you. 2. You can test let /lib/libsynopkg.so.1 /lib/libsynoshare.so.6 have no write authority like this: chmod u-w /lib/libsynopkg.so.1 chmod u-w /lib/libsynoshare.so.6 I have not test above. 3. You can use scp \ wget \ curl to download files into Synology. Or use usb storage mount or use Samba (Samba is also working) 4. If you have not enabled telnet or ssh server, you can't login in. You can Use 'Linux SystemRescue' iso write to usb storage to bootloader into SystemRescue, then copy two files into Synology's filesystems
  50. 1 point
    12 - How can I regain high amounts of reserved memory when looking in DSM's Resource Monitor? Add disable_mtrr_trim to the 'set common_args_3615' line in the grub.cfg file contained in the loader (applicable to jun's loader). It should look something like this: set common_args_3615='disable_mtrr_trim syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet' That should give you back all the reserved RAM. Note: DS3617xs use 'set common_args_3617' and DS916+ uses 'set common_args_916'