Leaderboard

  1. IG-88

    IG-88

    Members


    • Points

      439

    • Content Count

      2,212


  2. Olegin

    Olegin

    Members


    • Points

      387

    • Content Count

      2,406


  3. Polanskiman

    Polanskiman

    Administrators


    • Points

      363

    • Content Count

      2,565


  4. flyride

    flyride

    Members


    • Points

      297

    • Content Count

      892



Popular Content

Showing content with the highest reputation since 06/13/2017 in all areas

  1. 86 points
    Hi, everyone, Thanks for you patience. A new ds918 loader support 6.2/6.21 is uploaded. whats new: uefi issue fixed. i915 driver updated. link https://mega.nz/#F!Fgk01YoT!7fN9Uxe4lpzZWPLXPMONMA (for DS918+) - v1.04b ---Beginning of addition by polanskiman--- link https://mega.nz/#!OV4gVKyZ!dCgfXx1bgAOyvbFwFiov3s7RSNoFuqnAcNmSllLoUiw (for DS3615xs) - v1.03b link https://mega.nz/#!zcogjaDT!qIEazI49daggE2odvSwazn3VqBc_wv0zAvab6m6kHbA (for DS3617xs) - v1.03b Please read this topic to know what loader to chose: ---End of addition by polanskiman---
  2. 56 points
    As DSM 6.2 finally released, I spent a few days to identify new kernel side validation mechanism, and got some ideas to work around it, the early-stage experiment seems work, so, the exciting part(for me) is done. A new loader will be released when it is ready.
  3. 39 points
    DSM 6.2.3 will not work with these drivers, if you install or update you will fall back to "native" drivers that come with DSM, like no realtek nic on 3615/17 but on 918+ or no mpt2/mpt3sas on 918+ or no broadcom onboard nic on HP microserver or Dell server read this if you want to know about "native" drivers https://xpenology.com/forum/topic/13922-guide-to-native-drivers-dsm-617-and-621-on-ds3615/ synology reverted the changes made in 6.2.2 so the old drivers made for 6.2.(0) are working again and there are new drivers made for 6.2.3 too (we got recent kernel source from synology lately) https://xpenology.com/forum/topic/28321-driver-extension-jun-104b-for-dsm623-for-918/ 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, J1800 and N3150 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 one 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
  4. 37 points
    Hi! I made a little tool which can help you to get your XPEnology up & running without installing any software. It contains (as portable versions): - Nirsoft's USB device view (helps to identify the VID & PID of your USB boot media) - V2.76 - XPEnology Serial Generator for DS3615XS, DS3617XS and DS916+ (a converted version of the HTML site) - Win32 DiskImager (to write your modified synoboot.img to your USB boot media) - V1.0 (only available in V1.4.1) - OSFMount x64 (to mount the synoboot.img and modifiy it) - V1.5 - Notepad++ (best editor for changing values inside grub.cfg) - V7.5.3 - Synology Assistant (useful tool from Synology to find your XPEnology and install DSM) - V6.2-23733 - TFTP/DHCP portable (a small TFTP, DHCP and Syslog server by Ph. Jounin) - V4.6.2 - MiniTool Partition Wizard 10 (helps assigning already formatted/written USB devices to modify existing grub.cfg) - V10.3 - SoftPerfect Network Scanner - V6.2.1 - USB Image Tool - V1.75 - New: Rufus - V3.3 In the section "Downloads" all links open corresponding websites to download the files. For beginners I added a small HowTo for bare-metal installation. Update New link for download: https://mega.nz/#F!BtViHIJA!uNXJtEtXIWR0LNYUEpBuiA The download link/folder also contains @IG-88's extra.lzma (V0.6) for the DS918+. You'll have to run it "As Administrator" because some of these tools (like Win32 DiskImager) need to be executed with higher rights. It's possible that the SmartScreen filter will give you a warning, because the EXE isn't signed. Bug reports and comments are welcome Cheers Current version: V1.4.2 (2018-11-19)
  5. 35 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 17-Apr-2020 Loader DSM Platform DSM Versions Kernel Boot Method /dev/dri supported NVMe cache supported RAIDF1 supported Minimum CPU Architecture Max CPU Threads Notes 1.04b DS918+ 6.2 to 6.2.3 4.4.x EFI or Legacy BIOS Yes Yes No Haswell * 8 6.2.0 and 6.2.3 ok 6.2.2 (specifically) on ASRock Q/J-series requires real3x mod or extra.lzma 1.03b DS3617xs 6.2 to 6.2.3 3.10.x Legacy BIOS only No No Yes any x86-64 16 6.2.0 and 6.2.3 ok 6.2.1, 6.2.2 require e1000e or extra.lzma 1.03b DS3615xs 6.2 to 6.2.3 3.10.x Legacy BIOS only No No Yes any x86-64 8 6.2.0 and 6.2.3 ok 6.2.1, 6.2.2 require e1000e or extra.lzma 1.02b DS916+ 6.0.3 to 6.1.7 3.10.x EFI or Legacy BIOS or MBR (Genesys) Yes No No any x86-64 8 1.02b DS3617xs 6.0.3 to 6.1.6 3.10.x EFI or Legacy BIOS or MBR (Genesys) No No Yes any x86-64 16 6.1.7 fails with kernel panic on ESXi 1.02b DS3615xs 6.0.3 to 6.1.7 3.10.x EFI or Legacy BIOS or MBR (Genesys) No No Yes any x86-64 8 best compatibility on 6.1.x 1.01 DS916+ or DS3615xs or DS3617xs 6.0 to 6.0.2 3.10.x EFI or Legacy BIOS or MBR (Genesys) No No any x86-64 obsolete * AMD Piledriver is suspected to be the minimum chip architecture to support the DS918+ DSM platform, but this is unverified.
  6. 29 points
    Hello! I am xpenology user. And I am an IT engineer who creates shell scripts as hobbies. Please understand that it is written by a google translate site. because i’m korean who is not fluent in English. I created a tool to change cpu information for Xpenology’s users. Modify the actual cpu name and cores of your pc or server. Howto Run ============================================================= 1. Download attached file on your PC (ch_cpuinfo.tar) (ch_cpuinfo_en.tar) / (ch_cpuinfo_kr.tar is file for korean) 2. Upload file to your DSM location (by filestation, sftp, webdav etc....) 3. Connect to ssh by admin account. (dsm > control panel > terminal & snmp > terminal > enable ssh check) 4. Switch user to root: sudo su - (input admin password) 5. Change directory to where ch_cpuinfo.tar file is located: cd /volume1/temp 6. Decompress file & check file: tar xvf ch_cpuinfo.tar ls -lrt (check root’s run auth) 7. Run to Binary file ./ch_cpuinfo or ./ch_cpuinfo.sh (If you use busybox in DSM 5.x, you can use it as a source file) 8. When you execute it, proceed according to the description that is output. 9. Check your DSM’s CPU name, CPU cores at “information center” Extra Action If you want to use ch_cpuinfo in your language Modify and use the LANG.txt file in the same path as ch_cpuinfo. It is possible to use after changing the English content of each variable after translation and changing the value of CUSTLANG in line 8 to Y. ==================================================== Addtional, Adjust binary to excute file made by shc(http://www.datsi.fi.upm.es/~frosal) The tool does not inclue worms, bad code. If you want to edit the CPU information yourself manually, please refer to the contents below. ——————————————————————————————————————————————————————————————— Location : /usr/syno/synoman/webman/modules/AdminCenter Source : admin_center.js / admin_center.js.gz(above 6.2) Add Before -> if(Ext.isDefined(h.cpu_vendor)&&Ext.isDefined(h.cpu_family)&&Ext.isDefined(h.cpu_series)){ o.push([_T("status","cpu_model_name"),String.format("{0} {1} {2}",h.cpu_vendor,h.cpu_family,h.cpu_series)])} if(Ext.isDefined(h.cpu_cores)){o.push([_T("status","cpu_cores"),h.cpu_cores])} Add contents: h.cpu_vendor="Intel";h.cpu_family="Xeon";h.cpu_series="E3-1220 V3";h.cpu_cores="4 Cores (1 CPU/4 Cores | 4 Threads)"; h.cpu_detail="<a href='https://ark.intel.com/content/www/us/en/ark/search.html?_charset_=UTF-8&q=E3-1220 V3' target=_blank>detail</a>" Change contens: String.format("{0} {1} {2}",h.cpu_vendor,h.cpu_family,h.cpu_series) to String.format("{0} {1} {2} {3}",h.cpu_vendor,h.cpu_family,h.cpu_series,h.cpu_detail) ——————————————————————————————————————————————————————————————— Finally, All descriptions are based on version 6.2, and the actual executable file supports both 5.x and 6.x. Publish the source through github(https://github.com/FOXBI/ch_cpuinfo). For versions DSM 6.x and later, you can use the binary as before. If you use busybox in DSM 5.x, you can use it as a source file(ch_cpuinfo.sh). Please contact me by comment or bug report, i’ll respond to you as much as possible within my ability. Test & Made Environment ———————————————————————————————————— Base Server : HP ML310e v2 gen8 + VMware ESXi 6.0 + RDM DSM : 6.2.2-24922 Update 2 (DS3615xs/DS3617xs/918+) 6.1-15284 Update 2 (DS3615xs) Base Server : Intel E5-2630 v2 + VMware ESXi 6.7u2 DSM : 6.2.2-24922 Update 2 (DS3617xs) ———————————————————————————————————— Change Log 1. Support DSM 6.2.3-25423 2. Change of CPU information collection method, Collect using only /proc/cpuinfo. Do not use dmidecode(for systems without dmidecode commands ...) 3. Support MultiLanguage(User can modify LANG.txt and apply it) Maintaining Korean / English support by default 4. undefined error fixed(2020-04-29) I didn't know if the keyword to search for was changed in 6.2.3-25423, but it was checked and fixed while debugging through error reporting. Thanks!! Sample image(by Google trans) Thank you!! Have a nice day!! Cheer up!! We can do it!! Reduce activity & Stay home!! Let's overcome COVID-19 !! ============================================= Download links: ch_cpuinfo ver 2.1.1-r01 - new version update ch_cpuinfo ver 2.2.1-r01 - new version update(undefined error fixed) -> ch_cpuinfo.tar Reference images # 1.04b + DS918+ # 1.03b + DS3615xs # 1.03b + DS3617xs # Normal output is possible even when using more than 8core.
  7. 27 points
    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 ##################
  8. 25 points
    Перед тем как что-то менять в своей работающей системе, настоятельно рекомендуется сделать резервные копии своих особо ценных данных, чтобы потом не жалеть об их безвозвратной потере. Все, что вы творите - это ваш страх и риск, никто не побуждает вас это делать. Самый простой и надежный способ безопасно попробовать - выключить хрень, отключить все диски и загрузочную флешку от действующей системы, взять чистый диск и другую флешку и попробовать установить новую версию загрузчика и системы, если прокатило, то делать уже на действующей системе. 1. Как установить (подготовительные работы описаны для компа с Windows): а) скачать образ загрузчика 1.04b (исходная тема тут), создать каталог в корне диска без символов на кириллице, например, c:/918/ и поместить туда образ загрузчика б) определить VID/PID флешки или картридера в который она вставлена (Панель управления - Диспетчер устройств - Контроллеры USB - Ваша флешка/ридер - Свойства - Сведения - ИД оборудования, нужно для того, чтобы система DSM опознала этот диск и не пыталась устанавливать себя на него, если неправильно определите и пропишите эти параметры, то система будет вылетать по ошибке 13 при установке в) скачать, установить и запустить программу OSFmount, смонтировать Partition 0 (15 Mb) из файла загрузчика, перед монтированием убрать галку Read-only drive г) скачать, установить и запустить программу Akelpad, открыть файл grub/grub.cfg на ранее смонтированном диске, правим, сохраняем: set vid=0xA234 #VID флешки/ридера set pid=0xB678 #PID флешки/ридера set sn=1780PDN123456 #sn set mac1=001132123456 #mac первой сетевой карты set mac1=001132123457 #mac второй сетевой карты, второй и последующий отличаются от первого на +1 в последнем разряде в шестнадцатеричной системе ... set netif_num=2 #количество сетевых карт ... set sata_args='SataPortMap=6' #контроллер sata, значения: 6 - 1 контроллер на 6 портов; 22 - 2 контроллера по 2 порта; 42 - 2 контроллера, первый на 4 порта, второй на 2 и т.п. Где брать sn и mac - ваша головная боль, гугл в помощь, система установится и будет работать с теми, которые изначально прописаны в загрузчике, но с ограничением функционирования некоторых сервисов и модулей, таких как: QC, пуш уведомления, активация кодеков для транскодинга, установка лицензий syno... Но для большинства и без них будет достаточно. На форуме писали, что прокатывало с sn и mac от других реальных моделей syno, но так не пробовал, поэтому утверждать не буду, кто хочет - дерзайте. д) размонтировать диск в OSFmount е) скачать, установить и запустить программу Rufus и записать ранее подготовленный образ на флешку з) вставить флешку в машину, на которой планируете запустить хрень, подключить диски, включить питание ж) отключить брандмауэр в антивирусе, в браузере набрать http://find.synology.com или установить Synology Assistant с сайта syno и найти вновь установленную хрень в вашей сети и) установить DSM установить хрень следуя инструкциям программы установки и приступить к настройке (как это делать здесь не описываю, ибо все ответы есть в базе знаний syno) Для ленивых есть утилита, где собраны основные проги для Windows x64 2. Если хрень не обнаружилась в сети, то скорее всего в загрузчике нет драйверов для ваших сетевых карт и/или для sata контроллеров. a) запустить программу OSFmount, смонтировать Partition 1 (30 Mb) из файла загрузчика, перед монтированием убрать галку Read-only drive б) скачать extra.lzma из этой темы и перезаписать в смонтированном диске в) размонтировать диск и перезаписать образ с добавленными драйверами на флешку г) попробовать запустить и найти хрень в сети, если не получилось, то увы и ах, либо просить, чтобы добавили дрова для ваших устройств в этой теме или самому их добавлять - теория тут 3. Транскодинг (нужны sn и mac от реальной железки) С наибольшей степени вероятности запустиnся на процессорах Intel начиная с 4го поколения (Haswell), но есть нюансы с моделями материнских плат и биосами. Проверяем следующим образом: hardware (hw) транскодинг - в корне системы должен быть каталог /dev/dri с тремя подкаталогами внутри, если его нет, но нет и hw транскодинга, чтобы проверить - ищем каталог в терминале/ssh командой cd /dev/dri. software (sw) транскодинг - должны подняться соответствующие кодеки, проверить можно командой в терминале/ssh cat /usr/syno/etc/codec/activation.conf Если результат такой, то он есть: {"success":true,"activated_codec":["hevc_dec","h264_dec","h264_enc","mpeg4part2_dec","ac3_dec","vc1_dec","vc1_enc","aac_dec","aac_enc","mpeg4part2_enc"],"token":"абракадабра"} Если ничего похожего нет, то нет и транскодинга. P.S. Просьба к админам прибить тему в шапке и дать мне доступ на редактирование первого поста этой темы, буду добавлять по мере поступления вопросов, ибо задолбали оленеводы, которые задают вопросы по установке, во всех подряд темах.
  9. 24 points
    SS 8.1.2-5469.х86_х64 протестирован и работоспособен. Желающие могут постучать(только не громко) в личку. На заметку - Качаем архив и распаковываем. - Устанавливаем SS 8.1.2-5469!!!(взять можно Тут, но не запускаем(если запустили, останавливаем). - Заходим на свой NAS через web. - Заходим в Панель управления > терминал и SNMP. Ставим галку "включить службу ssh" и нажимаем применить. - Подключаемся к сино с помощью putty или другого ssh клиента под Админом - Вводим свой Админский пароль - Вводим команду: sudo su - - Вводим свой Админский пароль - Видим чудо в виде - root@... - Вводим команду: synouser --setpw root Ваш_Пароль_Для_Root - Далее можно заходить под root используя установленный пароль. - Скидываем файлики из архива на сино и при необходимости меняем владельца и права. Сделать это можно разными способами. p.s.При использовании WinSCP советую в настройках передачи установить тип файлов "двоичный/binary" для исключения возможных проблем. - Запускаем SS из центра пакетов.(если всё сделано правильно, имеем 25 камер) - Класть(или если хотите - ложить) сюда>>> /var/packages/SurveillanceStation/~target/lib/libssshm.so *chmod=644* *owner=SS* *group=SS* /var/packages/SurveillanceStation/~target/lib/libssutils.so *chmod=644* *owner=SS* *group=SS* /var/packages/SurveillanceStation/~target/sbin/ssmessaged *chmod=755* *owner=SS* *group=SS* /var/packages/SurveillanceStation/~target/webapi/Layout/src/SYNO.SurveillanceStation.Layout.so *chmod=644* *owner=SS* *group=SS* Hide
  10. 21 points
    Loader Download: here / (link updated due to directory structure change of mega share) -- by jun 2-28 I've uploaded a 6.1 alpha build to mega, for brave guys only . (Note: AMD needs extra work.) scripts I use to generate bootable image https://github.com/kref/scripts ---Beginning of addition by polanskiman--- Tutorials by polanskiman: Install/Upgrade DSM 5.2 to DSM 6.0.2 here Install/Upgrade DSM 5.2 to DSM 6.1 here Loader download mirrors: Managed by Polanskiman. includes .iso format images made by myself. here Managed by Trantor. This mirror is currently offline. here For info: v1.01 (DS3615xs) is for DSM 6.0.2 - AMD compatible - Latest version for DSM 6.0.2 v1.02b (DS3615xs, DS3617xs and DS916+) is for DSM 6.1 - AMD loosely compatible and with Bios tweaks - Latest version for DSM 6.1 DO NOT install DSM updates on your working machine BEFORE looking into the forum or testing the update on a test rig/vm. DO NOT update to DSM 6.2 with loader v.1.02b. It will not work. I repeat. DO NOT update to DSM 6.2 Further explanation by jun on AMD compatibly for loader v1.02a, v1.02a2 and v1.02b: ---End of addition by polanskiman---
  11. 19 points
    Hi all:) After a little bit of reverse engineering I was able to bypass the license checking mechanism introduced in DSM 6 successfully with a simple two line binary patch of synocodectool and therefore enable transcoding without a valid serial number[emoji4]. I wrote a little script to make it easier for everyone. For more information please check the github repo: https://github.com/likeadoc/synocodectool-patch HOWTO: 1. wget https://raw.githubusercontent.com/likeadoc/synocodectool-patch/master/patch.sh 2. chmod +x patch.sh 3. ./patch.sh Done:) If things go wrong simply restore the original file: ./patch.sh -r Cheers
  12. 18 points
    edit 14.05.2020: 6.2.3 is back online as v25426, for newer coffeelake cpu's with problems using hardware transcoding (dev/dri present after boot) there is a new videostation that fixes the problem https://xpenology.com/forum/topic/28321-driver-extension-jun-104b-for-dsm623-for-918/?do=findComment&comment=144918 edit2 02.06.2020: as @richv31 pointed out here https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/?do=findComment&comment=148564 there seems to be a serious problem with 918+ and scsi/scs drivers, at least with mpt2sas/mpt3sas, not just with 6.2.2/6.2.3 it also happens with jun's original loader 1.04b and dsm 6.2.0 (23824), breaking raid sets after not properly waking up from hdd hibernation means potential data loss i had a two disk raid1 set on a lsi 9211-8i and after disks spinning down only one came up and i saw some really worrying messages on the serial console, i was not able to log in to the system, not on the web gui, even not on the serial console, the whole system was in lock down and only switching off seemed to work as of the problems with not getting s.m.a.r.t. values i used juns old original raid_class.ko, scsi_transport_sas.ko, scsi_transport_spi.ko to get the old state back (replacing my newly made ones from more recent synology kernel source 24922 ) in 0.11/0.12 - these version inherit the problem that seems to be present since the beginning with loader 1.04b anyone using mpt2sas/mpt3sas and disk hibernation on 918+ should disable it for now to not risk any data loss the new 0.13 for 918+ will have the raid_class.ko, scsi_transport_sas.ko, scsi_transport_spi.ko from kernel source 24922, that version did work on testing on my system without breaking anything and without such alarming errors on wakeup of disks, there will be no smart data but at least it seems safer then disks not waking up properly for "proper" lsi sas controller support i'd suggest using 3615 or 3617 as it is "native" in these units and should work better, maybe there are kernel options missing in the 918+ kernel and that cant be fixed, if anyone finds out more just add a comment (i might not have the time to dig into this) the other alternative is to use sata/ahci instead of scsi/sas with 918+, that works without problems on my system using 918+ (12 disks), JMB585 based controller seem to be the best choice atm as they support pcie 3.0 and can have up to 2000 MByte/s for its 5 sata ports (the older marvell and asm chips use only pcie 2.0 limiting the data rate to 500 MB/s or 1000 MB/s, even 8 port controller with two of the older chips use a pcie bridge chip with just two lanes making them terrible choice for a high port count - might be ok with just one or two 1GBit nic's but will at least limit the rebuild speed and ssd's should be kept away from these controllers and place in internal sata ports) for Instructions about installing or updating please read "Driver extension jun 1.03b/1.04b for DSM6.2.2 for 3615xs / 3617xs / 918+" if i have time i will write more in this place the new package is not well tested i just did some tests with hardware i have at hand (ahci, e1000e, r8168, igb, bnx2x, mpt2sas/mpt3sas) and tested update from 6.2.2 to 6.2.3 basically synology reverted the kernel config change made in 6.2.2 back to what was before so old drivers from original 1.04b loader (and older driver i made before 6.2.2) should work again - but as synology also introduced there own new i915 driver with 6.2.3 there will be a conflict when jun's i915 driver is loaded with 6.2.3 there are two positive new things, synology released a nearly recent kernel source code (24922) and 6.2.3 has a new i915 driver supporting as much gpu hardware as jun's backported i915 driver in loader 1.04b - so there is no need for jun's i915 driver anymore and in theory we should have good support for apollo lake, gemini lake and other newer hardware but it seems not all new UHD630 is supported as there is dev id "3E98" unsupported (i5-9400, i5-9600k, i7-9700t, i7-9700), ark.intel.com and wikichip.og are usually good sources to check the id https://ark.intel.com/content/www/us/en/ark/products/134898/intel-core-i5-9400-processor-9m-cache-up-to-4-10-ghz.html https://en.wikichip.org/wiki/intel/core_i5/i5-9400 there is also a good document from intel listing all coffeelake's https://01.org/sites/default/files/documentation/intel-gfx-prm-osrc-cfl-vol01-configurations.pdf coffeelake cup's without driver support (no hardware transcoding), SKU numbers should be listed when buying and can be checked on the box i9 SKU S82 i7 SKU S82 i5 SKU S6f2 a new 10th gen i5-10500 / i3-10300 have device id's "9BC8" and there are no "9xxx" numbers in the driver we use so don't expect any newer gen10 cpu to work with hardware transcoding even when it "only" has UHD630 igpu i completely removed jun's i915 drivers from the extra/extra2 and changed/added the i915 firmware needed, also i took care of the "old" i915 drivers on the installed system in /usr/lib/modules/update/, they are now deleted on boot so if you come from 6.2.2 and used extra/extra2 std or recovery or you did already used juns original 1.04b extra/extra2, it should work as soon as you boot up (when drivers in "update" are not present then the default drivers from synology will be used and with the added i915 in place it will work on most intel gpu's up to coffee lake) the driver versions are the same as in the 6.2.2 extra/extra2 but are newly compiled, as every driver from 6.2.2 is renewed all the old drivers are overwritten and there should be no crashing drivers on boot (which can prevent proper shutdown or reboot) we now have one universal i915 driver (and not jun's and synologys) its back to one package for all cpu/gpu, if needed there will be a recovery version too i only did test a new created loader from 1.04b image file with zImage and rd.gz from "DSM_DS918+_25426.pat" and the new extra.extra2, it might work with the 6.2.0 kernel that is by default in the 1.04b image (i will test this) if you accidentally updated 6.2.2 to 6.2.3 and now have problems like no network after boot, no proper shutdown/reboot or missing /dev/dri (hardware transcoding) then you just copy the new extra/extra2 to your already updated usb drive (the update to 6.2.3 already installed the new kernel on it) with latest updates of win10 there is no drive letter anymore, its possible to still do it with the tools already used for creating the usb drive, read the usb to a imgae file with "Win32DiskImager 1.0" (activate "read only allocated partitions"), mount that image with osfmount (like in the tutorial section), overwrite old /extra/extra2.lzma and write the image back to usb with Win32DiskImager extra.lzma/extra2.lzma for loader 1.04b ds918+ DSM 6.2.3 v0.13.1 scsi/sas disks will have no s.m.a.r.t. infos (see edit2 above), newer atlantic.ko driver 2.3.4, r8125 added to rc.modules http://s000.tinyupload.com/?file_id=48537171527352619423 extra.lzma for loader 1.03b ds3615 DSM 6.2.3 v0.11_test, same added drivers as for 6.2.2 like newer intel drivers, 10G nics, ... http://s000.tinyupload.com/?file_id=04147311964729253115 extra.lzma for loader 1.03b ds3617 DSM 6.2.3 v0.11.2_test, same added drivers as for 6.2.2 like newer intel drivers, 10G nics, ... (0.11.2 because i forgot bnx2/bnx2x firmware and mpt2/mp3 driver problem when updating from 6.2.2 in 0.11) http://s000.tinyupload.com/?file_id=00282289527307524672
  13. 17 points
    List of mirror links to DSM 5.x and DSM 6.x boot loaders. Please drop a comment if you see a broken link or some erroneous information. All other posts will be deleted. Before downloading a loader I suggest you read this topic to know which loader to download. DSM 6.2(.1/.2/.3/.4) - Read Jun's topic Jun's Loader v1.03b DS3615xs Synoboot_3615.zip | 17.3 MB | MD5 = e145097bbff03c767cc59b00e60c4ded Jun's Loader v1.03b DS3617xs Synoboot_3617.zip | 19.5 MB | MD5 = 94d18efbc349da2bd45d6e57adabc54f Jun's Loader v1.04b DS918+ synoboot-ds918.zip | 20.9 MB | MD5 = 5a5303a154d907b4adf99dfd201769e4 DSM 6.1(.2/.3/.4/.5/.6/.7) - Read Jun's topic and Tutorial Jun's loader v1.02b DS3615xs DS3615xs 6.1 Jun's Mod V1.02b.img | 50.0 MB | MD5 = b4a2bc974070895407cd50990d96669a Jun's loader v1.02b DS3615xs with MBR partition (For older boards. Try if the above refuses to boot) - Rebuilt by @Genesys DS3615xs 6.1 Jun's Mod V1.02b (MBR_Genesys).img | 50.0 MB | MD5 = e30615bd02002479b58650c0862f25c4 Jun's loader v1.02b DS3617xs DS3617xs 6.1 Jun's Mod V1.02b.img | 50.0 MB | MD5 = e5d1608a9f43cf9a084277eb5640b439 Jun's loader v1.02b DS3617xs with MBR partition (For older boards. Try if the above refuses to boot) - Rebuilt by @Genesys DS3617xs 6.1 Jun's Mod V1.02b (MBR_Genesys).img | 50.0 MB | MD5 = 793c040f1093910e71236edc9a55de1f Jun's loader v1.02b DS916+ DS916p 6.1 Jun's Mod V1.02b.img | 50.0 MB | MD5 = 5ea01a50fd40426eb0e5344aa6d7bbff Jun's loader v1.02b DS916+ with MBR partition (For older boards. Try if the above refuses to boot) - Rebuilt by @Genesys DS916p 6.1 Jun's Mod V1.02b.img (MBR_Genesys).img | 50.0 MB | MD5 = 86bd66b2be35135cf13039ed783eb4c0 DSM 6.0.2 - Read Jun's topic and Tutorial Jun's loader v1.01 DS3615xs DS3615xs 6.0.2 Jun's Mod V1.01.zip | 24.0 MB | MD5 = cf9d920edef96d58ae709674dc71511b Jun's loader v1.01 DS3615xs with MBR partition (For older boards. Try if the above refuses to boot) - Rebuilt by @Genesys DS3615xs 6.0.2 Jun's Mod V1.01 (MBR_Genesys).img | 50.0 MB | MD5 = 25813aa17ee5b17db1b41d54bc6b4b74 DSM 5.2 XPEnoboot 5.2-5967.1 DS3615xs XPEnoboot_DS3615xs_5.2-5967.1.img | 24.0 MB | MD5 = 4b204b8200ea5d12dea8b578ad95f7ef XPEnoboot_DS3615xs_5.2-5967.1.iso | 19 MB | MD5 = c1ee885e6b74978512f2adb6fa6fc7ff XPEnoboot_DS3615xs_5.2-5967.1.vmdk | 19 MB | MD5 = 3fe4f459432f883fd2be8b7618a25159 XPEnoboot 5.2-5644.5 DS3615xs XPEnoboot_DS3615xs_5.2-5644.5.img | 24.0 MB | MD5 = a329929e5a91095e9258036485e01c9c XPEnoboot_DS3615xs_5.2-5644.5.iso | 17.4 MB | MD5 = a92ea8c869c48fc340a91e41a01d4cfd XPEnoboot_DS3615xs_5.2-5644.5.vmdk | 17.3 MB | MD5 = 9d5cfdc69e0e19ef207de9aaba76acf3 XPEnoboot 5.2-5644.4 DS3615xs XPEnoboot_DS3615xs_5.2-5644.4.img | 24.0 MB | MD5 = 59e96a63333b5c6d8911f902a23ca99f XPEnoboot_DS3615xs_5.2-5644.4.iso | 17.1 M | MD5 = bfa92964103438abd0f93c4ef58d0e38 XPEnoboot_DS3615xs_5.2-5644.4.vmdk | 17.1 MB | MD5 = 860259eaa222186860bc52bd6dff4919 XPEnoboot 5.2-5644.1 DS3615xs XPEnoboot_DS3615xs_5.2-5644.1.img | 24.0 MB | MD5 = d16c8877744a2d26bf44fc1b49a36484 XPEnoboot_DS3615xs_5.2-5644.1.iso | 22.2 M | MD5 = bdcb7a1a7586e208878807f2504cf2d5 XPEnoboot_DS3615xs_5.2-5644.1.vmdk | 22.1 MB | MD5 = 2d947faf0419668c1278fbee4281acb5 XPEnoboot 5.2-5592.2 DS3615xs XPEnoboot_DS3615xs_5.2-5592.2.img | 24.0 MB | MD5 = fbeba655ca0a77b56b025192b08eb55d XPEnoboot_DS3615xs_5.2-5592.2.iso | 21.1 MB | MD5 = c508e80e8a795514497244f798c663e2 XPEnoboot_DS3615xs_5.2-5592.2.vmdk | 21.1 MB | MD5 = ddeef445edeaba3684fcbb50c50adbe0 XPEnoboot 5.2-5592.1 DS3615xs XPEnoboot_DS3615xs_5.2-5592.1.img | 16.0 MB | MD5 = ebda68e9a7589ed1d145399f975d1232 XPEnoboot_DS3615xs_5.2-5592.1.iso | 16.1 MB | MD5 = 65c6b150ea6d26c70cc0d96d010ce5a6 XPEnoboot_DS3615xs_5.2-5592.1.vmdk | 16.0 MB | MD5 = 78cb2ff5bfcd14c1edb3dea93084443f XPEnoboot 5.2-5565.2 DS3615xs XPEnoboot_DS3615xs_5.2-5565.2.img | 16.0 MB | MD5 = 3016d6ffb5ea794033567ab7eb816184 XPEnoboot_DS3615xs_5.2-5565.2.iso | 15.6 MB | MD5 = a3ade9b08d24be96e2da775e4e06f13d XPEnoboot_DS3615xs_5.2-5565.2_vmdk.zip | 15.2 MB | MD5 = 4c314bbd4116427c5c85ceb08da7479c XPEnoboot 5.2-5565.1 DS3615xs XPEnoboot_DS3615xs_5.2-5565.1.img | 16.0 MB | MD5 = 1806870fe0a7b83ff65b25a9af9dc487 XPEnoboot_DS3615xs_5.2-5565.1.iso | 15.6 MB | MD5 = cfe9937aa76458c9e99efea5d3fee2db XPEnoboot_DS3615xs_5.2-5565.1_vmdk.zip | 15.3 MB | MD5 = 8c317e99b3db3869a480a6debf24b7b4 DSM 5.1 XPEnoboot 5.1-5055.1 DS3615xs XPEnoboot_DS3615xs_5.1-5055.1.img | 15.8 MB | MD5 = b069342f3bc6a10d1e0111e7c5341df7 XPEnoboot_DS3615xs_5.1-5055.1.iso | 14.1 MB | MD5 = c5c049a3e1e06aa6f498fb70c15dc133 XPEnoboot_DS3615xs_5.1-5055.1_vmdk.zip | 13.7 MB | MD5 = a654f3bb05033da98b32e55724f0b1ce XPEnoboot 5.1-5022.3 DS3615xs XPEnoboot_DS3615xs_5.1-5022.3.img | 15.8 MB | MD5 = 72175a41e5855b57b4c8ffc3d92f4b06 XPEnoboot_DS3615xs_5.1-5022.3.iso | 14.8 MB | MD5 = 46854ce39415d736fa5abd446ffa4352 XPEnoboot_DS3615xs_5.1-5022.3.vmdk | 14.8 MB | MD5 = a7343f03fe63a5aa7ad0fe01f41a4b76 XPEnoboot 5.1-5022.2 DS3615xs XPEnoboot_DS3615xs_5.1-5022.2.img | 15.8 MB | MD5 = 06b8435e1322c7a5ee5725ff80ea2a77 XPEnoboot_DS3615xs_5.1-5022.2.iso | 14.0 MB | MD5 = 0e211d3d19b7b461ae5df3aa91e18630 XPEnoboot_DS3615xs_5.1-5022.2.vmdk | 13.9 MB | MD5 = 929730848a31fc19bddd457998477a5f XPEnoboot 5.1-5022.1 DS3615xs XPEnoboot_DS3615xs_5.1-5022.1.img | 15.8 MB | MD5 = 6f7cb585519c5cb3acfb026d34585dbd XPEnoboot_DS3615xs_5.1-5022.1.iso | 13.4 MB | MD5 = 88bd5177fa7a4f54b7fcd5e4001bae5b XPEnoboot_DS3615xs_5.1-5022.1.vmdk | 13.3 MB | MD5 = f03125c86b2da60b5d38db1c6c62bcba DSM 5.0 NanoBoot 5.0.x DS3612xs NanoBoot-5.0.4.1-fat.img | 15.6 MB | MD5 = 2f201876ef576f4ef78a3c3bbbcee529 NanoBoot-5.0.3.2-fat.img | 15.6 MB | MD5 = 89ce54b38e83c7b94c422f6c9a0dbedb NanoBoot-5.0.3.1-fat.img | 15.6 MB | MD5 = 07bd106a7f6204962c801ecf851f1dc9 NanoBoot-5.0.2.4-vfat.img | 32.0 MB | MD5 = e1353d7143cbf8cc31ed320f82cf65d6 NanoBoot-5.0.2.4-fat.img | 15.6 MB | MD5 = 32e1f823219ec7963162e4e394687112 NanoBoot-5.0.2.3-fat.img | 15.6 MB | MD5 = 6fc6be138eb070938a9f14ff64fa4239 NanoBoot-5.0.2.2-fat.img | 15.6 MB | MD5 = 6bbf71f64909cda57c3a63e523d13ed8 NanoBoot-5.0.2.2-ext2.img | 31.3 MB | MD5 = 60233f771b934b5237e2037be0e64b95 NanoBoot-5.0.2.1-fat.img | 15.6 MB | MD5 = 039abc91883e09fd2f443ee10ba5690e NanoBoot x86 5.0.x DS214Play NanoBoot-x86-5.0.3.1-fat.img | 15.6 MB | MD5 = 3c6776570962926497088e6b3889205c NanoBoot-x86-5.0.2.5-fat.img | 15.6 MB | MD5 = b76c423d39129b19b2e0a62f741aaa8c NanoBoot-x86-5.0.2.4-vfat.img | 32.0 MB | MD5 = 8bc6d3b5aed1f41fa0ce4d93b17f9bf1 NanoBoot-x86-5.0.2.4-fat.img | 15.6 MB | MD5 = 90948500efde437ae56dfd51f31f55f8 NanoBoot-x86-5.0.2.3-fat.img | 15.6 MB | MD5 = 7acb8faf796a0e5d5a54a9734ecec728 NanoBoot-x86-5.0.2.2-fat.img | 15.6 MB | MD5 = f333038c8bcf1e530ddeb55075b9827c NanoBoot-x86-5.0.2.1-fat.img |15.6 MB | MD5 = 5bf7241df633ff48ce6a571aa27df88c
  14. 16 points
    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"
  15. 15 points
    I generated an easy to install package to activate a mainboard connected power button for clean shutting down (instead login in web page). Install package for DSM 5.2, DSM 6.0 and DSM 6.1(.1): powerbutton_6.1-0004.spk powerbutton_6.1-0005.spk I have tested DSM 5.2 and DSM 6.1 for the DS3617 versions only in VM. Please report if there are any problems.
  16. 15 points
    Решил немного облегчить жизнь новичкам и тем, кто успел подзабыть, где и что лежит. 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, инструкция в следующем) Просьба ссылки тут не обсуждать, добавляйте свои, если посчитаете полезным.
  17. 14 points
    Господа, товарищи.. Не пишите мне свою почту. Знать мне её не обязательно, а ответ всё равно прилетит в личку на ресурсе.
  18. 13 points
    All links below are provided for noobs and because I am a nice guy, but simply going to https://archive.synology.com/download/DSM/ or https://www.synology.com/en-global/support/download and then clicking the desired subsequent links will yield everything I am linking below. Seek and you shall find. Also keep in mind that I am not updating this post very often so you are better of learning how all this works. --------------------------------------------------------------------------------------------- DSM PAT files can be found here (Major updates): DSM 6.0.2: https://archive.synology.com/download/DSM/release/6.0.2/8451/ Chose .pat file DS3615xs DSM 6.1: https://archive.synology.com/download/DSM/release/6.1/15047/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.1: https://archive.synology.com/download/DSM/release/6.1.1/15101/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.2: https://archive.synology.com/download/DSM/release/6.1.2/15132/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.3: https://archive.synology.com/download/DSM/release/6.1.3/15152/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.4: https://archive.synology.com/download/DSM/release/6.1.4/15217/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM 6.1.5: https://archive.synology.com/download/DSM/release/6.1.5/15254/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM6.1.6: https://archive.synology.com/download/DSM/release/6.1.6/15266/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM6.1.7: https://archive.synology.com/download/DSM/release/6.1.7/15284/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly DSM6.2: https://archive.synology.com/download/DSM/release/6.2/23739/ Chose .pat file for DS3615xs or DS3617xs or DS918+ accordingly DSM6.2.1: https://archive.synology.com/download/DSM/release/6.2.1/23824/ Chose .pat file for DS3615xs or DS3617xs or DS918+ accordingly DSM6.2.2: https://archive.synology.com/download/DSM/release/6.2.2/24922/ Chose .pat file for DS3615xs or DS3617xs or DS918+ accordingly Critical Updates for all DSM versions can be found here: http://download.synology.com/download/DSM/criticalupdate/update_pack/ or http://archive.synology.com/download/DSM/criticalupdate/update_pack/ Critical Updates specifically for DSM 6.0.2 can be found here: Update 1: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-1/ Update 2:http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-2/ Update 3: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-3/ Update 4: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-4/ Update 5: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-5/ Update 6: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-6/ Update 7: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-7/ Update 8: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-8/ Update 9: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-9/ Update 10: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-10/ Update 11: http://download.synology.com/download/DSM/criticalupdate/update_pack/8451-11/ Chose .pat file DS3615xs Critical Updates specifically for DSM 6.1 can be found here: Update 1: http://download.synology.com/download/DSM/criticalupdate/update_pack/15047-1/ Update 2: http://download.synology.com/download/DSM/criticalupdate/update_pack/15047-2/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.1 can be found here: Update 1: http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-1/ Update 2: http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-2/ Update 3: http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-3/ Update 4: http://download.synology.com/download/DSM/criticalupdate/update_pack/15101-4/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.2 can be found here: Update 1: http://download.synology.com/download/DSM/criticalupdate/update_pack/15132-1/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.3 can be found here: Update 1: http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-1/ Update 2: http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-2/ - Does not apply to DS3615xs or DS3617xs or DS916+ Update 3: http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-3/ Update 4: http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-4/ Update 5: http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-5/ Update 6: http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-6/ Update 7: http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-7/ Update 8: http://download.synology.com/download/DSM/criticalupdate/update_pack/15152-8/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.4 can be found here: Update 1: http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-1/ Update 2: http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-2/ Update 3: http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-3/ - Update 3 was removed by Synology without warning Update 3: http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-3/ - Update 3 was re-added by Synology (different md5) Update 4: http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-4/ Update 5: http://download.synology.com/download/DSM/criticalupdate/update_pack/15217-5/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.5 can be found here: Update 1: http://download.synology.com/download/DSM/criticalupdate/update_pack/15254-1/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.6 can be found here: Update 1: http://download.synology.com/download/DSM/criticalupdate/update_pack/15266-1/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.1.7 can be found here: Update 1: http://download.synology.com/download/DSM/criticalupdate/update_pack/15284-1/ Update 2: http://download.synology.com/download/DSM/criticalupdate/update_pack/15284-2/ Update 3: http://download.synology.com/download/DSM/criticalupdate/update_pack/15284-3/ Chose .pat file for DS3615xs or DS3617xs or DS916+ accordingly Critical Updates specifically for DSM 6.2 can be found here: Update 1: http://download.synology.com/download/DSM/criticalupdate/update_pack/23739-1/ Update 2: http://download.synology.com/download/DSM/criticalupdate/update_pack/23739-2/ Chose .pat file for DS3615xs or DS3617xs or DS918+ accordingly Critical Updates specifically for DSM 6.2.1 can be found here: Update 1: http://download.synology.com/download/DSM/criticalupdate/update_pack/23824-1/ Update 2: http://download.synology.com/download/DSM/criticalupdate/update_pack/23824-2/ Update 3: http://download.synology.com/download/DSM/criticalupdate/update_pack/23824-3/ Update 4: http://download.synology.com/download/DSM/criticalupdate/update_pack/23824-4/ Update 5: http://download.synology.com/download/DSM/criticalupdate/update_pack/23824-5/ - Does not apply to DS3615xs or DS3617xs or DS918+ Update 6: http://download.synology.com/download/DSM/criticalupdate/update_pack/23824-6/ Chose .pat file for DS3615xs or DS3617xs or DS918+ accordingly Critical Updates specifically for DSM 6.2.2 can be found here: Update 1: http://download.synology.com/download/DSM/criticalupdate/update_pack/24922-1/ Update 2: http://download.synology.com/download/DSM/criticalupdate/update_pack/24922-2/ Update 3: http://download.synology.com/download/DSM/criticalupdate/update_pack/24922-3/ Update 4: http://download.synology.com/download/DSM/criticalupdate/update_pack/24922-4/ Update 5: http://download.synology.com/download/DSM/criticalupdate/update_pack/24922-5/ - Does not apply to DS3615xs or DS3617xs Update 6: http://download.synology.com/download/DSM/criticalupdate/update_pack/24922-6/ - Recalled on March 18, re-released on March 24 Chose .pat file for DS3615xs or DS3617xs or DS918+ accordingly
  19. 12 points
    NOTE: This problem is consistently manifested when running on ESXi, but many have encountered problems with Synoboot devices on baremetal installs of 6.2.3. The fix can be implemented safely on baremetal installs and does resolve the issue there also. TL;DR: When running DSM 6.2.3 under ESXi, Jun's 1.03b and 1.04b bootloaders fail to build /dev/synoboot (this can be fixed by installing an extracted script from the loader to re-run after the boot has completed) DSM 6.2.3 displays SATA devices (i.e. bootloader on 1.04b) that are mapped beyond the MaxDisks limit when previous versions did not DSM 6.2.3 update rewrites the synoinfo.cfg disk port bitmasks which may break some high-disk count arrays, and cause odd behavior with the bootloader device Background: Setting the PID/VID for a baremetal install allows Jun's loader to pretend that the USB key is a genuine Synology flash loader. On an ESXi install, there is no USB key - instead, the loader runs a script to find its own boot device, and then remakes it as /dev/synoboot. This was very reliable on 6.1.x and Jun's loader 1.02b. But moving to DSM 6.2.x and loaders 1.03b and 1.04b, there are circumstances when /dev/synoboot is created and the original boot device is not suppressed. The result is that sometimes the loader device is visible in Storage Manager. Someone found that if the controller was mapped beyond the maximum number of disk devices (MaxDisks), any errant /dev/sd boot device was suppressed. Adjusting DiskIdxMap became an alternative way to "hide" the loader device on ESXi and Jun's latest loaders use this technique. Now, DSM 6.2.3: The upgrade changes at least two fundamental DSM behaviors: SATA devices that are mapped beyond the MaxDisks limit no longer are suppressed, including the loader (appearing as /dev/sdm if DiskIdxMap is set to 0C) The disk port configuration bitmasks are rewritten in synoinfo.conf: internalportcfg, usbportcfg and esataportcfg and on 1.04b, do not match up with default MaxDisks=16 anymore. NOTE: If you have more than 12 disks, it will probably break your array and you will need to edit them back (and that's not just an ESXi issue)! Also, when running under ESXi, DSM 6.2.3 breaks Jun's loader synoboot script such that /dev/synoboot is not created at all. Negative impacts: The loader device might be accidentally configured in Storage Manager, which will crash the system The loader partitions may inadvertently be mapped as USB or eSata folders in File Station and become corrupted Absence of /dev/synoboot devices may cause future upgrades to fail, when the upgrade wants to modify rd.gz in the loader (often, ERROR 21) Unpacking Jun's synoboot script reveals that it harvests the device nodes, deletes the devices altogether, and remakes them as /dev/synoboot. It tries to identify the boot device by looking for a partition smaller than the smallest array partition allowed. It's an ambiguous strategy to identify the device, and something new in 6.2.3 is causing it to fail during early boot system state. There are a few technical configuration options can can cause the script to select the correct device, but they are difficult and dependent upon loader version, DSM platform, and BIOS/EFI boot. However, if Jun's script is re-run after the system is fully started, everything is as it should be. So extracting the script from the loader, and adding it to post-boot actions is a universal solution to this problem: Download the attached FixSynoboot.sh script Copy the file to /usr/local/etc/rc.d chmod 0755 /usr/local/etc/rc.d/FixSynoboot.sh Thus, Jun's own code will re-run after the initial boot after whatever system initialization parameters that break the first run of the script no longer apply. This solution works with either 1.03b or 1.04b and is simple to install. This should be considered required for ESXi running 6.2.3, and it won't hurt anything if installed or ported to another environment. FixSynoboot.sh
  20. 11 points
    Bonjour, [EDIT] @nicoueron08/05/2020 : adaptation du tuto pour DSM 6.2.3 sans aucun matos nécessaire en plus. Voici le tuto permettant d'installer proprement DSM 6.2.3 sur un HP gen7 N54L. Coté Loader et DSM: il y a la liste de tous les Loaders ici. Il recommandé d'utiliser le Synoboot_3615. Le Fichier .pat du DSM 6.2.3 (pour le DS3615XS) 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: Votre serveur XPENology est opérationnel ! Les actions suivantes sont facultatives.
  21. 11 points
    Updated powerbutton package to work with dsm 6.2 for ds3615, ds3617 and ds918+ POWERBUTTON_6.2-0002.SPK or https://www39.zippyshare.com/v/R3ftOA3X/file.html
  22. 11 points
    У меня в личке тоже нет ничего, кроме сообщений от желающих получить файлы. И многие пришли на форум именно за ними. От некоторых получивших я даже спасибо не услышал. И как по вашему я должен реагировать на сообщения от людей, которые регистрируются тут только ради своей "экономии"? Отвечу вам - никак.
  23. 11 points
    download this: https://www.dropbox.com/s/ytimsezu9cl61xx/synoboot_1.02b_ESXi_only.zip?dl=0 the only option available is ESXi, so you should not have problems regarding boot choice, it's for DS3615xs (i find has a better custom package support than DS3517xs). - extract and upload synoboot.vmdk and synoboot.img in your datastore - create a new VM (HW Version 11 or 13) dependent if you are on ESXi 6.0u2 or ESXi 6.5b - operating system should be Other -> FreeBSD 64bit - set bios to EFI - set nic to VMXNET3, set the mac manual to the same as the one in the grub.cfg - set scsi controller 0 to "LSI logic SAS" - add sata controller 0 if not there yet present - add existing hdd -> browse datastore -> add synoboot.vmdk - edit this hdd to "independent - persistent" and sata 0:0 on controller 0 - add how many new scsi disk you like, thin provisioning - dependent - save and poweron the VM - from your browser, go to find.synology.com, it should pop-up, connect and install it (manual or from internet is the same), reboot after finish the setup - create a new volume to your needs, if you want shr you have to modify synoinfo.conf - download this zip for open-vm-tools https://www.dropbox.com/s/k4hc343gwdepiuf/open-vm-tools_bromolow-6.0_10.0.7-1.spk.zip?dl=0 - extract the zip, install the spk in package manager - now ESXi should see that vm tools are installed and running Pretty much done.
  24. 10 points
    Download: 1. synoboot vmdk https://mega.nz/#!fdBWBJYB!P3MbGY2v_X_udUhaSgVBQZ74KNRf7vtjMCO39u1I91Y 2. juns loader for DSM 6.2 https://mega.nz/#F!ZlkHQTTb!keje3RK017OjTp3vuWb-Cw 3. synology DSM.pat for synology 3615xs https://www.synology.com https://archive.synology.com/download/DSM/release/ 4. open vm tools spk http://spk.4sag.ru/?fulllist=true 5. XPEnology Tool for Windows x64 PREPARATIONS unzip synoboot.vmdk from DS3615xs 6.0.2 Jun's Mod V1.01 (synoboot.vmdk works with 3615 and 3617 loaders) unzip synoboot.img from synoboot_3615 mount synoboot.img partition 0 with osf mount Make sure to uncheck Read-only drive Go to the mounted drive, Grub folder and edit grub.cfg with notepad++  If you want change default SN and mac1 comment boot option lines you dont need in esxi #menuentry "DS3615xs 6.2 Baremetal $VERSION" --class os { # set img= # savedefault # loadlinux 3615 usb # loadinitrd # showtips #} # #menuentry "DS3615xs 6.2 Baremetal $VERSION Reinstall" --class os { # set img= # loadlinux 3615 usb mfg # loadinitrd # showtips #} # #menuentry "DS3615xs 6.2 Baremetal AMD $VERSION" --class os { # set img= # set zImage=bzImage # savedefault # loadlinux 3615 usb # loadinitrd # showtips #} menuentry "DS3615xs 6.2 VMWare/ESXI $VERSION" --class os { set img= savedefault loadlinux 3615 sata loadinitrd showtips } save file, dismount all and exit. ESXi part: Upload synoboot.vmdk and synoboot.img to esxi (in one folder) Create new VM name the xpenology vm as you want and select Linux and Other 3.x Linux x64 select your storage and you should see customize settings now remove default disk remove scsi controller remove cd/dvd drive and if you are using 3617 loader you need to remove USB controller or change type to USB 3.0 now set cpu at 2 set memory 2GB change Network Adapter Type to E1000e set network adapter 1 mac addres you have in the grub.cfg for example 00:11:32:2C:A7:85 now add existing hard disk and point to the synoboot.vmdk uploaded before. Make sure its on SATA 0:0 now add another sata device and add vm disks to it (sata 1:0, 1:1 etc) and now, the vm is done and finish now start your VM and wait to see after few minutes open in new tab browser find.synology.com click connect accept EULA Set UP and manual install point to DSM 3615xs.pat file downloaded earlier after you confirm instalation you should see instalation progress after 10 minutes reboot enter username, password and server name for dsm skip configure quickconnect dont share location with synology (find.synology.com will not find virtual dsm) now DSM is ready This type of VM should work with dsm 6.2, 6.2.1, 6.2.2 and 3615xs/3617xs loaders DSM 6.2.3 is showing synoboot drive as eSata in dsm BIG thanks to @flyride and @Balrog for the fix
  25. 10 points
    Which DSM version shall I use? This is an oft-repeated question, complicated by the fact that different loaders support different DSM versions AND hardware platforms. In simple terms, DS3615/DS3617 has the widest support for hardware and packages, and DS916/DS918 has support for newer, low-cost CPU's, transcoding and NVMe cache (DS918 only). But the real questions are, what hardware do you have? What hardware do you want to buy in order to support what you want to do? And how does a DSM loader and platform support this? In order to answer, it's useful to understand what hardware is natively supported by DSM. Each DSM version is different as Synology does not need to support many types of hardware, as they build up a specific DSM for each hardware platform they sell. Fortunately, the base Linux kernel has much broader support for hardware than they intend. Most of us guessed at the hardware requirements and made (hopefully) intelligent selections on DSM versus hardware. Some build systems and then are distressed when the hardware isn't fully supported by the DSM platform they choose. Unfortunately, Synology hardware knowledge is often imperfect, as the main boards are custom designed. Refer to the example below for DS3615 (I hope it will be completed more precisely in the future). DS3615xs Reference Hardware: CPU: Intel Core i3-4130 (Haswell) Chipset: Intel C20x? 4x1Gbe Ethernet: ??? Secondary SATA: ??? 10Gbe OEM: E10G18 (Aquantia AQC107) E10G17 (Mellanox Connect X-2/3/4) E10G15 (Tehuti) With even this information, we can make some good guesses on what hardware might be supported. We certainly can act on the 10Gbe cards since those are well known. Wouldn't it be great if we knew ALL the different drivers that are natively supported? Unfortunately this is a fairly difficult process if you are not a Linux guru (and a bit laborious even if you are). There are "user-reported" hardware compatibility threads out there, but many don't understand that those reports are both DSM version and platform specific. Furthermore, with the way hardware manufacturers reissue hardware with the same name but new PCI device number (such as the Intel PHYs on desktop motherboards), often not enough information is reported to confirm whether a specific piece of hardware is suitable for use. If you aren't sure if your hardware is supported, this post and the complementary DS918 driver guide aim to help you. Download the appropriate Excel spreadsheet to see key driver support in the DS3615 6.1.7 or 6.2.1 Synology custom kernel, and via loadable modules supplied with DSM. Hopefully it will help you select the best DSM platform for your purposes, and possibly inform your hardware purchases. Common drivers missing from this platform, or newer driver versions that support the latest silicon may be available by installing additional compiled modules. DSM 6.1.7 DS3615 V1.04 2019-Feb-04.xls DSM 6.2.1 DS3615 V1.0 2019-Feb-04.xls
  26. 10 points
    This is a MAJOR update of DSM. DO NOT UPDATE TO DSM 6.2 with Jun's loader 1.02b or earlier. Your box will be bricked. Use loader 1.03b instead. You have been warned. https://www.synology.com/en-global/releaseNote/DS3615xs
  27. 10 points
    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
  28. 10 points
    Login (replace URL, PORT, USER, PASS) https://URL:PORT/webapi/auth.cgi?api=SYNO.API.Auth&method=Login&version=1&account=USER&passwd=PASS for ActiveBackup its the following urls Get Activationstatus https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=get&version=1 Set ActivationStatus (use your SERIALNUMBER) https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="SERIALNUMBER"  for Office365 its the following urls Get Activationstatus https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupOffice365&method=get_activation&version=1 Set ActivationStatus (use your SERIALNUMBER) https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupOffice365&method=set_activation&version=1&serial_number="SERIALNUMBER" for GSuite its the following urls Get Activationstatus https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=get_activation&version=1 Set ActivationStatus (use your SERIALNUMBER) https://URL:PORT/webapi/entry.cgi?api=SYNO.ActiveBackupGSuite&method=set_activation&version=1&serial_number="SERIALNUMBER"
  29. 10 points
    Failure to comply with the below guidelines will result in your topic or post being deleted. ---------------------------IF YOU ARE CREATING A TOPIC SCROLL DOWN TO THE NEXT SECTION--------------------------- ---------------------------IF YOU ARE SIMPLY MAKING A POST READ RIGHT BELOW--------------------------- I remind everyone that the DSM Updates Reporting forum is SOLELY AIMED at REPORTING SUCCESSFUL or UNSUCCESSFUL updates. This forum is NOT meant for asking questions whether they are in direct connection with the update or not. Such posts will be removed. Please follow the template below when making a post in this forum. It makes it easier for others to check the status of an update. - Outcome of the update: (Successful update or not) - DSM version prior update: (DSM 6.1.7-15284 UPDATE 3) - Loader version and model (3615xs or 3617xs or 916+ or 918+) - Using custom extra.lzma: (Yes / No and from who / version) - Installation type: (BAREMETAL / VM / Hardware details (specially NIC)) - Additional comments: (Problems encountered etc. No questions allowed here. Comments should be in direct connection to the upgrade. All other comments will be removed) EXAMPLE: - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.1.3 UPDATE 7 - Loader version and model: JUN'S LOADER v1.02b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Gigabyte H97N - NIC: Intel I217-V & Qualcomm Atheros AR8161 Gigabit Ethernet (rev 10) - Additional comments: HANGED BUT A REBOOT FIXED IT You can copy paste the above and modify the data according to your specific situation. Keep UPPER CASE and use RED color in the first line if the update is UNSUCCESSFUL. Use BOLD as above. If you have specific comments because there is a problem with an update use the Additional Comments line to mention them. If you have a question then use the appropriate sub-forum, not this one. When posting, please DO NOT refer to your hardware in your signature or post links to your configuration from any external website or from your About Me section. If for some reason you modify those (or the link breaks) one day then your post becomes useless to the community. ---------------------------IF YOU ARE CREATING A TOPIC READ BELOW---------------------------------- If you are the one creating a topic because a new update has been released by Synology please stick to the following guideline: 1 - Visit https://xpenology.com/forum/forum/78-critical-updates/ first to check that the topic has not been created. If not, then use the following topic naming convention: If it is a critical update: DSM X.X.X-XXXXX - Update X If it is an intermediate update: DSM X.X.X-XXXXX If it is a major update: DSM X.X-XXXXX 2 - Add the following tags to the topic according to the type of update: If it is a critical update: dsm x.x.x, critical update If it is an intermediate update: dsm x.x.x, intermediate update If it is a major update: dsm x.x.x, major update 3 - Visit this topic and create the OP following the same format: Screenshot of the release note Link to the Release note Copy and paste release note content using the spoiler tag as shown below
  30. 9 points
    kernel modules/drivers are specifically compiled for a kernel (-versions) and even distributions it's not like windows where you can download a driver somewhere and just put it in so don't take any *.ko file, stick it in and expect it to work if you haven't build the *.ko yourself or don't know exactly where it came from, expect it to fail I'm no expert but as there is no how-to here in the forum - lets start one hopefully other will correct and help refine or take over and rewrite it some steps are made in windows (osfmount) but will also possible in the chroot environment on linux basic knowledge about using a linux console and command-line tools (or midnight commander) is needed, if you never used this you should not start with this how-to, choose something easier or invite someone who is able to help (do a workshop) doing all this from scratch will take at least 1-2 hours, in most cases (re-read, google, try, google, try again, ...) much longer, maybe plan a weekend of text-adventure fun edit: i think it also will do for 6.0.2 and loader 1.01 (not tested), kernel sources are available: https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/8451branch/bromolow-source/linux-3.10.x.txz/download, extra.lzma is a little differently placed (boot.img\image\DS3615xs\) but the steps will be the same 1. building the kernel module (driver) 1.1 what driver/module i need you will have to find out (google) what the name of the driver/module is that your hardware needs or you will have to know where to find the rigt option in the menu-system of the kernel when configuring it example: nForce 630 chipset with RTL8211E, you might expect it to be a realtek driver like rtl*.ko but it's not its "forcedeth.ko" because the RTL8211 is not a fully working PCIe Network Chip in some cases you might be forced to find out by booting a linux distribution and look in /var/log/, use lspci or other tools it also helps if the hardware provider has already compiled packages for specific distributions like redhat, you can look inside these packages for *.ko files you also can look in the .config file of the kernel (more below) with a text editor to find a section where the module is mentioned, this will also give you a hint where to find it in the menu-system when configuring the kernel 1.2 you need the kernel source in the case of synology that seemed sometimes difficult but at the moment there is kernel source for dsm 6.1 https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/ 15047 is the synology build version and tells you about what dsm version it is (15057 = dsm 6.1) and what kernel was used to build the modules, it !!!might!!! change in a later version so always check for what version your bootloader from usb stick is made for (jun 1.02 is for 15047) edit: dsm 6.1.1 has a new build number 15101 but seems to use the same kernel 3.10.102 as 6.1 so it should work with 6.1.1 too as i write this for ds3615xs it's bromolow as a platform, for ds3617xs it's broadwell and ds916+ is braswell (you usually see that name on the update files for a synology system like "synology_broadwell_3617xs.pat") so for ds3615xs we use this: https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/15047branch/bromolow-source/linux-3.10.x.txz/download edit: it looks like as for building the modules there is no difference for kernels modules build for 3615 and 3617 even if https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/15047branch/ has extra kernel sources for bromolow and broadwell, there are all intel x86_64, same might go for the 916+ (not testet yet), at least a evdev.ko build from 3615 kernel source did load without problems in a vm with the 3617 image 1.3 setting up a DSM 6.1 ds3615xs test environment with virtualbox (its free) or whatever works with juns loader look in the forum to find something that works, basics for virtualbox are - mac of the nic (intel pro 1000 desktop) in vm and grub.conf need to be the same - boot controller for jun's image (vmdk with reference to img file) is ide, controller for dsm disks is scsi lsi (!!!) - choose esx server option in grub menu 1.4 installing chroot put in http://packages.synocommunity.com for custom packages and change the setting that beside synology packages trusted ones are also to install install debian-chroot plugin (https://synocommunity.com/package/debian-chroot) from community section (some info's about it: https://github.com/SynoCommunity/spksrc/wiki/Debian-Chroot#configure-services) you might also install midnight commander if you are on it, makes things easier if you're not a command-line junky and more used to a graphical environment that give you clues activate ssh in dsm connect with ssh/putty to you dsm, login with user admin (and if you want to be root use "sudo -i") start the chroot with: /var/packages/debian-chroot/scripts/start-stop-status chroot after that you are inside the chroot, check with ls and you won't see "/volume1" or other sysnology specific directory's from the dsm environment, you can leave the chroot environment with "exit" later if you want now we have to update and install tools: apt-get update apt-get upgrade apt-get install locales dpkg-reconfigure locales dpkg-reconfigure tzdata apt-get install mc make gcc build-essential kernel-wedge libncurses5 libncurses5-dev libelf-dev binutils-dev kexec-tools makedumpfile fakeroot linux-kernel-devel lzma bc after that we create a directory (lets say "test") 1.5 copying kernel files and create kernel modules copy the downloaded kernel (linux-3.10.x.txz) to a share on the dsm, open a 2nd putty and copy the linux-3.10.x.txz (/volume1/...) to /volume1/@appstore/debian-chroot/var/chroottarget/test/ (that's where the "test" directory of the chroot environment is located in your real system) change back to your first putty where you are in chroot (the same way can be used to get the created files back to your shared folder on your volume1 which can be accessed from windows) change into "test", extract the linux-3.10.x.txz to a directory named "linux-3.10.x" and change into it the following copy's the kernel config file from synology to the right place for use/build cp synoconfigs/bromolow .config we make a fallback copy make ARCH="x86_64" oldconfig we start the ascii art menu and search for the missing driver to activate cursor/return are your friend in navigating, space selects, we activate the driver to an "M" so its build as module (*.ko file we need) there will be tons of descriptions how to do it, just google if needed make ARCH="x86_64" menuconfig on exit we save the configuration and with the following we make/create the modules (will take a while) make ARCH="x86_64" modules now you have to find your *.ko file (use some nice ls options, to be expanded later) usually you will have to look in /test/linux-3.10.x/drivers/scsi or block copy that file to /test for easy access when we put it in the boot image 2. modify the "synoboot.img" use osfmount (windows) to extract the "extra.lzma" (see dsm 5.2 to 6.0 guide, used there to edit grub.cfg in synoboot.img) in "extra.lzma" are the additional *.ko files and a config file where the files to be loaded on boot are named -> see forum thread "dsm 5.2 to 6.0" with howto to modify jun's loader for usb vid/pid and mac, its basically the same you just open the other partition (30MB) and extract the "extra.lzma" copy the "extra.lzma" to the share of the dsm so we have local access in a putty session on dsm in putty session #2 ("normal" session without chroot) we copy the "extra.lzma" to the "test" directory in the chroot environment go to putty session#1 (in chroot) decompress "extra.lzma" to "extra" ("extra.lzma" is a compressed cpio file) with: lzma -d extra.lzma with ls we can check that "extra.lzma" is now just ""extra" (a cpio file without the extension cpio) create a new directory, copy the "extra" there, change into it and extract it with: cpio -idv < extra delete the remaining file "extra" inside this directory we copy the *.ko file into usr/lib/modules/ and in /etc we edit the file rc.modules (easy with midnight commander, go to file, press F4, internal editor) network drivers seems to be added under EXTRA_MODULES, storage drivers under DISK_MODULES, just go to the end of the line and fill in the name of the *.ko file without the ".ko", what you add is basically a blank and the name rc.modules looks like this: EXTRA_MODULES="mii mdio libphy atl1 atl1e atl1c alx uio ipg jme skge sky2 ptp_pch pch_gbe qla3xxx qlcnic qlge netxen_nic sfc e1000 pcnet32 vmxnet3 bnx2 libcrc32c bnx2x cnic e1000e igb ixgbe r8101 r8168 r8169 tg3 usbnet ax88179_178a button evdev ohci-hcd" DISK_MODULES="BusLogic vmw_pvscsi megaraid_mm megaraid_mbox megaraid scsi_transport_spi mptbase mptscsih mptspi mptsas mptctl ata_piix megaraid_sas mpt2sas mpt3sas" EXTRA_FIRMWARES="bnx2/bnx2-rv2p-09ax-6.0.17.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-06-6.0.15.fw tigon/tg3_tso5.bin tigon/tg3_tso.bin tigon/tg3.bin" if your controller or nic needs a firmware, you add the file under usr/lib/modules/firmware/ and add the appropriate line in EXTRA_FIRMWARES, if a extra directory inside "firmware" is used it has to be added to the name, see the bnx2 firmware files after everything is in place we recreate the cpio file, re-compress it as lzma and write it in the directory above as "extra.lzma" the command is used inside the directory where we extracted the file "extra" (command line taken from https://github.com/kref/scripts, its what jun uses to create it): (find . -name modprobe && find . \! -name modprobe) | cpio --owner root:root -oH newc | lzma -8 > ../extra.lzma in putty session #2 (without the chroot) we copy "extra.lzma" from the chroot position in filesystem to the location where we can access it from windows if you still have osfmount open to the "synoboot.img" replace the "extra.lzma" with the new one, dismount and close osfmount - our new "synoboot.img" is ready to test it ps: i was asked to make a video - thats much harder to change and i'm to old for this
  31. 9 points
    Compiled button.ko and evdev.ko with newest bromolow sources so itll work with dsm 6.2 (i guess it will only work for ds3615 and ds3617) HowTo: 1. download linux-VERSION_NUMBER.txz from newest branch https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/ according to your architecture https://github.com/SynoCommunity/spksrc/wiki/Architecture-per-Synology-model 2. extract archive and execute the following #if you have another architecture, change bromolow cp synoconfigs/bromolow .config make ARCH="x86_64" oldconfig make ARCH="x86_64" menuconfig # set as module: Device Drivers ---> Input device support --> Event interface make ARCH="x86_64" modules 3. search for button.ko and evdev.ko and put it into the package.tgz under modules/6.2/ in your powerbutton.spk and save. I attached a ready to go spk for bromolow (ds3615) but it works for ds3617 too POWERBUTTON_6.2-0001.SPK or https://www9.zippyshare.com/v/v32vxKUA/file.html
  32. 8 points
    Ce tuto est une mise à jour du tuto que j'ai déjà fait l'année dernière. Le tuto ci-dessous permet d'installer/migrer DSM 5.2 à DSM 6.1.7 directement sans devoir à passer par DSM 6.0.2. Si pour une raison ou une autre vous voulez migrer à DSM 6.0.2 d'abord ou alors tout simplement vous ne voulait pas migrer à DSM 6.1.7 mais souhaiter migrer à DSM 6.0.2 uniquement alors utilisez le lien ci dessus. Pour mettre à jour DSM 6.0.2 à DSM 6.1.7 voir ici. Comme la plupart de vous doivent déjà le savoir Jun a réussi un exploit en créant un loader permettant l'installation de DSM 6 sur du matériel non Synology. Voici le fil de la discussion pour ceux que ça intéressent: https://xpenology.com/forum/topic/6253-dsm-6xx-loader/. Il va vous falloir quelques outils. Je pars du principe que vous êtes sous Windows 10, 8, 7, Vista ou XP. Si vous êtes sur un MAC OS et que vous comprenez l'anglais réfèrerez vous au post que j'ai fait sur comment écrire et monter l'image sur une clef USB. Vous pouvez ensuite revenir sur ce tuto après avoir effectué les manips nécessaires sur MAC OS. Si vous avez des doutes n'hésitez pas à laisser un commentaire. Si vous êtes à DSM 5.1 ou sur une version antérieur, il faut tout d'abord mettre à jour DSM à la version 5.2. Si vous faites une installation fraîche de DSM 6.1 alors vous êtes bon pour la suite. Simplement omettez toute référence à DSM 5.2 Voici ce dont vous avez besoin: - Win32 Disk Imager. Application permettant de rendre une clef USB bootable. - Une clef USB que l'on utilisera pour y mettre le loader. 4GB suffiront largement. Je conseille une clef de marque (Kingston, SandDisk ou autre). Cela évitera les problèmes dans le future. - Comment connaitre le VID et PID de votre clef usb >>> voir ici - Un éditeur de texte avancé. Notepad++ fera l'affaire. L'éditeur de text Notepad inclu avec Windows est déconseillé. - DSM 6.1.7. Télécharger un des fichiers relatifs à un des 3 modèles suivant: DS3615sx ou DS3617sx ou DS916+. Télécharger uniquement le fichier avec l'extension ".pat" et non celui avec l'extension ".pat.md5". Les fichiers PAT viennent directement des serveurs de Synology, donc sans aucune altération. - Le loader (miroir) officiel v1.02b de Jun. Ce loader est hybrid c'est à dire qu'il marche en EFI ou BIOS donc il devrait marcher sur une majorité de machines capable de lire du GTP. Pour les machines plus vielles qui ne peuvent lire que du MBR ce loader ne marchera pas. Utilisez alors l'image du loader v1.02b faites par @Genesys construite à partir du loader de Jun mais faite avec une table de partitionnement de type MBR. Note: Le loader v1.02b de Jun est compatible avec les CPU Intel. Pour les CPU AMD cela n'est pas entièrement le cas mais plusieurs personnes ont mentionnée qu'il était possible d'utiliser ce loader. Il serait d'après eux nécessaire de désactiver la fonction C1E dans le BIOS (applicable aux machines HP comme le N40L ou N54L par exemple). Si vous avez un autre model/marque de machine AMD ne me demandez pas, je ne sais pas. Il faudra que vous regardiez dans le bios et fassiez des tests vous même. Partagez voter expérience ca en aidera surement d'autres. - Le ramdisk personnalisé extra.lzma. Ce ramdisk est optionnel et ne doit être utiliser que si le ramdisk par défaut inclus dans le loader ne permet pas la détection du matériel. Je le fourni pour ceux qui pourraient avoir des problèmes de détection réseau ou de contrôleurs de disques non reconnus. Ce ramdisk personnalisé contient des modules (drivers) additionnels qui ont été compilé par @IG-88 avec le code source de DSM 6.1.3. Je ne garantie pas qu'ils marchent tous. Vous devrez remplacer (ou renommer, au cas ou!) le ramdisk par défaut extra.lzma par celui ci. Si vous avez des questions spécifiquement liées au ramdisk de IG-88 merci de les poster directement dans le fil de discussion de IG-88, pas ici. - Faites attention à branchez vos HDD successivement en commençant par le premier port SATA normalement décrit comme SATA0 sur les cartes mères. Vérifiez avec le fabriquant de votre carte mère. Si vous faites une migration à partir de DSM 5.2 alors laissez tel quel. - OSFMount. Application permettant de modifier le fichier grub.cfg directement sur l'image. Ceci n'est pas strictement nécessaire car Jun a rendu possible la configuration du VID/PID, S/N et MAC directement à partir du Menu Boot Grub. Si vous préférez utiliser la nouvelle méthode il suffit d'omettre le Point 4, lisez plutôt la Note 4 et reprenez le tuto à partir du Point 5. SVP LISEZ TOUT LE TUTO AVANT DE FAIRE N'IMPORTE QUOI L'utilisation de ce loader relève de votre entière responsabilité. Ne me tenez pas responsable si vous perdez vos données ou que votre NAS part en fumée. Sachez aussi que ce loader contient moins de drivers que sous DSM 5.2 donc si il est primordiale pour vous d'avoir une machine opérationnelle h24 je vous conseille de lire en bas du tuto les drivers disponibles. Si votre module n'est pas inclus alors il vous faudra les compiler vous même ou utiliser le ramdisk personnalisé qui se trouve ci-dessus. Ne me demandez pas de compiler des modules à votre place, je ne le ferais pas. NE METTEZ PAS A JOUR DSM AU DELA DE LA VERSION 6.1.7 AVEC LE LOADER v1.02b. EN D'AUTRES TERMES NE METTEZ PAS A JOUR DSM A LA VERSION 6.2 A bon entendeur. Maintenant que vous avez tout ce qu'il vous faut, passons aux choses sérieuses: 1 - Faites un backup de vos données et de votre configuration avant toute chose. Cela évitera la pleurniche plus tard. Imprimez ce tuto si nécessaire. 2 - Eteignez votre NAS. Déconnectez votre clef USB avec votre loader 5.2. Je conseille que vous mettiez de coté la clef USB que vous utilisez actuellement avec DSM 5.2 et prenez une nouvelle clef USB pour DSM 6.1. Cela évitera de la refaire si l'upgrade ne marche pas pour vous et que vous avez besoin de revenir à DSM 5.2. 3 - Allez à votre PC, branchez votre clef USB et lancez votre application de choix permettant de voir le VID et PID de votre clef USB. Notez ça quelque part car vous en aurez besoin sous peu. 4 - Maintenant lancez OSFMount. Sélectionnez "Mount New", puis choisissez votre loader (fichier au format .img) dans "Image File". Une autre fenêtre s'ouvre. Sélectionnez la partition 0 (celle de 15 MB). Cliquez Ok. Sur la fenêtre principale décochez la case "Read only drive". Cliquez Ok. La partition de l'image devrait maintenant être montée dans votre explorateur de fichiers. Vous pouvez maintenant aller au dossier /grub et remplacer (ou renommé) le ramdisk par défaut extra.lzma par celui que j'ai fourni un peu plus haut. Maintenant revenez en arrière et aller dans le dossier /grub et éditer le fichier grub.cfg avec votre éditeur de texte avancé. Si vous avez besoin de remplacer le ramdisk par défaut par le ramdisk extra.lzma personnalisé il vous faudra alors aussi monter la partition 1 (celle de 30MB) avec OSFMount. Le contenue du fichier grub.cfg est le suivant: Je ne mets uniquement ici que la portion du code qui nous intéresse dans le cadre de ce tuto: [...] 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' [...] Les données à modifier sont les suivantes: vid=0x090C par vid=0x[le vid de votre clef usb] pid=0x1000 par pid=0x[le pid de votre clef usb] sn=C7LWN09761 par sn=générez votre sn ici avec le modèle DS3615xs ou DS3617xs ou DS916+ (cela va dépendre que quel loader vous avez choisi) mac1=0011322CA785 par mac1=[l'adresse MAC du port réseau #1]. Vous pouvez rajouter set mac2=[l'adresse MAC du port réseau #2] si vous avez un 2ième port réseau et ainsi de suite jusqu'à mac4 mais ceci n'est pas nécessaire. Conseil: changez timeout='1' par timeout='4' - Cela rallonge la durée d'affichage du Menu Boot Grub lorsqu'il apparaitra à l'écran. Une fois finie l'édition du fichier grub.cfg, sauvegardez les changements et fermez l'éditeur de texte. Sur OSFMount cliquez sur "Dismount all & Exit". Vous êtes maintenant fin prêt à écrire l'image sur votre clef USB. 5 - Utilisez Win32 Disk Imager pour rendre votre clef USB bootable avec l'image que vous venez d'éditer. 6 - Ejectez votre clef USB chaude et brulante proprement. Branchez la sur votre NAS (évitez les ports USB 3.0). Démarrez la machine et accédez immédiatement à votre BIOS afin de le reconfigurer pour que le boot se fasse à partir de la nouvelle clef usb. Faites les changements nécessaires pour redémarrer en UEFI ou en legacy bios, c'est à vous de choisir. Aussi, dans le BIOS, les HDD doivent être configurés en AHCI et non pas en IDE. Finalement et si possible, activez dans le BIOS le port série si il ne l'est déjà pas. Toutes les cartes mère n'ont pas forcément de port série. Si c'est le cas pour vous alors ce n'est pas bien grave, le loader se chargera du problème. Sauvegarder les changements fait au BIOS et redémarrez. 7 - Une fois redémarré, si vous avez un écran connecté au NAS vous verrez le Menu Boot Grub suivant: CONSEIL: avant même que le Menu Boot Grub n'apparaisse cliquez de façon répétée les touches haut ou bas. Cela aura comme effet d'arrêter le compte à rebours et vous donnera le temps de choisir la ligne que vous voulez. Vous verrez l'écran suivant après avoir fait entrer: Si vous avez démarrer la clef USB en mode EFI vous ne verrez normalement pas les 3 dernières lignes. Rien de grave. 8 - Retournez à votre PC et lancez de préférence Synology Assistant ou alors allez à http://find.synology.com. Normalement si vous avez bien tout suivi votre NAS devrait être détectée sur votre réseau local au bout d'une minute environ (j'ai testé avec un machine virtuelle et ça a prit ~55 secondes). Il suffit ensuite de suivre les indications pour soit faire une installation fraîche soit faire la migration de DSM 5.2 à DSM 6.1. A un moment donné DSM vous demandera le fichier PAT (DSM_DS3615xs_15217.pat ou DSM_DS3617xs_15217.pat ou DSM_DS916+_15217.pat) que vous avez normalement déjà téléchargé. 9 - Une fois finie la MAJ ou l'installation fraîche, accédez à votre NAS comme d'habitude. Il vous faudra surement mettre à jour plusieurs applications. Vous pouvez ensuite mettre à jour DSM 6.1.7 jusqu'à DSM 6.1.7 (critical update 3). Il est possible que vous soyez obligé de faire un reboot forcé. Certaines personnes ont dû refaire la clef usb aussi. Désactivez la mise à jour automatique dans DSM. Si besoin est, voici ou télécharger les fichiers individuels (DSM et updates): https://xpenology.com/forum/topic/7294-links-to-dsm-and-critical-updates/ 10 - Voila c'est fini. Si vous avez des questions cherchez le forum/Google d'abord. Si vous êtes toujours bloqué alors posez votre question en donnant les spécifications de votre matériel (model carte mère, contrôleur LAN, contrôleur disk etc) faute de quoi votre post sera supprimé ou sciemment ignoré. -------------- Note 1: Si après avoir suivi le tuto votre NAS n'est pas accessible via http://find.synology.com ou Synology Assistant la raison la plus probable c'est que les drivers de votre carte réseau n'ont pas été inclus dans le loader. Faites un effort et utilisez Google pour savoir quel module votre carte réseau et/ou votre contrôleur de disque utilisent sous linux suite à quoi vérifiez que ces modules soient inclus dans le ramdisk personnalisé. Si vous le voyez alors utilisez le ramdisk personnalisé. Si rien ne marche alors poser votre question. Note 2: Une fois passé à DSM 6.1 sachez que vous n'aurez plus accès au NAS via ssh avec le compte root. Vous pouvez ceci dit y accéder avec votre compte administrateur puis élever les droits en utilisant sudo -i Ceci est tout à fait normal. C'est Synology qui a voulu sécuriser l'accès à DSM. Note 3: Vérifiez bien le VID/PID de votre clef USB avant d'entamer la MAJ. Si lors de la migration vous obtenez l'erreur suivante: "Failed to install the file. The file is probably corrupted. (13)" (ou l'équivalent en français) c'est que le VID/PID ne correspond pas à votre clef USB. Si vous avez toujours des problèmes après avoir bien vérifié le VID/PID alors essayez une autre clef usb. Note 4: Les changements effectués sur le fichier grub.cg peuvent aussi être fait directement à partir du Menu Boot Grub donc en principe il est tout à fait possible d'ignorer le Point 4 et écrire l'image synoboot.img sur votre clef USB sans rien modifier (il suffit de continuer à lire à partir du Point 6). Pour faire les modifications il faut appuyer sur la lettre 'C' lorsque vous voyez le Menu Boot Grub apparaitre. Il faut être vif car vous n'avez qu'une seconde avant que le menu disparaisse. Apres avoir appuyé sur la lettre C vous vous retrouverez dans une invite de commande grub. Pour changer le VID vous devez écrire comme suit: vid 0xLES 4 CHIFFRES VID DE VOTRE CLEF USB Faites la même chose pour pid, sn et mac1. Appuyez sur entrer à chaque commande. Les commandes sont les suivantes: pid 0xLES 4 CHIFFRES PID DE VOTRE CLEF USB sn LE NUMERO DE SERIE DE VOTRE NAS mac1 L'ADRESSE MAC1 DE VOTRE NAS Si vous avez plusieurs cartes réseau vous pouvez les rajouter de la meme manière: Le maximum c'est mac4. Voir ci dessous: mac2 L'ADRESSE MAC2 DE VOTRE NAS mac3 L'ADRESSE MAC3 DE VOTRE NAS mac4 L'ADRESSE MAC4 DE VOTRE NAS Si vous pensez avoir fait une erreur il suffit de refaire la commande. Lorsque vous avez fini appuyez sur Esc et sélectionnez la ligne du menu qui convient. Ci dessous un example a quoi ressemble l'invite de commande grub avec les commandes: Note 5: Si lors de l'installation vous recevez un message d'erreur de type "Nous avons détecté des erreurs sur les disques [numero des disques] et les ports sata ont également été désactivés, remplacer les disques et réessayer" alors il faut rajouter SataPortMap dans l'invite de commande Grub (ou dans le fichier grub.cfg). Appuyer sur la letter C lors du Menu Boot Grub et écrivez ceci: append SataPortMap=XX XX est le nombre de HDD présent. N'oubliez pas de mettre à jour ce paramètres si vous rajouter des HDD. Par ailleurs, si vous êtes amené à utiliser Reinstall, il ne faut pas oublier de sélectionner le mode normal (première ligne du menu grub) lors du reboot automatique après l’installation, sinon le loader sélectionnera à nouveau Reinstall et cela occasionnera des problèmes ultérieurement. @@@@@@@@ Précisions sur ce que veut dire SataPortMap= @@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ ############## Problèmes connus ##################### - Sur des machines à coeur unique et lent le "patcher" charge trop tard. - Certains drivers de cartes réseau plantent lorsque le MTU est au delà de 4096 (Jumbo frame). ############# Modules inclus dans le Loader de Jun par défaut ############# ############### Log des modifications du Tuto ###################
  33. 8 points
    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
  34. 8 points
    This version is alpha, as the loader 1.03a2 is, so DO NOT use this on a "production" systems and be prepared to loose the data you have on the "test-system" (I recommend you have a very recent backup) !!!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 !!! HP SmartArray Controller driver (hpsa.ko) is back in for testing (for now the one that comes with kernel 4.4.59), my P400 i had access to was to old for this driver so please try to test, newer controller even seem to have a IT mode so if present try it with this mode 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. extra.lzma for DS918+ v0.2 (still online for testing against new 0.4) http://s000.tinyupload.com/?file_id=40794274174411841232 extra.lzma for DS918+ v0.3 http://s000.tinyupload.com/?file_id=09865768016965468337 extra.lzma for DS918+ v0.4 http://s000.tinyupload.com/?file_id=85078902011391385959 extra.lzma for DS918+ v0.5_test http://s000.tinyupload.com/?file_id=04554930831776996450 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.2 (kernel 4.4.59) 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  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 and provide relevant information such as: ramdisk version, loader model, motherboard and any additional storage/networks cards present in the system. Other things good to know about DS918+ image and loader 1.03a2: 1. DS918+ image comes with a limit for 2 internal network ports in synoinfo.conf (the original hardware has two ports and does not have a pcie slot for extending) jun's loader does not changes this (now?), so if you plan to user more then 2 ports you will have to manually change the synoinfo.conf (3615 and 3617 are bigger business models and have options for additional network card, the default from synology is 8 on this systems) further information can be read here: 2. hardware transcoding seems to crash the system when a monitor is attached, unplug monitor, reboot try again to see if there is decoding hardware present you can try this (there should be something in like card0) ls -al /dev/dri/ when using plex you should download the 64bit version from website, with plex pass active (hardware-accelerated streaming is a premium feature and requires an payed active Plex Pass subscription), Settings > Server > Transcoder, Turn on Show Advanced, Turn on Use hardware acceleration when available 3. if your screen goes blank during boot and the system does not show up in network the kernel might have crashed on boot while loading i915.ko driver (CPU internal GPU) look in your bios for a legacy mode option, disable it and try again (boot process and crash can be seen when using a "good old" serial cable and a console program like putty on a 2nd computer - that's rarely done but if you want to know for sure, that's your way to find out, DSM does not have a typical boot screen that shows log info and login prompt after boot, that's redirected to the serial port)
  35. 8 points
    Господа, я понимаю ваше желание получить всё и сразу. Попробуйте понять и меня. У меня не так много времени на разработку и проверку. Я мог бы конечно бросить все дела и заняться исключительно SS, но мне это не нужно. Это отнимает очень много личного времени и я занимаюсь "чтением" кода исключительно в свободное время. Как только будут новости, вы их сможете прочитать в этой теме. Не нужно мне в личку сыпать сообщениями с просьбой выслать файлики, это бесполезно. Те, кто успел получить нестабильный вариант конечно могут поделиться с остальными, но на то он и нестабильный, что за его работоспособность я отвечать не хочу. На этом всё.
  36. 8 points
    Hello, The Jun's versions 1.01 (DSM 6.0.2) and 1.02B (DSM 6.1X) are rebuild with a MBR partition table. I have put on the repository all images that i have rebuild with my automated conversion (MBR Partition table versions) tool. The repository link is here : https://mega.nz/#F!cIUXnCSS!VruDf235t2uLcRxIjji3qQ Hoping to move forward the XPEnology community. PS : The files "Convert_By_Genesys" contains the number of loader version and the partition table format use. PS2 : I will continue to make MBR Partition table version for next loaders. PS3 : The code base of my Automated Conversion Tool is the same as Jun's : https://github.com/kref/scripts
  37. 8 points
    If you can't access your Xpenology box but you still wish to try and 'fix' some configuration files or perhaps you wish to finally make that backup that you should have done before fiddling with the root user, then you can access the content of the system partition and data partitions through a Live Ubuntu CD (or whatever unix flavoured OS you so desire). Here is how to: 1 - Make a Live Ubuntu USB drive. Ideally it is more convenient to make a persistent Live Ubuntu USB drive but that's not required for this tutorial and it would just complicate things unnecessarily. 2 - Once you're done burning Ubuntu on the USB flash drive, go plug it in your Xpenology box and boot from it. 3 - Once in Ubuntu, launch Terminal. You will need to first be root so type: sudo -i 4 - Now install mdadm and lvm2 by typing the following command: apt-get install mdadm lvm2 You should get the following Postfix Configuration menu: Select as shown in the pictures above. If you wish to mount the data partition alone then proceed with the following command: 5 - To mount the data partition, simply issue this command and you are done: mdadm -Asf && vgchange -ay If you also wish to mount the system partition then proceed with the following commands (adapt to your case accordingly): 6 - Then you need to check your raid array and partitioning of your drives: fdisk -l | grep /dev/sd In my case I see this. Note I only have 2 drives /dev/sda and /dev/sdb root@server:/etc.defaults# fdisk -l | grep /dev/sd Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors /dev/sda1 256 4980735 4980480 2.4G fd Linux raid autodetect /dev/sda2 4980736 9175039 4194304 2G fd Linux raid autodetect /dev/sda3 9437184 3907015007 3897577824 1.8T f W95 Ext'd (LBA) /dev/sda5 9453280 3907015007 3897561728 1.8T fd Linux raid autodetect Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors /dev/sdb1 256 4980735 4980480 2.4G fd Linux raid autodetect /dev/sdb2 4980736 9175039 4194304 2G fd Linux raid autodetect /dev/sdb3 9437184 3907015007 3897577824 1.8T f W95 Ext'd (LBA) /dev/sdb5 9453280 3907015007 3897561728 1.8T fd Linux raid autodetect System partitions are the ones labeled sda1, sdb1. If you have more drives in the array, subsequent system partitions will probably be called sdc1, sdd1 so on and so forth. You get the point. 7 - Once you figured out all system partitions, you can examine the foreign endian array members by issuing (this is for my case, with 2 drives): mdadm -Ee0.swap /dev/sda1 /dev/sdb1 If you have 3 drives then you add /dev/sdc1. You get the idea. 8 - Finally, assemble the array and fix the byte order (this is for my case, with 2 drives): mdadm -AU byteorder /dev/md0 /dev/sda1 /dev/sdb1 Same comment as previous command; add any additional system partitions that you may have. Beware of the /dev/md0. It's normal, not a mistake. Your system partition should now be mounted and you can navigate through the system files. Simply unmount the drives and shutdown the machine when you are done. If for some reason you need to reboot and want to access the partitions again then you will need to re-install mdadm and lvm2 because the Live Ubuntu USB is not persistent. --------- Reference: https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Storage/How_can_I_recover_data_from_my_DiskStation_using_a_PC http://xpenology.com/forum/viewtopic.php?f=2&t=22100&p=83631&hilit=version#p83631 http://xpenology.com/forum/viewtopic.php?f=2&t=20216&p=74659&hilit=mdadm#p74659 >> Thanks to Jun
  38. 8 points
    its an old script bug due to my oversight, I am uploading a new version to fix it, hopefully without introduce new bugs
  39. 7 points
    This is nice work, and thank you for your contribution. For those who aren't familiar with patching binary files, here's a script to enable nvme support per this research. It must be run as sudo and you should reboot afterward. Note that an update to DSM might overwrite this file such that it has to be patched again (and/or can't be patched due to string changes, although this is unlikely). Your volume might appear as corrupt or not mountable until the patch is reapplied. To be very safe, you may want to remove the cache drive from the volume prior to each update. #!/bin/ash # patchnvme for DSM 6.2.x # TARGFILE="/usr/lib/libsynonvme.so.1" PCISTR="\x00\x30\x30\x30\x30\x3A\x30\x30\x3A\x31\x33\x2E\x31\x00" PHYSDEVSTR="\x00\x50\x48\x59\x53\x44\x45\x56\x50\x41\x54\x48\x00\x00\x00\x00\x00\x00" PCINEW="\x00\x6E\x76\x6D\x65\x00\x00\x00\x00\x00\x00\x00\x00\x00" PHYSDEVNEW="\x00\x50\x48\x59\x53\x44\x45\x56\x44\x52\x49\x56\x45\x52\x00\x00\x00\x00" # [ -f $TARGFILE.bak ] || cp $TARGFILE $TARGFILE.bak if [ $? == 1 ]; then echo "patchnvme: can't create backup (sudo?)" exit fi COUNT=`grep -obUaP "$PCISTR" $TARGFILE | wc -l` if [ $COUNT == 0 ]; then echo "patchnvme: can't find PCI reference (already patched?)" exit fi if [ $COUNT -gt 1 ]; then echo "patchnvme: multiple PCI reference! abort" exit fi COUNT=`grep -obUaP "$PHYSDEVSTR" $TARGFILE | wc -l` if [ $COUNT == 0 ]; then echo "patchnvme: can't find PHYSDEV reference (already patched?)" exit fi if [ $COUNT -gt 1 ]; then echo "patchnvme: multiple PHYSDEV reference! abort" exit fi sed "s/$PCISTR/$PCINEW/g" $TARGFILE >$TARGFILE.tmp if [ $? == 1 ]; then echo "patchnvme: patch could not be applied (sudo?)" exit fi sed "s/$PHYSDEVSTR/$PHYSDEVNEW/g" $TARGFILE.tmp >$TARGFILE if [ $? == 1 ]; then echo "patchnvme: patch could not be applied (sudo?)" exit fi echo "patchnvme: success" rm $TARGFILE.tmp 2>/dev/null
  40. 7 points
    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
  41. 7 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
  42. 6 points
    Before you begin to change something in your working system, it is strongly recommended to make backups of your most valuable data, so you do not regret about their irretrievable loss. Everything you do is your fear and risk, no one encourages you to do it. The easiest and most reliable way to safely try to do it, turn off all the disks and the boot flash drive from the current system, take a clean disk and another USB flash drive and try to install a new version of the bootloader and the system, if it rolled, then do already on the current system. 1. How to install (described for a computer with Windows): a) download the 1.04 b boot loader image (the original theme is here), create a directory in the root of the disk, for example, c:/918/ and put the bootloader image there b) determine the VID/PID of the flash drive or card reader into which it is inserted (control Panel-Device Manager-USB Controllers-Your flash drive/reader-Properties-Information-hardware ID, you need to ensure that the DSM system recognizes this disk and does not try to install itself on it, if you incorrectly define and register these parameters, the istall process will crash by mistake 13) c) download, install and run the OSFmount program, mount Partition 0 (15 Mb) from the bootloader file, remove the "Read-only drive" checkbox before mounting d) download, install and run Akelpad, open grub/grub file.cfg on previously mounted disk, edit and save: set vid=0xA234 #VID flash drive/reader set pid=0xB678 #PID of flash drive/reader set sn=1780PDN123456 #sn set mac1=001132123456 #mac of the first network card set mac2=001132123457 #mac of the second network card, the second and subsequent differ from the first by +1 in the last bit in the hex system ... set netif_num=2 #number of network cards ... set sata_args= 'SataPortMap=6' # sata controller, values: 6 - 1 controller on 6 ports; 22-2 controllers on 2 ports; 42-2 controllers, the first on 4 ports, the second on 2, etc. Where to get sn and mac - is your headache, Google will help you, the system will be installed and will work with those that are initially registered in the bootloader, but with the restriction of the functioning of some services and modules, such as: QC, push notifications, activation of codecs for transcoding, installation of syno licenses... e) unmount the disk in OSFmount f) download, install and run the Rufus program and record the previously prepared image on a flash drive g) insert the flash drive into the computer on which you plan to run xpen, connect the drives, turn on the power h) disable the firewall in the anti-virus, in the browser type http://find.synology.com or install Synology Assistant from the syno website and find the newly installed xpen on your network j) install DSM following the instructions of the installation program and start setting up (how to do it here is not described, because all the answers are in the syno knowledge base) There is a utility where the main programs for Windows x64 are collected 2. Transcoding (needs sn and mac from real syno hardware) Most likely to run on Intel processors starting from the 4th generation (Haswell), but there are nuances with motherboard models and BIOS. Check as follows: hardware (hw) transcoding - at the root of the system should be a directory /dev/dri with subdirectories in it, if not, but there is no HW transcoding to check - look for the directory with the terminal/ssh command cd /dev/dri . software (sw) transcoding - some codecs must run in DSM, you can check it with the command in the terminal / ssh cat /usr/syno/etc/codec/activation.conf If the result is the same, sw transcoding will ran {"success":true,"activated_codec":["h264_dec","h264_enc","mpeg4part2_dec","hevc_dec","aac_dec","aac_enc","ac3_dec","vc1_dec","vc1_enc"],"token":"123456789987654abc"} If there is nothing similar, there is no sw transcoding. 3. Perhaps the most optimal budget solutions with transcoding will be the following: ASRock J4105-ITX Asrock J5005-ITX Who wants more - use mb with the latest generation of Intel processors with Intel i210 or realtek 8111 . But this is already determined by the size of the your wallet and the functionality that you additionally want to get from xpen. P.S. Sorry for my english
  43. 6 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.
  44. 6 points
    For those who need a MBR Bootloader for DSM 6.2 i've uploaded it here, if someone will give them a Chance... i've successfully installed this on an Supermicro X7DBP-i with Intel Blackford 5000P Chipset. It is a loader for the DSM6.2-23739.pat and can be directly upgraded to 6.2.2-24922 Update 2.. http://ul.to/zg58eusm this loader is based on Jun's Mod of Genesys Loader and done with their help!... Thanks a lot..
  45. 6 points
    версия: 3.1.16, linux, Release Notes: - Поддержка мультибитрейтных потоков при адаптивном вещании в HLS - Включена обработка запроса на пинкод/пароль от внешнего устройства при использование AirCast - Настройки приложения теперь можно менять с пульта - Расширен функционал "Engine API", для максимальной совместимости с приложениями, использующими устаревший API - Автоматическое восстановление соединения для AirPlay и Google Cast. - В пульте добавлена кнопка "Рестарт", для возможности повторного запуска контента с места остановки. - Оптимизация HLS - Устранение артефактов при трансляции по HTTP - Совместимость со сторонними приложениями, использующими устаревший API - Добавлены настройки транскодирования аудиодорожек при выдаче потока в HLS Hide Краткое описание: Ace Stream – это медиа-платформа с децентрализованной/распределенной системой поставки и хранения мультимедийных данных, предназначенная для создания интернет-сервисов с функциями AVoD (Аудио и Видео по Запросу) и Live Streaming («живого»/потокового вещания). Используя функции Ace Stream, вы сможете проигрывать в онлайне видео/аудио контент из P2P –сетей (по протоколу BitTorrent и/или AceStream), в любых удобных вам плеерах и на любых устройствах (SmartTV, ТВ-приставки, iPad, iPhone, и др.), поддерживающих соответствующие кодеки и стандартные форматы вещания (HTTP и/или HLS). Эта Тема переросла из этого топика по причине того что там было решение для просмотра в остовном live-tv b и с помощью ресурса ттв, здесь же пойдёт речь в остовном о самом движке Ace Stream, который претерпел с момента написания той статьи значительные изменения(см. Release Notes) Сама установка на убунту вкратце есть в вике разработчика здесь. Для пользователей xpenology у которых уже установлена как минимум DSM-5.2, а в идеале и настоятельно рекомендуется DSM-6.1, и у которых архитектура железа x64, я собрал уже готовое решение которое упаковано в контейнер докера и которое находится здесь. После запуска контейнера на вашем nas-server DSM, потребуется только один раз зайти в контейнер для правки ip вашей сети и записи в кроне для чистки кеша и регулярного обновления плейлистов, дополнительно но не обязательно, можно также занести данные учётки ттв в HTTPAceProxy для воможности просмотра архивов и использования функционала офф. виджета ттв(скрины в спойлере ниже). виджета ттв только андроид Hide
  46. 6 points
    Как оказалось, у новичков возникают сложности с инсталляцией Хренологии на ESXI. поэтому решил написать краткий мануал, призванный облегчить жизнь. дополнения и уточнения приветствуются. 1. подключаемся к ESXI и создаем на датасторе директорию 2. далее в созданную директорию копируем 3 файла вот от сюда 3. после окончания копирования регистрируем нашу машину в ESXI указав на наш .vmx файл собственно доходим до финиша и жмем его все! машина установлена. но ее необходимо настроить перед запуском. 4. в настройках рекомендую задать необходимые параметры процессора и памяти, и обязательно указать размер резервируемой памяти. при недостаточном объеме зарезервированной памяти машина может не запуститься. далее необходимо создать виртуальный жесткий диск и указать его объем. после чего можно перейти на вкладку VM Options и поменять название машины на то которое нравится вам в принципе наша машина уже работоспособна. это простейший способ создания виртуальной машины. Лично я поступил немного иначе: можно или пробросить целиком дисковый контроллер в вашу виртуальную машину и подключить диски к контроллеру поставив крыжик и нажав на Toggle Passthrough после перезагрузки добавив в настройках новый PCI девайс. если у вас нет возможности пробросить целиком контроллер, можно подключить целиком физические диски, не пробрасывая весь контроллер называется это pRDM, как это делается подробно расписано здесь. данный способ хорош еще и тем, что диски целиком можно выдернуть и вставить в физическую машину, без лишних плясок с бубном, если вдруг ваши планы изменятся, а данные скопировать не куда. 5. запускаем машину. при первом запуске говорим: "я скопировал это" после чего стараемся успеть выбрать правильную загрузку далее выжидаем пару минут и начинаем искать свою машину в сети или через сервис http://find.synology.com, если вдруг сервис машину не найдет, то не паникуем и ищем через Синолоджи Ассистента. далее подключаемся к найденной машине и устанавливаем ОС просто нажав на Install Now и спокойно наблюдаем за процессом вводим свои данные, и желательно отключаем крыжик на следующем окне в самом низу говорим "пропустить данный шаг" вот и все, заходим в панель управления и в диспечере хранения радостно видим свои диски. ну и думаем как рачительно распорядиться этим богатством ну и в конце рекомендую установить vm-tools вопросов ввода серийного номера и МАК адреса касаться не стал, все это многократно расписано на форуме можете кидаться тапками, спасибами, кому что нравится.
  47. 6 points
    11 - Why all the issues with recent versions of DSM (6.2.x), and what options are available to mitigate them? Jun's loader attempts to fool the Synology code into thinking that the user hardware is actually Synology's platform hardware. How this is technically accomplished is a mystery to most everyone except Jun, but regardless of how it works, it has an impact on the DSM runtime environment. Some issues are fairly innocuous (spurious errors in the system logs, inability to leverage hardware features like CPU turbo and hibernation, etc.) but others may cause instability, driver and kernel crashes. By far, the most stable combination (meaning, compatibility with the largest inventory of hardware) is Jun's loader 1.02b and DSM 6.1.x. Jun has stated that the target platform for 1.02b was DS3615, and DS3617 was incidentally compatible enough to use the same loader. However, there are kernel crashes with DS3617 on certain combinations of hardware. There is very little functional difference between DS3615 and DS3617, which is why DS3615 is recommended. DSM 6.2 introduced new, more stringent Synology hardware checks and Jun came up with another approach to bypass them. While the loaders do work with optimal hardware, on many systems the 6.2 loaders often result in kernel loadable module crashes and kernel panics. Many have also noted substantially poorer disk I/O performance compared with prior versions. DSM's embedded NIC drivers have been inventoried and documented, but much of that catalogue is useless as the 1.03b loader crashes all but a select few drivers on DSM 6.2.1 and later. And, users with new hardware often find that those few functional network drivers don't support the newest revisions of their on-board silicon. Similarly, the 1.04b loader explicitly adds support for the Intel Graphics (i915) driver, but upgrading to 6.2.2 causes it to crash on some revisions of the Intel Graphics hardware (such as Apollo Lake J-series systems). A very large number of forum posts can be attributed to users seeking to install DSM 6.2.1 or 6.2.2 and encountering one of these two significant problems. ESXi or another virtualization platform is probably the most reliable way to mitigate hardware support limitations on XPEnology and DSM 6.2.x. However, this is an obstacle to those who want a baremetal solution for hardware accelerated video encoding support within DSM. That said, recent progress has been made with compiled modules for DSM 6.2.2 that improve the hardware compatibility of the 1.03b and 1.04b loaders on baremetal systems. This takes some trial and error experimentation, so testing with a non-production system is strongly recommended. It should be noted that many XPEnology super-users, forum admins and devs continue to use the stalwart combination of ESXi, Jun 1.02b and DS3615 DSM 6.1.7 for mission critical work, and have no intention of upgrading. That said, there really isn't much of a reason to stay current once you have a functioning system. DSM 7.0 is imminent and the current loaders are virtually guaranteed not to work with it. 6.2.x releases are simply security/bugfixes at this point, and offer no functional/incremental benefits.
  48. 6 points
    NOTE OF CAUTION It is strongly advised to never apply an update on a 'production' box as soon as the update is made available. ALWAYS test the update on a test machine first and make sure all features are working as expected. Also, I personally recommend you to wait several days (maybe 4/5 days) after the update is available to apply the update on a 'production' box. Reason is that Synology seems to have been making updates available and then suddenly withdrawing them for no apparent reason. This could mean that the update has some issues and needs to be withdrawn from the public.
  49. 6 points
    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.
  50. 6 points
    Есть у меня старенький UPS Powercom IMP-425AP. Давно хотел его подключить к Synology, но дело осложнялось тем, что он является устройством типа USB to Serial, и официально не поддерживается. В интернете гуглится статья на эту тему, по адресу: https://forum.synology.com/enu/viewtopic.php?f=39&t=17658 Но статья давно устарела, т.к. там идёт речь о DSM 3.0-1337 Сразу предупреждаю, я не очень "грамотный" пользователь *nux систем, но, собрав по крупицам некоторую информацию, я всё же смог подключить свой UPS Powercom IMP-425AP к DSM 6.1-15047 Может, я где-то допустил ошибки, но и итоге всё работает. Надеюсь мой опыт будет кому-то полезен. И так, наш UPS в системе определяется как: Bus 002 Device 004: ID 0d9f:0002 Powercom Co., Ltd Black Knight PRO / WOW Uninterruptible Power Supply (Cypress HID->COM RS232) (С таким ID 0d9f:0002 есть целая серия старых IMP-*25AP) Для DSM 6.1-15047 я использую загрузчик Jun's Loader v1.02b Вначале мы воспользуемся советами, описанными в этой статье: https://xpenology.com/forum/topic/7187-how-to-build-and-inject-missing-drivers-in-jun-loader-102a/ Качаем исходный код ядра: https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/15047branch/bromolow-source/linux-3.10.x.txz/download Synology 3615xs построен на архитектуре bromolow, нам нужна версия 15047 (я использую эту версию, т.к. в ней работает нужный мне VirtualBox) Устанавливаем плагин debian-chroot ( https://synocommunity.com/package/debian-chroot ) из раздела сообщества. Запускаем chroot: /var/packages/debian-chroot/scripts/start-stop-status chroot Ставим пакеты apt-get update apt-get upgrade apt-get install locales dpkg-reconfigure locales dpkg-reconfigure tzdata apt-get install mc make gcc build-essential kernel-wedge libncurses5 libncurses5-dev libelf-dev binutils-dev kexec-tools makedumpfile fakeroot linux-kernel* lzma Создаём рабочий каталог «/volume1/@appstore/debian-chroot/var/chroottarget/test/» Распаковываем в каталог /volume1/@appstore/debian-chroot/var/chroottarget/test/ исходники ядра linux-3.10.x.txz Заходим в каталог linux-3.10.x и запускаем cp synoconfigs/bromolow .config Делаем резервную копию конфигурации make ARCH="x86_64" oldconfig Настраиваем конфигурацию make ARCH="x86_64" menuconfig Выбираем «М» напротив драйвера Device Drivers/USB support/USB Serial Converter support/USB Cypress M8 USB Serial Driver Сохраняем конфигурацию и компилируем модули make ARCH="x86_64" modules Копируем скомпилированные модули cypress_m8.ko, usbcore.ko, usbserial.ko в рабочий каталог synology /lib/modules/ Не забываем проверять/выставлять права файлам: chmod 644 Дальше переходим к работе с пакетом NUT. Это нужно, чтобы скомпилировать модуль powercom Информацию по исправлению драйвера я нашёл тут: http://forum.pcm.ru/viewtopic.php?f=3&t=2627 Качаем исходники NUT 2.4.1 http://pkgs.fedoraproject.org/repo/extras/nut/nut-2.4.1.tar.gz/609ebaf2123fc7171d25a6c742dd7d66/nut-2.4.1.tar.gz Распаковываем их в каталог /volume1/@appstore/debian-chroot/var/chroottarget/test/ В каталоге /volume1/@appstore/debian-chroot/var/chroottarget/test/nut-2.4.1 создаём файл патча «patch-nut» с содержимым: --- drivers/powercom.c 2009-02-17 12:20:48.000000000 +0300 +++ drivers/powercom.c 2010-03-02 15:48:25.354735038 +0300 @@ -852,21 +852,30 @@ /* setup flow control */ types[type].flowControl.setup_flow_control(); - if (!strncmp(types[type].name, "BNT",3) || !strcmp(types[type].name, "KIN") || !strcmp(types[type].name, "IMP")){ + if (getval("type") == NULL){ if (!ups_getinfo()) return; if (raw_data[UPSVERSION]==0xFF){ types[type].name="IMP"; - model=IMPmodels[raw_data[MODELNUMBER]/16]; } if (raw_data[MODELNAME]==0x42){ if (!strcmp(types[type].name, "BNT-other")) types[type].name="BNT-other"; else types[type].name="BNT"; - model=BNTmodels[raw_data[MODELNUMBER]/16]; } if (raw_data[MODELNAME]==0x4B){ types[type].name="KIN"; + } + } + if (!strncmp(types[type].name, "BNT",3) || !strcmp(types[type].name, "KIN") || !strcmp(types[type].name, "IMP")){ + if (!ups_getinfo()) return; + if (!strcmp(types[type].name, "IMP")){ + model=IMPmodels[raw_data[MODELNUMBER]/16]; + } + if (!strncmp(types[type].name, "BNT",3)){ + model=BNTmodels[raw_data[MODELNUMBER]/16]; + } + if (!strcmp(types[type].name, "KIN")){ model=KINmodels[raw_data[MODELNUMBER]/16]; } linevoltage=voltages[raw_data[MODELNUMBER]%16]; Применяем патч: patch -p0 -l <patch-nut В драйвере powercom по умолчанию включена самопроверка батарей при каждом старте драйвера. Настройки или возможности отключения этой проверки – нет. Метод устранения этой особенности я подсмотрел здесь: http://forum.lissyara.su/viewtopic.php?t=17735&start=25 Если Вам это не актуально, можете данный шаг пропустить. В файле: /volume1/@appstore/debian-chroot/var/chroottarget/test/nut-2.4.1/drivers/powercom.c находим строчки: ... upsdebugx(1,"Detected: %s , %dV",modelname,linevoltage); if (ser_send_char (upsfd, BATTERY_TEST) != 1) { upslogx(LOG_NOTICE, "writing error"); dstate_datastale(); return; } ... и комментируем лишнее: ... upsdebugx(1,"Detected: %s , %dV",modelname,linevoltage); /*if (ser_send_char (upsfd, BATTERY_TEST) != 1) { upslogx(LOG_NOTICE, "writing error"); dstate_datastale(); return; }*/ ... Компилируем NUT (пути для конфигов и т.д. выставляем такие же, как у synology): ./configure --with-user=root --with-group=root --prefix=/usr/syno/etc/ups --sysconfdir=/usr/syno/etc/ups --datadir=/usr/syno/share make Копируем скомпилированный файл powercom из каталога /volume1/@appstore/debian-chroot/var/chroottarget/test/nut-2.4.1/drivers/ в рабочий каталог synology /bin Не забываем проверять/выставлять права файлам: chmod 644 Теперь нужно добавить скомпилированные драйвера, в загрузчик Jun's Loader v1.02b. Используем osfmount (под windows), чтобы извлечь «extra.lzma» (сжатый файл cpio) из synoboot.img (находится «extra.lzma» на втором разделе FAT). Osfmount часто используют для редактирования файла grub.cfg в synoboot.img. («extra.lzma» - содержит дополнительные драйвера *.ko, которые стартуют при загрузке) Скопируем «extra.lzma» в /volume1/@appstore/debian-chroot/var/chroottarget/test/extra-drv Для распаковки «extra.lzma» выполним команду: lzma -d extra.lzma Далее, извлекаем файлы из «extra»: cpio -idv <extra После чего файл «extra.lzma» можно удалить. В распакованный каталог …/usr/lib/modules/ копируем скомпилированные модули cypress_m8.ko, usbcore.ko, usbserial.ko, а в /etc редактируем файл rc.modules В конце списка EXTRA_MODULES добавляем свои три драйвера, без *.ko rc.modules выглядит примерно так: EXTRA_MODULES="mii mdio libphy atl1 atl1e atl1c alx uio ipg jme skge sky2 ptp_pch pch_gbe qla3xxx qlcnic qlge netxen_nic sfc e1000 pcnet32 vmxnet3 bnx2 libcrc32c bnx2x cnic e1000e igb ixgbe r8101 r8168 r8169 tg3 usbnet ax88179_178a button evdev ohci-hcd cypress_m8 usbcore usbserial" DISK_MODULES="BusLogic vmw_pvscsi megaraid_mm megaraid_mbox megaraid scsi_transport_spi mptbase mptscsih mptspi mptsas mptctl ata_piix megaraid_sas mpt2sas mpt3sas" EXTRA_FIRMWARES="bnx2/bnx2-rv2p-09ax-6.0.17.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-06-6.0.15.fw tigon/tg3_tso5.bin tigon/tg3_tso.bin tigon/tg3.bin" Дальше, внутри каталога, /volume1/@appstore/debian-chroot/var/chroottarget/test/extra-drv, создаём новый файл cpio, и сжимаем его lzma. Полученный, новый «extra.lzma» записывается в каталог уровнем выше. Выполняем команду: (find . -name modprobe && find . \! -name modprobe) | cpio --owner root:root -oH newc | lzma -8 > ../extra.lzma Полученный файл «extra.lzma», при помощи osfmount, записываем обратно в образ synoboot.img. Теперь произведём настройку DSM 6.1 Выполняем: insmod /lib/modules/cypress_m8.ko mknod /dev/ttyUSB0 c 188 0 chmod 644 /dev/ttyUSB0 Настраиваем скорость порта: stty -F /dev/ttyUSB0 speed 1200 cs8 raw (Дальнейшая настройка подсмотрена тут: https://xpenology.com/forum/topic/4413-dsm-52-5592-update-4-amp-serial-apc-ups/#comment-38621) Редактируем файл: /etc/rc Добавляем в KERNEL_MODULES драйвера «usblp cypress_m8 usbserial»: if [ $KERNEL_VCODE -ge $(KernelVersionCode "4.4") ]; then KERNEL_MODULES="usblp cypress_m8 usbserial llc p8022 psnap usbcore quota_tree quota_v2 crc-ccitt crc-itu-t zlib_inflate dm-bufio dm-snapshot" else KERNEL_MODULES="usblp cypress_m8 usbserial llc p8022 psnap usbcore quota_tree quota_v2 crc-ccitt crc-itu-t zlib_inflate dm-snapshot" fi В конце файла, перед exit 0 добавляем строку запуска службы UPS: /usr/syno/etc/rc.sysv/ups-usb.sh start В файле /usr/syno/etc/rc.sysv/ups-usb.sh правим строку StartAllDrv() { local DRV_LIST="usbhid-ups blazer_usb bcmxcp_usb richcomm_usb tripplite_usb" на StartAllDrv() { local DRV_LIST="powercom usbhid-ups blazer_usb bcmxcp_usb richcomm_usb tripplite_usb" Редактируем файл /usr/syno/etc/ups/ups.conf [ups] driver = powercom port = /dev/ttyUSB0 type = IMP Загружаем файл https://github.com/networkupstools/nut/raw/master/data/cmdvartab и копируем его в каталог /usr/syno/share/ На этом всё. После перезагрузки, UPS должен автоматически появиться в GUI: P.S. Посмотреть более подробный статус UPS можно командой: upsc ups admin@serv01:~$ upsc ups battery.charge: 100.0 driver.name: powercom driver.parameter.pollinterval: 5 driver.parameter.port: /dev/ttyUSB0 driver.parameter.type: IMP driver.version: 2.4.1 driver.version.internal: 0.12 input.frequency: 50.00 input.voltage: 226.0 input.voltage.nominal: 220 output.frequency: 50.00 output.voltage: 226.0 ups.load: 12.0 ups.mfr: PowerCom ups.model: IMP-425AP ups.model.type: IMP ups.serial: Unknown ups.status: OL