Leaderboard


Popular Content

Showing content with the highest reputation since 07/19/2019 in all areas

  1. 4 points
    Dear Xpenology forum members, I'm come back!!!! I have been very busy at work. So I could not cope with the changed code because I could not upgrade DSM. But! I have recently successfully migrationed the "ivybridge" of existing my systems to "haswell". I also added an additional LAN card. The latest version of "DSM 6.2.2-24922 Update 2" is now available for the DS3615xs, 918+ and other versions. I'll be updating and distributing the "ch_cpuinfo" tool soon so that it will work with the latest version. I'm sorry to have kept you waiting so long, and thank you for waiting. See you soon. Dear @Polanskiman , Thank you for your patience and care for the topic I could not manage. I'll update soon. Dear @gericb , Thank you for your concern and supportive mentality
  2. 3 points
    GOT IT !!!... I've succesfully installed DSM 6.2.2-24922 update 2 to my Supermicro Server !!!.. After a lot of fails with installing for 916+ or 918+ i tried the DS3615xs Version Took the 1.02 MBR Loader of Genesys and replaced the files with thes from 1.03b Loader… and it worked ! i'am happy thanks to all for your support and by now i am really more experienced !.. have a nice day..
  3. 3 points
    The real answer is VMware or other hypervisor outside of XPenology. But while you are contemplating that, please read this and this.
  4. 3 points
    In addition to bricked boxes due to inattentive upgrades, there seems to be a surge of questions regarding how to select a DSM platform, version and loader. This table should help navigate the options and current state of the loaders. While situations rapidly change, it should be correct as of the listed date. 6.x Loaders and Platforms as of 07/Apr/2019 Loader DSM Platform DSM Version Kernel DSM /dev/dri DSM NVMe cache Boot method CPU Needed Notes 1.04b DS918 6.2 to 6.2.2 4.4.x Supported Supported EFI or Legacy BIOS Haswell or later recommended, AsRock Jxxxx fails on 6.2.2 1.03b DS3615 or DS3617 6.2 to 6.2.2 3.10.x Not Supported Not Supported Legacy BIOS only Nehalem or later 6.2.1+ seems to require Intel e1000e NIC 1.02b DS916 6.0.3 to 6.1.7 3.10.x Supported Not Supported EFI or Legacy BIOS (Jun) MBR (Genesys) Nehalem or later 1.02b DS3615 6.0.3 to 6.1.7 3.10.x Not Supported Not Supported EFI or Legacy BIOS (Jun) MBR (Genesys) Nehalem or later recommended 1.02b DS3617 6.0.3 to 6.1.6 3.10.x Not Supported Not Supported EFI or Legacy BIOS (Jun) MBR (Genesys) Nehalem or later 6.1.7 on ESXi failures reported 1.01 DS916 or DS3615 or DS3617 6.0 to 6.0.2 3.10.x Not Supported Not Supported EFI or Legacy BIOS (Jun) MBR (Genesys) Nehalem or later obsolete
  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 et Photos PHOTOS A VENIR....................
  6. 2 points
    Hi, Since I was not yet able to build a working cpufreq_ondemand.ko to allow automatic frequency scaling for JUN's loader 1.04b (DSM 6.2.2-24922 Update 2), i've written this script to allow dynamic CPU frequency scaling. It's hosted here : https://github.com/Trauma/cpufreq-userspace-scaler # cpufreq-userspace-scaler ##### Cpu frequency scaling script for cpufreq userspace governor ## If you're missing ondemand or conservative governors, this script is for you. This script is scaling cpu frequency according to current average load. You can set 3 frequency steps : low, mid, high. This 3 thresholds will automatically set cpu frequency accordingly : - the `lowload` threshold will set the cpu to his minimal frequency, unless you force it to `scalingminfreq` - the `midload` threshold will set the cpu to approximate mid range cpu frequency - the `highload` threshold will set the cpu to his maximal frequency, unless you force it to `scalingmaxfreq` If you set `scalingmaxfreq` and/or `scalingminfreq` the cpu will never override those values. ### Usage : ### Parameters : Variable name | Default | Type | Comments ----------------|---------|-----------------------------|----------- lowload | 050 | integer between 000 and 999 | 050 = load average : 0.50 midload | 065 | integer between 000 and 999 | 065 = load average : 0.65 highload | 085 | integer between 000 and 999 | 085 = load average : 0.85 scalingminfreq | auto | integer in hertz | 800000 = 800 Mhz scalingmaxfreq | auto | integer in hertz | 2500000 = 2,5 Ghz ### Default commande line : `./scaling.sh &` ### Custom command line example : `lowload=100 highload=200 scalingmaxfreq=2000000 scalingminfreq=1500000 ./scaling.sh &` Enjoy.
  7. 2 points
    Bon j'ai fini au bout de 4h d'acharnement à réparer le système de fichiers mais au détriment de 2 services celui de SurveillanceStation et CloudSync. Un reparamétrage des deux et c'est revenu. Pfff quelle histoire ! Je pense que le pb ne venait pas de Plex, mais bien d'un défaut d'inodes qui devait exister depuis longtemps et que j'ai mis en évidence avec ces 2 commandes : find /volume2/photo -type d -exec chmod 775 {} ; find /volume2/photo -type f -exec chmod 664 {} ; Heureusement pour moi, j'ai réussi démonter le volume proprement pour faire un checkdisk et réparer ce qui n'allait pas ! merci google^^ Pour info voici les commandes qui m'ont sauvées la vie en root exclusivement et après avoir éteint tous services sauf ssh évidement : syno_poweroff_task -d vgchange -ay fsck.ext4 -yvf -C 0 /dev/vg1/volume2
  8. 2 points
  9. 2 points
    Good start in a forum... It has been 22 hours since you opened your thread and there’s no need to push and ask with „No one?“. Beside that you should read the Faq and forum rules. Aaah yes. We all know this PC/board... like thousands of other models. Do you think that users start searching the web for this to get informations about the chipset, CPU, NIC, etc.? Post as much details as possible about your system. We don’t have crystal balls nor do many of us have the will to do your job (searching the web for further and detailed system specs). Provide us with more informations and I think that someone will answer you soon. Cheers
  10. 2 points
    Try my extra : (no need to disable anything in bios) Change of this extra.lzma > - removed drivers i915.ko drm_kms_helper.ko drm.ko in usr/lib/modules - removed reference of this drivers in etc/rc.modules Installation > sudo -i echo 1 > /proc/sys/kernel/syno_install_flag mkdir -p /mnt/synoboot1 mkdir -p /mnt/synoboot2 mount /dev/synoboot1 /mnt/synoboot1 mount /dev/synoboot2 /mnt/synoboot2 Remove extra2.lzma and replace extra.lzma by the one attach at this is post in /mnt/synoboot2 Important > clean /usr/lib/modules/update/* - Be careful with the rm ! rm -rf /usr/lib/modules/update/* And reboot. you might not have KP on i915 but you''ll probably lost your LAN, since this motherboard only have an old PCI port, i have no clue about a LAN card in PCI that might work. Alternatively you can use a dongle USB3 > LAN, a one with a ax88179 chips like this one > https://www.amazon.fr/gp/product/B00MYTSN18/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 This chipset work natively with the DSM driver : [ 240.104583] ax88179_178a 2-3:1.0 eth1: register 'ax88179_178a' at usb-0000:00:15.0-3, ASIX AX88179 USB 3.0 Gigabit Ethernet, 00:0e:c6:bd:d5:13 [ 240.118675] usbcore: registered new interface driver ax88179_178a extra.lzma
  11. 1 point
    This is an updated tutorial version from the one I made last year. It will enable you to migrate from DSM 5.2 to DSM 6.1.7 directly without the need to upgrade to DSM 6.0.2 first. If for some reason you want to upgrade to DSM 6.0.2 first or simply you do not want to upgrade to DSM 6.1.7 but only to DSM 6.0.2 then use the link above. To upgrade from DSM 6.0.2 to DSM 6.1.7 read here. As most of you know by now Jun was able to find a way to install DSM 6 on non Synology boxes. Here is the thread that I recommend reading. At least make an effort and read the OP: https://xpenology.com/forum/topic/6253-dsm-6xx-loader/ Below is what you need for the operation. I will assume you are doing all this under Windows 10, 8, 7 or XP. If you are on a MAC computer have a look at this post I made on how to burn the image to a USB drive and then mounting the USB drive for editing the content. The rest of the tutorial still applies. If you are currently using DSM 5.1 or below first update to DSM 5.2. If you are doing a fresh install of DSM 6.1 then carry on with the tutorial and omit references to DSM 5.2. - Win32 Disk Imager to make a bootable USB drive; - A 4GB (or any size really) USB drive (flash drive) to install the loader. Not that this is necessary but use preferably a brand name (Kingston, SanDisk...); - A way to read your USB drive VID/PID. Here is a how-to >>> VID and PID; - A good text editor: Notepad++ I really don't recommend using Windows's Notepad; - DSM 6.1.4 PAT file. Chose the one you need: DS3615sx or DS3617sx or DS916+. Download the ".pat" file not the ".pat.md5" - Jun's official v1.02b loader (mirror). This is a hybrid UEFI/BIOS loader so it should work in most machines which are capable or reading GUID partition table (GPT). For older machines that can only read MBR the above loader will simply not boot. If that is your case then use @Genesys's v1.02b loader rebuilt image which is MBR based. Note: Jun's loader supports Intel CPUs. For AMD CPUs Jun has stated that the loader needs some work but it has been reported by many users using HP machines that it actually works. The C1E function in the bios (in some HP machines) needs to be deactivated. I am unsure for other motherboards brands therefore if you have an AMD machine that is not an HP you might be out of luck. Try looking in the bios configuration and play around. - Custom extra.lzma ramdisk. This ramdisk is optional and should only be used if the default ramdisk included in the loader is not detecting your hardware. I am just providing it for those who are having issues with network detection or unrecognised HDD controllers. This custom ramdisk contains additional and updated modules & firmwares. Credits go to @IG-88 for compiling the modules against the latest DSM 6.1.3 source code. I do not warranty they all work but I think most do. If you chose to use this ramdisk, you will need to replace (or rename, so you can revert) the default extra.lzma ramdisk from Jun's loader with this one. If you a have question specific to the custom ramdisk please post it in the topic of IG-88, not here. - If you are doing a fresh install make sure your drives are plugged in direct succession starting from the 1st SATA port. Usually the first port is described as SATA0 on motherboards. Check with your MoBo manufacturer for exact nomenclature. - OSFMount to modify the grub.cfg file within the loader's image and if necessary to replace the extra.lzma ramdisk with the custom one. This is not strictly necessary as Jun has made it possible to configure what needs to be modified via the Grub Boot Menu. If you prefer using Jun's Grub Boot Menu configuration technic, simply skip Point 4, read Note 4 instead and pick up at Point 5. PLEASE READ EVERYTHING PRIOR ATTEMPTING ANYTHING Use this loader at your own risk. I wont be held responsible for any loss of data or black smokes that may result in the use of this loader. Please note that this loader has a limited amount of modules (drivers) included. If it is fundamental for you to have a NAS operating as quick as possible I recommend you look at the included drivers very carefully at the bottom of this tutorial before attempting an upgrade. If they are not there you will have to compile your own modules/firmwares or use the custom ramdisk provided above. Don't ask me to compile modules for you. I wont do it. One last thing: DO NOT UPDATE DSM BEYOND VERSION 6.1.7 with loader v1.02b. IN OTHER WORDS DO NOT UPDATE TO DSM 6.2 You have been warned. Here we go: 1 - BACKUP your data and save your configuration prior any attempts to migrate from DMS 5.2 to DSM 6.1. I can't stress this enough. JUST DO IT, as Nike likes to say. Also, print this tutorial if you can. It will make your life easier. 2 - Turn off your NAS and unplug the USB drive you are currently using with DSM 5.2. I recommend you put this USB drive aside in case migration to DSM 6.1 doesn’t go as expected and you need to revert to DSM 5.2. It will just make your life easier. 3 - Now go to your workstation/PC, plug a new USB drive (or the old one if you really don’t have any spare USB drives). Use the link I provided earlier to check your USB drive VID/PID. Write down the info somewhere as we will need it later. 4 - Now launch OSFMount. Select Mount New, then select the image file you downloaded earlier (i.e. .img extension file) to open. Now select partition 0 (the one that is 15 MB). Click Ok. Then at the bottom of the window make sure to un-tick the "Read only drive". Click Ok. The partition should now be mounted in file explorer. At this point you can navigate to the /grub directory and edit the grub.cfg file. If you need to replace the extra.lzma ramdisk with the custom ramdisk provided above then you will also need to mount partition 1 (the one that is 30 MB). Below is what you will see in the grub.cfg file. I am only showing below the portion of the code that is relevant for the purpose of this tutorial [...] set extra_initrd="extra.lzma" set info="info.txt" set vid=0x058f set pid=0x6387 set sn=C7LWN09761 set mac1=0011322CA785 set rootdev=/dev/md0 set netif_num=1 set extra_args_3615='' set common_args_3615='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet' set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0' set default='0' set timeout='1' set fallback='1' [...] You want to modify the following: Change vid=0x090C to vid=0x[your usb drive vid] Change pid=0x1000 to pid=0x[your usb drive pid] Change sn=C7LWN09761 to sn=generate your sn here with DS3615xs or DS 3617xs or DS916+ model (this will depend on which loader you chose) Change mac1=0011322CA785 to mac1=[your NIC MAC address #1]. You can also add set mac2=[your NIC MAC address #2] and so on until mac4 if you have multiple NICs. However, this is not necessary. Recommended: Change set timeout='1' to set timeout='4' - This will allow you more time to make a selection in the Grub Boot Menu when it appears on screen. Once you are done editing the grub.cfg file, save it and close your text editor. Now in OSFMount click on Dismount all & Exit. You are now ready to burn the image to your USB drive. 5 - Now use Win32 Disk Imager to burn the image file onto the USB drive. This will also make the USB drive bootable. 6 - Eject and unplug the USB drive from your workstation. Plug it in your NAS (avoid USB 3.0 ports. Use USB 2.0 port if available). Boot your NAS and before doing anything fancy, access your BIOS so to make your USB drive the 1st boot drive if it's not the case. The Jun official loader can boot in UEFI or in legacy BIOS, so you chose what suits you best. Also, make sure your HDDs are booting in AHCI mode and not in IDE. Finally, if disabled, also enable the serial port in BIOS. Some BIOS don't have this option so don't get too cranky on this if you can't find it. Save changes to the BIOS and REBOOT the NAS. 7 - Once rebooted, if you have a monitor connected to your NAS you will see the following Grub Boot Menu: ADVICE: even before you see the Grub Boot Menu press the up/down key. This will stop the countdown so you will be able to select the desired line. You won’t see much other than the following after you press enter: If you booted the USB drive in EFI mode then you will see the same text without the last 3 lines but that's ok. 8 - Now go back to your workstation, and launch Synology Assitant or go to http://find.synology.com. Within one minute or so you should normally be able to see your NAS on your local network (it took ~55 seconds on a test I did on a VM). Just follow the instructions and either chose "Install" if you wish to have a clean install or chose “Migration” if you are coming from DMS 5.2 and wish to update while retaining your data. You will be asked to provide the .PAT file you downloaded earlier (DSM_DS3615xs_15217.pat or DSM_DS3617xs_15217.pat or DSM_DS916+_15217.pat). 9 - When the migration is finished you will most probably have to update some of your packages. You can then proceed and update DSM 6.1 up to DSM DSM 6.1.7-15284. It is possible you might either need to hard reboot or re-image your usb drive. Make sure to deactivate auto-updates within DSM. Link to individual files (DSM and critical updates) can be found here: https://xpenology.com/forum/topic/7294-links-to-dsm-and-critical-updates/. DO NOT UPDATE TO DSM 6.2. The loader is not compatible. 10 - You are done. If you have questions, first search the forum and/or Google then leave a comment if nothing helps. Please provide your hardware specifications (motherboard model, LAN controller, driver controller etc). Failure to prove such information will lead to the post being deleted or not answered. -------------- Note 1: If after following the tutorial you can’t find your NAS through http://find.synology.com ou Synology Assistant it is highly possible that the drivers of your NIC are not included in the ramdisk of the loader. Make an effort and use Google to know what modules your NIC and HDD controller are using, then check if those modules are included in the custom extra.lzma ramdisk. If yes then use the custom ramdisk. Don't ask me to look for you. If nothing works then ask your question. Note 2: Synology increased security since the introduction of DSM 6. Root access through SSH is no longer possible out of the box. You can however use your admin account and elevate permissions with the following command if you need root permissions: sudo -i Note 3: Please check you have the right VID/PID prior proceeding. If you get the following error ”Failed to install the file. The file is probably corrupted. (13)" it most certainly means your VID and/or PID is/are wrong. If you still have the same error message after verifying the VID/PID then try another USB drive. Note 4: Configuration added to the grub.cfg file can also be done directly during the Grub Boot Menu, so technically you can skip Point 4 and burn the image on the USB drive without editing anything (read Point 5 onward first). If you wish to do the changes from the Grub Boot Menu directly you need to press the letter 'C' when you see the Boot Menu. You will literally only have one second, so be fast. Once you press 'C' you will be in a Grub command line environment. To change your VID enter the following: vid 0xYOUR 4 DIGITS USB DRIVE VID Do the same for pid, sn and mac1. Press enter at each command. The commands are: pid 0xYOUR 4 DIGITS USB DRIVE PID sn YOUR NAS SERIAL NUMBER mac1 YOUR NAS MAC1 ADDRESS If you have multiple NICs you can also issue mac2, mac3 and mac4 as commands. Maximum is mac4. See below: mac2 YOUR NAS MAC2 ADDRESS mac3 YOUR NAS MAC3 ADDRESS mac4 YOUR NAS MAC4 ADDRESS If you think you made a mistake in the numbers simply re-issue the command. When you are done press esc and select the appropriate menu entry. Below is an example (fake numbers) of how it looks under the Grub command line environment : Note 5: If you encounter the error "We've detected errors on your hard drives [drive number] and the SATA ports have also been disabled" during installation, then you have to fallback to adding SataPortMap to the grub environment. Press the letter 'C' at the Grub Boot Menu and then add the following: append SataPortMap=XX where XX is the number of drives. Don’t forget to update this parameter if you add additional drives to your machine. If you use Reinstall, don't forget to re-select the first line of the Boot Menu once the NAS has rebooted after the installation else the Loader will re-select Reinstall and you will be faced with some issues so please beware of this. @@@@@@@@ What does SataPortMap mean? @@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ ############## Know issues ##################### - When running on a slow single core machine, there is a race condition that causes the patcher to load too late. The most obvious sign is that console is not working properly. - Some ethernet drivers crash when set MTU above about 4096 (Jumbo frame). ############# Included default modules & firmwares in Jun's Loader ############# ############## Tutorial UPDATES ##################
  12. 1 point
    Works for baremetal g8and nc 360t 6.2.2 dsm Wysłane z mojego SM-G970F przy użyciu Tapatalka
  13. 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 >
  14. 1 point
    You just see the "duplicate" extra when you unpack the extra.lzma ( cpio -idv < extra ) You' re right for the firmware, i'll test to remove then and see what's loaded. Nice ! but i did not make a lot, i just removed a driver
  15. 1 point
    у меня как раз RLC-423-5М прекрасно работает! pan-tilt настраивается в SS без проблем Да, дорого! Но по сравнению совсем с китаем-идеальное решение. на бовижн возможно будут проблемы с настройкой pan-tilt. Если такая функция не нужна то смело ее берите. По Онвив она будет работать
  16. 1 point
    finally done and migrated from 3715xs to 3615xs. The complete system is running with DSM 6.2 24922 U2 with 1.03b loader for 3615xs now on HP Gen8. Thanks for all support. Nice rest of the week
  17. 1 point
    Bonjour, Le diagnostic me semble bon, soit le système, soit la CM, soit... un câble peut-être Mais le système en dernier recours, le plus logique étant de remplacer le câble potentiellement en cause, où de le déplacer pour voir si le problème suit le port ou le disque sur lequel il est connecté. Ensuite, refaire la clef USB car c'est le plus facile. Quelques précisions : - SHR n'est pas propriétaire au sens habituel du terme, c'est une combinaison de raid soft linux (tout à fait classique) mais non pas sur des disques physiques mais sur des volumes logiques (LVM) reposant sur cette technologie logicielle pour répartir les données d'un volume sur un ou plusieurs disques physiques. Il est tout à fait possible de récupérer des données écrites avec SHR avec une simple distribution linux (liveCD ou liveUSB). - Le RAID de la carte mère (la plupart du temps c'est du miroir ou du JBOD) ne doit pas être utilisé, tout est géré par le NAS en raid soft (RAID5 par défaut sur le DSM6) ou SHR (sur DSM5 et en l'activant sur DSM6). Si le raid de la CM est utilisé, alors il est possible que ce soit lui qui provoque une incohérence quelconque et fasse passer le disque en faut (dans ce cas, l'absence d'erreur SMART serait logique). Donc, pour résumer : - Supprimer le raid de la CM s'il est activé (APRÈS SAUVEGARDE DES DONNÉES), cette opération provoque en principe la perte de la structure du disque, donc de l'accès aux données - Déplacer ou changer le câble SATA en cause - Déplacer le disque en cause sur un autre port SATA (IDEM, SAUVEGARDE AVANT) Jacques
  18. 1 point
    @Rezdbic Что-то не так поняли, лицензия для расширения функционала.
  19. 1 point
    WELCOME BACK @FOXBI !!! You are most welcome!!! I hope all is well with you. I will look forward to your renewed creative magic. 😎
  20. 1 point
    Synology NAS systems are - along with QNAPs - currently the target of a wide brute-force attack. A botnet tries to break in via weak passwords and infects the system with ransomware. Once infected, it encrypts all files and data. This affects systems which are reachable over the internet (open firewall ports / NAT). To protect yourself you should - activate the DoS protection including account blocking - apply strong password rules to all users - create a new admin account with a strong password and disable the standard „admin“ account More informations: https://www.synology.com/en-global/company/news/article/2019JulyRansomware
  21. 1 point
    Just correct cpu information view It does not affect performance or anything.
  22. 1 point
    My guess is that the maximum thread represented in DSM is 8. I have not had a system with more than 8 threads, so I have not checked, can you show me the full results of your system cat /proc/cpuinfo ?
  23. 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!
  24. 1 point
    Try to login from another computer or change ip. Default SSH port is 23, telnet is 22. Did you enable acsess to ssh/telnet in CP?
  25. 1 point
    😉 So can you give us more details about your system?
  26. 1 point
    Salut, DSM 4 ? C'est vieux, le loader n'est même plus dispo Se que je te conseillerai c'est d'essayer de migrer vers 5.2 ! https://xpenology.com/forum/topic/7848-links-to-loaders/ D'abord essaye ta config, voir si elle est compatible avant de faire quoi sue se soit sur les disques dur avec tes données ! L'idéal étant de débrancher tout des DD, de brancher un disque de test et d'essayer linstallation de DSM 5.2 ! Si le hack fonctionne bien ( et donc le NAS ) alors tu peut essayer la migration !
  27. 1 point
    Why would some invest time for an arm bootloader? A system with low energy consumption can be build with Celeron J3455 CPUs today. If you want it to be cheap like the Pi, you might want to take a look at the AtomicPI. It commes with a x86-64 cpu. Though, the nic is a RTL8111G, so you won't be able to run the latest DSM versions. I doubt this soc board is powerfull enough to run ESXi on it - even if it would, the RTL8111G is not supported ootb.
  28. 1 point
    8.2.2 тоже работает стабильно но только с рестартом службы. Так что решать вам.
  29. 1 point
  30. 1 point
    Tu as bien changé tes VID et PID et mis ceux de ta clef ? Peux-tu générer un autre numéro de série. J'ai eu le coup et chez moi, c'est comme ça que j'ai réglé le problème.
  31. 1 point
    Ну тады либо wifi мост, либо PLC адаптеры вместо второго или первого шнурка. Ну и еще вариант, хрень в роутер, а к роутеру по вафле от всех остальных устройств.
  32. 1 point
    salut @nicoueron Cela fait bien longtemps que je n'etais pas passé ici. Je suis passé sur un vrai syno pour une question de réactivité sur les MAJ et pour la conso Cela dit, j ai sorti mon ancien PC qui servait pour XPE et ta config fonctionne parfaitement. J'en ai profité pour mettre EXSi et aucun soucis avec ta config. Bon boulot ^^
  33. 1 point
    1.04b & DS918+ does not support your hardware - Intel 4th Gen CPU or above 1.03b & DS3615xs - works fine under 'Legacy BIOS' - you have to press F10 (or whatever your Boot Menu F-Key) and manually select USB Boot I have to do this every time I reboot, Q77 has KVM using Intel AMT8, so not so bad as I can do this remotely. Also i dont reboot every often. - we need a 1.03c or 1.04 for DS3615xs with UEFI boot fixed
  34. 1 point
    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-1 - Loader version and model: JUN'S LOADER v1.03b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - i7-3770k, MSI MPower Max z87 Motherboard. - Additional comments: Reboot Required
  35. 1 point
    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-1 - Loader version and model: JUN'S LOADER v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: VM - ESXI 6.7u2 - Additional comments: E1000e nic, 2 sata adapters, removed usb 2 adapter - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922-1 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: VM - ESXI 6.7u2 - Additional comments: E1000e nic, 2 sata adapters, RDM Disks, USB 3 passthrough
  36. 1 point
    Thank you Xtronets for this tip. You actually made my day!
  37. 1 point
    The latest script doesn't work with DSM version 6.2.2-24922, however it seems to work fine under mobile.
  38. 1 point
    Решил немного облегчить жизнь новичкам и тем, кто успел подзабыть, где и что лежит. 1. Ссылка на загрузчики от 5.0 до 6.2 2. Как установить на примере загрузчика 1.04b для DSM 6.2 (918+) 3. Совместимость загрузчиков 6.0-6.2 и железа 4. Тестирование и как проверить работает ли транскодинг на примере Asrock J4105-itx, там же сборка extra.lzma с гибернацией дисков 5. Как отредактировать grub.cfg и заменить extra.lzma на работающей хрени 6. Пакет для активации железной кнопки Power off на корпусе хрени (крайняя версия 6.2-0002, на нее и ссылка) 7. Корректное отображение процессора в Информационном центре 8. Librusec на хрени через COPS (скачивание в fb2 и mobi на читалку с wi-fi прямо с хрени) 9. Torrent TV через Ace Stream в docker (актуальные команды в посте ID 273, инструкция в следующем) Просьба ссылки тут не обсуждать, добавляйте свои, если посчитаете полезным.
  39. 1 point
    Hey there, this has been asked a couple of times but the only answers (if someone answered at all) were like, "Why bother? It works." In the picture above, both installations work. My inner monk (as well as my boss) prefer the right cabinet, however. In the following example I'll refer to a 10-bay system, if your setup is different, you can easily edit the numbers. I assume, you have successfully installed XPEnology on your box, following Polanskiman's tutorial. If you encountered any problems with drives not being recognized, or displayed as eSATA, etc. you checked Hedii's guide, as well. Still, your drives show up like this, maybe because your chipset would support 6 drives but your mainboard only offers 4 connectors. Drives 1,3,5,6 are connected to the mainboard, drives 7-10 to an additional 4-port controller, drives 11 and 12 to another 2-port controller. Drives 2 and 4 look like this in your dmesg: [ 1.835796] ata1: SATA max UDMA/133 abar m2048@0xfe525000 port 0xfe525100 irq 47 [ 1.835802] ata2: DUMMY [ 1.835806] ata3: SATA max UDMA/133 abar m2048@0xfe525000 port 0xfe525200 irq 47 [ 1.835807] ata4: DUMMY [ 1.835812] ata5: SATA max UDMA/133 abar m2048@0xfe525000 port 0xfe525300 irq 47 [ 1.835813] ata6: SATA max UDMA/133 abar m2048@0xfe525000 port 0xfe525400 irq 47 Playing around with internalportcfg (Hedii's guide) did not help you, getting rid of these "DUMMY" ports. Luckily Jun's loader has a feature called "sata_remap", mentioned here and here, that - well - does what it says. To fill the gaps, you can remap the drives from your 2-port controller. Reboot and press "C" in the GRUB menu. (See Polanskiman's guide "Step 7" and "Note 4" if you need help). At the command line enter: append "sata_remap=10>1:11>3:1>10:3>11" Be aware, that counting starts at 0, here. 10>1 will remap drive 11 to 2, 11>3 will remap drive 12 to 4, etc. After the next reboot, it will look like this: As you can see, the drives are now numbered sequentially from 1 to 10 with the two DUMMYs on ports 11 and 12. Now it's easy to hide them. Like in Hedii's guide open an SSH connection to your NAS and edit as follows: # first file to modify vi /etc/synoinfo.conf # second file to modify vi /etc.defaults/synoinfo.conf # In each file look for the line maxdisks="12" # and change it to maxdisks="10" Reboot and you finally have a 10-bay box displaying 10 sequentially numbered drives: Hope, this will help one or the other. Best Regards, The_Mole
  40. 1 point
    - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.1-23824 Update 2 - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - MSI H310I PRO, Intel Pentium Gold G5400, onboard LAN Realtek
  41. 1 point
    Кому лениво перезаписывать флешку или нужно сделать это удаленно при редактировании grub.cfg и замене extra.lzma, вспомнил про старый трюк, как это сделать прямо на работающей хрени: 1. Заходим по ssh через Putty или терминал 2. Делаем следующее: Admin@your_DS:~$ sudo -i #Заходим под root Password: #Вводим пароль Adminской учетки root@your_DS:~# mkdir -p /tmp/synoboot_part0 #Создаем временный каталог для монтирования 0 раздела загрузочной флешки root@your_DS:~# mkdir -p /tmp/synoboot_part1 #Создаем временный каталог для монтирования 1 раздела загрузочной флешки root@your_DS:~# cd /dev root@your_DS:/dev# mount -t vfat synoboot1 /tmp/synoboot_part0 #Монтируем 0 раздел загрузочной флешки root@your_DS:/dev# mount -t vfat synoboot2 /tmp/synoboot_part1 #Монтируем 1 раздел загрузочной флешки root@your_DS:/dev# ls /tmp/synoboot_part0 #Проверяем монтирование 0 раздела загрузочной флешки bzImage EFI grub info.txt root@your_DS:/dev# ls /tmp/synoboot_part1 #Проверяем монтирование 1 раздела загрузочной флешки checksum.syno extra2.lzma extra.lzma grub_cksum.syno rd.gz Sone.9 zImage 3. С помощью nano/mc правим grub.cfg и/или с помощью команд/mc заменяем extra.lzma 4. Перезагружаем хрень штатными средствами 5. Если перезагрузка сразу не планируется, то на всякий случай размонтируем и зачищаем: root@your_DS:/dev# cd / root@your_DS:/# umount /tmp/synoboot_part0 # Размонтируем 0 раздел загрузочной флешки root@your_DS:/# umount /tmp/synoboot_part1 # Размонтируем 1 раздел загрузочной флешки root@your_DS:/# rm -r /tmp/synoboot_part0 # Удаляем временный каталог root@your_DS:/# rm -r /tmp/synoboot_part1 # Удаляем временный каталог
  42. 1 point
    Thanks for the script. CPU information updated successfully. But the number of threads shows wrong. For Intel core i7 8700 processor, It is 6 core and 12 threads. But system shows 8 threads only.
  43. 1 point
    Обычно они отваливаются секунд на 10-30 не более. Затем опять подключаются.
  44. 1 point
    @XbladeX From earlier experience with a problem like that: try these steps: Activate the SSH service in DSM (if not active) Connect to your NAS with an SSH client (e.g. putty) (or from Win 10, open a cmd window, run : ssh admin@my.nas.ip (replace with the actual IP) Enter your credentials (user: admin) Change folder to root (cd /) Delete the xpenoboot folder (sudo rm -r .xpenoboot) If the SSH service keeps stopping, you have to be quick.
  45. 1 point
    Hi @bearcat 1 - What hardware are you currently using? Hp NL54 Micreoserver 2 - What bootloader are you using? Baremetal Boot 1.3b 3 - What is your Synology "base" (3615/3617/...)? DS3615xs -Versión - 6.2- 23739 4 - Has it been working before? - Yes, Works fine before, with boot 1.02b-red And 6.1.7 - 15284 5 - Did it stop working after an update from 6.1.7 to 6.2.1? I have Internal NIC and at the momnet I can´t update up to 6.2 - 23739 ( Need Intel NIC for Update 6.2.1) 6 - Are you using any "extra.lzma"? No, Dot use Extra.Izma 7 - Have you at any time been using any other types of bootloaders? (nanoboot/xpenoboot/…) Yes the first Boot used was "XPEnoboot_DS3615xs_5.2-5644.5" in year 2016, in 2017 UPDATE to synoboot-1.02b and All Works fine, NOW in 2019 i try Update and i have this problem Thank for all!
  46. 1 point
    If you have a dynamic IP, you will need to setup a DDNS to access your NAS from outside your local network. So to start thing off you will need to open an account with a DDNS service provider. There are plenty out there, some paid, some free. The two below are the ones that I use personally. They are free. If you find others then you should also be able to use those. Some of these providers might already be part of the list included by Synology in which case you can skip the 'Customize' button and simply use the 'Add' button and select your service provider from there. The configuration example I am giving below will be based on duckdns.org because it's the easiest I have seen out there but unfortunately it is not included in the DDNS service providers list included by Synology so you will need to use the 'Customize' button first. - http://www.duckdns.org - http://www.nsupdate.info Once you have chosen your domain with duckdns.org you will need to configure DSM accordingly. So here is how to: In Control Panel go to External Access (1), then click on Customize (2). A new window should open. You need to fill in as per the image. To save you some time you can copy paste from the code tag provided below the image: http://www.duckdns.org/update?domains=__HOSTNAME__&token=__PASSWORD__&ip=__MYIP__ When you are done click Save. The window should close. Now click on Add (3), see first image. A new window should open. Select *DuckDns from the service provider list and fill in your duckdns domain, username and token: Click on Test Connection to verify that it's working. If it is working you should see the word Normal in green next to Status. You can then click Ok. If it is not working then it means you screwed up somewhere. Recheck query URL, domain, username and token. All that is left to do is to configure port forwarding on your router. This is called at times "port forwarding" or "port mapping". You need to check with your router's user guide as sometimes the wording differs from one brand to the other. The port(s) you will be forwarding to your box also need to be opened on DSM's firewall else DSM will refuse access to the port/service requested. If your ISP implements double NAT you might have to do some additional configuration to your router to allow the ports to be forwarded correctly. Check with your ISP first and also check this site or this site on how to overcome double NAT. Google is your friend. Note of caution here: If you want to make things very safe you would only port forward VPN ports. This means that you can only access your box via VPN which in turn then gives you full access to the box (and to your local network if configured accordingly) once a VPN connection is established. You could also port forward the GUI ports (usually 5000/5001 or the ones you would have customised). This would give you full GUI access to DSM from outside of your network but this can be unsafe specially if you don't have a strong password and proper firewall and safety mechanisms configured in DSM. You could also just forward the port(s)/service(s) that you need. It really all depends what you are using your box for but in most cases the VPN solution is the safest although not the most convenient. NEVER EVER port forward port 22 unless you know exactly what you are doing. To test that your box is accessible from the outside world while being at home you could use your smart phone in data mode (not in wifi) at the following address: http://[yourdomain].duckdns.org:[port number] or https://[yourdomain].duckdns.org:[port number] - Do no put www
  47. 1 point
    Is It influences productivity? If DSM shows 4 cores, then 6 work all the same, right?
  48. 1 point
    Worked well for me on my Gen8 Microserver also, many thanks for creating and maintaining.
  49. 1 point
    364522dsmhyperv.png 60190dsm6hypervdata.png
  50. 1 point
    Bonjour, Les versions 1.01 (DSM 6.0.2) et 1.02b (DSM 6.1.X) de Jun's sont complètements refaites et fonctionnelles avec une table de partition MBR. J'ai posé sur le dépôt toutes les images que j'ai refaites via mon outil de conversion automatique. Voici le lien du dépôt : https://mega.nz/#F!cIUXnCSS!VruDf235t2uLcRxIjji3qQ En espérant faire avancer cette belle communauté. PS : Les fichiers "Convert_By_Genesys" présent sur les deux partitions des launchers contiennent le numéro de version du loader et le type de table de partition utilisé. PS2 : Je continuerai de mettre des versions avec une tables de partition MBR pour les prochain loaders. PS3 : Le code de base de mon outil de conversion automatique est le même que Jun's : https://github.com/kref/scripts C'est un plaisir de pouvoir faire avancer la communauté XPEnology