Popular Content

Showing content with the highest reputation since 07/31/2020 in all areas

  1. 2 points
    ^^ sympa ton monologue! Dis nous plutôt comment tu as fait :)
  2. 2 points
    Всем нравится халява, а не новые функции))
  3. 2 points
  4. 1 point
    NOTE: This problem is consistently manifested when running on ESXi, 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 and does resolve the issue there also. You can verify if you have an issue by launching SSH and issuing the following command: $ ls /dev/synoboot* /dev/synoboot /dev/synoboot1 /dev/synoboot2 If you see something other than the three devices returned, your Synoboot devices are not being configured correctly, and you should install the corrective (attached) script. TL;DR: When running DSM 6.2.3 under ESXi, Jun's 1.03b and 1.04b bootloaders fail to build /dev/synoboot (this can be fixed by installing an extracted script from the loader to re-run after the boot has completed) DSM 6.2.3 displays SATA devices (i.e. bootloader on 1.04b) that are mapped beyond the MaxDisks limit when previous versions did not DSM 6.2.3 update rewrites the synoinfo.cfg disk port bitmasks which may break some high-disk count arrays, and cause odd behavior with the bootloader device Background: Setting the PID/VID for a baremetal install allows Jun's loader to pretend that the USB key is a genuine Synology flash loader. On an ESXi install, there is no USB key - instead, the loader runs a script to find its own boot device, and then remakes it as /dev/synoboot. This was very reliable on 6.1.x and Jun's loader 1.02b. But moving to DSM 6.2.x and loaders 1.03b and 1.04b, there are circumstances when /dev/synoboot is created and the original boot device is not suppressed. The result is that sometimes the loader device is visible in Storage Manager. Someone found that if the controller was mapped beyond the maximum number of disk devices (MaxDisks), any errant /dev/sd boot device was suppressed. Adjusting DiskIdxMap became an alternative way to "hide" the loader device on ESXi and Jun's latest loaders use this technique. Now, DSM 6.2.3: The upgrade changes at least two fundamental DSM behaviors: SATA devices that are mapped beyond the MaxDisks limit no longer are suppressed, including the loader (appearing as /dev/sdm if DiskIdxMap is set to 0C) The disk port configuration bitmasks are rewritten in synoinfo.conf: internalportcfg, usbportcfg and esataportcfg and on 1.04b, do not match up with default MaxDisks=16 anymore. NOTE: If you have more than 12 disks, it will probably break your array and you will need to edit them back Also, when running under ESXi, DSM 6.2.3 breaks Jun's loader synoboot script such that /dev/synoboot is not created at all. Negative impacts: The loader device might be accidentally configured in Storage Manager, which will crash the system The loader partitions may inadvertently be mapped as USB or eSata folders in File Station and become corrupted Absence of /dev/synoboot devices may cause future upgrades to fail, when the upgrade wants to modify rd.gz in the loader (often, ERROR 21) Unpacking Jun's synoboot script reveals that it harvests the device nodes, deletes the devices altogether, and remakes them as /dev/synoboot. It tries to identify the boot device by looking for a partition smaller than the smallest array partition allowed. It's an ambiguous strategy to identify the device, and something new in 6.2.3 is causing it to fail during early boot system state. There are a few technical configuration options can can cause the script to select the correct device, but they are difficult and dependent upon loader version, DSM platform, and BIOS/EFI boot. However, if Jun's script is re-run after the system is fully started, everything is as it should be. So extracting the script from the loader, and adding it to post-boot actions appears to be a solution to this problem: Download the attached FixSynoboot.sh script Copy the file to /usr/local/etc/rc.d chmod 0755 /usr/local/etc/rc.d/FixSynoboot.sh Thus, Jun's own code will re-run after the initial boot after whatever system initialization parameters that break the first run of the script no longer apply. This solution works with either 1.03b or 1.04b and is simple to install. This should be considered required for ESXi running 6.2.3, and it won't hurt anything if installed or ported to another environment. FixSynoboot.sh
  5. 1 point
    Simple answer: if you try to use an external service (find.synology.com) with no internet access -> doesn’t work. DSM needs a DHCP in your network. If your router supports this feature you should check it‘s DHCP leases after the loader has started.
  6. 1 point
  7. 1 point
  8. 1 point
    Non tu ne pourras pas activer quickconnect , si tu n'as aucunes données a conserver sur ton NAS pourquoi ne pas simplement formater les HDD avec un live linux puis reprendre de zéro ?
  9. 1 point
    En choisissant au boot de réinstaller(2ieme ligne) , tu dois pouvoir dans l'interface d'installation web synology lui dire de partir de zero
  10. 1 point
  11. 1 point
    Difficile de savoir car chaque version majeure apporte son lot d'incompatibilité. Si tu viens juste de le monter de 0 autant tenter la dernière version et en cas d'échec tu réinstalles sans prise de tête. Dans le cas contraire recherche dans la section https://xpenology.com/forum/forum/78-dsm-updates-reporting/ si qqn dispose du même chipset que toi
  12. 1 point
  13. 1 point
    Buenas tardes Llevo ya un tiempo planteándome pasarme a un servidor Synology real principalmente por el soporte de actualizaciones. Tengo Xpenology montado en Baremetal sobre un Microserver Gen8, con un disco en un volúmen independiente y otros tres en un RAID 5. Mi idea sería pasarme a un DS1019+ cambiando lo discos directamente en el mismo orden que están en el synology. ¿Se puede hacer? ¿El sistema lo reconocería como una migración normal de discos entre synology? ¿Alquien lo ha hecho? Toda aportación es bienvenida Gracias
  14. 1 point
    Salut, La configuration n'est peut etre pas compatible ? Il faut s'assurer que le PID/VID de la clé est juste. Si tu boot en UEFI, essayer Legacy je te conseil aussi d'essayer avec une autre clé USB ( de préférence, utiliser une clé USB2 sur un port USB2 de la carte mere )
  15. 1 point
    1.04b 918+ no go with your cpu as its to old most likely for 3617 you used loader 1.03b an d that needs csm/legacy mode (also as boot device) https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ loader 1.02b and dsm 6.1 is more easy in that area also you might read faq and tutorial https://xpenology.com/forum/forum/83-faq-start-here/ https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/
  16. 1 point
    After upgraded to DSM 6.2.2 and moments 1.3.2, the face recognition is empty , and concept category only has child. I found thus shoud be a bug of photo detection plugin. So, there is the way to fix it: 1. enable SSH, and disable Moments. 2. replace /var/packages/SynologyMoments/target/usr/lib/libsynophoto-plugin-detection.so with my attachment. 3. enable Moments. (maybe need to reindex.) everything is fine. Enjoy~ libsynophoto-plugin-detection.so
  17. 1 point
    Собрал я себе домашний DIY NAS на SSD и GA-SBCAP3350. Давно хотел сделать полностью бесшумный, без активного охлаждения, экономичный и компактный NAS. И в принципе это удалось сделать. Подвернулась плата GA-SBCAP3350 с пассивным охлаждением (массивная пластина на днище), 2 SATA, 2 Ethernet, с питанием 9-36В, как раз под накопившиеся БП из под ноута. Вот описание платы: https://www.gigabyte.ru/products/page/mb/ga-sbcap3350rev_10#kf На борту 2х ядерный N3350. Существуют похожие платы на N3450, N4200 и др. Поставил 2 SSD Samsung Evo 860 и все это запихнул в корпус от старого eth коммутатора. Оба SSD питаются от разъема SATA_PWR1 на плате. В данный момент работает на: - Версия и модель загрузчика: JUN'S LOADER v1.03b - DS3615xs - Версия DSM: DSM 6.2.3-25426 - Дополнительные модули extra.lzma: NO Поставлено все с 0. По нагреву: БП от ноута 80Вт, немного теплый. Температура процессора в простое 43-45, в нагрузке 50+. Температура SSD в простое 43-45 в нагрузке 50+. Точнее проведу замеры и дополню информацию. В перспективе возможно использую более просторный корпус с оребрением для лучшего охлаждения SSD дисков
  18. 1 point
    Review this thread: https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available/
  19. 1 point
    Good day I try to install this software on my old pc, ga-z77x with it 3570, I boot with the flash drive,, but the synology assistant, don't find anything, I try this flash with my notebook, synology assistant find it. What the problem? I try to change network card, but got the same result
  20. 1 point
  21. 1 point
    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: Jun's Loader v1.03b DS3617xs - Using custom extra.lzma: No - Installation type: ESXi 6.7 I also had the "File is corrupt issue." Fixed it after installing FixBoot.sh :
  22. 1 point
  23. 1 point
    I'd suggest starting by having a look at this thread: You mentioned that you wanted to use VMM, sadly as the N54 has an AMD CPU that won't be possible as it's only supported on Intel CPU's. As for your data it should be ok, however you should always have a backup just in case things go awry.
  24. 1 point
    Hi all, I am an old PC user from the UK. I love old IT kit, still very capable for so little money. I keep all of my data on an old QNAP NAS which is great, but it cant run Plexserver and I miss that interface rather than browsing through folders when I want to play something. Combine that with 200Mb cable at the front of the house that drops to 60Mb by the time you get a signal via wifi or powerline networking to my PC and I decided to get a low power box to sort the issue. I have a 'new' N54L I plan to put in place with the router with xpenology on to run plex server, to sort my video files out from the NAS, but also to act as a torrent box that can max the connection out.
  25. 1 point
    Hello everyone, regards from Italy. i have been silently reading the forum for a while and finally decided to register and purchase my hardware which will be arriving in the next few days. a special thanks to who runs the website and to who develops and maintains the loader and driver, great work! I have a question, I wonder if I need a wired keyboard or if a wireless Bluetooth keyboard is ok also for the initial setup installation. After the installation will I ever need again the wired keyboard or could I use WiFi/Bluetooth connected keyboard? The reason I am asking is if is only need for initial installation then I will borrow from a friend, if need continuously, well, I will buy one
  26. 1 point
    Hi I am Laura from Sweden Just getting into this fantastic software. Have been successful in installing it on 3 HP Proliant ML110 G6 servers but have also had issues with trying to install it on similar servers (same make and model! and also issues with trying to install it on an ML110 G7 server, doesn't recognise the usb!) Issues with netscan not picking up mac and ip addresses. Also looking to install it on some i5 4th generation computers. First build on the ML110 G6, it will only accept 4 drives, yet the other 2 have accepted 6! Weird! I am sure I will find solutions to all these problems in the FAQ's and searches
  27. 1 point
    Hello all! Over the moon to find this place and software! First Build went well, until I stuffed it up! Hoping I don't have to start again!
  28. 1 point
    Hello from Bulgaria to all of you! Here is my specs and I am wonder will be able to run this on : Motherboard GA-B75-DV3 CPU i5 3570K RAM 16GB 2x used 2TB HDD 1x 60GB SSD 1x 25GB SSD on which i think to install Xpenology or have to be on 60GBs SSD? 2x 8TB Desktop Expansion Drives which are almost full! I just want first to see it in action and then i may buy good HDD/SSD`s Thanks in advance for your help and time! P.S. In fact, I want to make a home server with all my stuff so I don't have to take all my HDDs with me while I am on the go or on vacation, to use my stuff, watch movies or listen to music!
  29. 1 point
    Hi everyone, is Fran from Spain. I want to learn more about Xpenology. I'm using it for a year and i've some problems with the last actualization, especially hw acceleration in plex, so i'm tryin to fix it. I'm going to read to you and see if I can get something. Of course, thank you very much to everyone.
  30. 1 point
    Hello again, I am loving what has been developed with Xpenology and have it running on a bare metal system and it is running great : 2U 8 Bay 2x E5-2630 V1 6 Core 64GB RAM X9DR3-LN4F+ Supermicro and it is running the latest dsm version. but the reason for my post is I am looking for some advice. I started this road many years ago when M$ came out with the Homeserver software and I got my first HP ex475 4 bay unit and that turned out to be under powered so I built a newer system with a Norco 24 bay, well you may know where that went, as homeserver 2011 came out and they killed the drivepool I went with stablebit drive pool, moved on to Server 2012 r2 with the Essentials roll installed on a Supermicro 24 bay hotswap with X9QRI-F+ Motherboard 4x E5-4650 v2 2.4ghz 10-Core 8.0 GT/s / 25mb Smart Cache CPUs 16x 16gb 4Rx4 PC3-10600R Server Memory, than added a 45 bay expansion to that, so I have around 264Tb in two drivepools on that, just a little bit of overkill, but I am disabled and retired. But to make a long winded post shorter, I want to get away from M$, but I know the beast is a little overkill for xpenology and would like some suggestion. It will be a big pain in the back side to remove all of the files from those drivepools, So any suggestions would be welcomed. Thanks Badjames
  31. 1 point
    Hey, I have been using xpenology for 3 years now, without any heavy problems, instead of getting started Now the system doesnt start anymore and Im trying to find a solution. In general I like football and playing PS4. Not a digital native but built some stuff for them in my professional live - focusing on digitization, digitalization and conversational AI topics etc. best Jackie
  32. 1 point
    The issue is a matter of timing in the first place. Something in your system is causing the eSATA initialization to happen later than other systems, or perhaps there needs to be more time between unmounting and device deactivation. The moment where /etc/local/rc.d executes seems to work for most, but on your system it must be too soon. I'd try modifying the script to add pauses in the following locations and see if it helps: Add a line containing sleep 5 immediately before echo "remove" >/sys/class/block/$basename/uevent Add a line containing sleep 15 between start) and FixSynoboot
  33. 1 point
    asus h170m-plus : https://www.asus.com/fr/motherboards/h170m-plus/specifications/ avec carte reseau intel® i219v, 1 x contrôleur gigabit lan intel core i3 4130 2 x 8 gd ddr3 cle usb pour le boot (oui ok un peu haut de gamme mais je n'avais que ca dans la precipitation) : lexar jumpdrive p20 64Go https://www.lesnumeriques.com/cle-usb/lexar-jumpdrive-p20-64-go-p23621/test.html beyimie sata carte pcie 4 ports (marvell 88se9215) : https://www.amazon.fr/gp/product/B07MBFWH81?pf_rd_p=61e3aca3-2f4c-4ed4-8b56-08aa65c1d16f&pf_rd_r=KXSKEF2QC7H12MFBRT5W icy dock backplane mb155sp-b 5 disques sata 3"5 https://www.abix.fr/icy-dock-backplane-mb155sp-b-5-disques-sata-3-5-736905.html 6 seagate ironwolf de 8 to https://www.seagate.com/fr/fr/internal-hard-drives/hdd/ironwolf/ alim 400w eco (mais je pense la changer) ---------------------------------------------------------------------- config : synoboot_3615-loader jun v1.03b ds3615xs - dsm 6.2 ds3615xs dsm 6.2.2-24922 update 2 fichier : dsm_ds3615xs_24922.pat config bios : plug&play active sur les 6 sata ---------------------------------------------------------------------- j'ai fait un raid 5 sur 6 hdd (brancher sur carte mere) et un ssd samsung evo 860 pour le cache sur la carte sata additionnel je poste ce message car j'espere rendre a mon tour le service d'une config ok . merci pour tous les posts sur ce forum qui m'ont grandement aide et aussi merci a ceux qui nous propose des solutions de boot modifiees
  34. 1 point
  35. 1 point
    In this tutorial we are going to place the bootloader alongside the DSM OS and the remaining storage Keep in mind that i use DSM 6.1 and not 6.2! What you need: Win32DiskImager Jun's loader v1.02b DS3615xs with MBR partition DSM 6.1 (15047) grub2 (i used grub2-for-windows) partition/hard disk manager (i used Paragon Hard Disk Manager 15) USB stick for the bootloader empty SSD First we are going to put the bootloader on a USB stick using Win32DiskImager Then we are going to install DSM normally After the installation of DSM and configuring your device name, username, etc goto the Storage Manager and create a RAID Group for only the SSD in Basic then click Apply and goto Volume and create one (doesn't matter what File system you used, but i use ext4) then click OK and shutdown the server Now we are going to do some fun things with the SSD drive where DSM and the storage are installed on put the SSD drive and the USB stick with the bootloader on it (we need some files later) out of the DiskStation machine and put them in your main PC Start up your partition/hard disk manager and look for the SSD that you installed DSM on it should look like this: Look at the last Unallocated partition, it should be 100MB big thats plenty for the loader so we are going to make a new partition (50MB is enough) and make sure you put it at the very end of the drive dont forget to put the drive as Active and assign a drive letter to it Now we are going to install grub2 on that 50MB partition i used this website to make one (because i use Windows) After you have install grub2 on that partition that we need to copy all the files from the 2nd partition of the usb drive and place them in the root directory of the 50MB partition don't forget to place the grub.cfg (from the 1st partition) in the /grub folder of 50MB partition Now unplug the SSD from your PC and place it in your DiskStation pc and boot it up (you dont need to edit anything just let it boot) you can use Synology Assistant to find your DiskStation pc and you should see a normal welcome page were you can login After you have logged in you should see an error message, that is because of the small FAT16 partition you will get that everytime you startup that machine Storage Manager should say that your system is healthy. Thats it, you can now use it normally without an USB bootloader also you can update to the latest 6.1 version if you want (make sure you don't install 6.2, haven't tested that one)
  36. 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 Из личного опыта........ Всегда сохраняйте свой, правленый образ загрузчика. Всякое может случиться и всегда полезно иметь уже готовый для записи образ. Лично я, всегда делаю ДВЕ флешки. Тоже, на непредвиденный случай.
  37. 0 points
    Does it work with DSM 6.1? I can't seem to get it working. I get this after applying the patch: cat /usr/syno/etc/codec/activation.conf {"success":true,"activated_codec":["hevc_dec","ac3_dec","h264_dec","h264_enc","aac_dec","aac_enc","mpeg4part2_dec","vc1_dec","vc1_enc"],"token":"123456789987654abc"} Then this immediately after trying to play a video in video station: cat /usr/syno/etc/codec/activation.conf {"success":false,"msg":"SN format is wrong."} Video doesn't play.