Leaderboard

what do you prefer? crystal ball, tea leaves or throwing bones?

So I leave 3 days on holidays and everyone forgets the rules... They are rather simple and stated just above the first post. All Off-Topic posts have been moved.

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.

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 an

pretty sure you will not be the last download a rescue/live linux like system rescue cd, transfer it to a usb (not your dsm boot usb) to boot from it assemble your raid1 system partition like here (1st partitions of all disks as /dev/md0) skip anything about swap or volume1 data partition, we only need access to the dsm system partiton https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/ mount the assembled raid1 to /mnt with this mount /dev/md0 /mnt then remove some files with this rm -rf /mnt/SynoUpg

Зачем вам старая версия ? 6.2.3 заведётся без проблем на встроенной сетевой карте. Сначала - 6.2.3-25426 https://archive.synology.com/download/Os/DSM/6.2.3-25426 Потом апдейт 6.2.3-25426-3 https://archive.synology.com/download/Os/DSM/6.2.3-25426-3 Главное, что бы не получить Ошибку, внесите изменение в БИОС_е C1E Support - Disabled

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

I am reading that as either DS3617 doesn't work on your hardware or maybe there is a problem with the config on that stick. but I think you are saying that DS3615xs works perfectly. If it boots normally from the DS3615xs stick and all works, I would say that it is fine. Erase the other stick and move on!

Read previous posts in this topic from IG-88. 3617xs version works perfectly, 918+ not.

at least jun still logs in here from time to time, the interpretation depends on your point of view synology usually delivers 5 years updates, i expect at least one year security updates to 6.2 if you look into the units not getting 7.0 and find one that hast not been on sale 5 years in q1/2022 that might be a hint that 6.2 will get two years or more there is nothing to expect before 7.0 is released and if things go well synology will have to release the kernel source sooner the they did with 6.2 (there is someone breathing down there neck and trying to remind them t

NOTE: This problem is consistently manifested when running as a virtual machine, but many have encountered problems with Synoboot devices on baremetal installs of 6.2.3 and under certain conditions, other 6.2.x versions. The fix can be implemented safely on baremetal installs. You can verify if you have the issue by launching SSH and issuing the following command: $ ls /dev/synoboot* /dev/synoboot /dev/synoboot1 /dev/synoboot2 If these files are not present, your Synoboot devices are not being configured correctly, and you should install the fix script. If synoboot3 exists that is ok

10 - What is the relation between DSM updates and the loader? Synology delivers three types of updates to DSM: - Major updates: x.x (e.i DSM 6.1) - Intermediate updates: x.x.x (e.i DSM 6.1.4) - Critical updates: x.x update x (e.i DSM 6.1.7 update 1 or DSM 6.1 update 1) Whenever an update is released it is strongly advised to first make an update on a test machine prior updating your "production" machine. This goes for all types of updates but more so for major and intermediate updates where there tend to be enough changes to DSM's kernel for the loader no

As promised here some notes I have choosen to remember: Enable passthrough of the onboard Cannon Lake AHCI controller: - enable SSH access in ESXi and login as root - edit the file "/etc/vmware/passthru.map" (it is NOT "passthrough.map" : vi /etc/vmware/passthru.map - add this at the end of this file: # Intel Cannon Lake PCH-H Controller [AHCI mode] 8086 a352 d3d0 false - reboot ESXi - login to the ESXi-GUI and enable passthrough of the Cannon Lake AHCI controller - reboot ESXi again - Now you are able to attach the Cannon L

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++ (b

Аппаратный транскодинг. Програмный, он же софтовый, работает в любом конфиге.

That was with 6m Cat5e cable, with 15m Cat6A I get 950 write / 995 read...

Нашел на просторах великого и могучего;) SurveillanceStation-x86_64-8.2.2-5766 версия уже пропатчена, но есть одно НО где-то сидит тайм бомба. Даже при перезагрузке службы раз в день, камеры либо все пропадают либо виснут напрочь. Пытался понять как и когда вырубаются камеры, но увы все происходит рандомно. Надеюсь общими усилиями эта проблема будет решена. SurveillanceStation-x86_64-8.2.2-5766.spk https://mega.nz/#!L0UUxabI!IeUl_VIw1FcAreLDZWDnk-U0xX63A7Ju90dJs9k6QgY

Быстрее чем что ? Чем Майбах ))) У вас есть хотя бы общее понимание предполагаемых задач на Сервере ? Из этого и надо исходить. Если просто файлохранилище, качалка, камеры...... , то наверное разницы нет. А если есть какие то планы по высокой нагрузки, то..... В общем определитесь с задачами.

Я бы вам посоветовал записать новую флешку с новым загрузчиком и отредактировать под себя. Бытует мнение, что в Шестой версии, Хрень перезаписывает какие то файлы на загрузчике. Сам не сталкивался, но на форуме есть упоминания

After lots of googling, I was able to get access to my data from that crashed volume. I removed the vhd from the VM, added them to an ubuntu VM and followed the Synology link to recover the data. This was done after the raid was repaired that it showed up in the ubuntu files manager app. Previously when the failed drive was not repaired, the volume was not available. It was visible as an option but an error appeared when I tried to access it. I ran the lvscan to display what to mount and mine showed /dev/vg1003/lv. Since it was a btrfs file system, I then installed the btrfs-progs package an

for one thats only true for 918+ and the other thing is even when present since loader 1.04b existed it only came to attention years later, there seem to be lot of users not having trouble with it, there might be other factors involved like what bios version the controller hast a what chip version you could test it with 3 disk in a raid5 and hibernation on, i di provide a extra version with the old driver (that can do sn and smart) you are safe when using 3617, just do a migration with 1.03b 3617 loader and thats it, you cant use hardware transcoding with that but most/all dev

Ну вы не правы...... Вариантов описано много, в том числе и мною..... Если есть опасения, то советую потренироваться на стороннем харде, ну а так, обновление простое и уже пройдено много раз. Берёте флешку, пишите новый загрузчик 1.03b , правите его под себя Загрузчики: https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg!7AoyySoS Делаете резервную копию настроек, это там же, где обновление. Потом из неё восстановите настройки, если что то не так пойдёт Скачиваете себе файлы DSM под свою версию. Сначала релиз https://archive.synology.com/download/Os/DSM/6

Всем привет! Около года периодически почитываю данный форум, в основном английскую часть. Решил поделиться сетапом, и для себя сделать некую заметку, чтобы было от чего отталкиваться в дальнейшем . Началось все с покупки телевизора и желания смотреть на нем контент в 4к. А далее понеслось: пришлось заменить роутер, который стал выполнять функцию DLNA сервера, покупка внешних дисков на 8 ТБ, число которых выросло до четырех, мудрить с тем, как все это воткнуть в два разъемы usb на роутере и запитать. В конечном итоге пришло понимание, что все это безобразие из девайсов и проводов н

if its the same system keep mac, usb vid/pid needs to mach the usb device used mac is only needed for WOL and convenience (some protection, like in survailance station, check the match on sn and mac to it might be important to keep a sn and mach together if they are from a original system or "valid" generated) if adding or removing nic's it need to be looked for as the order of nic's may change, so the mac's 1,2,3, ... might not fit the hardware anymore also still some special in 918+, only 2 nic's are default, so when adding a 2 port nic one port will be outside when installin

du kannst die lizenz nicht direkt auf der xpenology installieren aber es müsste gehen wenn du sie auf der 218+ installierst und über cms im netzwerk teilst solltest du sie nutzen können https://xpenology.com/forum/topic/34502-surveillance-station-lizenz/?do=findComment&comment=170511 ansonsen gibts eine alte version von ss die 4 kameras kann (-> tutorial section) und es gibt wohl auch gehacke versionen (aber die sind hier mit links usw. nicht willkommen - zumindest nach den offiziellen regeln und solche sachen können natürlich auch schadsoftware enthalten)

Just to be clear, you are installing 6.2.3: DSM_DS3617xs_25426.pat Once installed and running, you should go to Control Panel > Update and Restore and make sure that it is set to install updates manually: You should never install an update until you have checked the "updates" forum. It should at this time offer to install the minor update, Update 3, to 6.2.3. It is safe to install that.

По сути ДА. И ..... Версия 3615 наиболее универсальная.

No. This is a limitation of DSM, not the patch. Right now the only "safe" way to do it is to embed DSM as a VM in ESXi, attach the NVMe disk to ESXi and syndicate it as an emulated SATA device to the VM. Yes, you would need to turn on TELNET and/or SSH capability via a checkbox in Control Panel. The apps are usually free, such as Putty (on Windows). You do need to learn a little about Linux command line, and there are thousands of Internet resources to help you there.

When setting up an XPEnology system, you must first select a DSM platform and version. XPEnology supports a few specific DSM platforms that enable certain hardware and software features. All support a minimum of 4 CPU cores, 64GB of RAM, 10Gbe network cards and 12-disk arrays. When you choose a platform and the desired DSM software version, you must download the correct corresponding loader. That may not be the "newest" loader available. Each of these combinations can be run "baremetal" as a stand-alone operating system OR as a virtual machine within a hypervisor (VMWare ESXi is mo

I found this, I'm going to try it in a virtual machine BRB

also dsm supports 2nd factor, that might be useful too https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Management/How_to_add_extra_security_to_your_Synology_NAS#t6 hiding it behind a firewall and using vpn to access it might be even better

This is for anyone here, i created a small manual for anyone here who want's to give it a try: How to install on m2 ssd and boot from instead of usb. Get Ven/Dev number from Last know parent: PCI\VEN_8086 = VID &DEV_06D7& = PID Dont rename but let the system think vid and pid are still hardware id's. change in grub.cfg s/n: mac: number of mac's needs to be upcounted set netif_num=1 fill in number of cards you have and be sure to have mac1: and mac2: syno_hdd_detect=0 to 1 skipped a part of the new installation and didn't ask fo

the z800 seem so have a intergated sas controller and from what i found and your symptoms its LSI SAS 1068E that has a hardware limit of 2.4TB for a disk, nothing you can do about it then using another controller like lsi sas 9211-8i and its clones (in IT mode) or a ahci sata controller (a two lane 88se9230 or a jmb585 would be working too, as its presumably only pcie 2.0 a one labe controller like 89se9215 would not be that good as it would only have max. 500MB/s on the one pcie lane) 9211-8i can have 8 sata ports and 8 pcie lanes and might be a good choice it its planned to be extended

before trying to boot from it you should check if its even working with dsm, my guess its not i did not find needed kernel config in synologys default kernel config "CONFIG_MMC_SDHCI_PCI" or a driver "sdhci-pci", so it seems like the hardware is not recognised after installing dsm with usb try "lspci" to check if a driver is used for this hardware

Going a bit OT, then in days of old and "real" IBM mainframes, there was a hardwired process to start the machine called Initial Program Load. There were dials on the console so that you could dial in the address of the IPL device (card, tape or disk) and press a button to load all of 24 bytes into memory (starting at address 0). Those 24 bytes contained the code to load the operating system - which needed to be loaded to address 0. So the first thing the 24 bytes would do is to copy themselves into "high" memory and branch to the copy. This left room for it to load the OS. This initial c

Нужно зайти в уведомления SS, а не в уведомления DS

Я в теме уже про это писал. Поищите. В SS зайдите в уведомления-правила-обнаружение движения

you can use the KB of synology for things like this as you use dsm as any other synology user https://www.synology.com/en-global/knowledgebase/DSM/help/DSM/StorageManager/storage_pool_expand_add_disk ... Drive requirements: Please make sure the drives that you intend to add to your Synology NAS meet the following requirements: RAID or SHR configuration must be created by drives of the same type. Using drives of different types will affect system reliability and performance. Mixed drive types as shown below are not supported for RAID or SHR configuration: SATA drives and SAS drives 4

as a general rule, dont use driver (*.ko) from 6.2.1 and 6.2.2 for 6.2.3 for 6.2.3 you should try stuff that worked with 6.2.(0) and the original loader back in 2018

Si on lance un débat Jellyfin vs Plex : aujourd'hui encore j'utilise les 2, mais mon seul frein à basculer sur Jellyfin définitivement c'est le fait que l'application mobile sur iOS n'est pas compatible Chromecast contrairement à Plex et visiblement vu l'architecture de leur application mobile c'est pas prêt de changer, dommage. c'est d'ailleurs une doléance partagée par de nombreux utilisateurs : https://features.jellyfin.org/posts/466/chromecast-support-on-ios

Migration install should work. You should back up everything before doing any type of migration.

Для этого, необходимо иметь Валидную пару (Сериник + Мак), прошедшую регистрацию на сайте Синолоджи. Некоторым пользователям удаётся получить Валидную пару. Вот вам один из способов (середина текста) http://compkampf.blogspot.com/2018/02/nas-synology-dsm-6.html

Если у вас 918+ , то 1.04 как раз то что надо и последняя версия встанет без проблем. Загрузчика выше 1.04 пока что нет и в помине

Certainly, 10g home networks is now something new, and newbies necessarily fall in an expensive solutions and configuration errors. It is for that reason that I have shared my experience, so others newbies can understand that spending three times more does not imply three times more speed. Sometimes a simple solution like yours is better. I'm glad you publish both your successes and your failures.

I will reply a solution to myself that I have not read on the Faq section. I Have change the timeoute timer to 0 and after that the boot continue.

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: Jun's Loader v1.04b DS918+ - Using custom extra.lzma: Yes, v0.11 from IG-88 - Installation type: BAREMETAL - J4105-ITX - Additional comments: Standard update from WebUI.

For those Linux newbs who need exact instructions on installing the script, follow this here. Please be VERY careful with syntax especially when working as root. If you have not turned on ssh in Control Panel remote access, do it Download putty or other ssh terminal emulator for ssh access Connect to your nas with putty and use your admin credentials. It will give you a command line "$" which means non-privileged In File Station, upload FixSynoboot.sh to a shared folder. If the folder name is "folder" and it's on Volume 1

ALL of 2 XPENOLOGY Videos where deleted by YouTube from my tiny channel . Copy of Video stored here for now. https://mega.nz/#!AFRkhCBa!DgjU1joAsNsKOLuDknIHkVaYpdP3H_kCYvgNPYEZFlw

9 - How do I reset DSM remotely without loosing my data? Contrary to a real Synology box, on an XPEnology box, reseting DSM from the Control Panel > Update & Restore > Reset will not only reset settings but ERASE ALL USER DATA. Therefore this method should not be used if you intend to preserve your data. The only way your data would be safe is if you had a real Synology box. Then you would also need to press the reset button located at the back of the box twice within a determined time frame to have your data preserved. More info here: https://www.synology.com/en-us/knowl

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 r