Leaderboard

This is the new 2nd test version of the driver extension for loader 1.04b and 918+ DSM 6.2.2, network drivers for intel and realtek are now all latest and the same as in 3615/17 from mid. december (also broadcoam tg3 driver is working), tries to address the problems with the different GPU's by haveing 3 versions of the pack additional information and packages for 1.03b and 3615/3617 are in the lower half under a separate topic (i will unify the 918+ and 3615/17 parts later as they are now on the same level again) mainly tested as fresh install with 1.04b loader with DSM 6.2.2, there are extra.lzma and extra2.lzma in the zip file - you need both - the "extra2" file is used when booting the 1st time and under normal working conditions the extra.lzma is used (i guess also normal updates - jun left no notes about that so i had to find out and guess). Hardware in my test system used additional driver: r8168, igb, e1000e, bnx2x, tn40xx, mpt2sas The rest of the drivers just load without any comment on my system, i've seen drivers crashing only when real hardware is present so be warned, i assume any storage driver beside ahci and mps2sas/mpt3sas as not working, so if you use any other storage as listed before you would need to do a test install with a new usb and a single empty disk to find out before doing anything with your "production" system i suggest testing with a new usb and a empty disk and it that's ok then you have a good chance for updating for updating its the same as below in the 3615/17 section with case 1 and 2 but you have extra.lzma and extra2.lzma and you will need to use https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS918+_24922.pat most important is to have zImage and rd.gz from the "DSM_DS918+_24922.pat" file (can be opened with 7zip) together with the new extra/extra2, same procedure as for the new extra for 3615/17 (see below) all 4 files extra.lzma, extra2.lzma (both extracted from the zip downloaded), zImage and rd.gz go to the 2nd partition of the usb (or image when using osfmount), replacing the 4 files there if you want the "old" files of the original loader back you can always use 7zip to open the img file from jun and extract the original files for copying them to usb if really wanting to test with a running 6.2.x system then you should empty /usr/lib/modules/update/ and /usr/lib/firmware/i915/ before rebooting with the new extra/extra2 rm -rf /usr/lib/modules/update/* rm -rf /usr/lib/firmware/i915/* the loader will put its files on that locations when booting again, this step will prevent having old incompatible drivers in that locations as the loader replaces only files that are listed in rc.modules and in case of "syno" and "recovery" there are fewer entries, leaving out i915 related files, as long as the system boots up this cleaning can be done with the new 0.8 test version there a 3 types of driver package, all come with the same drivers (latest nic drivers for realtek and intel) and conditions/limitations as the 3615/17 driver set from mid. december (mainly storage untested, ahci and mpt3sas is tested). 1. "syno" - all extended i915 stuff removed and some firmware added to max compatibility, mainly for "iGPU gen9" (Skylake, Apollo Lake and some Kaby Lake) and older and cases where std did not work, i915 driver source date: 20160919, positive feedback for J3455 and J1800 2. "std" - with jun's i915 driver from 1.04b (tested for coffee lake cpu from q2/2018), needed for anything newer then kaby lake like gemini lake, coffee lake, cannon lake, ice lake, i915 driver source date: 20180514 - as i had no source i915 driver is the same binary as in jun's original extra/extra2, on my system its working with a G5400, not just /dev/dri present, tested completely with really transcoding a video, so its working in general but might fail in some(?) cases, also 8th/9th gen cpu like i3/i5 8100/9400 produce a /dev/dri, tested with a 9400 and it does work 3. "recovery" - mainly for cases where the system stops booting because of i915 driver (seen on N3150 braswell), it overwrites all gpu drivers and firmware with files of 0 size on booting so they can't be loaded anymore, should also work for any system above but guarantees not having /dev/dri as even the firmware used from the dsm's own i915 driver is invalid (on purpose) - if that does not work its most likely a network driver problem, safe choice but no transcoding support start with syno, then std and last resort would be recovery anything with a kernel driver oops in the log is a "invalid" as it will result in shutdown problems - so check /var/log/dmesg the often seen Gemini Lake GPU's might work with "std", pretty sure not with "syno", most (all?) testers with gemini lake where unsuccessful with "std" so if you don't like experimenting and need hardware transcoding you should wait with the version you have the "_mod" on the end of the loader name below is a reminder that you need to to "modding" as in make sure you have zImage and rd.gz from DSM 6.2.2 on you usb for booting, the new extra.lzma will not work with older files 0.8_syno ds918+ - extra.lzma/extra2.lzma for loader 1.04b_mod ds918+ DSM 6.2.2 v0.8_syno http://s000.tinyupload.com/?file_id=27662133308664190275 SHA256: 21B0CCC8BE24A71311D3CC6D7241D8D8887BE367C800AC97CE2CCB84B48D869A 0.8_std ds918+ - extra.lzma/extra2.lzma for loader 1.04b_mod ds918+ DSM 6.2.2 v0.8_std http://s000.tinyupload.com/?file_id=00354004133254441591 SHA256: F611BCA5457A74AE65ABC4596F1D0E6B36A2749B16A827087D97C1CAF3FEA89A 0.8_recovery ds918+ - extra.lzma/extra2.lzma for loader 1.04b_mod ds918+ DSM 6.2.2 v0.8_recovery http://s000.tinyupload.com/?file_id=02568989419278984390 SHA256: 5236CC6235FB7B5BB303460FC0281730EEA64852D210DA636E472299C07DE5E5 !!! still network limit in 1.04b loader for 918+ !!! atm 918+ has a limit of 2 nic's (as the original hardware) If there are more than 2 nic's present and you can't find your system in network then you will have to try after boot witch nic is "active" (not necessarily the onboard) or remove additional nic's and look for this after installation You can change the synoinfo.conf after install to support more then 2 nic's (with 3615/17 it was 8 and keep in mind when doing a major update it will be reset to 2 and you will have manually change this again, same as when you change for more disk as there are in jun's default setting) - more info's are already in the old thread about 918+ DSM 6.2.(0) and here https://xpenology.com/forum/topic/12679-progress-of-62-loader/?do=findComment&comment=92682 I might change that later so it will be set the same way as more disks are set by jun's patch - syno's max disk default for this hardware was 4 disks but jun's pach changes it on boot to 16!!! (so if you have 6+8 sata ports then you should not have problems when updating like you used to have with 3615/17) Basically what is on the old page is valid, so no sata_*, pata_* drivers Here are the drivers in the test version listed as kernel modules: The old thread as reference !!! especially read "Other things good to know about DS918+ image and loader 1.03a2:" its still valid for 1.04b loader !!! This section is about drivers for ds3615xs and ds3617xs image/dsm version 6.2.2 (v24922) Both use the same kernel (3.10.105) but have different kernel options so don't swap or mix, some drivers might work on the other system some don't at all (kernel oops) Its a test version and it has limits in case of storage support, read careful and only use it when you know how to recover/downgrade your system !!! do not use this to update when you have a different storage controller then AHCI, LSI MPT SAS 6Gb/s Host Adapters SAS2004/SAS2008/SAS2108/SAS2116/SAS2208/SAS2308/SSS6200 (mpt2sas) or LSI MPT SAS 12Gb/s Host Adapters SAS3004/SAS3008/SAS3108 (mpt3sas - only in 3617), instead you can try a fresh "test" install with a different usb flash drive and a empty single disk on the controller in question to confirm if its working (most likely it will not, reason below) !!! The reason why 1.03b loader from usb does not work when updating from 6.2.0 to 6.2.2 is that the kernel from 6.2.2 has different options set witch make the drivers from before that change useless (its not a protection or anything), the dsm updating process extracts the new files for the update to HDD, writes the new kernel to the usb flash drive and then reboots - resulting (on USB) in a new kernel and a extra.lzma (jun's original from loader 1.03b for dsm 6.2.0) that contains now incompatible drivers, the only drivers working reliable in that state are the drivers that come with dsm from synology Beside the different kernel option there is another thing, nearly none of the new compiled scsi und sas drivers worked They only load as long as no drive is connected to the controller. ATM I assume there was some changes in the kernel source about counting/indexing the drives for scsi/sas, as we only have the 2.5 years old dsm 6 beta kernel source there is hardly a way to compensate People with 12GBit SAS controllers from LSI/Avago are in luck, the 6.2.2 of 3617 comes with a much newer driver mpt3sas then 6.2.0 and 6.2.1 (13.00 -> 21.00), confirmed install with a SAS3008 based controller (ds3617 loader) Driver not in this release: ata_piix, mptspi (aka lsi scsi), mptsas (aka lsi sas) - these are drivers for extremely old hardware and mainly important for vmware users, also the vmw_pvscsi is confirmed not to work, bad for vmware/esxi too Only alternative as scsi diver is the buslogic, the "normal" choice for vmware/ESXi would be SATA/AHCI I removed all drivers confirmed to not work from rc.modules so they will not be loaded but the *.ko files are still in the extra.lzma and will be copied to /usr/modules/update/ so if some people want to test they can load the driver manually after booting These drivers will be loaded and are not tested yet (likely to fail when a disk is connected) megaraid, megaraid_sas, sx8, aacraid, aic94xx, 3w-9xxx, 3w-sas, 3w-xxxx, mvumi, mvsas, arcmsr, isci, hpsa, hptio (for some explanation of what hardware this means look into to old thread for loader 1.02b) virtio driver: i added virtio drivers, they will not load automatically (for now), the drivers can be tested and when confirmed working we will try if there are any problems when they are loaded by default along with the other drivers they should be in /usr/modules/update/ after install To get a working loader for 6.2.2 it needs the new kernel (zImage and rd.gz) and a (new) extra.lzma containing new drivers (*.ko files) zImage and rd.gz will be copied to usb when updating DSM or can be manually extracted from the 6.2.2 DSM *.pat file and copied to usb manually and that's the point where to split up between cases/way's case 1: update from 6.2.0 to 6.2.2 case 2: fresh install with 6.2.2 or "migration" (aka upgrade) from 6.0/6.1 Case 1: update from 6.2.0 to 6.2.2 Basically you semi brick your system on purpose by installing 6.2.2 and when booting fails you just copy the new extra.lzma to your usb flash drive by plugging it to a windows system (witch can only mount the 2nd partition that contains the extra.lzma) or you mount the 2nd partition of the usb on a linux system Restart and then it will finish the update process and when internet is available it will (without asking) install the latest update (at the moment update4) and reboot, so check your webinterface of DSM to see whats going or if in doubt wait 15-20 minutes check if the hdd led's are active and check the webinterface or with synology assistant, if there is no activity for that long then power off and start the system, it should work now Case 2: fresh install with 6.2.2 or "migration" (aka upgrade) from 6.0/6.1 Pretty much the normal way as described in the tutorial for installing 6.x (juns loader, osfmount, Win32DiskImager) but in addition to copy the extra.lzma to the 2nd partition of the usb flash drive you need to copy the new kernel of dsm 6.2.2 too so that kernel (booted from usb) and extra.lzma "match" You can extract the 2 files (zImage and rd.gz) from the DSM *.pat file you download from synology https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3615xs_24922.pat or https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3617xs_24922.pat These are basically zip files so you can extract the two files in question with 7zip (or other programs) You replace the files on the 2nd partition with the new ones and that's it, install as in the tutorial In case of a "migration" the dsm installer will detect your former dsm installation and offer you to upgrade (migrate) the installation, usually you will loose plugins, but keep user/shares and network settings DS3615: extra.lzma for loader 1.03b_mod ds3615 DSM 6.2.2 v0.5_test http://s000.tinyupload.com/?file_id=87576629927396429210 SHA256: BAA019C55B0D4366864DE67E29D45A2F624877726552DA2AD64E4057143DBAF0 DS3617: extra.lzma for loader 1.03b_mod ds3617 DSM 6.2.2 v0.5_test http://s000.tinyupload.com/?file_id=06641076704622277403 SHA256: 4A2922F5181B3DB604262236CE70BA7B1927A829B9C67F53B613F40C85DA9209

Hi all, I just check if this project is still alive and it is and some amazing work have been done. Unfortunately I don't have time to spent of this but I just seen that Synology uploaded new source code for 24922branch: https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/24922branch/ Long life to XPEnology

Moin Jungs, ich habe mich neulich in einigen chinesischen Foren rum getrieben und die Jungs haben einen Weg gefunden QNAP auf eigener Hardware zu betreiben. Ich habe es auf einem J3455-ITX Board getestet und es funktioniert tadellos. Man kann sich das QNAP Modell aussuchen und die Installation ist recht simpel (mittlerweile). Besteht Interesse an einer Anleitung?

personne peux nous partager un *.pat ?

Apart from the kernel version that changes from DSM 6.1 (3.10.102) to 6.2 (3.10.105), does syno included new protection ? The issue with 6.2 when loading drivers/modules that crash, does it crash because of protection or "just" because these modules are not build with latest GPL released ? I've been offline from long long time but I discovered that Syno released GPL sources for DSM 6.1-15047 (kernel 3.10.102) in september 2017 and no one tried to build it's own kernel from there. I am very suprised since there are loader that fool the protection, the only missing part is a working kernel that we can custom.

@wanye are you sure you need the few things you got from updating, you might just use the 2nd option in the loader and do a fresh install, your raid/data partitons should not be effected, this step would on do a fresh install of dsm on the system partition(s) it might be much less time consuming to redo the ip address and user/group, shares configuration, the plugins would be needing reinstalling new versions anyway even if ou could use the updated dsm you also need diferent drivers when using 6.2.2, the loader 1.03b has drivers that will fail in a lot of cases with 6.2.2 as the "original" drivers from jun a made for 6.2.0 and synology made some kernel config changes with 6.2.2 https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/

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.7 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 method, 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.7 up to DSM 6.1.7 critical update 3. 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 ##################

not with that hardware, 1.04b loader is only 918+ and that need min. 4th gen intel cpu (haswell) https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ 3615 or 3617 should work if you use loader 1.03b in its original state you will have to stay with dsm 6.2.0 aka v23739 because of kernel option changes later in the 6.2 versions the driver for 6.2.0 will not work and you will need drivers compiled with these new options but staying on 6.2.0 defeats your purpose upgrading i made drivers for 6.2.2 available mid. december (2nd half about 3615/17), already seen people using it with your hardware https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ yes for 6.2.0 all the time as tg3 driver was in juns default driver set from loader 1.03b and yes for 6.2.2 latest update for about 6 weeks

HP Proliant MicroServer G7 N54L . Новая сетевая карта интел чипсет. DSM 6.2.2 - 24922 . Настройки Биос Мануал навеян моими мимолётными страданиями, описанными в этой теме: Очищен от лишнего, описана только суть В рамках эволюционирования и продвижения вперёд, в светлое будущее ( DSM 6.2.2 - 24922 ), для HP Proliant MicroServer G7 N54L была приобретена новая Сетевая карта на чипсете интел. Ниже приведу настройки Биос_а (BIOS), давшие возможность работать серверу и далее. Имеем HP Proliant MicroServer G7 N54L (Описание подходит и для моделей MicroServer G7 N40L и MicroServer G7 N36L за небольшим исключением некоторых пунктов БИОС_а, которые не влияют на конечный результат.) , имеем модифицированный БИОС, дающий доступ к некоторым, скрытым настройкам (кто то делал без модификации, проверить не могу). Установлена Новая Сетевая карта на чипсете Интел (Модель и количество портов на ваше усмотрение и по вашим потребностям) C1E Support - Disabled , встроенную сетевуху отключаем Atheros AR8132M NIC - Disabled Ну и сами настройки БИОС_А Спасибо Olegin_у и XPEH_у за помощь мне в этих познаниях, коими делюсь с вами.

There is a better way^^ Just activate it: In your browser open the following urls one after another: Replace the following: URL, PORT, USER, PASS, SERIALNUMBER (dont replace any other symbols like : oder ") https://URL:PORT/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=USER&passwd=PASS https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="SERIALNUMBER" To get the current activation status call the 1. query above and then https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=get&version=1 ------------------------------ Example for url: server, port: 5001, user: admin, pass: admin, serialnumber: 123400 https://server:5001/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=admin&passwd=admin https://server:5001/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="123400"

У вас сеть Realtek RTL8111GR и у вас два варианта.. Купить стороннюю сетевую карту от интел или же замена файлов extra.lzma Новый загрузчик: https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg!7AoyySoS Редактируете под себя: Если сторонняя сетевая карта от Интел, то немного правим БИОС. Можно без сторонней карты с заменой extra.lzma, читаем тут Сами файлы DSM берём тут: https://archive.synology.com/download/DSM/release/ 6.2.2 под 3615 - https://archive.synology.com/download/DSM/release/6.2.2/24922/DSM_DS3615xs_24922.pat При правильной подготовке, вам будет предложена миграция и файлы буду сохранены. Не забывайте сделать резервную копию конфигурации в админ разделе и потом восстановите её, если что то не так пойдёт.

Salut, En théorie s'il te dit sa, c'est plutot bon signe C'est que DSM, et donc tes données sont toujours présente. Il te faut suivre la procédure de réinstallaton de DSM. Tu va perdre ta configuration, mais aucune de tes données ( Attention aux questions qu'il pourrait te poser ! ) Dans Synology Assistant, quel est la statut du NAS ? Configuration perdu ou Non installé ? C'est c'est configuration perdu, il te faut suivre les étapes de réinstallation de DSM

hey, quick and dirty. connect via terminal over ssh ... became "root" permissions sudo -i list disks fdisk -l in this example, my source drive Disk /dev/sdr: 931.5 GiB, ... Device Boot Start End Sectors Size Id Type /dev/sdr1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdr2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdr3 9437184 1953320351 1943883168 926.9G fd Linux raid autodetect look for an free md-slot and change "/dev/mdX" mdadm -A --verbose --run /dev/mdX /dev/sdr3 message... mdadm: looking for devices for /dev/md4 mdadm: /dev/sdr3 is identified as a member of /dev/md4, slot 0. mdadm: added /dev/sdr3 to /dev/md4 as 0 mdadm: /dev/md4 has been started with 1 drive. ... ok, its fine needed or not? mdadm -Sf /dev/md4 mdadm -Asf && vgchange -ay check for correctness fdisk -l message... Disk /dev/md4: 926.9 GiB, ... Disk /dev/md127: 2 GiB, ... Disk /dev/md126: 2.4 GiB, ... ... ok make a dir in useable range for "File Station" mkdir /volume1/public/tmp mount "/dev/mdX" with read-only permission mount /dev/md4 /volume1/public/tmp -o ro greets Sky

There is no explicit AMD support OR hyper-v. That needs a different (newly compiled) kernel and that is not the way jun's approach works, it uses the kernel that comes with DSM, this package is only about kernel modules that can be loaded with the original Synology kernel. !!!all sata_* and pata_* drivers are still not working because of the kernel source changes Synology did (same as in kernel 3.10.102 used and modded by Synology), as long as no one writes a patch for this I can use to fix this, it will stay this way !!! The extra.lzma ramdisks provided below have been tested to load on DSM 6.1.3 (15152 kernel source available), but I expect it also to work with 6.1.4 (15217, no source available yet) as it uses the same kernel (3.10.102) as base. To check if the hardware is supported with a driver, use a running DSM installation or boot a live Ubuntu from usb. In console type the following: lspci -k | grep 'Kernel driver' That command will list the used kernel modules for the hardware. Modules for network and storage will be listed. Compare that with the list of modules that comes with the extra.lzma ramdisks provided below. I am trying to keep the same supported hardware for all the three supported DSM images, namely DS3615xs, DS3617xs and DS916+. I will mention if there are differences between the ramdisks. Most likely it will be 916+ as the kernel seems to be compiled with less options then the other two (mostly in the network driver section. If the kernel internal driver cannot be compiled (like missing kernel options) or does not work (like newer hardware revisions not working - the 3.10.102 kernel is kind of "old") I will try to use external sources. By providing the source link, you will speed up the process of supporting your hardware. Below are the custom ramdisks for each version. Modules within them are not interchangeable so don't start playing smart by moving modules between them. It will not work. You also need to de-zip the downloaded file before adding the ramdisk to the loader. extra.lzma for ds3615 v4.8 http://s000.tinyupload.com/?file_id=91524959186499470323 extra.lzma for ds3615 v4.9_test - new Aquantia driver (atlantic.ko) v2.0.10.0, positive feedback to work with Asus XG-C100C http://s000.tinyupload.com/?file_id=15978611613403584302 extra.lzma for ds3617 v4.8 http://s000.tinyupload.com/index.php?file_id=10571518971292995794 extra.lzma for ds916+ v4.8 http://s000.tinyupload.com/?file_id=82597508855747953494 If you wish to make a driver request do so in the topic linked below: If you wish to discuss problems about modules in these ramdisks then drop a post below. Please be specific. Provide ramdisk version and loader model: e.g.: "extra.lzma 4.4 for ds3617". Note: the driver list below with related hardware is based on Trantor/Quicknick's older list for 5.2 and 6.0 so thanks goes to them and all others who helped to build the older list for 5.2 and 6.0. Caption (…) Not compiled for now, ask for it […] Either confirmed by users that it is not working OR not supported for DSM 6.1 (kernel 3.10.102) OR does not load at all. Driver was compiled/tested but removed - if someone finds a way to get it working in some way, tell us here and it will be added

you might want to read this, its a good way of understanding the process for recovering a raid system https://xpenology.com/forum/topic/24525-help-save-my-55tb-shr1-or-mount-it-via-ubuntu/ a easy estimate about the potential loss of data will be to know the sequence number of the disks, to get something you can access again you would need to force one of the disks into the raid set - meaning loss of data, - and then rebuild the redundancy disk but before doing this you need to know what caused the problem and make sure it does not happen again, as in the case above seen it will be a fruitless effort trying to repair a unstable system in a "real" recovery where your date would be worth money you would clone all disks and work with copy's or image files on a proven stable hardware, professional would not try to repair on a system with unknown's this will tell you more about the state of the disks mdadm --detail /dev/md2 mdadm --examine /dev/sd[abcd]5 | egrep 'Event|/dev/sd' also check log files and check s.m.a.r.t. status of the disks, you need to know how it happened are you sure? i can tell you from personal experience that even a 2 disk redundancy is not enough and there can be also file system corruptions just to make sure - you need backup, not more redundancy btw. did you ever thought about possible "other" scenarios? theft, fire, ... in some cases it just needs one big usb disk to cover the most valuable data or maybe cloud storage like this https://www.backblaze.com/blog/synology-cloud-backup-guide/ https://www.backblaze.com/b2/partner-synology.html (i followed them over the years because of the storage pod designs and disk statistics - having data in the cloud is not my thing but might be a option for some people)

si tu as 90% de charge cpu, c'est que le transcodage hardware ne fonctionne pas. Ton docker est-il bien configuré, avec un devices: - /dev/dri:/dev/dri bien déclaré? Pendant un transcodage, Il y a bien un petit (hw) à côté du flux transcodé dans le tableau de bord plex?

Avec https://plexguide.com/threads/howto-enable-nvidia-gpu-support-in-plex-emby.5553/ Et dans les paramètres dans le docker plex : NVIDIA_VISIBLE_DEVICES=all NVIDIA_DRIVER_CAPABILITIES=compute,video,utility

I might be totally off-topic, but did your DSM 5.2 use the "xpenoboot" bootloader? If so, you are now using Jun's bootloader? Then, you might as well look for, and delete the xpenoboot folder (sudo rm -r .xpenoboot), as that is known to cause funky sh*t.

Sure https://gofile.io/?c=NPQliB

To earn hw trancoding, you need a processor begining from the 4th generation (haswell) with onboard GPU and a 1.04b loader with DSM 918. Transcoding will not work on your hardware. You can remove the video card, it only consumes extra electricity and warms the air.

And another one: https://blocksandfiles.com/2020/03/24/hpe-enterprise-ssd-40k-hours-flaw/

CPU is "Prestonia" which is Netburst architecture. Unlikely to work as the Linux kernel compile requires Nehalem or later. That chip is more than 15 years old!

Hello, I have an old dual xeon server (see picture below). Since i do not have any other function for it besides making a nas from it i would like to know if i would be able to install DSM on it? I have other Synology Nasses and i love how they work. Should i try or can’t it work on this hardware? Thanks!

Это попробуйте...

Yup, all in IT mode. Sorry, I wrote that wrong; not sure what I was thinking then! Its 16 ports and the others have 8 ports each. In addition the board has 10 SATA ports of which I used 4.

Saludos, Downgrade from 6.2 espero te sirva

6.2 has received a few patches for security fixes when 6.1 has not. However, Synology lags so badly with critical updates versus a normal Linux distro, I personally won't rely on 6.2.2's security state. My recommendation is that you should assume it's hackable and never expose your NAS to the Internet. VPN or 2-factor encrypted proxy service are really the only options to safely access it remotely. If you subscribe to that opinion, the difference between 6.1 and 6.2's security state is really irrelevant.

Pour pouvoir modifier le fichier config de la clé usb on peut aussi le faire avec tel net il suffit simplement de ce connecter avec telnet et de monter la partition on ce trouve le fichier Après on redémarrer dsm est le tour est joué Envoyé de mon BLA-L29 en utilisant Tapatalk

Long time lurker. Finally took the plunge and bought a HP microserver gen10 with 8GB ram for less than an empty two bay Synology 218j 219j 220j. Thanks to the guide from luchuma (Tutorial: Install DSM 6.2 on ESXi 6.7) i've managed to get DSM 6.2.2-24922 working with Jun's Loader 1.04b in ESXi with the DS918+ image without too much trouble. Still some things to work out.

И вам дня доброго. Посмотрите тут. Здесь небольшой мануальчик по G7, но он почти не отличим от GEN8. C1E Support - Disabled

Try enabling the setting just above "PME Wake up from S5" and/or "USB Device Wakeup from S3/S4" Either setting should work, or both...

Can you @flyride tell us exactly what files to copy? That information is in the thread you quoted. My first response explained three different options to you. If you pick the third option (1.03b loader, DS3615xs and DSM 6.2.2 without Intel NIC) you will probably need the drivers in extra.lzma. @zzgus just posted the link, you can follow that thread.

I don't know if you can assume anything, and you need to know how your server works before you do anything else. ICH10R (Intel chipset) connected ports may have a simple BIOS-accessible RAID 0/1 option which you should turn "off." However, some server motherboards can have an embedded third-party RAID controller such as an LSI/MegaRAID which would not work well unless flashed to "IT" mode as previously described. Embedded controllers may not be flashable so ports connected to those controllers would not be good candidates for XPEnology.

There is no such a thing as hw acceleration with gemini lakes and 6.2.2. So you obviously can't turn it off. You should use syno 0.8 custom extra.lzma (created by IG-88). Keep searching

Вопрос не в дсм, а в загрузчике. Он должен поддерживать железо, а не дсм.

You gotta modify synoboot.img to run dsm 6.2.2. successfully. Just remember that hw acceleration doesn't work on 6.2.2. with gemini lakes.

С процессорами амд надо в англо ветку идти и смотреть какие драйвера и в каком загрузчике будут поддерживать. Что то мне кажется что дсм 5-й серии будет максимум даже в случае успеха запуска, что так же не факт. Возможно нужна подмена extra.lzma и т.д...

Bonjour à toutes et tous, je suis tout nouveau dans le monde de XPenology, j'ai installé ce système sur deux machines, HP EX490 (DSM 6.2) et un HP N54L (DSM 6.1), vraiment étoné par la vélocité et l'efficacité de ce système. Merci à tous pour les informations qui nous sont très utiles quand nous débutons. Hello everyone, I'm new in the world of XPenology, I installed this system on two machines, HP EX490 (DSM 6.2) and an HP N54L (DSM 6.1), really amazed by the speed and efficiency of this system. Thank you all for the informations which are very useful to us when we start.

thanks heaps I actually found that patch and got it working - same for my 10Gb card. I just forgot to update the post!!

I'm not using IPv6 but i curious why slow working on realtec nic and why IPv6 is enabled on deffault settings DSM.

Hello one and all. My name is Tom (( Paul Thomas Berry)) and I live in Southern Illinois, USA. Please don't hold that against me.....I've been around more blocks than I care to remember. One could say that I am a legacy and not only in my own mind which is how we logicians like to think of ourselves. I'm a legacy because of my age: soon to be 73. What I know about the post 2K world of technology is certainly NOT impressive. However , what I do know I have assimilated by my desire to make these Personal Computers serve me with as much effectiveness as their distributive nature does for networking across the globe. Please forgive me in advance if I ask very basic questions. My need to understand begins at the root in order that I may forge my ideas and my actions regarding what it is that with these fantastifc machines. I can state accurately that that the first computer I worked on could only be communicated with thru a card-reader. If anyone thinks that was challenging , it most certainly was. I went through so many cards at the key machine that I was a fire hazard because of the pile of cards on the floor. Which is why II I got out of the business for 20 years and went back in when the 'machines' had evolved to at least interact with them thru a real-time portal or video portal. SO these PCs and new technology fascinate me and aggravate the crap out of me at the same time. I have 40 or so TBs of HDD and Memory storage in my home. They are powerful and they are sophisticated but much of their evolution has been market driven as I see it. Markets that operate with freedom are prone to unforeseen problems and knee jerk reactions which in turn leads to a road map that sometimes looks more like spaghetti than an outline to a destination. I hope to contribute as well as ask but that may take a while. If I live long enough I might be able to answer questions from others on this forum. For now, soon, I will ask some bery basic questions and do so tainted by a paradigm of system architecture that is pretty much obsolete and yet which set the stage upon all this notion of Artificial Intelligence we now seem to take for granted. As a side note in the interest of semantics, I will state that the term "artificial intelligence" is an oxymoron. It is true that machines can think, but that is merely the definition of a concept. I now a lot of humans that cannot think. Intelligence, whatever it is has something to do with the esoteric, the mystical, and if we eliminate that from our reality then we will become little more than parasites scrubbing through the skin or veneer of civilized evolution. If I annoy anyone with my questions, please be gentle reminding me. As you can see I have a very big ego..... "survival in the 21st century demands a continual reinvention of one's self..." So here I am. Thank YOU for digesting my non-sense thoughts. ONE last thought. I am an non-discriminatory 'dick'. I don't care where your came from, what colors your eyes OR your skin, how you grew up or what culture shaped you. My respect for others hinges on whether or not they try to BS me as so many in our business turn into a profession. Ask me a question in order to understand my question and you will earn my respect. Saying "I don't understand" is NOT a question. One learns by forging questions that have merit to the subject at hand. At least in my world. Thx for our patience. Can you teach a dinosaur some neat tricks? If it is willing to ask questions, why NOT?

Hello everyone, I have inherited a second hand Datto device (4-bay dersktop unit) and plan to re-purpose it as a home NAS. I looked around the web and found out how to get in to the BIOS (password needed - discovered it to be "R@str", which workd). Phase one complete. Having booted the Datto device from USB in to Windows 10 setup, I wiped all the internal disks ready for new deployment. (it has 1 x 120GB Kingston SSD and 2 x 2TB 5.25" SATA in the drive bays, 8GB RAM and a 2-core Xeon 2.4GHz CPU, so not althogther awfull!) I tried out OpenMediaVault but would prefer the Synology DSM as it has many advantages over OMV, not the least of which is the Apps available. So, next pahse is to get this device booted up and instal XPEnology and then DSM.

Bonsoir a tous, Mon DSM commence a etre vieux , presque 2 ans J'ai un hp micro gen8 d'origine (pas de carte reseau additionnelle) A quelle version je peux maj mon serveur ? J'ai aussi un N54L d'origine qui a la meme version EDIT: j'ai trouvé ça mais je suis un peu depassé

Here are three topics from the very prominently featured FAQs that may be considered as such a warning: https://xpenology.com/forum/topic/9392-general-faq/?tab=comments#comment-95507 https://xpenology.com/forum/topic/9392-general-faq/?tab=comments#comment-113011 https://xpenology.com/forum/topic/9394-installation-faq/?tab=comments#comment-81100

Удалось завести транскодинг на j1800, но главное сеть на realtek 8111F выше чем на DSM 6.2 23739. Мучился часов 5 в разных манипуляция. С последними zlma v0.6, сеть не заводилась и c теми что в загрузчике 1.04 918+. Спустя часа четыре безуспешных установок и восстановлений. Пришла мысль стянуть lzma с рабочей машины на j1900 DSM 6.2.2-24922. (я уже не помню какие именно использовал lzma) но помню точно, что летом c установкой версии DSM 6.2.2 тоже боролся на j1900. Может кому пригодится: 1. накатываем DSM 6.2-23739. 2. меняем lzma (в архиве прикрепил) 3. перезагружаемся 4. обновляем вручную на 6.2.2-24922 5. сеть должна подняться. P.S. методом тыка все таки нашел как отключить video в bios. Я всегда думал что за это отвечает пункт integrated video enable/disable. Но оказалось надо отключить в пункте CSM где выбирается uefi или legacy? и на пункте video выбрать NO Launch. HDD sleep работает на DSM 6.2.2-24922 "из коробки" рабочий zlma j1900-j1800.zip

Вот сравнение 918 и 1019. (в случае xpenology, нет разницы) https://nascompares.com/2019/02/15/synology-ds1019-vs-ds918-nas-which-should-you-buy/ Коротко:

Try this file! POWERBUTTON_6.2-0002.SPK

Итак, случилось. HW транс заработал на моей хрени . Скачал новый биос 3.5, залил, настроил северный мост как на картинке, ребут, ничего больше не делал и вуаля - заветная папка /dev/dri c содержимым на месте, железный транс работает, как при перекодировке 4К, так и блюриков (запуск файлов *.m2ts), в plex тоже нормально.

@jun A fresh baremetal install on a HP Microserver Gen7 N54L seems to be working ok. Many thanks for your hard work

1 - Turn off machine and remove usb with v1.02a loader. Keep that usb aside in case you need it later. 2 - Burn new loader v1.02b on usb. Make sure to edit the grub.cfg file like you did for v1.02a (vid/pid, SN, MAC etc). When done, plug the usb key on the machine 3 - Turn on the machine 4 - Use find.synology.com or Synology Assistant to find the machine on the network 5 - Migrate the machine by following the steps indicated on screen. You will be asked to provide the PAT file for 6.1.x so download it first. Download links can he found here: 6 - Let it update. After a while you should be under DSM 6.1.x. You can then apply through the GUI critical updates up to the one that is working. See the critical update section to know which is the latest working one.