Leaderboard

  1. flyride

    flyride

    Members


    • Points

      27

    • Content Count

      1,732


  2. IG-88

    IG-88

    Members


    • Points

      21

    • Content Count

      3,742


  3. i926

    i926

    Members


    • Points

      8

    • Content Count

      1,237


  4. Dfds

    Dfds

    Moderators


    • Points

      5

    • Content Count

      525


Popular Content

Showing content with the highest reputation since 04/12/2021 in all areas

  1. this is kind of work in progress and not perfect for all scenarios but as synology now offers 6.2.4 in the DSM GUI as update (instead of 6.2.3 U3) more people might have that problem, some people tested that already here (https://xpenology.com/forum/topic/41473-dsm-624-25554-install-experience/) but i wanted to continue in a easier to find area and try to sort out problems and fine tune here in the tutorial and guides section there is the more complicated way of going back to 6.2.3, keeping all settings and data, that needs some experience in general and some linux skills and a eas
    4 points
  2. First welcome to the forum, second there is no need to upgrade to 6.2.4 as it doesn’t bring anything new & 6.2.3 is stable. Going forward it’s unlikely there will be any effort given to make 6.2.4 work given that Synology will be releasing DSM 7 later this year so it would make sense for jun or anyone else to concentrate on that.
    4 points
  3. "Most all of your problems with going to 6.2.4 is because VMWare pushed out patches with deprecation to linuxkernel." VMWare may use a variant of Linux as its core hypervisor OS, but what it supplies as a hardware platform has nothing to with it - the VM doesn't even know what OS is going to run on it. Yes, we select "Linux 3.x 64-bit blah blah" as a profile, but that is not linking to anything that is actually Linux, it's just defining a standard virtual hardware configuration that is presented to the client OS installation. Furthermore, if this were somehow true, how
    4 points
  4. Установка и настройка DSM на основе версии 6.2.3 Ну вот, муки поиска позади и вы пришли к эпохальному решению создать сервер на основе Хрени.....)))) Надеюсь, что подошли к этому шагу с долей познаний и оценили свои возможности. Данный мануал является общим, без акцента на частные настройки и особенности применяемого вами железа, такие как настройки БИОС_а и хардово-софтовые нюансы вашего железа. Процедура описана на основе последней возможной (на данный момент) для установки версии DSM. Но она применима и на ранние версии DSM 6 . Более древние уже не помню )))
    3 points
  5. Ошибочное обновление на версию 6.2.4. Откат на раннюю версию DSM. Восстановление после утери пароля. Вы являетесь счастливым обладателем сервера на основе Хрени , обновлены до последней, возможной на данный момент, версии 6.2.3 и всё хорошо, но...... Зуд творчества и жажда познаний не даёт вам покоя, а тут ещё и обнова в Панели управления просится на установку. И вот вы нажали на "Обновиться", невзирая на массу предупреждений запретов размещённых на форуме, и вот беда подкралась незаметно....... Все, ниже приведённые скрины Обновления до версии 6.2.4 , показаны ради нагл
    2 points
  6. Tenia el mismo problema con la version 6.1.7 y realizando los cambios siguientes se soluciona el problema del registro en Let's Encrypt Synology DSM 6.1 (xpenology) Lets Encrypt ACMEv1 to ACMEv2 If you get messages like: synoscgi_SYNO.Core.Certificate.LetsEncrypt_1_create[5038]: certificate.cpp:957 syno-letsencrypt failed. 200 [new-req, unexpect httpcode] synoscgi_SYNO.Core.Certificate.LetsEncrypt_1_create[5038]: certificate.cpp:1359 Failed to create Let'sEncrypt certificate. [200][new-req, unexpect httpcode] Then you need to upgrade your DSM up to version 6.2 o
    2 points
  7. Désolé, je n'étais pas présent... J'avais écrit en fin de mon message : Mais tu as trouvé la réponse à ta question. Rajouter un compte peut se faire manuellement, mais il faut l'ajouter ET dans le fichier passwd ET dans le fichier shadow. Et dans ce cas, il faut être très prudent avec le répertoire HOME associé tout comme avec l'ID, il est possible de dupliquer un ID et d'avoir un HOME identique pour deux comptes, mais lors de la suppression d'un compte, selon les paramètres passés à la commande il est possible que le dossier utilisateur soit supprimé, ce qui dans le ca
    2 points
  8. i maintain the alternative of using open medial vault, if dsm breaks i can boot up omv from a disk or usb and have network access to my files and if synology gets nasty i will just switch to omv (btrfs and SHR are no problem, just work when starting omv) Just a quick comment on this, if folks do feel the need to start reposturing themselves away from DSM because they are concerned with access to security patches or just have to have the "latest" on whatever platform they want, it would probably make sense to steer away from using SHR - yes it can be supported on OMV or plain o
    2 points
  9. Я делал это, когда еще было не жалко что-то терять, теперь никогда не спешу обновляться. Сорри, переводить нет возможности и желания, но там все утилитарно, создать загрузочную флешку с любым lunix, который нравится, воткнуть ее вместо флешки хрени, загрузитцо, смонтировать рейд системы (он будет со всех дисков, чтобы не форматировать системный раздел по одному и не потерять настройки системы и установленные приложения), удалить промежуточные файлы, поправить файлы VERSION, внести коррективы в загрузочную флешку системы, воткнуть ее снова, ребут... и вуаля. P.S.Погряз в home assistant и z
    2 points
  10. as 6.2 is a new major version you need a new loader https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ in theory you could use 918+ (loader 1.04b) but the only gain would be the option to use nvme cache drives (after additional patching), it has a newer kernel but is most cases thats not important, downside of 918+ is problems with lsi sas controller (and scsi/sas controller in general) its best to stick with 3617 (especially when using lsi sas controllers) and use loader 1.03b (that needs csm mode in uefi bios and booting from the non-uefi usb d
    2 points
  11. My DSM is back in the original state. I cannot express my thanks to IG-88 for his incredible advice. @phinemariatry to follow IG-88's reply here and you should be fine. In case you struggle I will try to help you as IG-88 helped me. Just PM me here and I will help you. Many MANY thanks to IG-88 for his knowledge and willingness. You do not see too many people like him nowadays. Cheers.
    2 points
  12. Should we be concerned? Long term, with the intermediate updates not working? (assuming we already have backups and have all the functionality we need) Define concern? Is there anything that can be done with 6.2.4 that cannot be done with 6.2.3? The assumption has always been is that any update has the possibility of breaking the loader. Could DSM 6.2.3-25426 Update 3 possibly be the last safe Xpen Version for us using Jun's Loaders? Maybe. Is Jun still kicking around to come up with a possible solution? Or anyone else? Jun is the only one that can ans
    2 points
  13. 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.
    2 points
  14. Всем привет! Около года периодически почитываю данный форум, в основном английскую часть. Решил поделиться сетапом, и для себя сделать некую заметку, чтобы было от чего отталкиваться в дальнейшем . Началось все с покупки телевизора и желания смотреть на нем контент в 4к. А далее понеслось: пришлось заменить роутер, который стал выполнять функцию DLNA сервера, покупка внешних дисков на 8 ТБ, число которых выросло до четырех, мудрить с тем, как все это воткнуть в два разъемы usb на роутере и запитать. В конечном итоге пришло понимание, что все это безобразие из девайсов и проводов н
    1 point
  15. Pour ma part je le fait toujours en ligne de commande : j'ouvre l'invite de commande windows : Puis : diskpart Cela m'ouvre une nouvelle fenetre : Ensuite : list disk Je repère le numero du disque étant celui que je veut formater, et je fait : select disk X ( ou X étant le numero du disque a formater ) Ensuite pour l'effacer : clean A partir de ce moment, le disque est vide Pour créer une partition : create partition primary Puis lui donner une lettre non deja utilisé sur ton ps, pour y avoir acces, par exemple G : as
    1 point
  16. Just an update. I had nothing special to do this weekind so I installed whsv1 on a spare hd and temp running around 120 F while transferring large files so it looks like it's running at the same temp as when the E5200 was installed. Just thought I would update in case anyone else wanted to use the 8200s cpu.
    1 point
  17. I believe the Control Panel System Temp hover indication is the temperature of the hottest disk, not the CPU. The cache device(s) are excluded from this assessment of highest temperature.
    1 point
  18. Unfortunately not a simple answer that applies to everyone. It depends on the hardware you have and the platform you have picked (DS3615xs/DS3617xs/DS918+). On my ASRock 4205-ITX baremetal I can see temperature per core. Virtual servers don't show anything within the VM's. Poke around /sys/class/hwmon, /sys/class/thermal, and /sys/devices/platform directory structures for files referencing temperature. Or, install lm-sensors or acpi may help.
    1 point
  19. Телик 4К на Андроиде, на XPE запускаем torreserv
    1 point
  20. Result: SUCCESSFUL (migration DS3615xs to DS918+) Old loader version: Jun's Loader v1.02b Old version DSM: DSM 6.1.7-15284 update 3 New loader version: Jun's Loader v1.04b New version DSM: DSM 6.2.3-25426 update 3 Additional module extra.lzma, extra.2lzma: NO Bare Metal Motherboard: GA-B250M-DS3H Chipset: Intel B250 CPU: Intel Core i5-6500 (Socket 1151v1) RAM: 8GB DDR4-2400 DIMM Integrated NIC: Realtek RTL 8111G
    1 point
  21. Per the previous post, you have some additional testing to do to make sure that all the drives will be seen. It is very useful to have a backup of your data as the migration process is If you are absolutely sure that all the drives can be reached by the new system install, you can migrate the drives in one of two ways: 1) Leave the test disk installed as the first drive (controller #1, port #1), remove its Storage Pool (but working DSM will remain intact). Then shut it down and install the 8 drives. When you boot back up, your old Storage Pool and volume should be vis
    1 point
  22. Yes exactly is what you are thinking!! But there are some traps Yes we can run xpenology on docker fully functional but inside a KVM VM but works pretty fine really. Right now what I have is a simple docker that execute an instance of xpenology (clean, so the page of installation is shown to install) I thinking which features do you think could be interesting for you? give support to docker volumes inside the xpenology? -v /myhost/data:/Volume1/myshare ? Please let me know what do you think could be interesting for you. when I have a more stable ve
    1 point
  23. Do you intend to re-use the stick as a normal storage device? Otherwise deleting the partitions for XPE is not a good idea. To clean the stick run the CMD as Administrator: - diskpart (CMD changes to DISKPART>) - list disk (you should see a list beginning from 0 that shows all connected devices/drives and their size) - select disk X (< replace X with the number of your USB drive, be absolutely sure about this) - clean (this wipes all(!) partitions from the drive) - create partition primary - active - format fs=ntfs quick (this formats
    1 point
  24. Regarding QuickConnect: https://xpenology.com/forum/topic/9392-general-faq/?tab=comments#comment-82390 DSM heavily leverages GPL code, which essentially says that source code and use must be freely made available to all. DSM is an "aggregate" program with GPL and a few non-GPL components - particularly those that rely on Synology's own cloud services such as QuickConnect. Synology uses real serial numbers and registrations to determine valid connections to their cloud services. In the interest of maintaining appropriate use of DSM under XPenology, trying to use QuickConnect
    1 point
  25. Если Вы обновились до 6.2.4-25556 (в теории можно откатываться и с других версий) и поняли что перестала работать сеть. То скорее всего единственное что поможет - откатиться на прошлую версию. Сделать это можно вот так. 1) На флешке в разделе который сразу монтируется, удалить все кроме extra.lzma. Залить туда zImage и rd.gz из DSM_DS3615xs_25426.pat (если у Вас DS3615xs) 2) Скачать последнюю ubuntu и залить ее на usb (инструкция даже на официальном сайте есть) В загрузившейся ОС (в терминале) sudo -i apt-get install mdadm lvm2
    1 point
  26. You can do this but there will be some level of performance impact, and it's another layer of services to get corrupted and damaged. On ESXi my testing indicated something approaching 10% cost to virtualizing storage. If the storage is fast enough that probably doesn't matter. My preference is to pass through disks into a DSM VM and allow DSM to manage them completely. Part of the value of DSM is that it is really designed to work directly with the disk hardware for redundancy and data recovery. Of course, you then need separate storage for the hypervisor and other VM's (techni
    1 point
  27. Фигня делов: - порт соседа выводишь в отдельный бриджСоседа; - на бриджСоседа вешаешь другую подсеть и настраиваешь dhcp-server; - на файерволе запрещаешь пакетам ходить между бриджами.
    1 point
  28. Worked fine for me. Thank you very much
    1 point
  29. AFAIK VID/PID tells real Syno code what the bootloader device is so that it hides it properly. Since it is hardcoded and the VID/PID is Synology's it is a simple way for Syno to ensure DSM doesn't run on non-Synology hardware (except if hacked). VID/PID error is essentially their code rejecting non-Syno hardware. Anytime you attempt a (6.2.4) install on a loader device, it will write those files to the loader and then it cannot install a version earlier than that. It doesn't matter if it worked or not. So just write a new clean loader from a fresh download and this proble
    1 point
  30. looks like as if you would have created a new storagepool with the ssd the drive needs to be unused, no pool or volume, there is a special ssd cache option in storage manager, left down below https://www.thomas-krenn.com/de/wiki/Synology_NAS_SSD_Cache_Konfiguration
    1 point
  31. Inital though: since all xpe docker images depend on kvm and it's possible to run kvm inside wsl2 (after building a custom kernel of course) it might actualy be possible. Though, you would end up running XPE in kvm started by a docker container, which runs in wsl2 (which itself is a container and not a full fledged os). You would need to compile and use a custom kernel for wsl2, then install kvm in wsl2, then use a docker container to create a xpe-vm in wsl2.... Sounds brittle to me. For me this looks like a case of "technicaly possible", but far away from beeing
    1 point
  32. beside the mounting with partitionwizard there is a better way to use the tool to get easy access to the loaders 1st and 2nd partition start the tool, right click on the loaders main entry where is states GPT, convert it to MBR, apply to execute the oüeration, do the same again but revers it, convert it to GPT and click apply now windows 10 can access both partitions as its supposed to be and you don't need any additional tools and with that its also possible to get the MBR version of the loader (often needed for HP desktop's), no need for a special download of the loader
    1 point
  33. Oui c'est bien du Linux Le planificateur de tâche est une interface qui s'appuie sur la commande cron de Linux (et qui simplifie grandement le paramétrage de la planification des tâches) Dans le script développé par l'utilisateur il s'agit de Bash (acronyme de Bourne-Again shell) qui est un interpréteur en ligne de commande de type script. C'est le shell Unix du projet GNU. Fondé sur le Bourne shell Certains paquets comme Hyperbackup inscrivent les opérations de backup dans le planificateur de tâche. Perso j'utilise le planificateur de tâche pour sauveg
    1 point
  34. @bearcat Sorry for the miss understanding , integrated graphic card /dev/dri make me write pci my bad. I have the M93p Tiny running Openmediavault docker and KVM it performs well.
    1 point
  35. i'd suggest a jmb585 based card in the pcie 16x slot (that has pcie 3.0, the other slots seem to be 2.0) https://xpenology.com/forum/topic/35882-new-sataahci-cards-with-more-then-4-ports-and-no-sata-multiplexer/ i guess so, not much choice for >6 onboard, maybe a used system is a option 88SE9128, sees extremly old silicon, if anything then use 88se9235 two pcie 2.0 lanes and 4 ports, if you just want to use two atm there is no bandwidth problem at all (pci4 4x slot with pcie 2.0 on you board) if you use 3617 as base you could also use a lsi
    1 point
  36. From what I was able to determine it actually is boosting. You can tell by looking for it running at 3601 Mhz. That extra 1 indicated that turbo is active. Since that sounded like a load of BS to me I decided to run a benchmark. The benchmark came came with a value that I would have expected only with turbo active, thus I am now convinced that Turbo is actually kicking in.
    1 point
  37. most people dont get that one right, synology did some kernel changes in 6.2.1/6.2.2 that made most extra drivers not working, only the drivers originally within dsm (aka native) where still working, as no one was willing to have a look into this (jun even pointed out where the problem came from) and make new drivers some people needed to revert to 6.2.0 other bought certain intel nic's to get around the problem (often seen are cases with hp microserver's onboard broadcom driver not working anymore and people buying a hp intel based nic to get the system back into network - it was running, the
    1 point
  38. не раз пробовал OMV, но синоложи удобнее интерфейс. Но если прижмёт, придётся усиленно разбираться. Зато там нет никаких проблем с лицензиями и процесс установки намного проще
    1 point
  39. CPU Frequency scaling for DS918+ Я эту тему мучал как только мог, потом плюнул, т.к. толку от этого никакого. У меня UPS и потребляемая мощность отображается. И никакой экономии от изменения частоты нет, совершенно нет. Полноценной регулировки на Хреноложи нету. Для экономии надо регулировать не только частоту но и напряжение проца, а этого, фиг вам. Так что не занимайтесь фигней. У меня 4 ядра без виртуальных работают на частоте 3.6 ГГц, потребление без нагрузки с тремя ЖД, примерно 70 ватт\час, со 100% нагрузкой при транскодинге 130 ватт.
    1 point
  40. Outcome of the update: FAILED - DSM version prior update: DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: ESXi VM - Notes: Installation seems fine, but than stuck at bootloader. FixSynoboot.sh (latest from feb 2021) was used. Logging in COM-port (serial) shows the following right after the grub2 bootloader menu selection: This looks to be the same as some users reported with DSM7 preview. Seems Synolgy has changed a lot in their boot-process/images/kernel in 6.2.4.
    1 point
  41. ну как бы совсем не так PCI-E 3.0 кои как раз у меня используются пропускают 8 ГТ/с -по одной линии. Итого для PCI-E 3.0 x8 получаем 7,88 Гбайт/с или 63Гбит\с - то есть можно спокойно создавать сеть на Infiniband 40Гбит а если ставить в слот x16 то и все 100Гбит. - но это совсем не для дома расходы. Мне Switch 10Gb на 8 портов SFP соил 17тр + по 3тр за карту SSD и прочее не имеет к пропускной способности сети отношение. Так как в случае прокачки через iperf они не задействуются. Хе - у меня самые обычные десктопные Toshiba по 2Тб - 12шт Raid5 по тестам DiscSpeed л
    1 point
  42. La solución mas sencilla que he hecho, varias veces por cierto, es crear un USB con live-cd de Ubuntu y que lea esos discos con xpenology....con el administrador de discos de UBUNTU simplemente es eliminar la primera partición de cada disco que es donde se instala lo referente a la version de DSM...vuelve a poner el PenDrive con el loader que quieras y vuelta a instalar de cero sin perder la información. Y ya te digo, lo he hecho muchisimas veces y no he perdido la información ni una vez...y simplemente iba cambiando de DSM 3615 a 3617 para ver la estabilidad y cual me interesaba,
    1 point
  43. Yeah, the only thing in that whole long terminal session that did anything was the copy file above. You're lucky the random shell action didn't do any damage as root. Now you need to make the script executable: Then reboot and your drive should show up in Storage Manager. Please do yourself a favor and only use R/O cache mode, not R/W ...
    1 point
  44. So. IG-88 create for me extra.izma Tutorial. 1. Download Jun 1.03b - https://mega.nz/#!zcogjaDT!qIEazI49daggE2odvSwazn3VqBc_wv0zAvab6m6kHbA 2. Replace in Jun 1.03b «rd.gz» and «zImage» from https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3617xs_24922.pat 3. Replace in Jun 1.03b - extra.lzma for loader 1.03b_mod ds3617 DSM 6.2.2 v0.4_Beta http://s000.tinyupload.com/?file_id=81158484589811846693 4.After start need need to get root rights and and open access for WinCSP - https://suboshare.blogspot.com/2019/02/synology-nas-dsm-62-root-acces
    1 point
  45. Should the system show that two processors are installed? Added extra.ism and extra2.ism files from the topic: Disks are in the server from 1-16 In DSM it is displayed from 11-25 (14 disks), somewhere 2 disks disappeared.
    1 point
  46. Is there a way to do a shellscript automagically post-update or at boot/premount time? Hmmm…
    1 point
  47. First of all I cant mount synoboot.img with osf, It say that no partitions found, I could read it only with poweriso, ok i change mac on virtual machine match it in grub.cfg but I cant find it with find.synology.com or synology assistant, what I could do wrong?
    1 point
  48. Je n'ai pas testé la mise à niveau, j'ai refait une installation from scratch en DSM6. Donc, je ne sais pas si lors de la mise à jour le compte admin est sollicité à partir de l'authentification du DSM5 ou si c'est une authentification dans la version 6. Le plus simple, ce serait de démarrer le serveur à partir d'un LiveCD (via une clef USB) comme SystemRescueCD (qui possède une interface graphique, mais la dernière version semblait ne pas tenir compte correctement du codage du clavier, et coder un mot de passe en QWERTY, c'est chaud). Une fois le système linux démarré, a
    1 point
  49. 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
    1 point